NetworkManager/clients
Dan Winship 29ed625fea tui: fix gateway editing
Since adding NMSettingIPConfig:gateway, we were just binding that
property to the Gateway entry as a string. But this caused two
different problems: first, we were trying to set the :gateway property
from the entry even when the IP address in the entry was incomplete
(causing warnings), and second, we were no longer enforcing the rule
that the gateway can only be set when there are static addresses
configured.

Fix this by adding back nm_editor_bind_ip_gateway_to_string(), but
with new semantics reflecting the new way NMSettingIPConfig:addresses
and :gateway work. (Besides just fixing the new bugs, this also makes
the Gateway entry insensitive when there are no addresses; before,
nmtui would allow you to type there, but the value would not be
saved.)

Fixes: Test263_nmtui_ipv4_addresses_delete_ip_and_back_to_auto

https://bugzilla.gnome.org/show_bug.cgi?id=740017
2014-11-12 16:04:59 -05:00
..
cli clients: only handle secret requests for connection being explicitly activated 2014-11-12 13:41:49 +01:00
common clients: only handle secret requests for connection being explicitly activated 2014-11-12 13:41:49 +01:00
tui tui: fix gateway editing 2014-11-12 16:04:59 -05:00
Makefile.am libnm: port to GDBus 2014-09-18 11:51:09 -04:00
nm-online.c libnm: synchronize NMClient and NMRemoteSettings "is NM running" properties 2014-08-07 15:43:43 -04:00