[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Comment #21 fixed the issue for me. Bug does also apply to current 12.10 release (upgrade: 16/11/2012). -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
@all: - this particular bug applies only if you installed Ubuntu-Secure-Remix, and upgraded from it. If you had installed a standard version of Ubuntu, please create a new bug report here: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+filebug - this bug should concern only people who installed Ubuntu-Secure-Remix ISOs dated 04/10/2012. If you installed a newer Ubuntu-Secure-Remix ISO (downloaded after 04/10/2012), and upgrade from it, you should not get this bug. - If you reproduce it with a recent (04/10/2012) ISO, please create a new bug report here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+filebug ** Changed in: ubuntu-secure-remix Status: Fix Committed = Fix Released ** Summary changed: - No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta + No resolving after upgrade from Ubuntu-Secure ** Description changed: - I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that - this is a network-manager issue, though I'm not certain. + *** PLEASE READ BEFORE POSTING: + - this particular bug applies only if you installed Ubuntu-Secure-Remix, and upgraded from it. If you had installed a standard version of Ubuntu, please create a new bug report here: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+filebug + - this bug should concern only people who installed Ubuntu-Secure-Remix ISOs dated 04/10/2012. If you installed a newer Ubuntu-Secure-Remix ISO (downloaded after 04/10/2012), and upgrade from it, you should not get this bug. + - If you reproduce it with a recent (04/10/2012) ISO, please create a new bug report here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+filebug + + *** ORIGINAL BUG REPORT: + I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: - 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). + 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): - server=208.67.222.222 + server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: - auto lo - iface lo inet loopback + auto lo + iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: - default via 192.168.1.1 dev wlan0 proto static - 169.254.0.0/16 dev wlan0 scope link metric 1000 - 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 + default via 192.168.1.1 dev wlan0 proto static + 169.254.0.0/16 dev wlan0 scope link metric 1000 + 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
I had a similar problem and running dpkg-reconfigure resolvconf seems to have fixed it. Running that asked me two yes/no questions -- I think one of them was about making the missing symlink, and I answered yes to both. (I'm running regular 12.10, so I realize this shouldn't be the place to post about that, but it's where I found the fix, so I'm posting here anyway.) -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Hi Leon. Please look at bug #1000244, e.g., at my comment #66. -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Francisco: Are you running Ubuntu Secure Remix? -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Just upgraded my ubuntu 12.10 and was hit by this bug. I'm not running secure remix, just the normal Ubuntu 64 -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
sudo aptitude purge resolveconf has solved the problem. But I'm not sure if this package is actually required for something. -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Lanoxx: Resolvconf is the part of the base system that manages resolv.conf dynamically. Removing it is never the right solution. Try installing it again and then doing dpkg-reconfigure resolvconf and then rebooting. If you still have problems then we should investigate the cause. In a new bug report. This one is about a bug in Ubuntu Secure Remix. -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Thanks for this post. I have used Ubuntu for 2 years, had upgraded to 12.04 and yesterday to 12.10. And for the first time I could not get online although I was connected to my router,and I tried your suggestions and It's working great. Thanks Sander Sturwold. I'm running 12.10 on an EeePc 1005PBE, Atheros Communications Inc AR9285 Wireless Network, ath9k driver, Linux Aztlanow 3.5.0-18-generic #29-Ubuntu SMP, if that's any help to anybody. -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
On my machine the /etc/resolv was present. It said: nameserver 127.0.0.1 search lokaal I changed in nameserver 8.8.8.8 search lokaal And now i get connected and going to update. -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
** Summary changed: - No resolving after upgrade from 12.04 to 12.10 beta + No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta ** This bug is no longer a duplicate of bug 1000244 /etc/resolv.conf symlink does not exist after initial installation of resolvconf package ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in “network-manager” package in Ubuntu: Fix Committed Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
Thanks a lot jrog for your bug report. I confirm there was no /etc/resolv.conf in Ubuntu-Secure-Remix iso. I will fix it and upload new Ubuntu-Secure ISOs in the coming days. ** Changed in: network-manager (Ubuntu) Status: Invalid = Fix Committed -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in “network-manager” package in Ubuntu: Fix Committed Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
** Also affects: ubuntu-secure-remix Importance: Undecided Status: New -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: New Status in “network-manager” package in Ubuntu: Fix Committed Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta
** Changed in: ubuntu-secure-remix Status: New = Fix Committed ** Changed in: network-manager (Ubuntu) Status: Fix Committed = Invalid ** Changed in: ubuntu-secure-remix Assignee: (unassigned) = YannUbuntu (yannubuntu) ** Changed in: ubuntu-secure-remix Importance: Undecided = Medium -- 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/1051348 Title: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta Status in Ubuntu-Secure-Remix: Fix Committed Status in “network-manager” package in Ubuntu: Invalid Bug description: I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf) that this is a network-manager issue, though I'm not certain. I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network- manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual. On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This appears to be the source ofthe problem, as I can fix the issue by doing the following: 1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?). 2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the following (this line identifies an OpenDNS server): server=208.67.222.222 3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically. So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sat Sep 15 13:02:05 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84 802-3-ethernet1347727737 Sat 15 Sep 2012 12:48:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 NotThat! 968fa0a6-be87-47bb-b306-daf2188393e9 802-11-wireless 1347728337 Sat 15 Sep 2012 12:58:57 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
