From Fedora Project Wiki

mNo edit summary
 
(40 intermediate revisions by 3 users not shown)
Line 4: Line 4:
infrastructure.
infrastructure.


=== Networking concepts and configuration ===
TODO: Move any QA related information to [[QA/Networking]].


* [[Networking/Ethernet|Ethernet]]
== Current topics ==
* [[Networking/Addressing|Addressing]]
* [[Networking/Routing|Routing]]
* [[Networking/Bridging|Bridging]]
* [[Networking/Teaming|Bonding / Teaming]]
* [[Networking/NAT|TCP, UDP and ICMP NAT]]
* [[Networking/Traffic control|Traffic control]]
* [[Networking/Tunneling|Tunneling]]
* [[Networking/NameResolution|Name Resolution]]
* [[Networking/Dependencies|Network connectivity dependencies]]


=== Most prominent projects involved in linux networking ===
* [[Networking/TODO|Fedora Networking TODO List]]


* Kernel
== Networking concepts and configuration ==
* GLIBC
* [[Tools/NetworkManager/IPv6|NetworkManager]]
* ISC DHCP


=== Notable networking problems ===
Connectivity:


Only platform bugs that can influence various application and/or the overall behavior of the system belong here.
* [[/Ethernet|Ethernet]]
* [[/Addressing|Addressing]]
* [[/Routing|Routing]]
* [[/Bridging|Bridging]]
* [[/VLAN|VLAN]]
* [[/Bonding|Bonding]] / [[Networking/Teaming|Teaming]]
* [[/Tunneling|Tunneling]]


==== Kernel ====
User experience:


* Bridge: Adding first interface after setting MAC address changes the MAC address
* [[/Hostname|Hostname]]
* IPv4: Kernel can't store DHCP lifetime and cannot mark IPv6 addresses dynamic (in the DHCP sense)
* [[/NameResolution|Name Resolution]], [[Networking/NameResolution/DNS|DNS]], [[Networking/NameResolution/DNSSEC|DNSSEC]]
* IPv6: Kernel ignores RA router preference
* [[/LaptopAndDesktop|Laptop and desktop configuration]]
* IPv6: Tempaddr cycling breaks TCP connections prematurely
* [[/ServerSoftware|Server software operations]]
* IPv6: Kernel doesn't cache RDNSS and DNSSL
* [[/ClientSoftware|Client software operations]]
* IPv6: Kernel doesn't provide default route information when defrtr is disabled
* IPv6: Kernel doesn't provide prefix route information when pinfo is disabled


==== libnl ====
Black magic:


* rtnl_link_bond_add() succeeds when device already exists
* [[/NAT|TCP, UDP and ICMP NAT]]
* rtnl_link_bridge_add() and rtnl_link_vlan_add missing
* [[/Traffic control|Traffic control]]
* [[/Dependencies|Network connectivity dependencies]]


==== iproute ====
== Important networking projects ==


* iproute won't distinguish bridges and bonds
* Kernel
* iproute won't show vlan id
* GLIBC
 
* [[Tools/NetworkManager/IPv6|NetworkManager]]
==== GLIBC ====
* ISC DHCP
 
