From: Stephen Hemminger <shemminger@osdl.org>
To: "Jason Chan <MIS>" <jsonchan@ebhk.com.hk>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] NIC's binding order
Date: Wed, 26 Jul 2006 08:31:49 -0700 [thread overview]
Message-ID: <20060726083149.552d9e57@localhost.localdomain> (raw)
In-Reply-To: <714D3CA502C1D21199DD0004ACD9DEAF0391FC97@starcase_nt.starcase.com.hk>
On Wed, 26 Jul 2006 18:22:37 +0800
"Jason Chan <MIS>" <jsonchan@ebhk.com.hk> wrote:
> Hi Folk,
>
> My BOX is running Debian Sarge. i recently setup a bridge with two NIC's for
> transparent proxy. However something weird i found as listed below when i
> run ifconfig. So just curious to ask why the hardware address of "br0" is
> the same as "eth1", it's supposed to be the same as "eth0"...normally.
> Should this cause a probelm with the bridge?? If so how can i correct the
> binding order?
The MAC address of the bridge pseudo-device is the minimum of the addresses
of the connected interfaces. This is part of the 802.1d spec probably to prevent
possible loops.
You can change address of bridge on recent kernels to be any of the addresses
of the interfaces. As I remember, Debian Sarge kernel is ancient so you may
need to run a newer kernel.
> Best regards
> Jason
>
> root@bridge:~> ifconfig
>
> br0 Link encap:Ethernet HWaddr 00:04:75:81:D2:1D
>
> inet addr:10.0.3.129 Bcast:195.30.198.255 Mask:255.255.255.128
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:826 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:737 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:0
>
> RX bytes:161180 (157.4 Kb) TX bytes:66708 (65.1 Kb)
>
>
>
> eth0 Link encap:Ethernet HWaddr 00:04:75:81:ED:B7
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:5729 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:3115 errors:0 dropped:0 overruns:0 carrier:656
>
> collisions:0 txqueuelen:100
>
> RX bytes:1922290 (1.8 Mb) TX bytes:298837 (291.8 Kb)
>
> Interrupt:11 Base address:0xe400
>
>
>
> eth1 Link encap:Ethernet HWaddr 00:04:75:81:D2:1D
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:0 errors:0 dropped:0 overruns:1 frame:0
>
> TX packets:243 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:100
>
> RX bytes:342 (342.0 b) TX bytes:48379 (47.2 Kb)
>
> Interrupt:7 Base address:0xe800
>
>
>
> lo Link encap:Local Loopback
>
> inet addr:127.0.0.1 Mask:255.0.0.0
>
> UP LOOPBACK RUNNING MTU:16436 Metric:1
>
> RX packets:1034 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:1034 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:0
>
> RX bytes:82068 (80.1 Kb) TX bytes:82068 (80.1 Kb)
>
>
prev parent reply other threads:[~2006-07-26 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 10:22 [Bridge] NIC's binding order Jason Chan <MIS>
2006-07-26 15:31 ` Stephen Hemminger [this message]
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=20060726083149.552d9e57@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=jsonchan@ebhk.com.hk \
/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.