If I recall well, the ifupdown/examples/bridge is just an example of a script for ifupdown which doesn't have anything to do with how you configure your bridge, as it states on the comments on the header, the bridge-utils package already provides a similar script but more prowerfull, which is the one that should be used. Anyway, the user doesn't have to take care of these scripts, he just needs to focus on /etc/network/interfaces.
I'd like to note that configuring a bridge is not a thing for knewbies or so, and that a person trying to configure a bridge must be aware of what a bridge does, having said that, of course I'd like to make people's configuration as easy as possible, and that's why I wrote the scripts to configure the bridge and maintain this package. For what I see on your bug, the main problem here seems to be that you are declaring the interfaces which you want to put on your bridge as stand alone interfaces, and even though that can be the wanted behaviour on some weird cases, this is not typically what you want, so... you should remove your eth0 declaration and everything should work as expected and things should be more clear. I want to hear from you if this solves the problem and if adding an statement to the doc explaining this would clarify things a bit. Another thing is bridging with a wireless... this is not something that is easy to do unless we are talking about a wds interface or one working in master mode, which means... if your wireless interface is working as a client associated to an access point, bridging typically makes no sense here, you should go to a routing solution or some other stuff, but not bridging. I'd really like to receive your input on the bug to see if we can close it before Lenny, even though I think it's a little bit late already, but I hadn't noticed the bug till now, sorry. Regards... -- Santiago García Mantiñán -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