* IPv4: [http://bugzilla.redhat.com/show_bug.cgi?id=721350 getaddrinfo(127.0.0.1, AI_ADDRCONFIG) fails on hosts without global IPv4 (e.g. notebooks not connected to any networks)]
* IPv6: [http://bugzilla.redhat.com/show_bug.cgi?id=808147 getaddrinfo(::1, AI_ADDRCONFIG) fails on hosts without any other IPv6 address]
* IPv6: getaddrinfo(link-local-address, AI_ADDRCONFIG) fails on hosts without global IPv6 (hopefully solved)
* IPv6: [http://bugzilla.redhat.com/show_bug.cgi?id=843054 GLIBC's nsswitch doesn't support overriding <code>getaddrinfo</code> which is requred to resolve link-local IPv6 addresses]
* DNS: [http://sourceware.org/bugzilla/show_bug.cgi?id=2099 <code>getaddrinfo</code> doesn't support SRV records]
 
[http://fedoraproject.org/wiki/Networking/NameResolution#Flag_AI_ADDRCONFIG_considered_harmful More information about AI_ADDRCONFIG problems]
 
==== dhclient ====
 
* Fixed: [http://bugzilla.redhat.com/show_bug.cgi?id=662254 <code>dhclient</code> fails with large values of dhcp-renawal-time, notably the infinity (0xffffffff) value]
* People say that dhclient exchange is slow, especially on wireless (I can't reproduce)
 
==== Avahi ====
 
* [http://bugzilla.redhat.com/show_bug.cgi?id=719178 Avahi's ''nss-mdns'' returns link-local IPv6 addresses ''without'' scope_id and applications fail to connect]
* [http://bugzilla.redhat.com/show_bug.cgi?id=821127 Avahi's IPv6 support is disabled by default (this has been resolved in the past)]
 
==== NetworkManager ====
 
* Various bugs in [[Tools/NetworkManager|NetworkManager]]
 
==== Testing tools ====


* ping doesn't support IPv6 (you have to use ping6)
== Known networking bugs ==
* netstat and ss won't mark non-v6only sockets


==== Various applications ====
I moved all the information about known networking bugs to a separate article: [[Networking/Bugs|Known networking bugs]]


* Assume that <code>getaddrinfo()</code> returns only one address and/or that such the first returned address works. See [[Networking/NameResolution]].
== Pieces of the puzzle ==
 
==== Network related standards ====
 
* RFC 6106 (RA DNS): [http://tools.ietf.org/html/draft-gont-6man-slaac-dns-config-issues-00 Relies on a false assuption that every (even multicast) IP packet is delivered to its destination.]
* RFC 4861 (NDP): Doesn't specify how zero lifetimes should be used and lets implementations rely on the same false assumption.
* RFC 3493 (socket interfce): Breaks both IPv4 and IPv6 localhost and link-local networking depending on available global addresses.
* POSIX.1-2008: [https://bugzilla.redhat.com/show_bug.cgi?id=721350#c8 Defines the AI_ADDRCONFIG in a bad way]
 
=== Peaces of the puzzle ===


* Interface for static IPv4 and IPv6 configuration (kernel)
* Interface for static IPv4 and IPv6 configuration (kernel)
Line 108: Line 67:
most of the stuff yourself. Virtually all linux distributions now converge to network solutions based on network
most of the stuff yourself. Virtually all linux distributions now converge to network solutions based on network
configuration daemons.
configuration daemons.


Examples of such daemons (without feature comparison):
Examples of such daemons (without feature comparison):
Line 118: Line 76:
* netcfg (Archlinux)
* netcfg (Archlinux)
* wicked
* wicked
* systemd-networkd
* pyroute2 (?)


Yeah, it's a lot of fun writing new and new network configuration daemons.
Yeah, it's a lot of fun writing new and new network configuration daemons.


=== Features to be proposed at some point of time ===
== Fedora feature pages ==


* [[Features/DualstackNetworking]]
=== F20 ===
* [[Features/ZeroconfNetworking]]
 
* [[Features/NetworkManagerBridging]]
* [[Features/NetworkManagerBonding]]
* [[Features/NetworkManagerBonding]]
* [[Features/NetworkManagerBridging]]
* [[Features/NetworkManagerCLIAddConnection]]
* [[Features/FixNetworkNameResolution]]
* [[Features/NetworkManagerNameBasedConfiguration]]
 
=== Unknown ===
 
* [[Features/NetworkManagerAdvancedIPv6]]
* [[Features/NetworkManagerAdvancedIPv6]]
* [[Features/NetworkManagerCLIAddConnection]]
* [[Features/DualstackNetworkTestingTools]]
* [[Features/ZeroconfNetworking]]
* [[Features/NetworkManagerRuntimeConfigurationAPI]]
* [[Features/NetworkManagerForInitramfs]]
* [[Features/NetworkManagerTestSuites]]
* [[Features/NetworkManagerTeaming]]
 
== Testing ==
 
* [[QA/IPv6|IPv6]]


=== Contacts ===
== Contacts ==


Name: [[User:pavlix|Pavel Šimerda]]
* Name: [[User:pavlix|Pavel Šimerda]]
Email: psimerda@redhat.com
* Email: psimerda@redhat.com, pavlix@pavlix.net
IRC: pavlix, #nm at freenode
* IRC: pavlix, #nm at freenode


Use the above contacts or [[Talk:Networking]] for discussions about
Use the above contacts or [[Talk:Networking]] for discussions about
Line 140: Line 115:
to the contacts if you want to help me maintaining this set of
to the contacts if you want to help me maintaining this set of
information resources.
information resources.
----
[[category:Networking| ]]

Latest revision as of 21:31, 26 April 2020

Networking features are nowadays important for virtually all users of Fedora and other linux distributions. Fedora's main network use cases are laptops, desktops, servers and virtualization. Fedora could also be used for routers, becoming part of networking infrastructure.

TODO: Move any QA related information to QA/Networking.

Current topics

Networking concepts and configuration

Connectivity:

User experience:

Black magic:

Important networking projects

Known networking bugs

I moved all the information about known networking bugs to a separate article: Known networking bugs

Pieces of the puzzle

  • Interface for static IPv4 and IPv6 configuration (kernel)
  • Interface for bridging/bonding/vlan configuration (kernel)
  • Interface for DNS configuration (/etc/resolv.conf)
  • DHCP client implementation for IPv4 automatic configuration (dhclient)
  • RA client implementation for IPv6 address configuration (kernel, with workarounds in NetworkManager)
  • RDNSS/DNSSL client implementation for IPv6 DNS configuration (NetworkManager through kernel, with workarounds)
  • DHCP client implementation for IPv6 address/DNS/other configuration (dhclient)
  • IPsec, VPN and tunneling implementations (various daemons)
  • A network management daemon to properly manage all of the above together with user configuration (NetworkManager)
  • Networking API for applications (glibc, with many problems)

I may have missed something but the objective is to show that networking is rather complex and the various tools need to be centrally managed by a network management service in order to make users and administrators happy.

You can only live without network configuration daemons if you use static IP configuration and you avoid encrypted wireless networks at the same time. You can live with just wpa_supplicant and dhclient only if you are used to do most of the stuff yourself. Virtually all linux distributions now converge to network solutions based on network configuration daemons.

Examples of such daemons (without feature comparison):

  • NetworkManager
  • connman (MeeGo)
  • WICD
  • netifd (OpenWRT)
  • netcfg (Archlinux)
  • wicked
  • systemd-networkd
  • pyroute2 (?)

Yeah, it's a lot of fun writing new and new network configuration daemons.

Fedora feature pages

F20

Unknown

Testing

Contacts

  • Name: Pavel Šimerda
  • Email: psimerda@redhat.com, pavlix@pavlix.net
  • IRC: pavlix, #nm at freenode

Use the above contacts or Talk:Networking for discussions about Networking page, its subpages, related pages and covered topics. Add yourself to the contacts if you want to help me maintaining this set of information resources.