Um. I haven't realized that it is possible to just stop networkManager process (and disable it in /etc/rc?.d/) in order to restore the functionality back, -- after stopping it, all applications which were previously refusing doing anything starts working again (What a nice feature it is, NetworkManager!..)
So indeed, the severity of this bug may be lowered. Now, after stopping nm, I realized it ruined my /etc/resolv.conf with some non-trivial sorting rules in it, replacing it with a file with just one comment line -- "# generated by NM". So I had to resort to restoring that file from a backup. So it looks like NM does good job at _ruining_ network. Note that the bridge setup becomes more and more common, with more and more people discovering virtualisation technologies. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
