Networking

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Networking concepts and configuration)
(Networking concepts and configuration)
Line 16: Line 16:
 
* [[Networking/Traffic control|Traffic control]]
 
* [[Networking/Traffic control|Traffic control]]
 
* [[Networking/Tunneling|Tunneling]]
 
* [[Networking/Tunneling|Tunneling]]
* [[Networking/DNS|Domain name system]]
+
* [[Networking/NameResolution|Name Resolution]]
  
 
== Networking problems ==
 
== Networking problems ==

Revision as of 23:59, 21 November 2012

Fedora networking is done with the following components:

Contents

Networking concepts and configuration

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

dhclient

Avahi

NetworkManager

Testing tools

  • ping doesn't support IPv6 (you have to use ping6)