From: Stephen Hemminger <shemminger@vyatta.com>
To: czj <linuxdemo@126.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] 4 ports bridge problem
Date: Sun, 21 Sep 2008 22:51:32 -0700 [thread overview]
Message-ID: <20080921225132.4fa4639f@extreme> (raw)
In-Reply-To: <48D6DF9D.10708@126.com>
On Mon, 22 Sep 2008 07:58:21 +0800
czj <linuxdemo@126.com> wrote:
> Hi all,
> I work on a SOC based on AMCC/glacier based on PPC460GT. (
> http://WWW.AMCC.com <http://micrel.com/page.do?page=product-info/sys_on_chip.jsp>)
> This component has 4 network interfaces.
>
> Every one is connected to a PC.
>
> eth0 =>192.168.1.11
> eth1 => 192.168.1.22
> eth2 => 192.168.1.33
> eth3 => 192.168.1.44
You have layer 2 and 3 confused. Are you sure you don't intend
to route (layer 3) rather than bridging.
> I want to make a bridge with these 4 ports
>
> #brctl addbr br0
>
> #ifconfig br0 192.168.1.20 netmask 255.255.255.0
>
> #ifconfig eth0 0.0.0.0 up
>
> #ifconfig eth1 0.0.0.0 up
>
> #ifconfig eth2 0.0.0.0 up
>
> #ifconfig eth3 0.0.0.0 up
>
> # brctl addif br0 eth0
>
> # brctl addif br0 eth1
>
> # brctl addif br0 eth2
>
> # brctl addif br0 eth3
>
> #brctl stp on
>
> but my problem is that when I used the PC(which IP is 192.168.1.11/24) to ping other PCs,
>
> the ping reply time from 192.168.1.22 was about 1000ms;
> the ping reply time from 192.168.1.33 was about 0.2ms;
> the ping reply time form 192.168.1.44 was about 300ms;
>
> Why? and how to configure the 4 ethernet-ports glacier board to be a bridge or switch correctly? thanks a lot.
Don't assign IP addresses to the ethernet devices, only one common address
to the bridge.
next prev parent reply other threads:[~2008-09-22 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 23:58 [Bridge] 4 ports bridge problem czj
2008-09-22 5:51 ` Stephen Hemminger [this message]
2008-09-22 17:52 ` Srinivas M.A.
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=20080921225132.4fa4639f@extreme \
--to=shemminger@vyatta.com \
--cc=bridge@lists.linux-foundation.org \
--cc=linuxdemo@126.com \
/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