> 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`
>
Ah nice, here is what upstream has to say about this:
> Already fixed in nm-connection- editor: /git.gnome. org/browse/ network- manager- applet/ commit/ ?id=e8a16438d8e 3696d5e818d48bd 49b9c1f284fd2c /bugzilla. gnome.org/ show_bug. cgi?id= 763937 ***
>
> https:/
>
> 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:/
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`
>