From Fedora Project Wiki
No edit summary |
|||
Line 50: | Line 50: | ||
=== GLIBC === | === GLIBC === | ||
* IPv4: [ | * IPv4: [http://bugzilla.redhat.com/show_bug.cgi?id=721350 <code>getaddrinfo("127.0.0.1", ...)</code> fail with some AI_ADDRCONFIG configurations] | ||
* IPv6: [ | * IPv6: [http://bugzilla.redhat.com/show_bug.cgi?id=808147 Fedora 808147 - <code>getaddrinfo("::1", ...)</code> fails with some configurations of AI_ADDRCONFIG] | ||
* IPv6: <code>getaddrinfo("fe80::1234:56ff:fe78:90%eth0", ...)</code> also fails as above | * IPv6: <code>getaddrinfo("fe80::1234:56ff:fe78:90%eth0", ...)</code> also fails as above | ||
* IPv6: [ | * 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] | * DNS: [http://sourceware.org/bugzilla/show_bug.cgi?id=2099 <code>getaddrinfo</code> doesn't support SRV records] | ||
=== dhclient === | === dhclient === | ||
* Fixed: [ | * 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) | * People say that dhclient exchange is slow, especially on wireless (I can't reproduce) | ||
=== Avahi === | === 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 === | === NetworkManager === |
Revision as of 15:22, 23 November 2012
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.
Networking concepts and configuration
- Ethernet
- Addressing
- Routing
- Bridging
- Bonding / Teaming
- TCP, UDP and ICMP NAT
- Traffic control
- Tunneling
- Name Resolution
- Network connectivity dependencies
Most prominent projects involved in linux networking
- Kernel
- GLIBC
- NetworkManager
- ISC DHCP
Networking problems
Only platform bugs that can influence various application and/or the overall behavior of the system belong here.
Kernel
- Bridge: Adding first interface after setting MAC address changes the MAC address
- IPv4: Kernel can't store DHCP lifetime and cannot mark IPv6 addresses dynamic (in the DHCP sense)
- IPv6: Kernel ignores RA router preference
- IPv6: Tempaddr cycling breaks TCP connections prematurely
- IPv6: Kernel doesn't cache RDNSS and DNSSL
- 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
- rtnl_link_bond_add() succeeds when device already exists
- rtnl_link_bridge_add() and rtnl_link_vlan_add missing
iproute
- iproute won't distinguish bridges and bonds
- iproute won't show vlan id
GLIBC
- IPv4:
getaddrinfo("127.0.0.1", ...)
fail with some AI_ADDRCONFIG configurations - IPv6: Fedora 808147 -
getaddrinfo("::1", ...)
fails with some configurations of AI_ADDRCONFIG - IPv6:
getaddrinfo("fe80::1234:56ff:fe78:90%eth0", ...)
also fails as above - IPv6: GLIBC's nsswitch doesn't support overriding
getaddrinfo
which is requred to resolve link-local IPv6 addresses - DNS:
getaddrinfo
doesn't support SRV records
dhclient
- Fixed:
dhclient
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
- Avahi's nss-mdns returns link-local IPv6 addresses without scope_id and applications fail to connect
- Avahi's IPv6 support is disabled by default (this has been resolved in the past)
NetworkManager
- Various bugs in NetworkManager
Testing tools
- ping doesn't support IPv6 (you have to use ping6)