summaryrefslogtreecommitdiff
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* all: add support for thunderbolt networkingChristian Kellner2018-04-192-1/+15
| | | | | | | | | | Load the thunderbolt-net module if we see a host-to-host connection and configure the resulting ethernet connection automatically to be a link-local only one. The latter is done by setting a new udev property "NM_AUTO_DEFAULT_LINK_LOCAL_ONLY" which is picked up when we configure the connection for the device. https://github.com/NetworkManager/NetworkManager/pull/97
* systemd: make enablement of n-m-wait-online.service follow n-m.serviceAlan Jenkins2018-03-141-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | This is the approach used by systemd-networkd. I don't understand the logic that caused systemd-networkd to make the change - https://github.com/systemd/systemd/commit/9e49656037717b96c06b1f1507a41550bdb2c795 Instead, I am suggesting it for consistency, and because it seems to me this is the exact correct behaviour. Because if you enable NetworkManager, and rely on it to configure your network devices, then network mounts will not start correctly at boot time unless you also enable NetworkManager-wait-online.service. Enabling NetworkManager-wait-online.service does not cause unnecessary serialization of the boot process; it is only pulled in if something else (like a network mount) pulls in network-online.target. I am suggesting this in response to reading this user support request [1]. [1] https://unix.stackexchange.com/questions/429604/fstab-not-automatically-mounting-smb-storage [thaller@redhat.com: reworded commit message] https://github.com/NetworkManager/NetworkManager/pull/76
* build: add initial support for meson build systemIñigo Martínez2017-12-131-0/+79
| | | | | | | | | | meson is a build system focused on speed an ease of use, which helps speeding up the software development. This patch adds meson support along autotools. [thaller@redhat.com: rebased patch and adjusted for iwd support] https://mail.gnome.org/archives/networkmanager-list/2017-December/msg00022.html
* systemd: let "NetworkManager-wait-online.service" require ↵Thomas Haller2017-11-021-1/+1
| | | | | | | | | | | | | | | | | | | | "NetworkManager.service" `systemctl start network-online.target` should suffice to start "NetworkManager.service". That would work because - "network-online.target" has "Wants=NetworkManager-wait-online.service" - "NetworkManager-wait-online.service" has "Require=NetworkManager.service". But previously, "NetworkManager-wait-online.service" would just fail with missing dependency. See also https://github.com/systemd/systemd/pull/6065 which does the same for networkd's wait-online serice, and see rh#1452866 for a use-case. Related: https://bugzilla.redhat.com/show_bug.cgi?id=1452866
* device: add support for OpenVSwitch devicesLubomir Rintel2017-10-301-0/+2
|
* manager: add connectivity-check-{available,enabled} properties.James Henstridge2017-08-171-0/+9
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=785117
* systemd: update service unit file to use dbus-send for ExecReloadThomas Haller2017-06-071-2/+2
| | | | | instead of `kill -HUP`. We support "org.freedesktop.NetworkManager.Reload" D-Bus method for a long time now. Use it because it is synchronous.
* all: fix typos in documentation and commentsYuri Chornoivan2017-03-171-1/+1
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=780199 [thaller@redhat.com: reworded commit message]
* build: move policy file from "policy/" to "data/"Thomas Haller2016-11-031-0/+155
|
* build: merge "data/Makefile.am" into toplevel MakefileThomas Haller2016-10-211-71/+0
|
* doc: add comment to systemd's NetworkManager.service about ibft requiring ↵Thomas Haller2016-09-021-0/+4
| | | | | | | | | | CAP_SYS_ADMIN We don't want to enable this upstream, but make the requirement more discoverable by documenting it and put a comment to NetworkManager.service. https://bugzilla.redhat.com/show_bug.cgi?id=1371201
* systemd: add Documentation to service filesMichael Biebl2016-06-023-0/+3
| | | | | | | | | Reference the nm-online and NetworkManager man page in the corresponding service files. https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Documentation= https://bugzilla.gnome.org/show_bug.cgi?id=767168
* systemd: use RemainAfterExit=yes for NetworkManager-wait-online.serviceMichael Biebl2016-06-022-0/+2
| | | | | | | | | | | RemainAfterExit=yes is typically used for Type=oneshot services. systemd-networkd-wait-online.service uses it, so we should as well. See https://www.freedesktop.org/software/systemd/man/systemd.service.html#RemainAfterExit= https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type= https://bugzilla.gnome.org/show_bug.cgi?id=767170
* manager: add Reload() D-Bus commandThomas Haller2016-06-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new Reload D-Bus command to reload NetworkManager configuration. For now, this is like sending SIGHUP to the process. There are several advantages here: - it is guarded via PolicyKit authentication while signals can only be sent by root. - the user can wait for the reload to be complete instead of sending an asynchronous signal. For now, we operation completes after nm_config_reload() returns, but later we could delay the response further until specific parts are fully reloaded. - SIGHUP reloads everything including re-reading configuration from disk while SIGUSR1 reloads just certain parts such as writing out DNS configuration anew. Now, the Reload command has a flags argument which is more granular in selecting parts which are to be reloaded. For example, via signals the user can: 1) send SIGUSR1: this writes out the DNS configuration to resolv.conf and possibly reloads other parts without re-reading configuration and without restarting the DNS plugin. 2) send SIGHUP: this reloads configuration from disk, writes out resolv.conf and restarts the DNS plugin. There is no way, to only restart the DNS plugin without also reloading everything else.
* systemd: order NetworkManager.serivce after network-pre.targetThomas Haller2016-01-231-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=761001
* systemd: add chroot capabilityLubomir Rintel2016-01-221-1/+1
| | | | CAP_SYS_CHROOT is needed for openvpn hardening.
* linux-platform: treat gadget devices as ethernet devicesLubomir Rintel2016-01-211-0/+5
| | | | | Also, don't manage them by default. Whatver created it should take care of management.
* systemd: add "After=dbus.service" to NetworkManager.serviceThomas Haller2016-01-211-0/+1
| | | | | | | | | Order NetworkManager after dbus. Otherwise during shutdown, both service are killed together and possibly NetworkManager can no longer use D-Bus during shutdown. It will need it however to communicate with VPN plugins and wpa-supplicant. Related: https://bugs.freedesktop.org/show_bug.cgi?id=89847#c14 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1214466
* systemd: stop blocking network.target in NetworkManager-wait-online.serviceMartin Pitt2015-10-301-2/+1
| | | | | | | | | | | | network.target is a very early boot target which basically says "I can start opening sockets now". It has nothing to do with being connected to the internet and is often required by early boot services as well. Drop the unnecessary and wrong Wants=/Before=network.target to avoid dependency cycles and boot delays. https://bugzilla.gnome.org/show_bug.cgi?id=746039 https://launchpad.net/1430280
* systemd: install NetworkManager-wait-online.service into network-online.targetMartin Pitt2015-10-301-1/+1
| | | | | | | | This unit "implements" network-online.target, which is fairly independent from multi-user.target, so specify the correct install target. https://bugzilla.gnome.org/show_bug.cgi?id=746039 https://launchpad.net/1430280
* systemd: grant the daemon a license to kill kidsLubomir Rintel2015-10-081-1/+1
| | | | | It's for their own good. Otherwise stale dnsmasq instances haunt the shared connections.
* Split out the bits which determine ID_NET_DRIVER or DRIVERS into separate ↵Michael Biebl2015-08-313-7/+15
| | | | | | | | | udev rules file Those are not required with systemd-udevd v210 or newer. This way distros which have a new enough version of udev can skip installing 84-nm-drivers.rules. While at it, don't use absolute paths for sed and ethtool.
* udev-rules: avoid ifname shell expansionLubomir Rintel2015-08-191-1/+1
|
* udev-rules: one less useless use of catLubomir Rintel2015-08-181-2/+2
|
* udev-rules: only invoke ethtool for existing interfacesBeniamino Galvani2015-08-181-0/+1
| | | | | ethtool may cause the auto-loading of a kernel module for non-existing interface-names. Avoid that by checking whether such an interface exists.
* Revert "udev-rules: only invoke ethtool for existing interfaces"Lubomir Rintel2015-08-181-1/+1
| | | | | | | This reverts commit 44fee0f6fff42773aa73a9a46220db697907751f. Bad quoting here. Also, this is not quite the best fix for the issue, filtering on ACTION=="add" is probably a bit more elegant.
* udev-rules: only invoke ethtool for existing interfacesBeniamino Galvani2015-08-111-1/+1
| | | | | | | ethtool may cause the auto-loading of a kernel module for non-existing interface-names. Avoid that by checking whether such an interface exists. This is inherently racy.
* systemd: require CAP_AUDIT_WRITE for NetworkManager serviceBeniamino Galvani2015-08-041-1/+1
| | | | We need it to write messages to kernel auditing log.
* service: harden the NetworkManager service a bitlr/systemd-hardenedLubomir Rintel2015-07-011-0/+3
| | | | | | Tested with dnsmasq (ipv4.method=shared), openvpn & vpnc. https://bugzilla.gnome.org/show_bug.cgi?id=750598
* platform: don't use udev for link type determinationDan Williams2015-05-012-9/+1
| | | | | This allows us to always announce links when the kernel advertises them, instead of waiting for udev.
* systemd: make NetworkManager reloadable via SIGHUPThomas Haller2015-04-171-0/+1
| | | | | | | | | | | | | Since f9e4af2, parts of the configuration can be reloaded by sending SIGHUP to NetworkManager. Add ExecReload option to service file to support reloading by sending a signal. Note that 'man 5 systemd.service' advices to use a blocking command instead of a sending a signal. Later we should add a D-Bus method to allow reloading synchronously. For now, this is better then nothing. https://mail.gnome.org/archives/networkmanager-list/2015-April/msg00042.html
* data: move OLPC MESH udev rules away from calloutsLubomir Rintel2015-03-232-1/+10
| | | | | | | No idea why was it there in the first place. This also fixes a bug that the rules file was conditionally included in dist depending on presence of udev dir at configure time.
* data: add udev rules to make emulated ethernet devices default unmanagedLubomir Rintel2015-03-232-0/+40
| | | | | | | | | There are some out-of-tree drivers that create devices masquerading as ethernets which are supposed to use their own management tools. Avoid touching them. The rules should be run after 80-net-setup-link.rules, so that the ID_NET_DRIVER is set.
* core: tell systemd to restart NetworkManager.service if it exited with ↵Mikko Rapeli2014-12-161-0/+1
| | | | | | | | | | failure (bgo #741587) Crashed NetworkManager.service was not restarted by systemd. Signed-off-by: Mikko Rapeli <mikko.rapeli@iki.fi> https://bugzilla.gnome.org/show_bug.cgi?id=741587
* dispatcher: rename executable to 'nm-dispatcher'Dan Williams2014-06-061-1/+1
|
* build: fix installing network-online.target for existing linkThomas Haller2014-06-021-1/+1
| | | | | | | | | | | | | | | | When reinstalling NM on the same location, it would fail with Making install in data make[1]: Entering directory `/home/data/src/NetworkManager/data' make[2]: Entering directory `/home/data/src/NetworkManager/data' install -d /opt/test/lib/systemd/system/network-online.target.wants ln -s /opt/test/lib/systemd/system/NetworkManager-wait-online.service /opt/test/lib/systemd/system/network-online.target.wants ln: failed to create symbolic link ‘/opt/test/lib/systemd/system/network-online.target.wants/NetworkManager-wait-online.service’: File exists make[2]: *** [install-exec-local] Error 1 https://bugzilla.gnome.org/show_bug.cgi?id=728965 Signed-off-by: Thomas Haller <thaller@redhat.com>
* implement systemd network-online.target properly (bgo #728965)Pavel Šimerda2014-05-301-0/+4
| | | | | | | | | | | | | | | Make network-online.target depend on NetworkManager-wait-online.service just as is done in Fedora. This makes network-online.target work with NetworkManager as described in systemd documentation. An alternative way would be to use a combination of setting Install.WantedBy to network-online.target and enabling the service by default. This alternative approach is currently used by systemd-networkd. https://bugzilla.gnome.org/show_bug.cgi?id=728965 Acked-By: Dan Williams <dcbw@redhat.com>
* dispatcher: tell systemd to not kill dispatcher childrenDan Winship2014-04-181-0/+4
| | | | | | | | You're supposed to be able to use dispatcher scripts to spawn long-running processes, but currently systemd will kill them when nm-dispatcher exits. Fix that. https://bugzilla.gnome.org/show_bug.cgi?id=725492
* systemd: update NetworkManager-wait-online.service to wait for startupJiří Klimeš2014-03-312-2/+2
|
* systemd: add "Before=network.service" on Fedora/RHEL (rh #1034983)Dan Winship2013-12-172-2/+3
| | | | | | On Fedora/RHEL, NetworkManager.service needs to be started before network.service, or else network.service may try to bring up NM's devices itself.
* systemd: fix up dispatcher unit install (rh #948433)Dan Williams2013-08-062-1/+1
| | | | | | | | | | | | | Lennart sez: "Oh, I wasn't aware it is short-lived only. In that case, drop the multi-user.target bit, and just make it create the dbus alias. [Install] Alias=dbus-org.freedesktop.nm-dispatcher.service And yeah, adding Also=NetworkManager-dispatcher.service to NetworkManager.service certainly would be a good idea."
* core: change the rules for ignore-carrierDan Winship2013-07-221-1/+1
| | | | | | | The previous ignore-carrier rules did not work well with dynamic IP (dhcp/slaac) connections. Change the rule so that only static IP connections can be activated when carrier is not present (but both static and dynamic connections will remain up when carrier is lost).
* server.conf: We're no longer a sample, reword introductionColin Walters2013-07-221-3/+4
| | | | Now we actually change configuration, explain that better.
* Merge some comments from server.conf into "man NetworkManager.conf"Colin Walters2013-07-221-35/+9
| | | | | The latter should have the full+canonical description, and the config file comments should be very brief, and link to it for more info.
* server.conf: Remove dns=none exampleColin Walters2013-07-221-12/+0
| | | | | This is covered in the manpage adequately, and we want this file to be actual options now, not just commented out ones.
* core: make monitor-connection-files be false by defaultDan Winship2013-07-221-9/+0
|
* core: add monitor-connection-files=false and ReloadConnectionsDan Winship2013-06-141-0/+9
| | | | | | | | | Add a "monitor-connection-files" config option, which can be set to "false" to disable automatic reloading of connections on file change. To go with this, add a new ReloadConnections method on o.fd.NM.Settings that can be used to manually reload connections, and add an nm-cli command to call it.
* systemd: update for network-online.target for systemd >= 200 (rh #787314)Dan Williams2013-06-034-4/+21
| | | | | | | systemd's new network-online target abstracts the "wait until networking is up" stuff, and NM-wait-online implements that functionality. Thus NM-wait-online should be ordered before (and thus be a dependency of) network-online.
* systemd: add service for dispatcher (rh #948433)Dan Williams2013-06-032-2/+21
|
* main: add --debug, fix logging under systemdDan Winship2013-05-211-4/+0
| | | | | | | | | | | | | | | When run with --no-daemon, NM used to duplicate all syslog output to stderr, for ease of debugging. But this meant it had to tell systemd to ignore stderr, so you wouldn't get duplicated log entries. But that meant we lost error messages that didn't go through nm_log. (eg, g_warning()s and g_return_if_fail()s). Fix this by making --no-daemon no longer duplicate syslog output to stderr, and removing the "StandardError=null" from the systemd service file. To get the old behavior, you can use --debug instead of --no-daemon. https://bugzilla.gnome.org/show_bug.cgi?id=700550
View Lorry Controller Status