No edit summary |
|||
| Line 29: | Line 29: | ||
* Support for unmanaged devices (see known problems) | * Support for unmanaged devices (see known problems) | ||
* [[Tools/NetworkManager/Integration|Integration with other tools]] | * [[Tools/NetworkManager/Integration|Integration with other tools]] | ||
== Possible future features == | == Possible future features == | ||
| Line 38: | Line 37: | ||
* Event-based IPv6 handling without timers and duplicate processing (would clean logs and make code more robust) | * Event-based IPv6 handling without timers and duplicate processing (would clean logs and make code more robust) | ||
* Exporting list of DNS servers and handing it over to recursive DNS servers like unbound and dnsmasq (especially necessary for proper VPN access) | * Exporting list of DNS servers and handing it over to recursive DNS servers like unbound and dnsmasq (especially necessary for proper VPN access) | ||
* Local caching nameserver with DNSSEC and forwarders | |||
Note: Some of the features described here may have been already available and working at some point of time. | Note: Some of the features described here may have been already available and working at some point of time. | ||
Revision as of 11:55, 24 July 2012
NetworkManager
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.
NetworkManager may only work with network interfaces once the relevant drivers are correctly installed on your system. Reboot your system after installing a new firmware or a new driver in order to ensure that the changes take effect.
Features
- Configuration using keyfile and ifcfg-rh formats
- Good IPv4 support
- Moderate IPv6 support
- Device bonding
- D-Bus interface
- CLI frontends
- GUI frontends
Broken features
- Support for unmanaged devices (see known problems)
- Integration with other tools
Possible future features
- Ethernet Bridging
- Keeping wired devices allways on (for IPv6 link-local networking)
- Support for IPv6 automatic reconfiguration (changing default routes, etc...)
- Event-based IPv6 handling without timers and duplicate processing (would clean logs and make code more robust)
- Exporting list of DNS servers and handing it over to recursive DNS servers like unbound and dnsmasq (especially necessary for proper VPN access)
- Local caching nameserver with DNSSEC and forwarders
Note: Some of the features described here may have been already available and working at some point of time.
More resources:
Known problems
- NetworkManager gets automaticaly respawned, no sane way to temporarily disable it
- List of unmanaged devices (by MAC) is sometimes ignored (hard to reproduce)
- Manually assigned IPv4 addresses get lost (in tens of seconds)
- 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 git, targeting 0.9.6), affecting also IPv4 networking and link
- IPv6 code is still full of workarounds
- Malfunctioning connection 'assume' functionality for IPv4 (removed for IPv6)
- Serious doubts about working integration with network-scripts
- Doesn't work well with dnssec-trigger/unbound/dnsmasq (DNS is not conveyed)
- Missing CLI tools that would be as simple as manual (iproute/wpa_supplicant/wvdial/...) configuration
- Other things work only when in some specific state
- Too many open bug reports, many probably obsolete
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.
Notes
- NetworkManager builds against specific distributions, not tools or dependencies (--with-distro)
About this section of the wiki
Currently most of the information in this page and the Tools/NetworkManager subtree have been added by me (User:Pavlix). Please feel free to add, correct and clarify stuff but please get in touch with me before deleting.
Further Information
- 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