* [Bridge] NIC's binding order
@ 2006-07-26 10:22 Jason Chan <MIS>
2006-07-26 15:31 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Jason Chan <MIS> @ 2006-07-26 10:22 UTC (permalink / raw)
To: bridge
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
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?
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)
[-- Attachment #2: Type: text/html, Size: 3119 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bridge] NIC's binding order
2006-07-26 10:22 [Bridge] NIC's binding order Jason Chan <MIS>
@ 2006-07-26 15:31 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2006-07-26 15:31 UTC (permalink / raw)
To: Jason Chan <MIS>; +Cc: bridge
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)
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-07-26 15:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-26 10:22 [Bridge] NIC's binding order Jason Chan <MIS>
2006-07-26 15:31 ` Stephen Hemminger
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.