resolv.conf, nameservers not properly updated (Was: Not able to connect to network)

[Rajeev Sharma]

Binary package hint: network-manager

I updated my system today, and I remeber there was a network-manager update too. After update, my network is screwed up. I am not able to connect to any network (Wired, Wireless). Network manager says I am connected, but can't ping anyone in my network.

Can't upload any more information from that box, because no internet connection

[Fahim Abdun-Nur (fahim-a)]

There could be countless permutations of what could be a misconfiguration issue somewhere; requesting additional info:
- What *ubuntu release are you running?
- What output do you get when you issue ifconfig on a terminal?

Could be a miriad of issues (dns, dhcp, etc. etc.). I'm personally running the latest and greatest package version (for intrepid though) and everything seems fine...

[Rajeev Sharma (rajeev1982)]

ok so here it is.

I figured out the problem. I was able to ping any IP (be it my local network
or google's ip) but not able to ping any site by name (not even my local
network or google.com). In the connection information dialog (In the network
manager GUI) I could see the Primary, Secondary DNS and all other stuff set
up correctly, still could not ping any website with the name.

I changed the resolve.conf file and added my nameserver manually and it's
working now.

I am not a network expert, so don't have much Idea on what is wrong.

My OS version is ubuntu 8.10

Regards,
Rajeev

On Fri, Sep 12, 2008 at 3:11 PM, Fahim Abdun-Nur <email address hidden>wrote:

> There could be countless permutations of what could be a misconfiguration
> issue somewhere; requesting additional info:
> - What *ubuntu release are you running?
> - What output do you get when you issue ifconfig on a terminal?
>
> Could be a miriad of issues (dns, dhcp, etc. etc.). I'm personally
> running the latest and greatest package version (for intrepid though)
> and everything seems fine...
>
> --
> Not able to connect to network
> https://bugs.launchpad.net/bugs/269340
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Alexander Sack (asac)]

do you have the resolvconf package installed?

[Alexander Sack (asac)]

also, please tell us what was in your resolv.conf was it just empty? or wrong nameserver information?

[Rajeev Sharma (rajeev1982)]

I don't have that box with me right now, need to check as soon as I get that
box. but I would like to give you little more details perhaps it will help
you.

I updated the system at home, where I have a wireless internet router
(modem+wireless router). when the system was updated my resolv.conf file was
renamed to resolv.conf.old (and this file had all my nameservers in it.).
The new resolv.conf file had only one nameserver 192.168.1.1 which is my
wireless router's ip.

I took the same laptop to my office and tried to connect and you already
know couldn't get the proper network setup. In my office I couldn't get the
nameservers updated in resolv.conf file (which are obviously different from
192.168.1.1). I could very well see the nameserver information in the
network manager gui and all were correct.

So the new bug summary is correct it should be a problem in updating the
information in resolv.conf. It retrived the correct information related to
my network so there seems no problem there.

All the network stuff was working for me earlier so idealy I should have all
the required packages installed. If anything got removed during the update
then I am not sure. I will let you know about the package (resolvconf) as
soon I get the same box.

Regards,
Rajeev

On Sat, Sep 13, 2008 at 7:28 AM, Alexander Sack <email address hidden> wrote:

> do you have the resolvconf package installed?
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Not able to connect to network
> + resolv.conf, nameservers not properly updated (Was: Not able to connect
> to network)
>
> --
> resolv.conf, nameservers not properly updated (Was: Not able to connect to
> network)
> https://bugs.launchpad.net/bugs/269340
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Rajeev Sharma (rajeev1982)]

I checked my system, I do have resolvconf installed (version1.42)

On Sat, Sep 13, 2008 at 7:30 AM, Alexander Sack <email address hidden> wrote:

> also, please tell us what was in your resolv.conf was it just empty? or
> wrong nameserver information?
>
> --
> resolv.conf, nameservers not properly updated (Was: Not able to connect to
> network)
> https://bugs.launchpad.net/bugs/269340
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[xnv (xnvvnx)]

