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 14:22:21 +1000 [thread overview]
Message-ID: <26051.995343741@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Brad Bonkoski <bradb59@home.com> of "16 Jul 2001 17:19:36 MST." <20010717002518.YUJE5550.femail18.sdc1.sfba.home.com@cx263713-b.mesa1.az.home.com>
On 16 Jul 2001 17:19:36 -0700, Brad Bonkoski <bradb59@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.
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!
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/
next prev parent reply other threads:[~2001-07-17 4:22 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 [this message]
2001-07-17 5:30 ` Brad Bonkoski
2001-07-17 9:09 ` Murray Jensen
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=26051.995343741@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).