Cyril Brulebois wrote: > Michael Biebl <[email protected]> (17/12/2008): >> That's a known issue. For unmanaged devices, NM assumes the state to >> be offline. I'm merging this with the existing bug reports. >> >> See e.g. #491826 for more info. > > Hmm, OK. But that bug has been reported against 0.6.6-2 and previous > versions (unstable's) were working fine for me, so (IMHO) that looks > like a regression from previous versions.
It's the same underlying issue. What has changed though between 0.6 and 0.7 is the way, how NM determines when to mark a device managed or unmanaged (see the 0.6 README.Debian and the new README.Debian). That's why you see this "regression" with 0.7. (It actually isn't a regression, as you can now controll more easily when to mark a device managed/unmanaged) > >> You need to restart the system settings service (see the README.Debian >> file I referring to in my previous email [1]) >> Asudo killall nm-system-settings >> >> After that, NM should pick up you eth0 interface. > > FWIW, it didn't. (I checked the daemon restarted, and invoke-rc.d > restarted network-manager as well afterwards.) > >> An alternative is to configure >> eth0 via /e/n/i and set >> >> [ifupdown] >> managed=true > > That did the trick, thanks. > > Cheers, -- 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
