Re: [TCLUG:8342] Multiple Ethernet

["Brian Ackermann" <brianj@subrad.com>]

Ok, here's the route table....

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
205.218.57.25   0.0.0.0         255.255.255.255 UH    0      0      0   eth0
192.168.6.49    0.0.0.0         255.255.255.255 UH    0      0      0   eth1
192.168.6.0     0.0.0.0         255.255.255.0   U     0      0      0   eth1
205.218.57.0    0.0.0.0         255.255.255.0   U     0      0      0   eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0      0   lo
0.0.0.0         205.218.57.17   0.0.0.0         UG    0      0      0   eth0

----------
>From: "Eric Hillman" <ehillman@cccu.com>
>To: <tclug-list@mn-linux.org>
>Subject: RE: [TCLUG:8342] Multiple Ethernet
>Date: Mon, Sep 20, 1999, 3:33 PM
>

>> Right now, eth0 is set to an addy on 205.218, and eth1 is on 192.168.
>>
>> Both of these are plugged into the switch, which goes to the router, which
>> is forwarding BOTH domains.  Right now, internet stuff works, but
>> no internal
>> networking works on these two cards.  I can't see other computers on our
>> hubs, and they cant see me.
>
>
>   Okay.  What about the routing tables on the linux box?  If you type
> /sbin/route -n at a command prompt, you should see something like this:
>
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 205.218.0.0     0.0.0.0         255.255.0.0     U     0      0      XXX eth0
> 192.168.0.0     0.0.0.0         255.255.0.0     U     0      0      XXX eth1
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0      XXX lo
> 0.0.0.0         205.218.NNN.NNN 0.0.0.0         UG    0      0      XXX eth0
>
> (That last entry with the NNNs should be your router. The XXX's will be
> replaced by numbers indicating the number of packets sent since the last
> time the interface was reset, or something.)
>
> You'll want to read the manpages for route before dealing with this, but
> what you need to do is make sure the machine understands that:
>
> Packets for 205.218.x.x go out eth0;
> Packets for 192.168.x.x go out eth1; and
> Everything else (0.0.0.0) goes out eth0, via the router.
>
> The syntax for adding and deleting "route" entries is a little complex, but
> it's all in the manual.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>
>