From Fedora Project Wiki

(Networking concepts and configuration)
(Networking concepts and configuration)
Line 9: Line 9:
* [[Networking/Ethernet|Ethernet]]
* [[Networking/Ethernet|Ethernet]]
* [[Networking/Addressing|IPv4 and IPv6 addressing]]
* [[Networking/Addressing|Addressing]]
* [[Networking/Routing|IPv4 and IPv6 routing]]
* [[Networking/Routing|Routing]]
* [[Networking/Bridging|Ethernet bridging]]
* [[Networking/Bridging|Bridging]]
* [[Networking/Teaming|Ethernet bonding/teaming]]
* [[Networking/Teaming|Bonding / Teaming]]
* [[Networking/NAT|TCP, UDP and ICMP NAT]]
* [[Networking/NAT|TCP, UDP and ICMP NAT]]
* [[Networking/Traffic control|Traffic control]]
* [[Networking/Traffic control|Traffic control]]

Revision as of 07:45, 21 November 2012

Fedora networking is done with the following components:

Networking concepts and configuration

Networking problems

Only platform bugs that can influence various application and/or the overall behavior of the system belong here.


  • 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


  • rtnl_link_bond_add() succeeds when device already exists
  • rtnl_link_bridge_add() and rtnl_link_vlan_add missing


  • iproute won't distinguish bridges and bonds
  • iproute won't show vlan id





Testing tools

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