Documentation Networking Beat: Difference between revisions

Revision as of 15:58, 26 October 2012

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

Consistent network device naming

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 em<port_number>, while ports on PCI cards will be named p<slot_number>p<port_number>, corresponding to the chassis labels. This feature may be disabled by passing "biosdevname=0" on the kernel command line, in which case, behavior will revert to using ethX names.

better network security with firewalld

firewalld will be the default firewall solution for Fedora 18, replacing iptables. Using firewalldwill allow for application of policy changes without reloading, allowing connection states to stay unbroken when rules are changed.

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.

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.

@@ Line 1: / Line 1: @@
-{{Admon/warning | F13 | Beat owner should begin placing Fedora 13 content in this beat. }}
+{{header|docs}}
-===[[Features/NetworkManagerBluetoothDUN |NetworkManager Bluetooth DUN ]]===
+{{Docs_beat_open}}
-Many older phones support mobile broadband sharing to computers through Bluetooth Dial-Up Networking (DUN). When the phone is paired with a computer, the computer may request that the phone provide a virtual serial port, and then the computer treats that virtual serial port as a normal mobile broadband connection card, sending AT commands and starting PPP.
+== Consistent network device naming ==
-Enhanced functionality in the gnome-bluetooth plugin allows users to set up their network connection with a few clicks, after which the phone and the network connection are available from the nm-applet menu.
+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.
-Fedora user now will only have one tool to use instead of having to use a 3rd-party tool that doesn't fully function with Fedora.
+== better network security with firewalld ==
+'''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.
-===[[Features/NetworkManagerCmdline |NetworkManager Command Line ]]===
+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.
-NetworkManager Command Line allows a user to control the NetworkManager without using a GUI.
+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).
-NetworkManager Command Line has created tools that will allow a user to control the NetworkManager from a terminal, headless machine, or the initscripts with a proper CLI client. The purpose of this program is to have very lightweight tooll. Therefore, tools written in C are preferred over tools written in Python.
+== 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).
-NetworkManager Command Line tools will benefit the Fedora user by making the NetworkManager more suitable to the server enviroment and consolidating network configuration.
+== 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.
-===[[Features/NetworkManagerMobileStatus |NetworkManager Mobile Status]]===
+[[Category:Docs Project]]
+[[Category:Draft documentation]]
-The NetworkManager applet shows the current signal strength, cellular technology (GPRS/EDGE/UMTS/HSPA or 1x/EVDO etc), and roaming status while connected for cards where this functionality is supported.
+[[Category:Documentation beats]]
-The benefits to Fedora users are Mobile Status makes it easier to use mobile broadband. Users will be able to know when their device has a signal and if they are roaming or not. This could potentially save the user money.
-===[[Features/NFSv4Default |NFSv4 Default ]]===
-Changes the default NFS protocol to version 4. NFSv4 will check to see if the server supports version 4. If the server does then it will connect. Otherwise it will connect using version 3.
-One of the major benefit is performance. In version 4, the server has state which means it can communicate with each NFS client. The means the server can issue things called delegations (or leases) for files allowing the v4 client to aggressively cache which drastically cuts down on network traffic between the client and server.
-There are a number of other benefits which are documented [http://www.iaps.com/NFSv4-new-features.html here]
-===[[Features/NFSClientIPv6 |NFS Client IPv6]]===
-NFS Client IPv6 supports the mounting of NFS servers over IPv6. The benefits for Fedora users is the now servers and network file systems can talk to each other over IPv6 networks.
-There are a number of other benefits which are documented
-Possible related feature pages:
-* [[Features/NetworkManagerBluetoothDUN |NetworkManager Bluetooth DUN ]]
-* [[Features/NetworkManagerCmdline |NetworkManager Command Line ]]
-* [[Features/NetworkManagerMobileStatus |NetworkManager Mobile Status ]]
-* [[Features/NFSv4Default |NFSv4 Default ]]
-* [[Features/NFSClientIPv6 | NFS Client IPv6]]
-<noinclude>[[Category:Release Notes]]<noinclude>
-[[Category:Documentation_beats]]

Search