On Wed, 18 Dec 2013 01:36:41 +0100
Santiago Garcia Mantinan <ma...@debian.org> wrote:

> First tests went really wrong.
> 
> I have this setup:
> 
> auto br0
> iface br0 inet static
>         address X.X.X.X
>         netmask 255.255.255.0
>         bridge_ports all
>         bridge_fd 2
>         bridge_stp on
>         bridge_hw XX:XX:XX:XX:XX:XX
> 
> Can you test something like this (I had just one ethernet card on the
> bridge) on your systems to see if it works?
> 
> I had different behaviours, sometimes it didn't even learn arps,
> others it did learn arps but ping and other things wouldn't work. I
> believe the difference may be that I'm using stp.

You are right, it doesn't work for me either. I did some additional
testing and will try to summarize my findings. The two ways I created
bridges during testing were:

A)
# ip link add brX address XX:XX:XX:XX:XX:XX type bridge

B)
# ip link add brX type bridge
# ip link set brX address XX:XX:XX:XX:XX:XX

With A) the bridge is unable to communicate via enslaved network
devices (probably other things fail too, haven't checked). Only once
the bridge device itself is put into promiscuous mode (which shouldn't
be necessary), e.g. by starting tcpdump (without -p) or wireshark,
things start to work.

Witch B) the bridge seems to works fine, at least in simple scenarios
(I did no extensive testing).

I was trying to find any difference between the two created bridges
but I couldn't find any. I looked at netlink communication via `bridge
monitor`/`ip monitor` and I checked all the parameters of the bridge
in /proc/sys/net/ipv{4,6}/{conf,neigh}/brX/* .

As of now I couldn't find out what is responsible for the bad behavior
in A). By now I agree with your suggestion to use
        ip link set brX address XX:XX:XX:XX:XX:XX
after the interface was created (with either brctl or iproute2). I'm
still interested why A) doesn't work; if I find the time I will look
into this more extensively. If you have any ideas that might help
tracing this problem please let me know. As for my “special” problem,
I will try to work around it by attaching a dummy interface to the
bridge.


Thanks for your effort and sorry for suggesting something that doesn't
work with ”real“ bridges.

Lukas


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to