All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bridge] Bridge Woes...
@ 2006-10-05  4:20 Chris U
  2006-10-05  4:58 ` Jothis T.V
                   ` (2 more replies)
  0 siblings, 3 replies; 12+ messages in thread
From: Chris U @ 2006-10-05  4:20 UTC (permalink / raw)
  To: bridge

[-- Attachment #1: Type: text/plain, Size: 2802 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 8423 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  4:20 [Bridge] Bridge Woes Chris U
@ 2006-10-05  4:58 ` Jothis T.V
  2006-10-05  7:59   ` Chris U
  2006-10-05  8:18 ` Alex Zeffertt
  2006-10-05 14:39 ` Stephen Hemminger
  2 siblings, 1 reply; 12+ messages in thread
From: Jothis T.V @ 2006-10-05  4:58 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 3341 bytes --]

Hi Chris,

Just wanted to ensure some basic points here.

1. Can the laptop ping the router OR any other machine in the subnet
128.171.103.0/24?
2. Also, hope that you have set the gateway of the laptop as 128.171.103.1.

regards,
Jothis


On 10/5/06, Chris U <chris.uyehara@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
>
>
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
>
>

[-- Attachment #2: Type: text/html, Size: 9979 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  4:58 ` Jothis T.V
@ 2006-10-05  7:59   ` Chris U
  0 siblings, 0 replies; 12+ messages in thread
From: Chris U @ 2006-10-05  7:59 UTC (permalink / raw)
  To: Jothis T.V; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 3987 bytes --]

Hi Jothis,

1. When the laptop is connected to the bridge, the laptop cannot ping the
router or any other machine in the subnet.
2. Yes, I have set the gateway of the laptop to 128.171.103.1

By chance do you know how to debug the the bridge?

Mahalo,
Chris

On 10/4/06, Jothis T.V <jothistv@gmail.com> wrote:
>
> Hi Chris,
>
> Just wanted to ensure some basic points here.
>
> 1. Can the laptop ping the router OR any other machine in the subnet
> 128.171.103.0/24?
> 2. Also, hope that you have set the gateway of the laptop as 128.171.103.1
> .
>
> regards,
> Jothis
>
>
> On 10/5/06, Chris U <chris.uyehara@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
> >
> >
> >
> > _______________________________________________
> > Bridge mailing list
> > Bridge@lists.osdl.org
> > https://lists.osdl.org/mailman/listinfo/bridge
> >
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 11041 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  4:20 [Bridge] Bridge Woes Chris U
  2006-10-05  4:58 ` Jothis T.V
@ 2006-10-05  8:18 ` Alex Zeffertt
  2006-10-05  8:39   ` Chris U
  2006-10-05 14:39 ` Stephen Hemminger
  2 siblings, 1 reply; 12+ messages in thread
From: Alex Zeffertt @ 2006-10-05  8:18 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

> 
> 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 <http://128.171.1.1>, 
> 128.171.3.13 <http://128.171.3.13>, 64.233.167.99 
> <http://64.233.167.99>. The laptop cannot ping the previously listed 
> IPs. The only thing the laptop can ping is 128.171.103.11 

Hi Chris,

I have seen a problem with some ethernet drivers where the interface
does not go into promiscuous mode automatically as the interface is added
to a bridge.

It's worth trying to do this manually with "ifconfig eth0 promisc" and
likewise for eth1, then seeing if things work.

A few ethernet drivers don't support promiscuous mode at all.  But it
definitely looks to me the way you describe the problem that the devices
on the bridge are not in promiscuous mode.

Regards,

Alex

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  8:18 ` Alex Zeffertt
@ 2006-10-05  8:39   ` Chris U
  2006-10-05  9:05     ` Jothis T.V
  2006-10-05  9:05     ` Alex Zeffertt
  0 siblings, 2 replies; 12+ messages in thread
From: Chris U @ 2006-10-05  8:39 UTC (permalink / raw)
  To: Alex Zeffertt; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 3706 bytes --]

Hi Alex,

In the case you mentioned previously, does ifconfig show the interface in
promisc mode? I have tried further investigating whether or not the
interface is in promisc mode by using ethtool, a soft tool, however
unsuccessful. I also attempted to use a hub on eth0 to see if tcpdump would
pick up the packets in promisc mode; the packets are successfully captured
on the hub. [I did not test eth1, but I shall tomorrow morning.] Both
network interfaces are the same model/brand. Listed below is a snapshot of
my ifconfig and a snippet from my lspci.

This list is pretty responsive - I just wanted to say thanks to everyone for
taking time to help me out. ;)

Mahalo,
Chris

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:7792 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9417 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:699418 (683.0 KiB)  TX bytes:1846522 (1.7 MiB)
          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 RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:318 errors:0 dropped:0 overruns:0 frame:0
          TX packets:165 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34204 (33.4 KiB)  TX bytes:10886 (10.6 KiB)
          Interrupt:225

04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
Ethernet PCI Express (rev 11)
        Subsystem: Dell: Unknown device 01b6
        Flags: bus master, fast devsel, latency 0, IRQ 169
        Memory at fe6f0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3
Enable-
        Capabilities: [d0] Express Endpoint IRQ 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel

05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
Ethernet PCI Express (rev 11)
        Subsystem: Dell: Unknown device 01b6
        Flags: bus master, fast devsel, latency 0, IRQ 225
        Memory at fe4f0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3
Enable-
        Capabilities: [d0] Express Endpoint IRQ 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel


On 10/4/06, Alex Zeffertt <ajz@cambridgebroadband.com> wrote:
>
> >
> > 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 <http://128.171.1.1>,
> > 128.171.3.13 <http://128.171.3.13>, 64.233.167.99
> > <http://64.233.167.99>. The laptop cannot ping the previously listed
> > IPs. The only thing the laptop can ping is 128.171.103.11
>
> Hi Chris,
>
> I have seen a problem with some ethernet drivers where the interface
> does not go into promiscuous mode automatically as the interface is added
> to a bridge.
>
> It's worth trying to do this manually with "ifconfig eth0 promisc" and
> likewise for eth1, then seeing if things work.
>
> A few ethernet drivers don't support promiscuous mode at all.  But it
> definitely looks to me the way you describe the problem that the devices
> on the bridge are not in promiscuous mode.
>
> Regards,
>
> Alex
>

[-- Attachment #2: Type: text/html, Size: 5829 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  8:39   ` Chris U
@ 2006-10-05  9:05     ` Jothis T.V
  2006-10-05  9:05     ` Alex Zeffertt
  1 sibling, 0 replies; 12+ messages in thread
From: Jothis T.V @ 2006-10-05  9:05 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 3246 bytes --]

