*** This bug is a duplicate of bug 1003842 ***
https://bugs.launchpad.net/bugs/1003842
Brian Marks wrote:
> Yes, tried restarting network-manager but used UI 'enable
> networking' checkmark to disable and re-enable. Would this be
> consistent with using command line to restart service?
Using the indicator to dis-"Enable Networking" and re-"Enable
Networking" does not restart the NetworkManager daemon, which is
necessary for changes to /etc/NetworkManager/NetworkManager.conf to
become effective. You have to open a Terminal and do "sudo restart
network-manager" or reboot.
> I have reviewed the resolv.conf file before and after connecting and the
> problem appears to be that the VPN DNS servers are not getting added to
> the file although search domains are getting added.
Well, when NM is in "dns=dnsmasq" mode you will only see "nameserver 127.0.0.1"
in /etc/resolv.conf. No further addresses will be added there. The addresses
of the upstream nameservers including the VPN ones should appear in
/var/run/nm-dns-dnsmasq.conf instead.
If you comment out "dns=dnsmasq" in
/etc/NetworkManager/NetworkManager.conf and restart network-manager then
up to three upstream nameserver addresses will be included directly in
/etc/resolv.conf and there will be no /var/run/nm-dns-dnsmasq.conf file.
If, in either case, you don't see your VPN nameserver addresses in the
appropriate file then there is something wrong with, e.g., your DHCP
server configuration, DHCP client, ....
But I suspect that you have also hit #1003842 and that you will find
that everything works after you restart network-manager with
"dns=dnsmasq" commented out.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/994575
Title:
dnsmasq does not update nameserver info after network change
Status in “network-manager” package in Ubuntu:
Confirmed
Bug description:
I have a VPN set up in Network Manager, which worked well when my
system was running 11.10.
After upgrading to 12.04, I've noticed that DNS changes needed by the
VPN aren't happening. Hosts that only resolve within the VPN won't
resolve, and hosts that are supposed to resolve with different IP
addresses inside the VPN don't.
I can see the new, proper nameserver configuration in /var/run/nm-dns-
dnsmasq.conf. I can resolve properly if I query the name server
directly, i.e. "host <name-to-resolve> <vpn-dns-server-ip>". And, if
I use that IP address instead of the name, I can successfully do
things like ssh. But simple resolution appears to still be using the
old name server.
At one point, I killed off dnsmasq and wrote a new /etc/resolv.conf
with the VPN name servers. That worked, but caused all manner of
problems later.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 4 09:04:23 2012
EcryptfsInUse: Yes
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 192.168.50.2 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.50.0/24 dev eth0 proto kernel scope link src 192.168.50.222
metric 1
192.168.50.0/24 dev wlan0 proto kernel scope link src 192.168.50.106
metric 2
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-05-02 (1 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/1
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994575/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
