forked from progmaticlab/NetworkManager
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
With RHEL 8 the systemd network service will go away. We use it today for creating the vhost0 interface. Replacement will be NetworkManager. RedHat asked us to collaboratively integrate vhost0 mgmt into NM. This will also benefit recent problems we had with OpenShift which also uses NM. Closes-Jira-Bug: CEM-3697
- Loading branch information
Dmitry_Eremeev
committed
Sep 27, 2019
1 parent
2979c89
commit a3e36a4
Showing
47 changed files
with
1,427 additions
and
241 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,85 +1,65 @@ | ||
|
|
||
| ****************** | ||
| 2008-12-11: NetworkManager core daemon has moved to git.freedesktop.org! | ||
|
|
||
| git clone git://git.freedesktop.org/git/NetworkManager/NetworkManager.git | ||
| ****************** | ||
|
|
||
|
|
||
| Networking that Just Works | ||
| -------------------------- | ||
|
|
||
| NetworkManager attempts to keep an active network connection available at all | ||
| times. The point of NetworkManager is to make networking configuration and | ||
| setup as painless and automatic as possible. NetworkManager is intended to | ||
| replace default route, replace other routes, set IP addresses, and in general | ||
| configure networking as NM sees fit (with the possibility of manual override as | ||
| necessary). In effect, the goal of NetworkManager is to make networking Just | ||
| Work with a minimum of user hassle, but still allow customization and a high | ||
| level of manual network control. If you have special needs, we'd like to hear | ||
| about them, but understand that NetworkManager is not intended for every | ||
| use-case. | ||
|
|
||
| NetworkManager will attempt to keep every network device in the system up and | ||
| active, as long as the device is available for use (has a cable plugged in, | ||
| the killswitch isn't turned on, etc). Network connections can be set to | ||
| 'autoconnect', meaning that NetworkManager will make that connection active | ||
| whenever it and the hardware is available. | ||
|
|
||
| "Settings services" store lists of user- or administrator-defined "connections", | ||
| which contain all the settings and parameters required to connect to a specific | ||
| network. NetworkManager will _never_ activate a connection that is not in this | ||
| list, or that the user has not directed NetworkManager to connect to. | ||
|
|
||
|
|
||
| How it works: | ||
|
|
||
| The NetworkManager daemon runs as a privileged service (since it must access | ||
| and control hardware), but provides a D-Bus interface on the system bus to | ||
| allow for fine-grained control of networking. NetworkManager does not store | ||
| connections or settings, it is only the mechanism by which those connections | ||
| are selected and activated. | ||
|
|
||
| To store pre-defined network connections, two separate services, the "system | ||
| settings service" and the "user settings service" store connection information | ||
| and provide these to NetworkManager, also via D-Bus. Each settings service | ||
| can determine how and where it persistently stores the connection information; | ||
| for example, the GNOME applet stores its configuration in GConf, and the system | ||
| settings service stores its config in distro-specific formats, or in a distro- | ||
| agnostic format, depending on user/administrator preference. | ||
|
|
||
| A variety of other system services are used by NetworkManager to provide | ||
| network functionality: wpa_supplicant for wireless connections and 802.1x | ||
| wired connections, pppd for PPP and mobile broadband connections, DHCP clients | ||
| for dynamic IP addressing, dnsmasq for proxy nameserver and DHCP server | ||
| functionality for internet connection sharing, and avahi-autoipd for IPv4 | ||
| link-local addresses. Most communication with these daemons occurs, again, | ||
| via D-Bus. | ||
|
|
||
|
|
||
| Why doesn't my network Just Work? | ||
|
|
||
| Driver problems are the #1 cause of why NetworkManager sometimes fails to | ||
| connect to wireless networks. Often, the driver simply doesn't behave in a | ||
| consistent manner, or is just plain buggy. NetworkManager supports _only_ | ||
| those drivers that are shipped with the upstream Linux kernel, because only | ||
| those drivers can be easily fixed and debugged. ndiswrapper, vendor binary | ||
| drivers, or other out-of-tree drivers may or may not work well with | ||
| NetworkManager, precisely because they have not been vetted and improved by the | ||
| open-source community, and because problems in these drivers usually cannot | ||
| be fixed. | ||
|
|
||
| Sometimes, command-line tools like 'iwconfig' will work, but NetworkManager will | ||
| fail. This is again often due to buggy drivers, because these drivers simply | ||
| aren't expecting the dynamic requests that NetworkManager and wpa_supplicant | ||
| make. Driver bugs should be filed in the bug tracker of the distribution being | ||
| run, since often distributions customize their kernel and drivers. | ||
|
|
||
| Sometimes, it really is NetworkManager's fault. If you think that's the case, | ||
| please file a bug at http://bugzilla.gnome.org and choose the NetworkManager | ||
| component. Attaching the output of /var/log/messages or /var/log/daemon.log | ||
| (wherever your distribution directs syslog's 'daemon' facility output) is often | ||
| very helpful, and (if you can get) a working wpa_supplicant config file helps | ||
| enormously. | ||
|
|
||
| Environment | ||
| -------------- | ||
| RHEL 8.0 | ||
| NetworkManager 1.14.0 | ||
| installed vrouter.ko for running kernel version (unloaded) | ||
| installed vif utility (contrail-vrouter-utils) | ||
|
|
||
| How to build RPMs | ||
| ------------------ | ||
| git clone --single-branch --branch contrail-vrouter https://github.com/progmaticlab/NetworkManager.git | ||
| export PYTHON=python3 | ||
| export NM_RPMBUILD_ARGS="--without=adsl --without=bluetooth --without=wwan --without=team --without=wifi --without=ovs" | ||
| NetworkManager/contrib/fedora/REQUIRED_PACKAGES | ||
| NetworkManager/contrib/fedora/rpm/build.sh | ||
|
|
||
| How to apply Contrail vrouter plugin | ||
| ------------------ | ||
| dnf remove -y NetworkManager-libnm* | ||
| rpm -iv NetworkManager/contrib/fedora/rpm/latest/RPMS/x86_64/NetworkManager-libnm | ||
| rpm -iv NetworkManager/contrib/fedora/rpm/latest/RPMS/x86_64/NetworkManager-1.14.0* | ||
| rpm -iv NetworkManager/contrib/fedora/rpm/latest/RPMS/x86_64/NetworkManager-contrail-1.14* | ||
| systemctl daemon-reload | ||
| systemctl restart NetworkManager | ||
|
|
||
| Usage | ||
| ------- | ||
| nmcli c add type contrail-vrouter physdev enp0s3 conn.interface vhost0 autoconnect no | ||
| nmcli c up contrail-vrouter-vhost0 | ||
| nmcli c down contrail-vrouter-vhost0 | ||
|
|
||
| Troubleshooting | ||
| ---------------- | ||
| To set maximum log level: | ||
| nmcli general logging level TRACE domains ALL | ||
|
|
||
| To get all system logs regarding the component "NetworkManager" for last hour and get new logs in real time (tail -f): | ||
| journalctl -f --no-tail --since "1 hour ago" -u NetworkManager | ||
|
|
||
| To get all system logs regarding the component "NetworkManager" with keyword "CONTRAILl" for last hour and get new logs in real time (tail -f): | ||
| journalctl -f --no-tail -g "CONTRAIL" --since "1 hour ago" -u NetworkManager | ||
|
|
||
| To load vrouter module or get error message if it's already loaded: | ||
| modprobe -v --first-time vrouter | ||
|
|
||
| To unload vrouter module or get error message if it's already unloaded: | ||
| modprobe -rv --first-time vrouter | ||
|
|
||
| To get log level for core component of NetworkManager: | ||
| nmcli general logging | ||
|
|
||
| To get list of network devices (network interfaces): | ||
| nmcli device | ||
|
|
||
| To set debug log level for core component of NetworkManager: | ||
| nmcli g log level DEBUG | ||
|
|
||
| To notify NetworkManager about changes after connection profile was manually changed (/etc/NetworkManager/system-connections/), not by nmcli means | ||
| nmcli connection reload | ||
|
|
||
| To delete all connection profiles with keyword "vhost" in their names (by means of nmcli): | ||
| for i in `nmcli -f NAME c show | grep "vhost"`; do nmcli c del $i; done | ||
|
|
||
| To delete all connection profiles with keyword "contrail" in their names (manual deleting, not by nmcli means): | ||
| rm -rf /etc/NetworkManager/system-connections/contrail* | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.