Desktops and laptops
NetworkManager provides automatic network detection and configuration for the system. Once enabled, the NetworkManager service also monitors the network interfaces, and may automatically switch to the best connection at any given time. Applications that include NetworkManager support may automatically switch between on-line and off-line modes when the system gains or loses network connectivity.
These facilities are most useful for modern laptops, where the user may move between wireless networks, and plug in to a variety of wired networks, but NetworkManager also provides features that are relevant to workstations. Current versions of NetworkManager support modem connections, and certain types of VPN. Development of these features is ongoing.
NetworkManager requires Fedora to have drivers for the wired and wireless interfaces on the computer. Many manufacturers of modems and wireless devices provide limited support for Linux. You may need to install additional drivers or firmware on your Fedora system in order to activate these interfaces.
Fedora now by default relies on NetworkManager for network configuration. This is the case also for minimal installations and server installations. We are trying to make NetworkManager as suitable for this task as possible. You can file bug reports and feature requests at http://bugzilla.gnome.org/ or, if they are related to interoperability with the rest of the system, http://bugzilla.redhat.com/.
Upcoming release of NetworkManager will enhance the command-line tools and make server/enterprise capabilities more robust and less surprising. Some demos of upcoming capabilities are:
- creating a bridge with nmcli
- creating a bridge with nm-connection-editor
- virtual interfaces and Wi-Fi with nmcli
You can also find many configuration examples on this wiki, just follow internal links about NetworkManager features.
NM is slowly changing from a desktop network connection configurator to a universal network configuration software that could be used as a part of the base system.
- Provide core network configuration features
- Expose the features through on-disk text-based configuration
- Expose the features through D-Bus API
- Provide basic CLI and GUI (other CLI/GUI frontends can be built on top of NetworkManager)
The current version of NetworkManager is Fedora 17 is 0.9.4. Some of the features below may not be available there. The current version of upstream NetworkManager is 0.9.6 and the development version is 0.9.7 and is included in branched Fedora 18.
Only features that can be considered fully working belong here.
- Configuration using keyfile and ifcfg-rh formats (other formats are used with other distributions)
- CLI frontend
- GUI frontend
- Good IPv4 support (static and automatic configuration)
- D-Bus interface
- Local caching nameserver (dnsmasq)
- Ethernet connections (802.3)
- WiFi connections (802.11)
- VPN plugin interface
- Mobile broadband via USB or bluetooth
- WiMAX connections (802.16)
- Bluetooth (tested with mobile DUN but that may be a different story)
- OLPC Mesh
Only features that work reasonably well for everyday use belong here.
- Basic IPv6 support (broken reconfiguration, excessively many interaction with the kernel causing log bloat)
Features that fail even with the most casual use belong here.
- Bonding – devices won't join (nor automatically, nor manually) [TODO test 0.9.8.2]
- Integration with other tools
- Connection 'assume', bad for IPv4, none for IPv6 (breaks IPv4 in dualstack networks)
- dispatcher.d – problems after wake up
- VLAN (it reportedly doesn't start automatically) [TODO test 0.9.8.2]
Note that there are huge improvements in git master which will eventually reach Fedora and will be published as NetworkManager 0.9.10.
Possible future features
- Ethernet Bridging – there is a feature branch, but devices won't automatically join [TODO test 0.9.8.2]
- Keeping wired devices always on (for IPv6 link-local networking)
- Support for IPv6 automatic reconfiguration (changing default routes, etc...) [in git master, for 0.9.10]
- Event-based IPv6 handling without timers and duplicate processing (would clean logs and make code more robust) [in git master, for 0.9.10]
- Exporting list of DNS servers and handing it over to recursive DNS servers like unbound and dnsmasq (especially necessary for proper VPN access) [WIP]
- Local caching nameserver with DNSSEC and forwarders [WIP]
- Support for networking on manually created interfaces (e.g. bridges) [WIP]
- Support for easy temporary connection setup through CLI, D-Bus and GUI [WIP]
- Support for making (the above) temporary connections permanent [WIP]
- It should be possible to configure NetworkManager not to manage any devices by default (each device managed only by explicit configuration), cmdline switch might be handy [WIP]
- NetworkManager should probably log external IPv4/IPv6 address/routing changes, as well as bridge configuration changes [WIP]
- NetworkManager should have an option to clean up any stuff created by itself (bridge/bond devices, addresses, etc) [WIP]
Note: Some of the features described here may have been already available and working at some point of time.
Community feature requests (mostly from bugzilla)
- Automatically connect VPN for a physical connection
- Implement (wireless) connections priority
- Automatically reconnect dropped VPN
- Simultaneous VPN connections
- Captive portal authentication
- IPv6 connection sharing
- Importing various VPN configuration formats
- NetworkManager gets automaticaly respawned in F17, no sane way to temporarily disable it
- dhclient left over upon exist and spawned duplicately (also dhclient's check failes when permision denied when writing pidfile)
- Serious IPv6 problems (some of fixed in 0.9.6), affecting also IPv4 networking and link [reworked in master, for 0.9.10]
- IPv6 code is still full of workarounds [reworked in master, for 0.9.10]
- Malfunctioning connection 'assume' functionality for IPv4 (removed for IPv6)
- NetworkManager's dispatcher fails to call scripts at resume
- NM writes to its own configuration file [WIP]
- Desktop: NM GUIs keep asking for wifi passwords [TODO re-test]
- NetworkManager features are not currently implemented with testability in mind [WIP]
- NM won't sometimes set custom MAC address
- nmcli is essentially lame and its syntax and output is inconsistent (e.g. true/false versus yes/no) [WIP]
Note: some of the problems are deep in the core of NetworkManager. It can be expected that more problems will emerge over time or while fixing the currently known ones. https://bugzilla.redhat.com/show_bug.cgi?id=815243
- List of unmanaged devices (by MAC) is sometimes ignored
- Manually assigned IPv4 addresses get lost (in tens of seconds)
- Serious doubts about working integration with network-scripts
- Doubts about overall robustness of NM behavior in non-standard situations
- Doubts about *local* NetworkManager security (polkit rules would deserve some auditing)
Steps to 100% reproduce those are unknown, any help appreciated.
- NetworkManager builds against specific distributions, not tools or dependencies (--with-distro) [fixed in 0.9.8]
- Networking – the starting point for those who seek network-related information on Fedora Wiki
- Refer to the System Administrator's Guide here: Fedora Documentation
- Red Hat Magazine article on NetworkManager : Good summary of the technology
- The NetworkManager Website
- The NetworkManager mailing list
- Local Caching Nameserver
Imported ovpn file does not work
When you add your VPN connection (for OpenVPN for example) by using Import from file… (with an
ovpn file (created by a pfSense OpenVPN server instance) for example) at Settings -> Network -> VPN -> + Tools/NetworkManager is used to handle that connection for you. But maybe this does not work as expected. As an alternative you can try to use the pure client (for OpenVPN).
connect to your VPN (OpenVPN) by running
openvpn with your server created client config file (ovpn file format)
- In the example we are using a file pfSense-UDP-1194-admin-config.ovpn that was downloaded in the Downloads folder of your home directory.
- In the example we are using a file pfSense-UDP-1194-admin-config.ovpn that was created on a pfSense system. It was created to connect to the on the system running OpenVPN server (for the default protocol UDP for OpenVPN, for the default port 1194 for OpenVPN, for the default user admin for pfSense).
sudo openvpn ~/Downloads/pfSense-UDP-1194-admin-config.ovpn