Cannot set manual IP and DNS with nm-connection-editor

When you say "Press apply", is the button actually active?

I'm running the latest version of network-manager ( 0.8~a~git.20090930t162132.866d48b-0ubuntu1~nmt1 ) and -applet ( 0.8~a~git.20090930t162757.5fbd4b8-0ubuntu1~nmt1 ) from the daily trunk ( https://edge.launchpad.net/~network-manager/+archive/trunk ), and I see some inconsistent behavior:

1. Sometime when I select an network on the Wireless Tab, and click "Edit", the "Apply" button is insensitive ( ie. you can't click it ). This seems to apply to the network as a whole ( ie. you can't modify any of it's attributes ).

2. If on the other hand, the button is sensitive ( ie. click-able ), then I'm able to change the IP settings from DHCP to Manual and the next time I click the network, the changes were saved. Note, I haven't actually tested if they're used yet.

I've solved my issue for now by adding this ppa: https://edge.launchpad.net/~network-manager/+archive/trunk
This will upgrade network manager (0.8~a~git.20090930t162132.866d48b-0ubuntu1~nmt1) and network-manager-applet (0.8~a~git.20091001t060520.d45a2d0-0ubuntu1~nmt1).

Hope this helps.

Installing PPAs version solved for me. Please, update networkmanager to 0.8 before RC of Karmic.

should be fixed in latest trunk build. please test from here: https://edge.launchpad.net/~network-manager/+archive/trunk before it hits the archive.

I've tested with cable connections and it works fine.
On the other hand with wireless connections i get the same issue that have Tony Espy, Sometimes the button isn't clickable, the password isn't stored and, finally, i can't connect.

I experience this problem when setting up a wired connection manually as described above, not just with wireless connections.

Confirmed that the 0.8~a~git.20090930t162757.5fbd4b8-0ubuntu1~nmt1 build listed above fixed the issue for me.

Same as Andrew, nm-connection-editor was segfaulting when trying to change settings.

Andrea's linked ppa solved the issue for me as well.

PPA version selved the problem :)

There is another bug, but I don't know if it depends by Network Manager or not... If I use my router as DNS address, I can't resolv IP by hostnames... For which packet can i open this bus in your opinion?

Ravic,

This sounds like a configuration issue with your router. For testing, try using the DNS information provided by your ISP or network administrator. Better yet, use the servers from http://www.opendns.org:

208.67.222.222
208.67.220.220

These are very reliable and should behave in the same way regardless or your geography, ISP, or network configuration. If you can resolve hostnames using these DNS servers, then the problem is likely your network.

Andrew, thank you, infact i'm just using OpenDNS :)
But I don't think it's a problem of my network: infact with Ubuntu 9.04, Fedora 11 (and also with Fedora 12) using my router like dns server works fine...
I would open a bug, but I don't know which process fails (i've to use apport to open the bug)...

Alexander,
latest trunk solved the problem fome me, thanks.

Having the same issue in Ubuntu Karmic. I hope, that will be fixed with upgrade. The way to reproduce: enter network manager editor, select wired connection, select 'Manual' in ipv4 tab, set your params, click 'Ok' and see, that nothing changed. After re-opening of nm-connection-editor there's still DHCP there. (Ubuntu Karmic beta).

Oh, no, i still have this bug with nm-connection-editor crashing when changing connection settings.

This bug was fixed in the package network-manager-applet - 0.8~a~git.20091002t194214.8515a07-0ubuntu1

---------------
network-manager-applet (0.8~a~git.20091002t194214.8515a07-0ubuntu1) karmic; urgency=low

  * upstream snapshot 2009-10-02 19:42:14 (GMT)
    + 8515a07e507847c4372fe8f95bddf57aea66acd5
  * fixed upstream
    - LP: #285219 - Critical warning while running nm-connection-editor
    - LP: #442988 - network manager mobile broadband does not remember username
      and password
    - LP: #439956 - Cannot set manual IP and DNS with nm-connection-editor
    - LP: #438160 - nm-applet loses ipv4 configuration
    - LP: #431265 - Network Manager can't connect to hidden wireless networks
    - LP: #443049 - MASTER nm-connection-editor crashed with SIGSEGV in get_permissions_cb
    - LP: #438374 - Failure to retain edited MTU value
    - LP: #436839 - Disconnect menu option looks like wireless network

  [ Tony Espy <email address hidden> ]
  * drop wifi toplevel_sort patch that was committed upstream
    - delete debian/patches/wifi_toplevel_ap_sort.patch
    - update debian/patches/series

  [ Alexander Sack <email address hidden> ]
  * drop preview patch that was committed upstream
    - delete debian/patches/nm08-applet-preview.patch
    - update debian/patches/series
  * require network-manager and libnm-* >= 0.8~a~git.20090930t162132
    - update debian/control
  * adjust patches to new upstream code base
    - update debian/patches/lp341684_device_sensitive_disconnect_notify.patch
  * (re-)sort wifi toplevel AP list alphabetically before adding to menu
    - add debian/patches/toplevel_sort.patch
    - update debian/patches/series
  * rebuild against latest NM after padding additions to libnm-* APIs
    - update debian/control

 -- Alexander Sack <email address hidden> Mon, 05 Oct 2009 23:45:07 +0200

I am able to reproduce this behavior in the Karmic release.

I confirm this on my machine. Can't change to manual (or any other than the default auto DHCP).

I have the same problem on Linux Mint 8 (helena) static IP assignments do not save, if i rename Auto eth0 as manual-eth0 and give it a manual IP, the next time network-manager restarts it adds a Auto eth0 configuration ...

Sorry to bother You but I still have this problem (impossible to manual configure a wired connection) after upgrading to 9.10

I'm not able to fix it by applying the proposed PPA "ppa:network-manager/trunk" just because my machine is not able to connect to the Internet, just because of the but itself.

How to fix it? I'm only able to download something from another machine and loading it into the bugged machine by some CD-ROM or memory stick. Please, could You explain me how to this?

Regards.

This bug vanished (for me at least) after upgrading to Lucid.

Thanks you all.

CM

It works on Lucid, doesn't on Maverick, same machine, same eth card and network settings, but booting from different drive (Lucid / 10.10). It annoys out of the hell that you can'teven fix manually the prob. unless you remove NM