Two NICs in one computer
Adam Frank Nevraumont
Neil DeBoni <ncde...@undergrad.math.uwaterloo.ca> wrote:
>In article <7va5im$sm8$1...@watserv3.uwaterloo.ca>, at 3 or so,
>Matthew Nichols <mjni...@undergrad.math.uwaterloo.ca> wrote:
>>I'm planning on putting two NICs in my computer. One will connect to DSL,
>>the other to Resnet.
>>
>>The problem is: how do I set up the Resnet connection to connect only to
>>the uwaterloo.ca domain (i.e. nothing external), and also set up the DSL
>>to connect to everything EXCEPT uwaterloo.ca stuff?
>>
>>The reasons I would do this are: Obviously, local stuff will be faster
>>through a local connection (rather than DSL). But, there is a 25Mb/day
>>average limit for external use for Resnet, so that's why I want to use
>>DSL for sites external to uwaterloo.ca
>>
>>How would I set this up in both Win98 and Linux environments?
>You should be able to (in Linux) set up the routing table such that:
>
>1. all traffic going out to the 129.97 network (i.e., uwaterloo.ca) goes
>out on the IP address corresponding to your Resnet nic
>2. all other traffic (i.e., default route) goes out on the IP address
>corresponding to your DSL nic.
>
>The commands would be _something like_ the following:
>
>route add net 129.97.0.0 gw <resnet nic IP>
>route add default gw <dsl nic IP>
Do you know what Linux's main problem is?
Lack of support.
:-)
--
Adam_Nevraumont at uwaterloo.ca
"My God's dad makes more money than your god's dad..." - Ethan
Hi. Im the signature immune system. Why dont you copy me into your .sig?
Jason Testart [MFCF]
I don't totally agree with that statement. There is LOTS of documentation
on Linux out there on the internet, and such documentation has helped me
out on several occations.
For instance, when I first tried Linux many years ago on a 486, I had a
Mach64 (VLB) video card which was quite new at the time. The newest ATI driver
written was for Mach32. Now, you would think the Mach32 driver would work,
but that was not the case. So, I went into the labs on campus one Friday at
lunch time and spent about 25 minutes searching newsgroups and using
search engines using meaningful keywords. Eventually, I found a web page
titled "How to get your ATI Mach64 card to work with XFree86". It was sweet.
More recently, I had trouble getting my Linux box to connect with HSE. So,
again, I searched the newsgroups. I didn't have to go far this time, since
there was a posting on uw.general that eventually led me to the PPPoE HowTo
which helped me out big time.
Jason
MFCF
Dave Vandervies
I think that the point was that Linux is *perceived* to lack support because there's no `official' support structure for it.
Just my $0.02 worth.
dave
Adam Frank Nevraumont
Jason Testart [MFCF] <jate...@math.uwaterloo.ca> wrote:
>In article <7vabrv$3sn$1...@watserv3.uwaterloo.ca>,
>Adam Frank Nevraumont <afne...@undergrad.math.uwaterloo.ca> wrote:
>>In article <7va6h4$5e$1...@watserv3.uwaterloo.ca>, at 3:15 or so,
>>Neil DeBoni <ncde...@undergrad.math.uwaterloo.ca> wrote:
>>>Matthew Nichols <mjni...@undergrad.math.uwaterloo.ca> wrote:
>>>>I'm planning on putting two NICs in my computer. One will connect to DSL,
>>>>the other to Resnet.
>>>>
>>>>The problem is: how do I set up the Resnet connection to connect only to
>>>>the uwaterloo.ca domain (i.e. nothing external), and also set up the DSL
>>>>to connect to everything EXCEPT uwaterloo.ca stuff?
>>>>
>>>>The reasons I would do this are: Obviously, local stuff will be faster
>>>>through a local connection (rather than DSL). But, there is a 25Mb/day
>>>>average limit for external use for Resnet, so that's why I want to use
>>>>DSL for sites external to uwaterloo.ca
>>>>
>>>>How would I set this up in both Win98 and Linux environments?
>>
>>>
>>>1. all traffic going out to the 129.97 network (i.e., uwaterloo.ca) goes
>>>out on the IP address corresponding to your Resnet nic
>>>2. all other traffic (i.e., default route) goes out on the IP address
>>>corresponding to your DSL nic.
>>>
>>>The commands would be _something like_ the following:
>>>
>>>route add net 129.97.0.0 gw <resnet nic IP>
>>>route add default gw <dsl nic IP>
>>
>>Do you know what Linux's main problem is?
>>
>>Lack of support.
>>
>>:-)
>
>on Linux out there on the internet, and such documentation has helped me
>out on several occations.
Check the timestamps on the first two posts in this thread.
(PS: I was off by 15 minutes in my manual timestamps)
HTH,