Documentation Networking Beat: Difference between revisions

Revision as of 19:14, 1 May 2014

Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer

-- 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.

@@ Line 1: / Line 1: @@
-== Networking ==
+{{header|docs}}{{Docs_beat_open}}
+[[Category:Docs Project]]
-=== NetworkManager with system wide connections and enhanced support for Mobile Broadband ===
+[[Category:Draft documentation]]
+[[Category:Documentation beats]]
-NetworkManager can now create and edit system-wide network connections in /etc/sysconfig. NetworkManager has been able to read information about system-wide network connections from /etc/sysconfig for a while. Now we have enabled full read-write support for system connections. The ability to create or modify new system connections will be controlled by PolicyKit policies. Initially, only wired/wireless connections will be supported. Later on, vpn connections will follow. For connections that require secrets, those will be stored in .keys files in /etc/sysconfig.
-By providing a database of preconfigured mobile broadband providers, supporting more hardware and permit to scan GSM networks, NetworkManager makes the use of mobile broadband much easier. Your broadband provider will be automatically recognized by NetworkManager and it will make it easy to just plug it your USB device and get you online within minutes.
-=== Enhanced IPV6 Support in NetworkManager ===
-For non GUI users, and those that use ifcfg files directly, NetworkMangaer should bring up the interface with IPv6 connectivity correctly at boot. No modification of the ifcfg files should be necessary.
+-- https://git.fedorahosted.org/cgit/initscripts.git/log/?showmsg=1 reviewed as of [[User:Immanetize|Pete Travis]] ([[User talk:Immanetize|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>
-For GUI users, a new IPv6 tab will appear in the connection editor which will allow for control if the IPv6 settings similar to control of IPv4 settings already. After selecting the configuration method ("auto" is the default, which will honor router-advertisements and attempt to retrieve DNS information with DHCPv6 information-only mode) and entering any additional settings they may wish to use, then saving the connection, activating that connection should configure the interface fully with IPv6 as requested by the user.
+=== 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.
-=== NetworkManager System Connections ===
+  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.
-NetworkManager has been able to read information about system-wide network connections from /etc/sysconfig for a while. This feature is about enabling full read-write support for system connections. The ability to create or modify new system connections will be controlled by PolicyKit policies.
-Initially, only wired/wireless connections will be supported. Later on, vpn connections will follow.
-For connections that require secrets, those will be stored in .keys files in /etc/sysconfig.
-=== Network Interface Management ===
-Configuring the network interfaces on a machine for moderately complicated
-yet common scenarios is generally only accessible to advanced users, and
-very poorly supported by existing tools. Such scenarios include creating a
-bridge and enslaving a physical NIC to it, or bonding two NIC's, adding a
-VLAN interface to the bond and enslaving that to a bridge.
-Complicated bridge setups are commonly needed on virtualized hosts, and
-often have to be performed remotely by higher-level management tools,
-rather than a human user.
-This feature addresses these needs by providing a general-purpose network
-configuration library ([http://fedorahosted.org/netcf netcf]) and additions
-to the [http://libvirt.org libvirt API] to expose netcf's local API through
-libvirt's remoting facilities.
-With <code>netcf</code>, a logical network interface (e.g. a bridge and its
-slaves) is described as a unit, and <code>netcf</code> takes care of
-translating that description into the appropriate <code>ifcfg-*</code>
-files. To guarantee the happy coexistence of <code>netcf</code> with other
-network configuration utilities, including <code>vi</code>,
-<code>netcf</code> is bidirectional: it modifies <code>ifcfg-*</code> files
-based on a <code>netcf</code> interface description, but also reads
-<code>ifcfg-*</code> files to generate such a description. It is therefore
-possible to use <code>netcf</code> side-by-side with any other method of
-changing network configuration, and many of the pitfalls of earlier
-attempts to do this, e.g., the Xen networking scripts, are avoided.
-It is planned to switch NetworkManager to <code>netcf</code> as the backend
-for system-wide network configuration in a future release; while it's not part of this feature,
-it will further unify the user experience around network configuration. In
-the same vein, it is planned to expose network configuration functionality
-in a future release of [http://virt-manager.et.redhat.com/ virt-manager]
-=== Bluetooth Service On Demand ===
-In order to support bluetooth devices, bluetooth background service was started by default in previous versions of Fedora. In this release, bluetooth service is started on demand when needed and automatically stops 30 seconds after last device use instead reducing initial startup time and resources.
-=== NFS V4 Default ===
-The latest version of the NFS protocol is version 4, which was first introduced in Fedora F-2 (the first distro to have such support). The current default NFS version is version 3. Meaning when an simple NFS mount is done (i.e. mount server:/export /mnt) version 3 is the first protocol version that is tried.
-In Fedora 12, version 4 is tried first. If the server does not support version 4, the mount would then try version 3.
-[[Category:Docs Project]]
-[[Category:Draft documentation]]

Search

Documentation Networking Beat: Difference between revisions

Revision as of 19:14, 1 May 2014

ppp support moved from initsccripts to ppp

initscripts support for bridge prio, aging