All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: ppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Ethernet on 8260
Date: Tue, 17 Jul 2001 19:09:34 +1000	[thread overview]
Message-ID: <5065.995360974@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Brad Bonkoski <bradb59@home.com> of "16 Jul 2001 22:30:24 MST." <20010717053606.PQKG23117.femail17.sdc1.sfba.home.com@cx263713-b.mesa1.az.home.com>


On 16 Jul 2001 22:30:24 -0700, Brad Bonkoski <bradb59@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...
--
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@cmst.csiro.au  (old address was mjj@mlb.dmt.csiro.au)


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-17  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bradb59@home.com>
2001-07-17  0:19 ` Ethernet on 8260 Brad Bonkoski
2001-07-17  4:22   ` Murray Jensen
2001-07-17  5:30     ` Brad Bonkoski
2001-07-17  9:09       ` Murray Jensen [this message]
2001-07-17 19:07         ` Brad Bonkoski
2001-07-18  6:26           ` Murray Jensen
2001-07-17  8:28   ` August Hoerandl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5065.995360974@msa.cmst.csiro.au \
    --to=murray.jensen@cmst.csiro.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.