From: jbi130@yahoo.com
To: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet bridging on MPC8248
Date: 03 May 2005 00:15:14 -0600 [thread overview]
Message-ID: <87sm14n8ct.fsf@nimrod.unx.ca> (raw)
In-Reply-To: 4275F2BB.9050100@radionor.no
Ole Andreas Torvmark <ole.torvmark@radionor.no> writes:
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 eth1
> ifconfig br0 192.168.0.222 netmask 255.255.255.0
>
> If I connect a machine to port 0 (eth0) then I can ping the bridge
> from that machine,
>
> If I connect a machine to port 1 (eth1) I cannot ping the bridge.
> If I connect machines to both ports, I cannot ping one machine from
> the other, the only thing i can successfully ping is from port 0 to
> bridge and from bridge to port 0
>
> Is this a known problem with the FCC ENET driver or does it support
> bridging fully ?
Have you made sure that eth0 and eth1 are 'up'? eg) ifconfig eth0 up.
I'm not sure, but br0 may need to be up as well.
next prev parent reply other threads:[~2005-05-03 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 9:28 Ethernet bridging on MPC8248 Ole Andreas Torvmark
2005-05-03 6:15 ` jbi130 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 6:24 Bastos Fernandez Alexandre
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=87sm14n8ct.fsf@nimrod.unx.ca \
--to=jbi130@yahoo.com \
--cc=linuxppc-embedded@ozlabs.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).