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
