Ethernet on 8260
bradb59 at home.com
Tue Jul 17 15:30:24 EST 2001
On 17 Jul 2001 14:22:21 +1000, Murray Jensen wrote:
> On 16 Jul 2001 17:19:36 -0700, Brad Bonkoski <bradb59 at home.com> writes:
> >Essentailly, I have them all set up on the same
> >network: 192.168.0.X.
> Use different IP network numbers for each ethernet interface. e.g.
> FCC1 - eth0 - 192.168.1.x
> FCC2 - eth1 - 192.168.2.x
> FCC3 - eth2 - 192.168.3.x
> (assuming a netmask of 255.255.255.0). If they all have the same IP *network*
> number (i.e. the number is the same after applying the netmask), then Linux
> will only use one of them. In other words, you can only have one route for
> each subnet.
Does Linux _really_ do this? Shouldn't it route at the host layer
before the network layer? Like it I ping 192.168.0.1 it should return
the ping on that interface regardless of if another network device lives
on this network! Or, do I have to explicitly set up host routes in the
routing table? I guess what is the point of having multiple interfaces
on one board live on the same network, but even so, I would still think
it should choose the host route before the network route. Any thoughts
> By the way, if you want Linux to forward packets between the interfaces, then
> ensure you enable forwarding (echo 1 > /proc/sys/net/ipv4/ip_forward).
> Also, you could by-pass all this IP stuff and do things at the ethernet level
> (using a RAW socket?). Cheers!
This is a good idea, but I would like to keep it simple, as they say
simplicity is the 'key' to High availability.
> Murray Jensen, CSIRO Manufacturing Sci & Tech, Phone: +61 3 9662 7763
> Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
> Internet: Murray.Jensen at cmst.csiro.au (old address was mjj at mlb.dmt.csiro.au)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-embedded