Documentation Networking Beat

Beat Closed on Wiki
Work on beats has now moved to git at https://pagure.io/fedora-docs/release-notes. If you have changes or additions, please contact the docs team via #fedora-docs, docs@lists.fedoraproject.org, or with the release-notes BZ component.

-- https://git.fedorahosted.org/cgit/initscripts.git/log/?showmsg=1 reviewed as of Pete Travis (talk) 19:14, 1 May 2014 (UTC)

• from initscripts:

 Currently, team masters and slaves are supported 
 via ifup-Team* and ifdown-Team* scripts shipped in 
 teamd package. It uses somehow ugly workaround where
 user have to specify DEVIVETYPE to "Team" or "TeamPort". 
 This turned out to be non-optimal solution as this is 
 confusing users. Also it does not work when TYPE is set. 
 So fix this by adding the team support hooks directly 
 into initscripts. Now for team port, user needs only to set: 
 TEAM_MASTER="teamx" and for team master, user needs only to set: 
 TEAM_CONFIG="...whatever..." 
 Signed-off-by: Jiri Pirko <jiri@resnulli.us>

ppp support moved from initsccripts to ppp

""" The ppp package contains the PPP (Point-to-Point Protocol) daemon and documentation for PPP support. The PPP protocol provides a method for transmitting datagrams over serial point-to-point links. PPP is usually used to dial in to an ISP (Internet Service Provider) or other organization over a modem and phone line. """

initscripts support for bridge prio, aging

( maybe also NetworkManager supports these? ) When using network.servoce, interface definitions in /etc/sysconfig/network-scripts/ for bridges can now include declarations for bridge priority and aging. Use these parameters:

 PRIO=<num>

• where <num> a number between 0 and 255 is used to determine the relative bridge priority. Useful for applications requiring multiple bridges. See http://www.tldp.org/HOWTO/BRIDGE-STP-HOWTO/advanced-bridge.html#STP for more details.

 AGEING=<NUM>

• where num is the number of seconds to keep a MAC address in the forwarding database after the last packet received from it. Usually does not need to be modified.

Network device naming scheme changed

In Fedora releases from Fedora 15 through to Fedora 20, network interface naming was performed by default by biosdevname, as per Features/ConsistentNetworkDeviceNaming. In Fedora 21, by default for new installations network interface naming is handled by systemd, as per Features/SystemdPredictableNetworkInterfaceNames. The naming scheme used is different, meaning all interfaces will have different names in a fresh install of Fedora 21 to the names they had in previous releases. Full details of the new naming scheme are available here. Existing installations that are upgraded to Fedora 21 will continue to use whatever naming scheme they were using prior to the upgrade.

You can disable systemd's interface naming by passing the kernel parameter net.ifnames=0. By default biosdevname is no longer installed, so this will result in the use of old-style non-'predictable' names (eth0 etc) in most cases. Changing interface names in an installed system can require non-obvious configuration changes, so if you want to use static or biosdevname naming, it is probably best to ensure this at install time. To use static naming, simply install with net.ifnames=0 and ensure the biosdevname package is not installed (or also pass biosdevname=0). To use biosdevname naming, install with net.ifnames=0 and also install the biosdevname package (using a kickstart).