DHCP settings for network manager shared connection are hard-coded source, should be editable

[John Thompson]

1) Ubuntu 10.04, but it's in all versions.
2) any version of network manager
3) I want to be able to change the DHCP settings for a shared network connection
4) YOUR OPERATING SYSTEM WON'T LET ME!

The file nm-device.c contains this line:

nm-device.c: guint32 start = (guint32) ntohl (0x0a2a2b01); /* 10.42.43.1 */

hard-coding DHCP settings that should obviously be editable by the user is a TERRIBLE IDEA. PLEASE FIX.

[Thomas Hood (jdthood)]

It's true. Looking at current NM src/nm-device.c line 1978:

  static guint32
  reserve_shared_ip (void)
  {
 guint32 start = (guint32) ntohl (0x0a2a0001); /* 10.42.0.1 */
 guint32 count = 0;

This is upstream source code. Please file a bug report upstream.

    https://bugzilla.gnome.org/browse.cgi?product=NetworkManager

[Thomas Hood (jdthood)]

To reduce administration, closed the report in Launchpad.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Raul (raulrm)]

Other DHCP settings are fixed in code also. By example DHCP_TIMEOUT is fixed to 45 seconds. Terminals gaining ip leases thru radio links or vpn's aren't able to work with such short timeout.

[ggallozz (ggallozz-gmail)]

... and since 2013 nothing has gone further ?! :(

[sdaau (sd-imi)]

Ok, re-posted this bug upstream, at:

  Bug 777313 - DHCP settings for network manager shared connection are hard-coded source, should be editable
  https://bugzilla.gnome.org/show_bug.cgi?id=777313

[sdaau (sd-imi)]

Ah nice, here is what upstream has to say about this:

> Already fixed in nm-connection-editor:
>
> https://git.gnome.org/browse/network-manager-applet/commit/?id=e8a16438d8e3696d5e818d48bd49b9c1f284fd2c
>
> Note that before this commit it was already possible to manually modify the connection address using nmcli or editing the connection file to also change the DHCP pool served to clients.
>
> *** This bug has been marked as a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=763937 ***

The manual setting trick, from https://bugzilla.gnome.org/show_bug.cgi?id=763937 :

> Yes, that is a limitation in nm-connection-editor, which should probably be fixed. Which also means, it's non-obvious to the user that the range is configurable.
>
>
> Try for example:
>
> nmcli connection modify $CONNECTION_ID +ipv4.addresses 192.168.5.1/24
>
> where you can find $CONNECTION_ID via `nmcli connection show`
> Afterwards, verify with `nmcli connection show $CONNECTION_ID`
>

[Lucas Magasweran (lucasrangit)]

This has been fixed and merged upstream in nm-applet/network-manager 1.4.2.

https://bugzilla.gnome.org/show_bug.cgi?id=763937#c14

Ubuntu 17.04 has 1.4.4. Is it possible to backport this to 16.04 LTS?