Documentation Networking Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(added content from https://fedoraproject.org/wiki/Features/RealHotspot)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{header|docs}}
+
{{header|docs}}{{Docs_beat_open}}
{{Docs_beat_open}}
+
[[Category:Docs Project]]
 +
[[Category:Draft documentation]]
 +
[[Category:Documentation beats]]
  
== Consistent network device naming ==
+
-- 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>
  
Fedora 18 continues previous releases' use of '''biosdevname''' to set network device names in a deterministic manner. Ethernet ports embedded on server motherboards will be named <code>em<port_number></code>, while ports on PCI cards will be named <code>p<slot_number>p<port_number></code>, corresponding to the chassis labels. This feature may be disabled by passing <code>"biosdevname=0"</code> on the kernel command line, in which case, behavior will revert to using ethX names.  
+
=== 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.
 +
"""
  
== better network security with firewalld ==
+
=== initscripts support for bridge prio, aging ===
'''firewalld''' will be the default firewall solution for Fedora 18, replacing '''iptables'''Using '''firewalld'''will allow for application of policy changes without reloading, allowing connection states to stay unbroken when rules are changed.  
+
( 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.
  
A D-BUS interface allows approved applications to communicate status and present complex or temporary needs to the firewall without requiring hand configuration by an administrator. This improves support for dynamic environments like libvirtd, which previously had to be restarted when iptables rules were changed.
+
  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.
Manual administration can be done with firewall-cmd. Documentation on firewalld can be found in the included manpages, firewall-cmd(1), firewalld(1), firewalld.conf(5), firewalld.icmptype(5), firewalld.service(5), firewalld.zone(5).
+
 
+
== Team Driver improves NIC bonding ==
+
Fedora 18 includes Team Driver which facilitates grouping of multiple network interfaces together so they act like a single network interface. This extends teaming possibilities provided by existing bonding driver. It also provides userspace driven, modular alternative to bonding driver. Usage information can be found in man teamd.conf(5), man teamd(8), and man teamdctl(8).
+
 
+
== Bring your own hotspot ==
+
NetworkManager now supports an enhanced Hotspot/Internet Connection Sharing mode for WiFi, which enables a much smoother connection sharing experience and is better supported by hardware. This mode is automatically enabled only for newly created connection to ensure existing configuration is unchanged.
+
 
+
[[Category:Docs Project]]
+
[[Category:Draft documentation]]
+
[[Category:Documentation beats]]
+

Latest revision as of 19:14, 1 May 2014

DocsProject Header docTeam1.png
Note.png
Beat is open
This beat is now ready to have Fedora 21 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>

[edit] 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. """

[edit] 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>
 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.