NetworkManager doesn't use manual set DNS although there's an option for that
Bug #382161 reported by
FriedChicken
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
knetworkmanager |
Fix Released
|
Medium
|
|||
network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
plasma-widget-networkmanagement (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Karmic |
Invalid
|
Medium
|
Jonathan Thomas | ||
Lucid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: network-manager
Jaunty, KDE 4.2.4
I liked to use dnsmasq for local dns caching. So I set up NetworkManager using the plasma-
After dis- and re-enabling the wireless network to enable the new settings (why isn't this done immediately?) resolv.conf always has 192.168.2.1 as DNS. Manual edit of resolv.conf always get overwritten by NetworkManager.
Actually I don't know whether this is a bug in the plasma widget or NM itself.
affects: | plasma-widget-network-manager (Ubuntu) → plasma-widget-networkmanagement (Ubuntu) |
tags: | removed: plasma-widget-network-manager |
Changed in plasma-widget-networkmanagement (Ubuntu): | |
status: | Fix Released → Confirmed |
Changed in knetworkmanager: | |
status: | New → Confirmed |
Changed in network-manager (Ubuntu Karmic): | |
status: | New → Invalid |
Changed in plasma-widget-networkmanagement (Ubuntu Karmic): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Jonathan Thomas (echidnaman) |
Changed in knetworkmanager: | |
status: | Unknown → Fix Released |
Changed in knetworkmanager: | |
importance: | Unknown → Medium |
To post a comment you must log in.
I have a similar problem. Except If I use "DHCP with Manual DNS", I can't get the wireless to even establish a connection at all. Cchange it back to just plain DHCP and it connects straight away