Ethernet on 8260
bradb59 at home.com
Wed Jul 18 05:07:19 EST 2001
Thanks for the recoomendations, look like things are on thier way!
One further question, is it possible for a detection of a loss of the
actual Ethernet cable at the kernel level? Are there any pointers to
docs I could read on this?
On 17 Jul 2001 19:09:34 +1000, Murray Jensen wrote:
> On 16 Jul 2001 22:30:24 -0700, Brad Bonkoski <bradb59 at home.com> writes:
> >Does Linux _really_ do this? Shouldn't it route at the host layer
> >before the network layer?
> I think it does look for host routes before matching network routes, but
> there needs to be one in your routing table. I believe when you configure
> the interface the driver installs the network route only. i.e. by default
> they will clash.
> >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?
> Yes, I believe you need to explicitly add them to the routing tables.
> >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
> >on this?
> You are correct, but you have to set it up manually. Or maybe it depends on
> what net-tools package you use - the one I use doesn't add the host routes.
> >This is a good idea, but I would like to keep it simple, as they say
> >simplicity is the 'key' to High availability.
> What could be more simple than removing all that really complicated IP
> protocol overhead? :-) Cheers!
> 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