Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
Hey folks On Sun, Mar 15, 2009, Santiago Garcia Mantinan wrote: Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. Of all the info you are giving me... the most suspicious part is this, as I don't use gnome I don't know how it works or what it does, but I've seen several network managers do really weird things. So if you could somehow disable this, either by uninstalling that part of gnome or by disabling it or not running gnome for some time just to see if things would work that way and that way determine if the gnome guys can somehow be responsable for this and ask them to help on this. I was hit by this issue in the past; I think NM ignores the interfaces which have an iface stanza, not the ones with an auto line. The way I worked around this in the past was to add a manual stanza for eth0 to my config: iface eth0 inet manual with a slightly different stanza you can even bring the interface up and down with ifup/ifdown if you have any use for this: iface eth0 inet manual up ifconfig $IFACE up down ifconfig $IFACE down This should be enough to tell NM not to touch the bridge. The true fix would be for NM to handle bridges too, or at least extend the Debian plugin to not use interfaces which are in a Debian bridge. I think bridge support for NM is in the works upstream and might or might not be in the experimental NM. Cheers, -- Loïc Minier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
I'm using the bridge so that my virtualbox instances can operate like regular machines on my network. They'll get a dhcp address from my server etc - it really is an easy way to get networking up and runnnig in virtualbox. There is no need for this, virtualbox (at least 2.1 onwards) can do this using the ethernet device directly, no need for a bridge, in fact, this even works with a wireless card, which surprised me (I'm using ath5k). Now if you have the time and energy, it'd be interesting if you can duplicate the error with network-manager (should be quick to install and deinstall again, it does not depend on much afaik). Then maybe this bug could get reassigned to network-manager, because it clearly is missbehaving. The problem is that I don't have the time right now, I'd suggest you assign it to the gnome guys, if they need any help from me I'll be around, but I don't have experience with gnome and thus it may be difficult for me to replicate this. I really think this is a problem with gnome, seems to me that gnome somehow is running a dhcp over eth2 even though you have just configured br0, don't know gnome gnome got this eth2 idea from :-? Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. Of all the info you are giving me... the most suspicious part is this, as I don't use gnome I don't know how it works or what it does, but I've seen several network managers do really weird things. So if you could somehow disable this, either by uninstalling that part of gnome or by disabling it or not running gnome for some time just to see if things would work that way and that way determine if the gnome guys can somehow be responsable for this and ask them to help on this. Aside from that the only other noteworthy package I use (this is on a desktop btw), is virtualbox - which was also the reason I setup the bridge. But, aside from loading the vobxnetflt module, this problem occurs before I start virtualbox. Thanks for pointing this out, I know virtualbox, but I don't know what vboxnetflt does, so if you can explain this a little bit, it would be great. For what I know virtualbox loads its modules on startup, so even though I doubt it can be responsable for this, It could be, as it is doing things on our startup. How are you using this? I mean... 1- you are loading the vbox modules and not running virtualbox and already seing this bug, right? 2- how are you using virtualbox, why are you using a bridge with it? Please elaborate a bit on your network setup (you use eth2 bound to br0, how about eth0, eth1, ... how does virtualbox relate to the network interfaces, attaches using nat, host interface, ... and which interface it uses, ...) 3- add any other thing you think could help us here :-) Sorry, I'm not being of much help here, but I don't know what can be causing all this, I'm trying to get enough info so that I can try to setup something similar here that replicates the problem so that I can trace it. Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
On Sun, Mar 15, 2009 at 6:30 AM, Santiago Garcia Mantinan ma...@debian.org wrote: Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. Of all the info you are giving me... the most suspicious part is this, as I don't use gnome I don't know how it works or what it does, but I've seen several network managers do really weird things. So if you could somehow disable this, either by uninstalling that part of gnome or by disabling it or not running gnome for some time just to see if things would work that way and that way determine if the gnome guys can somehow be responsable for this and ask them to help on this. Heh, I am not even running gnome. But network-manager got pulled in on some update, and xfce is a bit too compatible sometimes it seems, as it was then automatically added to my session... Since I have absolutely no need for this on my machine, I removed it and woosh, everything works just as expected. Now I _only_ see br0 up, and thus of course no route (or ip address for that matter) on eth2. Aside from that the only other noteworthy package I use (this is on a desktop btw), is virtualbox - which was also the reason I setup the bridge. But, aside from loading the vobxnetflt module, this problem occurs before I start virtualbox. Thanks for pointing this out, I know virtualbox, but I don't know what vboxnetflt does, so if you can explain this a little bit, it would be great. For what I know virtualbox loads its modules on startup, so even though I doubt it can be responsable for this, It could be, as it is doing things on our startup. How are you using this? I mean... For completeness' sake, I'll answer the rest of these, though the problem is solved. 1- you are loading the vbox modules and not running virtualbox and already seing this bug, right? Yes, exactly. The virtualbox modules don't get autoloaded for some reason, so I add them to /etc/modules. 2- how are you using virtualbox, why are you using a bridge with it? Please elaborate a bit on your network setup (you use eth2 bound to br0, how about eth0, eth1, ... how does virtualbox relate to the network interfaces, attaches using nat, host interface, ... and which interface it uses, ...) eth0 is non-existant due to udev persistent rules. eth1 is the onboard network card, but it's not connected to anything. eth2 is an intel gigabit card. I'm using the bridge so that my virtualbox instances can operate like regular machines on my network. They'll get a dhcp address from my server etc - it really is an easy way to get networking up and runnnig in virtualbox. 3- add any other thing you think could help us here :-) Sorry, I'm not being of much help here, but I don't know what can be causing all this, I'm trying to get enough info so that I can try to setup something similar here that replicates the problem so that I can trace it. =) You certainly were helpful! Now if you have the time and energy, it'd be interesting if you can duplicate the error with network-manager (should be quick to install and deinstall again, it does not depend on much afaik). Then maybe this bug could get reassigned to network-manager, because it clearly is missbehaving. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
---snip--- auto lo iface lo inet loopback auto br0 iface br0 inet dhcp bridge_ports eth2 bridge_fd 2.5 ---snap--- I have setups that look mostly like yours and they work perfectly, I'd like to know a bit more about your setup, you say that your interfaces is exactly like that and if it is just like that I cannot see how eth2 can get the default route. After booting the default route is now set for eth2, not for br0. I think it used to be that it would always get set for both interfaces, which seemed to work fine. Both interfaces are up with the same ip address, exactly as before when it used to work fine. Having it set for both interfaces was also not good. If you don't have eth2 mentioned on your interfaces other than on the bridge_ports line then you must have it somewhere else. I'm thinking about some daemon doing dirty things, I would do a grep -r eth2 /etc and see what that accounts for. What dhcp client do you have installed? can you have a look at its config? Any network daemons running? maybe something related to gnome or kde? I don't think this is a but on bridge-utils but on your setup, but I'd like to know what is hapenning for the next time this happens to anybody else. Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
On Wed, Mar 11, 2009 at 12:47 PM, Santiago Garcia Mantinan ma...@debian.org wrote: If you don't have eth2 mentioned on your interfaces other than on the bridge_ports line then you must have it somewhere else. I'm thinking about some daemon doing dirty things, I would do a grep -r eth2 /etc and see what that accounts for. The grep only showed some commented lines in interfaces (I will delete them and see if they caused some effect although they were commented out). Aside from that only udev persistency rules, and one hit in a xend-config.sxp.dpkg-old (I don't have xen installed anymore). What dhcp client do you have installed? can you have a look at its config? Any network daemons running? maybe something related to gnome or kde? Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. I'm running dhcp3-client 3.1.1-6, AFAIK that's the only one I have installed. Trimming of comments, I think I have only the stock config: ---snip--- option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes; ---snap--- I have some entries in the enter/exit hooks, but all from packages, nothing custom. I don't think this is a but on bridge-utils but on your setup, but I'd like to know what is hapenning for the next time this happens to anybody else. Thanks, I appreciate it that you're interested in helping out anyway! I'm running a custom .26 kernel, but I just checked my config and it has IP_PNP not set (kernel level autoconfiguration), which as far as I know is the only option that does ip address assignment. Aside from that the only other noteworthy package I use (this is on a desktop btw), is virtualbox - which was also the reason I setup the bridge. But, aside from loading the vobxnetflt module, this problem occurs before I start virtualbox. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
Package: bridge-utils Version: 1.4-5 Severity: important I'm configuring a bridge with dhcp. It used to work just fine, but recently the default interface gets set for the wrong interface. My /etc/network/interfaces contains exactly: ---snip--- auto lo iface lo inet loopback auto br0 iface br0 inet dhcp bridge_ports eth2 bridge_fd 2.5 ---snap--- After booting the default route is now set for eth2, not for br0. I think it used to be that it would always get set for both interfaces, which seemed to work fine. Both interfaces are up with the same ip address, exactly as before when it used to work fine. I think this broke sometimes after lenny was released, but I'm not certain, sorry. Let me know if I can somehow help debug this problem. Thanks, ~David -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bridge-utils depends on: ii libc6 2.9-4 GNU C Library: Shared libraries Versions of packages bridge-utils recommends: ii ifupdown 0.6.8+nmu1 high level tools to configure netw bridge-utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
