You are not logged in.
I've been running an ASUS EeePC 1000 for almost a year now over my 802.11n Verizon FiOS WPA2 connection. Everything had been working fine until networkmanager got updated from 1.0.2-3 to 1.0.2-4. I couldn't even find a network connection unless I went hardwire. Downgrading to 1.0.2-3 fixed the problem, but what was the issue in the first place? Did something major change from one version to the next?
Last edited by ProfessorTomoe (2015-06-26 10:49:46)
Offline
You can view the changes for Network Manager over here - https://projects.archlinux.org/svntogit … orkmanager
I can see a fix for FS# 44878, which states that Network Manager doesn't automatically rely on resolvconf for managing resolv.conf anymore. You might need to add
set rc-manager=resolvconf
to /etc/NetworkManager/NetworkManager.conf.
Offline
You can view the changes for Network Manager over here - https://projects.archlinux.org/svntogit … orkmanager
I can see a fix for FS# 44878, which states that Network Manager doesn't automatically rely on resolvconf for managing resolv.conf anymore. You might need to add
set rc-manager=resolvconf
to /etc/NetworkManager/NetworkManager.conf.
This fixed it—thank you! Can you please add this to the wiki?
Offline
Glad to see you fixed your problem, but I didn't really face any such problems even though I'm using resolvconf with Network Manager just like you. I think we should wait and hear other's opinions before making any changes to the wiki.
Offline