I just installed 8.10 and ran into this problem. Initially, it used DHCP to connect. I changed it to 'Manual', set a new IP, changed the DNS server, and the search domain. None of these changes took effect immediately, but there was no indication that they would not. (IIRC, they did take effect immediately in 8.04.) I went and looked at resolv.conf and the contents matched those that DHCP would detect. I then checked and uncheck 'Enable Networking', which solved the problem. Yes, that's an obvious thing to try for most of us, but I think the user should somehow be alerted with the option to reset the connection if it's not simply reset automatically.

[Alexander Sack (asac)]

what connection type are you using?

[Matt C (proteus400)]

I too have this problem. I've recently upgraded both a laptop (using ath5k) and a PC (wired network) from 8.04.
The PC works fine.

On the laptop; I had reason to go into the new network manager, which looks great but when I try to enter DNS servers for wlan0 and save, I am shown an error dialog:

  Updating connection failed: nm-ifupdown-connection.c.82 - connection update not supported (read-only)..

It doesn't ask me to authenticate as root, which I presume I must be to do this.

resolv.conf seems to be cleared on boot, so when I have put nameserver entries into resolv.conf myself so that I can google the problem, I must do so again every boot. I can't find the equivalent network manager configs to edit.

In 8.04 on this laptop I had madwifi ath drivers installed and I had to do /etc/init.d/networking restart every boot before wireless network would come up; so expected a problem or two..

On the laptop, resolvconf was found to be *not* installed after the upgrade. (I've installed it now.)

I'm a programmer and familiar with Linux if I can help further. Congrats on an overall great release of a great distro :)

Regards,
Matt

[angus (angus-fairhaven)]

even with starting it as root (sudo) it still gives that error. resolvconf is installed. If i edit the resolv.conf manualy then it works, if i try edit anything in the nm-connection-manager, it then throws this error. This the output i get when doing it from command line. Looking at the connection, the MAC address is blank and the netmask is set to 24, i can not change the netmask.

angus@kate:~$ nm-connection-editor
Xlib: extension "RANDR" missing on display ":0.0".

(nm-connection-editor:9857): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed
** Message: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.

** (nm-connection-editor:9857): WARNING **: No connections defined

(nm-connection-editor:9857): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

** (nm-connection-editor:9857): WARNING **: Invalid setting IPv4 Settings

[Philip.Rowney (philip-rowney)]

I updated to 8.10 Today (14/11/2008) and tried to enable my wireless again.
I have a broadcom card with the latest proprietary driver installed. (nice bit of desktop software the new 'restricted drivers' management tool)

several things I noticed
1. Network Configuration is now in System->Preferances not System->Administration.
2. Network Configuration does not ask for Authentication.
3. It doesn't work!!!

I ran nm-connection-editor from the command line to capture the output.

I clicked on the tab for wireless, then selected my profile "ifupdown(eth1)"
then selected 'edit'.
When the window popped up, I supplied a password for WPA (it never saved it correctly with Hardy before)
clicked OK.

And to finish it all off I get a dialog displaying this.

"Updating connection failed: nm-ifupdown-connection.c.82 - connection update not supported (read-only)"

Here is the output at the command line.

(nm-connection-editor:21544): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed
** Message: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.

** (nm-connection-editor:21544): WARNING **: Bad value '0' for key 'wpa_psk_key_mgt' on NM 0.6 connection MingeMound

** (nm-connection-editor:21544): WARNING **: No connections defined

(nm-connection-editor:21544): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(nm-connection-editor:21544): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(nm-connection-editor:21544): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(nm-connection-editor:21544): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

** (nm-connection-editor:21544): WARNING **: Invalid setting Wireless Security: Invalid wireless security

Hmmm, I get the same dialog whatever I try to do!!!!!!

It looks like a permissions problem, but running it 'sudo' doesn't make a difference.

Confused

[Stormx (stormx2006)]

Same thing happening here. My brother's network stopped working last night. He plugged his phone in and BAM!

nm-connection-editor gives the same error as people have been describing (about it being read only)

netmask is set to 4 for some reason.

DNS field has been blanked, was previously working.

This needs to be fixed ASAP. Can you PLEASE just get rid of Network Manger, or at least allow us to use the old, reliable and less confusing GNOME interface. The new one is HORRIBLE.

[Alexander Sack (asac)]

this is more or less bug 284298. also read-only connection UI can be improved. this needs to be backported from 0.7