On Thu, Jan 10, 2002 at 10:01:48AM -0000, John, Gareth wrote:
> Hi,
Hi,
> All seemed to go well (except for a hunk failure with the last
> patch, which I assume is because some of these fixes made it into the 2.4.17
> kernel...).
It's because one of the additional fixes exports a symbol that is also
exported by the bridge-nf patch. It's safe to ignore that hunk.
> However, when I configured my bridge:
>
> brctl addbr br0
> brctl addif eth0
> brctl addif eth1
>
> and used the 'ip' tool to configure ip addresses and activate the br0
> interface, I was unable to ping any other ip addresses on my LAN, or my ADSL
> router.
Did you up the br0 device?
# ip link set br0 up
Did you wait 30 seconds?
# sleep 30
Did you up the eth0, eth1 interfaces as well?
# ip link set eth0 up
# ip link set eth1 up
> What I'd like to know is, does the 'ip' configuration do anything
> differently to ifconfig that would cause my bridge not to work correctly,
> and if this isn't the case, is it possible to enable any debug options to
> get some output that may be useful for debugging my bridge?
Try the 'show' and 'showstp' options.
# brctl show
# brctl showstp br0
If it lists port state as 'disabled', either the physical device or the
bridge device isn't up. If it lists 'listening' or 'learning', you have
to wait. If it lists 'forwarding', it should be working. If it lists
'blocking', you have created a loop in your network and the bridge shut
down one or more ports not to create a forwarding loop.
cheers,
Lennert
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
