No nameserver addresses in resolv.conf when connecting to Wi-Fi network with no gateway
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
When connecting to LAN nameserver gets set correctly, when using WIFI no nameserver is set in resolv.conf
dhcp provides a dns server - nm-tool output:
- Device: wlan0 -------
Type: 802.11 WiFi
Driver: iwlagn
State: connected
Default: no
[... truncated ...]
IPv4 Settings:
Address: 10.30.50.110
Prefix: 24 (255.255.255.0)
Gateway: 0.0.0.0
DNS: 10.30.49.10
But: No entry in resolv.conf (resolvconf package is installed)
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
ii network-manager 0.7~~svn2008090
ii resolvconf 1.42ubuntu2 name server information handler
I know that not setting a default gateway in this setup does not make immediate sense, except that I use openvpn and in previous network-
This output is without the vpn started, btw!
Changed in network-manager (Ubuntu): | |
status: | Triaged → Fix Released |
Same problem here, with updated packages as of 2008-10-23. This seems the problem only for local networks. When connecting to my 802.1x university's network I get an external IP (130.x) and resolv.conf is updated fine. When connecting to local networks it will not and my resolv.conf is empty, despite NM shows clearly it's given the the addresses on dhcp!
syslog output when connecting to local network, shows three nameservers available.
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.71'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.72'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.73'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> domain name 'BalPol.Local'
resolv.conf file after connect shows only the line it's managed by Networkmanager. It does not matter if resolvconf is installed or not. If it is, the resolv.conf file will only show it's managed by resolvconf.
Additionally, when entering the nameservers manually in NM it won't appear in resolv.conf even then!
FYI: I have disabled avahi-daemon for (proper) use of the local network and it has worked well in Hardy.