Hi Chris,

"UP BROADCAST RUNNING *PROMISC* MULTICAST  MTU:1500  Metric:1"
Your ifconfig output does show the interfaces to be running in promiscous
mode.

The best method forward from here would be to sniff the packets on the
interfaces using tools like ethereal and analyse them.

regards,
Jothis


On 10/5/06, Chris U <chris.uyehara@gmail.com> wrote:
>
> Hi Alex,
>
> In the case you mentioned previously, does ifconfig show the interface in
> promisc mode? I have tried further investigating whether or not the
> interface is in promisc mode by using ethtool, a soft tool, however
> unsuccessful. I also attempted to use a hub on eth0 to see if tcpdump would
> pick up the packets in promisc mode; the packets are successfully captured
> on the hub. [I did not test eth1, but I shall tomorrow morning.] Both
> network interfaces are the same model/brand. Listed below is a snapshot of
> my ifconfig and a snippet from my lspci.
>
> This list is pretty responsive - I just wanted to say thanks to everyone
> for taking time to help me out. ;)
>
> Mahalo,
> Chris
>
> 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:7792 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9417 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:699418 (683.0 KiB)  TX bytes:1846522 (1.7 MiB)
>           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 RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:318 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:165 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:34204 (33.4 KiB)  TX bytes:10886 (10.6 KiB)
>           Interrupt:225
>
> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
> Gigabit Ethernet PCI Express (rev 11)
>         Subsystem: Dell: Unknown device 01b6
>         Flags: bus master, fast devsel, latency 0, IRQ 169
>         Memory at fe6f0000 (64-bit, non-prefetchable) [size=64K]
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3
> Enable-
>         Capabilities: [d0] Express Endpoint IRQ 0
>         Capabilities: [100] Advanced Error Reporting
>         Capabilities: [13c] Virtual Channel
>
> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721
> Gigabit Ethernet PCI Express (rev 11)
>         Subsystem: Dell: Unknown device 01b6
>         Flags: bus master, fast devsel, latency 0, IRQ 225
>         Memory at fe4f0000 (64-bit, non-prefetchable) [size=64K]
>         Capabilities: [48] Power Management version 2
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3
> Enable-
>         Capabilities: [d0] Express Endpoint IRQ 0
>         Capabilities: [100] Advanced Error Reporting
>         Capabilities: [13c] Virtual Channel

[-- Attachment #2: Type: text/html, Size: 5045 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  8:39   ` Chris U
  2006-10-05  9:05     ` Jothis T.V
@ 2006-10-05  9:05     ` Alex Zeffertt
  1 sibling, 0 replies; 12+ messages in thread
From: Alex Zeffertt @ 2006-10-05  9:05 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

You can't always believe ifconfig - it's really down to the driver.
However, if you see packets that contain source MAC addresses other
than those of eth1 or eth0, coming out of both bridge interfaces, then
they must be in promisc mode.

It might be useful to run tcpdump/ethereal on the bridge, br0, itself to
check whether it is seeing packets sent by the laptop, and if so, if it
is seeing reply packets from the router.

Another useful tool is "brctl showmacs br0"

Alex

Chris U wrote:
> Hi Alex,
> 
> In the case you mentioned previously, does ifconfig show the interface 
> in promisc mode? I have tried further investigating whether or not the 
> interface is in promisc mode by using ethtool, a soft tool, however 
> unsuccessful. I also attempted to use a hub on eth0 to see if tcpdump 
> would pick up the packets in promisc mode; the packets are successfully 
> captured on the hub. [I did not test eth1, but I shall tomorrow 
> morning.] Both network interfaces are the same model/brand. Listed below 
> is a snapshot of my ifconfig and a snippet from my lspci.
> 
> This list is pretty responsive - I just wanted to say thanks to everyone 
> for taking time to help me out. ;)
> 


