Drew Parsons wrote: > On Tue, 2008-12-16 at 02:15 +0100, Michael Biebl wrote: >> Drew Parsons wrote: >>> On Tue, 2008-12-16 at 01:39 +0100, Michael Biebl wrote: >>>> Could you please show me your /etc/network/interfaces? >>>> >>> Attached. It's showing my static office address, since that's the nm >>> profile I've currently selected. >> Try to add the dns-* settings in /e/n/i, as I suggested, that should help. >> > > Wouldn't that only be a temporary bandaid, since it would be lost the > next time I switch location in the Network tool?
I dunno exactly what the Network tool is doing. > >>>> Have you configured the static configuration vi /e/n/i or the >>>> nm-connection-editor, i.e. a keyfile connection. >>>> >>> No, I did all the configuration using network-manager (i.e the Network >>> Settings tool). When I select my roaming (dhcp) profile in nm, for >>> instance, then the static configuration in /etc/network/interfaces >>> disappears. >>> >>> I may have had a look at nm-connection-editor (Gnome >>> System->Preferences->Network Configuration) but didn't see any useful >>> settings there (the new 0.7 version seems to have more but I only had a >>> brief glimpse without configuring settings), so I've been using >>> System->Administration->Network instead. >> These are two different tools, not related to each other. >> >> The Gnome Network tool will directly edit /etc/resolv.conf, but this >> information >> will be lost, as soon as you activate the connection. >> > > OK, this might be the real problem. The Network admin tool I've been > using is /usr/bin/network-admin. I see know it's from the > gnome-network-admin package. I had thought it was a network-manager > tool so I apologise if I misfiled the bug report. Should we reassign > the bug, or is there a bug here in the interactions between > network-admin, network-manager and resolvconf that we should sort out > here? > > Am I right in understanding then that this is a bug > in /usr/bin/network-admin, that it does not set up resolv.conf at boot? Not quite, the problem is, that network-admin expects plain ifupdown and so edit /etc/resolv.conf directly. If you are using resolvconf and/or NetworkManager this changes will be lost. > > It sounds like nm-connection-editor (package network-manager-gnome) is > the tool I'm really after. It truly is very confusing having two > separate Gnome tools like this. Does that mean I should completely > ignore network-admin altgoether? Previously I've just managed my > interfaces manually in /e/n/i, so I thought I should try the Gnome tools > on this new laptop, but it's more confusing than I expected. I agree, the situation is a bit unfortunate. So, basically you have (legacy) net-admin which edit /e/n/i and /etc/resolv.conf and on the other hand you have NM, which has read only support for /e/n/i, and rw support for system settings via the keyfile plugin (/etc/NetworkManager/system-connections). > >> There are basically three ways, how to store a connection: >> >> 1.) As a user connection (stored in gconf) >> 2.) As a system connection (stored via keyfile plugin, see >> /etc/NetworkManager/system-connections) >> 3.) As a (read only) system connection (/etc/network/interfaces) > > > OK. So I've used 3) in the past (manually). Maybe 1) is what I want, so > long as the last interface still comes up at boot (so I can use it from > the virtual terminals without X). > > I can't seem to let network-manager take control of eth0 though. I've Please wait until 0.7.0-1 hits the archive (currently in NEW) and read the README.Debian about the managed/unmanaged mode. If there is still something unclear, I can *try* to explain. > now deleted all mention of eth0 from /e/n/i, added a configuration in > nm-connection-editor, ran /etc/init.d/network-manager restart, but eth0 > is ignored completely. nm-tool continues to declare "Device: eth0 > State: unmanaged". Run "killall nm-system-settings". Michael, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature