summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* settings: add notification after connections loadfg/fix_beaker_testsFrancesco Giudici2016-04-261-0/+1
|
* settings: disconnect connection_ready_changed() handler when reaching ↵Thomas Haller2016-04-261-2/+12
| | | | | | | | startup_complete We connect to notify::startup-complete signal of each connection, but after we signal startup-complete once, we don't need that signal anymore. Disconnect.
* dns: merge branch 'th/dns-rc-manager-bgo765387'Thomas Haller2016-04-264-154/+151
|\ | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=765387
| * dns: add new rc-manager=unmanagedThomas Haller2016-04-262-1/+6
| | | | | | | | | | | | | | | | | | | | | | The following settings are effectively identical: dns=none,rc-manager=*any* dns=none,rc-manager=unmanaged dns=default,rc-manager=unmanaged The new setting is only there for completeness and only makes sense for a dns plugin.
| * dns: merge the dns "mode" and "rc-manager"Thomas Haller2016-04-263-115/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Already previously, the mode and rc-manager were intertwined in a complicated way: - dns=none effectively disables rc-manager. - if resolv.conf was immutable, it would disable the rc-manager by setting "resolv_conf_mode=NM_DNS_MANAGER_RESOLV_CONF_UNMANAGED". - resolv_conf_mode was anyway a redundant piece of information to rc_manager. Now there are only two relevant settings: priv->plugin and priv->rc_manager. And they can be set independently from each other. Before that was not possible. For example, you could not set a dns plugin with rc-manager=unmanaged (the only way to achive that was via an immutable resolv.conf or by having rc-manager=symlink and let resolv.conf link somewhere else.
| * dns: when clearing "plugin" always disconnect signal handlersThomas Haller2016-04-261-6/+14
| |
| * dns: initialize rc-manager in init_resolv_conf_mode()Thomas Haller2016-04-261-24/+13
| | | | | | | | | | | | | | | | The "dns" and "rc-manager" properties are strongly related. Initialize them together in init_resolv_conf_mode(). One difference is, that we now set rc_manager before setting the mode. But that shouldn't matter.
| * dns: split parsing of rc-manager out of init_resolv_conf_manager()Thomas Haller2016-04-262-25/+51
| | | | | | | | | | Makes more sense in the next commit, when init_resolv_conf_manager() gets merged with init_resolv_conf_mode(). Bear with me.
| * dns: rename "rc-manager=none" to "symlink"Thomas Haller2016-04-263-12/+14
|/ | | | | | We already have "rc-manager=file", rename "rc-manager=none" to "symlink" because that better describes what it is actually doing. Of course, the old name is still accepted.
* device: merge branch 'th/default-wired-connection-stable-uuid-bgo765464'Thomas Haller2016-04-268-104/+163
|\ | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=765464
| * device: generate stable UUID for default-wired-connectionThomas Haller2016-04-262-7/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Generate a stable connection UUID for the default-wired-connection. Otherwise, on every reboot, the UUID changes although the generated connection is the same. But also hash into the UUID the machine-id, the device name and the hardware address. So, the UUID is only the same if the connection is identical in every aspect. Also, the UUID is used as Network_ID for the stable-privacy address generation mode. It is bad to re-create different UUIDs on every boot as it causes different addresses.
| * core: use nm_utils_machine_id_read() in "nm-dhcp-client.c"Thomas Haller2016-04-261-48/+10
| |
| * core: add nm_utils_machine_id_read() and parse() utilThomas Haller2016-04-264-0/+63
| |
| * core: add nm_utils_get_secret_key() utilThomas Haller2016-04-263-49/+69
|/
* linux-platform: re-read the link type if the name changedLubomir Rintel2016-04-261-1/+4
| | | | | | | | | | | | | | | | | For some device types, we use the DEVTYPE from sysfs to determine the link type. However, the way we read from sysfs can race with device renames and we could miss the chance to read DEVTYPE correctly. This doesn't completely fix the sysfs race, but cures the boot-time race with systemd renaming the device while we are initializing the link. We ideally should use GUDev for all sysfs accesses, but that would need some more work for this particular case as currently we need the link type before we have an udev device instance. https://bugzilla.gnome.org/show_bug.cgi?id=764803 Co-Authored-By: Beniamino Galvani <bgalvani@redhat.com>
* dhcp/systemd: actually hook up information-only modeDan Williams2016-04-251-0/+4
| | | | | Fixes: 89d1e466157839096b446068a780cb2563424a5a Tested-by: Celti on IRC
* libnm/doc: fix documentation of NMSettingIP6Config:addr-gen-modeThomas Haller2016-04-251-3/+5
| | | | | The value cannot be unset. It must be set to one of the two currently supported values.
* bluetooth: add a missing GError initializerLubomir Rintel2016-04-251-1/+1
| | | | (cherry picked from commit 3ad7be3e6a124fe9e279ec6d9de06c423ca50cc2)
* settings: merge branch 'th/settings-read-hostname'Thomas Haller2016-04-251-16/+52
|\
| * settings: refactor read_hostname_*()Thomas Haller2016-04-251-20/+16
| |
| * settings: cleanup #if blocks for HOSTNAME_PERSIST_*Thomas Haller2016-04-251-12/+12
| |
| * settings: fix Slackware hostname settingPatrick J. Volkerding2016-04-251-0/+40
|/ | | | https://mail.gnome.org/archives/networkmanager-list/2016-April/msg00075.html
* sleep-monitor-systemd: merge branch 'th/sleep-monitor-sd-cleanup'Thomas Haller2016-04-251-49/+92
|\ | | | | | | Some cleanup of "nm-sleep-monitor-systemd.c"
| * sleep-monitor: disconnect signal handlers from D-Bus proxy on destroyThomas Haller2016-04-251-4/+13
| | | | | | | | | | The lifetime of the proxy is not necesarily the same as the lifetime of the NMSleepMonitor instance. Disconnect the signals during dispose().
| * sleep-monitor: don't localize messages in core daemonThomas Haller2016-04-251-1/+1
| | | | | | | | | | | | The daemon does not run with a particular locale of a user. Localizing makes no sense (at least, we don't do it usually and it would make logging localized).
| * sleep-monitor: properly handle cancelling of "Inhibit" D-Bus callThomas Haller2016-04-251-17/+28
| | | | | | | | | | | | | | | | | | | | As we don't take a reference on @self during the asynchronous request, we must properly support cancelling in case of early destruction. I think, it's gdbus' responsibility not to leak any file descriptors when cancelling a D-Bus request that returns file descriptors. Thus, our usual pattern works here too.
| * sleep-monitor: handle early destruction of NMSleepMonitor instanceThomas Haller2016-04-251-4/+12
| | | | | | | | | | When destroing the sleep monitor before the D-Bus proxy is created, we must cancel creation of the proxy.
| * sleep-monitor: drop unused class methods for signalsThomas Haller2016-04-251-10/+2
| |
| * sleep-monitor: implement dispose() instead of finalize()Thomas Haller2016-04-251-6/+5
| | | | | | | | | | To release resources, dispose() is preferred over finalize() because it is called earlier.
| * sleep-monitor: don't return value from drop_inhibitor()Thomas Haller2016-04-251-4/+2
| |
| * sleep-monitor: use LOG macros in "nm-sleep-monitor-systemd.c"Thomas Haller2016-04-251-11/+37
|/
* lldp: fix crash in nm_device_update_dynamic_ip_setup() due to uninitialized ↵Thomas Haller2016-04-251-1/+1
| | | | | | @error Fixes: 07a9364d9c151bc3086a863759d31d0857ae011e
* libnm/vpn: consider VPN service aliases in nm_vpn_plugin_info_new_search_file()Thomas Haller2016-04-251-4/+14
| | | | Fixes: 4271c9650c1cfcbd487cc471099b1c0c9bbfa290
* tools: add forgotten file to distLubomir Rintel2016-04-231-1/+2
| | | | Fixes: f15c412015647b378a187bdf98ccf8cd75eb0475
* libnm-core: fix compiler warning in nm_vpn_plugin_info_get_auth_dialog()Beniamino Galvani2016-04-221-3/+2
| | | | | | | libnm-core/nm-vpn-plugin-info.c: In function ‘nm_vpn_plugin_info_get_auth_dialog’: shared/gsystem-local-alloc.h:53:46: error: ‘prog_basename’ may be used uninitialized in this function [-Werror=maybe-uninitialized] Fixes: a3f94f451b910bbaf38a172f6bb9a2050a9553e5
* auth: allow failures to read process start_time from /proc/$PID/stat with ↵Thomas Haller2016-04-221-3/+12
| | | | | | | | | | | | | | | | | | | | | | hidepid When mounting /proc with hidepid, we might fail to read the start-time of the process from /proc/$PID/stat. In this case, we should just accept a start-time of zero. On the other side of authentication, polkit should accept a zero start-time too. nm_utils_get_start_time_for_pid() has other uses in NetworkManager, mostly when killing a process from a PIDFILE or during nm_utils_kill_process_sync(). In both these cases, this will only succeed if we try to kill a process that also runs a root. For processes started by the current instance, we don't care about the PIDFILE and use nm_utils_kill_child_?sync() -- so there is no problem with hidepid there. https://bugzilla.gnome.org/show_bug.cgi?id=764502
* libnm/vpn: merge branch 'th/vpn-auth-dialog-bgo765329'Thomas Haller2016-04-225-22/+169
|\ | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=765329
| * libnm/vpn: add nm_vpn_plugin_info_new_search_file()Thomas Haller2016-04-223-15/+77
| |
| * libnm/vpn: add nm_vpn_plugin_info_supports_hints()Thomas Haller2016-04-223-0/+22
| |
| * libnm/vpn: add nm_vpn_plugin_info_get_auth_dialog()Thomas Haller2016-04-224-0/+43
| |
| * libnm/vpn: add nm_vpn_plugin_info_get_service()Thomas Haller2016-04-224-6/+23
| | | | | | | | | | | | | | Re-add nm_vpn_plugin_info_get_service(). This function *is* useful and could be used by nm-applet. This reverts commit 3517084b92aa64817ce8cd82163e5ab6e1947017.
| * libnm/vpn: gracefully handle empty dirname in ↵Thomas Haller2016-04-221-1/+4
|/ | | | | | | _nm_vpn_plugin_info_list_load_dir() No need to assert against an empty dirname. It's not different from any other non-existing directory and we should be graceful about that.
* dhcp: refactor nm_dhcp_client_stop_existing()Thomas Haller2016-04-221-34/+32
|
* core: minor cleanup of nm_utils_get_start_time_for_pid()Thomas Haller2016-04-221-17/+19
| | | | | | And for @out_state, return ' ' instead of '\0' in case of failure. That is more friendly, when the user happens to print the value.
* docs: include the D-Bus enums reference with the API documentationLubomir Rintel2016-04-225-1/+214
| | | | | | Otherwise the types links would be dangling or resolved to slightly irrelevant documentation in libnm or completely irrelevant documentation in libnm-util.
* libnm-core: don't link to NMDevice type from the D-Bus specLubomir Rintel2016-04-221-2/+2
| | | | | | It isn't right in that context -- NMDevice is a libnm-core object, not a bus object. In rendered documentation this would generate a dangling link.
* misc: update maintainers and authorsDan Williams2016-04-212-9/+4
|
* dns: avoid using global "/etc/dnsmasq.conf" config for dnsmasqThomas Haller2016-04-211-0/+1
| | | | | | | | | | | Pass an empty configuration file otherwise dnsmasq loads "/etc/dnsmasq.conf". We already allow for a config.d/ directory "/etc/NetworkManager/dnsmasq.d" to allow the user to overwrite configuration. We don't want to consider the global config file. Fixes: 497a8aa5c6463404200a3fcc745aa65396dc4f22
* dns: merge branch 'th/dnsmasq-dbus-bgo765043'Thomas Haller2016-04-213-139/+308
|\ | | | | | | | | https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00144.html https://bugzilla.gnome.org/show_bug.cgi?id=765043
| * dns: various cleanup for new dnsmasq's D-Bus supportThomas Haller2016-04-214-210/+116
| |
View Lorry Controller Status