^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes
@ 2006-10-05  9:26 Skept
  0 siblings, 0 replies; 12+ messages in thread
From: Skept @ 2006-10-05  9:26 UTC (permalink / raw)
  To: bridge

see if the interfaces attached to the bridge interface are up. if not, try

ip link set dev eth0 up
ip link set dev eth1 up

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05  4:20 [Bridge] Bridge Woes Chris U
  2006-10-05  4:58 ` Jothis T.V
  2006-10-05  8:18 ` Alex Zeffertt
@ 2006-10-05 14:39 ` Stephen Hemminger
  2006-10-05 19:07   ` Chris U
  2006-10-05 19:43   ` Chris U
  2 siblings, 2 replies; 12+ messages in thread
From: Stephen Hemminger @ 2006-10-05 14:39 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

On Wed, 4 Oct 2006 18:20:43 -1000
"Chris U" <chris.uyehara@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?

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05 14:39 ` Stephen Hemminger
@ 2006-10-05 19:07   ` Chris U
  2006-10-05 19:33     ` Gergely Madarasz
  2006-10-05 19:43   ` Chris U
  1 sibling, 1 reply; 12+ messages in thread
From: Chris U @ 2006-10-05 19:07 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 4858 bytes --]

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@osdl.org> wrote:
>
> On Wed, 4 Oct 2006 18:20:43 -1000
> "Chris U" <chris.uyehara@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?
>

[-- Attachment #2: Type: text/html, Size: 10513 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05 19:07   ` Chris U
@ 2006-10-05 19:33     ` Gergely Madarasz
  0 siblings, 0 replies; 12+ messages in thread
From: Gergely Madarasz @ 2006-10-05 19:33 UTC (permalink / raw)
  To: Chris U; +Cc: bridge

On Thu, Oct 05, 2006 at 09:07:14AM -1000, Chris U wrote:
> 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)

If this a server with an ipmi bmc and the network card firmware supporting
ipmi, you might be experiencing the same problem as I did last year. 

The situation was that the broadcom firmware turned off promisc several
seconds after the card was set up. So if the driver set promisc right
after ifconfig up, it never noticed that the hardware actually cancelled
promisc mode. Small workaround to test this: ifconfig eth0 -promisc;
ifconfig eth0 promisc a minute after it has been brought up by ifconfig.

A more permanent workaround was to turn off IPMI support in the network
card using a utility downloaded from the vendor... 

-- 
Madarasz Gergely        gorgo@broadband.hu         gorgo@linux.rulez.org
    It's practically impossible to look at a penguin and feel angry.
        Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: [Bridge] Bridge Woes...
  2006-10-05 14:39 ` Stephen Hemminger
  2006-10-05 19:07   ` Chris U
@ 2006-10-05 19:43   ` Chris U
  1 sibling, 0 replies; 12+ messages in thread
From: Chris U @ 2006-10-05 19:43 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: bridge

[-- Attachment #1: Type: text/plain, Size: 3839 bytes --]

Alright list... good news and bad news.

Good news - the bridge works!

Bad news - one of the cat5 cables went "bad" sometime between posting to the
list and now; or maybe someone changed the cables on me w/o my knowledge.

In any case it works! =)

Thanks list for helping me out!

On 10/5/06, Stephen Hemminger <shemminger@osdl.org> wrote:
>
> On Wed, 4 Oct 2006 18:20:43 -1000
> "Chris U" <chris.uyehara@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?
>

[-- Attachment #2: Type: text/html, Size: 8643 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2006-10-05 19:43 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-05  4:20 [Bridge] Bridge Woes Chris U
2006-10-05  4:58 ` Jothis T.V
2006-10-05  7:59   ` Chris U
2006-10-05  8:18 ` Alex Zeffertt
2006-10-05  8:39   ` Chris U
2006-10-05  9:05     ` Jothis T.V
2006-10-05  9:05     ` Alex Zeffertt
2006-10-05 14:39 ` Stephen Hemminger
2006-10-05 19:07   ` Chris U
2006-10-05 19:33     ` Gergely Madarasz
2006-10-05 19:43   ` Chris U
  -- strict thread matches above, loose matches on Subject: below --
2006-10-05  9:26 Skept

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.