[Bridge] Bridge Woes...

Chris U chris.uyehara at hawaii.edu
Thu Oct 5 12:07:14 PDT 2006


Hi Stephen,

Setting IP address via: ifconfig br0 128.171.103.11 netmask 255.255.255.0 up

eth0 and eth1 do not have an IP assigned.

---
eth0      Link encap:Ethernet  HWaddr 00:13:72:FC:84:36
          inet6 addr: fe80::213:72ff:fefc:8436/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:237 errors:0 dropped:0 overruns:0 frame:0
          TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:23977 (23.4 KiB)  TX bytes:28139 (27.4 KiB)
          Interrupt:169

eth1      Link encap:Ethernet  HWaddr 00:13:72:FC:84:37
          inet6 addr: fe80::213:72ff:fefc:8437/64 Scope:Link
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2481 (2.4 KiB)  TX bytes:0 (0.0 b)
          Interrupt:225
---

Kernel Version: 2.6.9-42.0.2.ELsmp x86_64

Hardware... neither are wireless devices.
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
Ethernet PCI Express (rev 11)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
Ethernet PCI Express (rev 11)

On 10/5/06, Stephen Hemminger <shemminger at osdl.org> wrote:
>
> On Wed, 4 Oct 2006 18:20:43 -1000
> "Chris U" <chris.uyehara at gmail.com> wrote:
>
> > Hi List,
> >
> > I have setup a bridge labeled br0. br0 has an ip address assigned to it.
> My
> > network looks something similar to this...
> >
> > |--------------------|                |--------------------|
> > |------------------|
> > |      laptop        |                |      bridge        |
> > |     router       |
> > | 128.171.103.10/24  |  ----->  (eth1)| 128.171.103.11/24
>   |(eth0)  ----->
> > | 128.171.103.1/24 |
> > | statically assignd |                | statically assignd |
> > | tested / working |
> > |--------------------|                |--------------------|
> > |------------------|
> >
> > Now for the PROBLEM! The bridge can access IP's outside of the subnet
> via
> > eth0 of the bridge, ie - pinging 128.171.1.1, 128.171.3.13,
> 64.233.167.99.
> > The laptop cannot ping the previously listed IPs. The only thing the
> laptop
> > can ping is 128.171.103.11. It's very odd... I tried running tcpdump on
> the
> > bridge. From the bridge I could see the laptop pinging the bridge but I
> > couldn't see the laptop pinging any other IPs. So basically I have a
> bridge
> > that's not really working but the bridge utils show that its working...
> any
> > help would be greatly appreciated!
> >
> > (The laptop works when taken off the bridge and connected to the router,
> the
> > iptables default policy is ACCEPT and the rules are FLUSHED.)
> >
> > Thanks for taking time to read this!
> >
> > ###brctl show br0
> > bridge name     bridge id               STP enabled     interfaces
> > br0             8000.001372fc8436       no              eth0
> >                                                         eth1
> >
> > ###brctl showstp br0
> > br0
> >  bridge id              8000.001372fc8436
> >  designated root        8000.001372fc8436
> >  root port                 0                    path
> cost                  0
> >  max age                  19.99                 bridge max age
> > 19.99
> >  hello time                1.99                 bridge hello time
> > 1.99
> >  forward delay            14.99                 bridge forward delay
> > 14.99
> >  ageing time             299.95
> >  hello timer               0.03                 tcn timer
> > 0.00
> >  topology change timer     0.00                 gc timer
> > 7.97
> >  flags
> >
> >
> > eth0 (1)
> >  port id                8001                    state
> > forwarding
> >  designated root        8000.001372fc8436       path
> cost                100
> >  designated bridge      8000.001372fc8436       message age timer
> > 0.00
> >  designated port        8001                    forward delay timer
> > 0.00
> >  designated cost           0                    hold timer
> > 0.00
> >  flags
> >
> > eth1 (2)
> >  port id                8002                    state
> > forwarding
> >  designated root        8000.001372fc8436       path
> cost                100
> >  designated bridge      8000.001372fc8436       message age timer
> > 0.00
> >  designated port        8002                    forward delay timer
> > 0.00
> >  designated cost           0                    hold timer
> > 0.00
> >  flags
>
>
> How are you setting IP addresses on the bridge.
> You need to NOT assign IP addresses to eth0, eth1 and assign
> an IP address to bridge pseudo device.
>
> What kernel version?
> What hardware is being used for eth0 and eth1? Are either one
> of these wireless (802.11) devices?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/bridge/attachments/2006100=
5/ac66e837/attachment-0002.htm


More information about the Bridge mailing list