Documentation Networking Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(NM mobile broadband)
(31 intermediate revisions by 8 users not shown)
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}}
 +
= federated VOIP=
  
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.
+
= Improved Mobile Broadband Support =
 +
Fedora 19 includes a new, more capable version of ModemManager for interacting with mobile broadband devices. This version provides better support for multi-mode devices like Qualcomm Gobi WWAN cards and other devices that support both CDMA/EVDO/LTE and/or GSM/UMTS/LTE simultaneously. To provide this support, the D-Bus API of ModemManager has changed, which may require updates in applications that interact with ModemManager to control WWAN devices.
  
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.
+
Many devices will connect and authenticate using the NetworkManager GUI. `nm-cli` has added features to configure mobile connections. For more detailed usage information, consult http://fedoraproject.org/wiki/Features/MoreMobileBroadband .
  
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.
+
= firewalld =
 +
== locking the firewall ==
 +
Dynamic firewall configuration by application can now be locked down completely, or limited to a whitelist. The whitelist can contain commands, users, UIDs, and selinux contexts.
 +
<!-- asked for manpages at https://bugzilla.redhat.com/show_bug.cgi?id=952364 -->
  
===[[Features/NetworkManagerCmdline |NetworkManager Command Line ]]===
+
To lock down the firewall, set `Lockdown=yes` in `/etc/firewalld/firewalld.conf`
  
NetworkManager Command Line allows a user to control the NetworkManager without using a GUI.
+
Whitelist definitions are kept in `/etc/firewalld/lockdown-whitelist.xml`. This example whitelist allows `firewall-cmd` to configure the firewall:
 +
<whitelist>
 +
<command name="/usr/bin/python /usr/bin/firewall-cmd"
 +
</whitelist>
  
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.
+
The firewall must be reloaded to refresh the whitelist:
 +
firewall-cmd --reload
  
NetworkManager Command Line tools will benefit the Fedora user by making the NetworkManager more suitable to the server enviroment and consolidating network configuration.
+
== configuring the firewall ==
 +
Configuring firewalld is now possible using high level, human readable language. firewalld's XML rule definitions make advanced configuration easy. For more information, read the feature page at http://fedoraproject.org/wiki/Features/FirewalldRichLanguage .
  
===[[Features/NetworkManagerMobileStatus |NetworkManager Mobile Status]]===
+
= BIND10 =
 +
The latest versions of the  popular nameserver `bind` and dhcp server `dhcpd` server are now available for Fedora. The BIND10 suite features include a RESTful configuration API and sqlite database backend for `named` and SQL backend for `dhcpd`.
  
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.  
+
For more information, consult the `bind10` manual at http://bind10.isc.org/docs/bind10-guide.html .
 +
 +
= stable network interface naming =
 +
The udevd service has a long history of providing predictable names for block devices and others. Fedora will now also use udev naming for network interfaces by default, providing more reliable interface names on systems with multiple network devices.  Alternative naming schemes, such as custom udev rules or biosdevname, will override this default.  Users upgrading from previous releases may need to update the device names referenced in `/etc/system/network-scripts`, although in most cases `biosdevname` will continue to manage naming.
  
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.  
+
For more information, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .
  
===[[Features/NFSv4Default |NFSv4 Default ]]===
+
[[Category:Docs Project]]
 
+
[[Category:Draft documentation]]
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.
+
[[Category:Documentation beats]]
 
+
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]]
+

Revision as of 20:08, 15 April 2013

DocsProject Header docTeam1.png
Note.png
Beat is open
This beat is now ready to have Fedora 21 content added by the beat writer

Contents

federated VOIP

Improved Mobile Broadband Support

Fedora 19 includes a new, more capable version of ModemManager for interacting with mobile broadband devices. This version provides better support for multi-mode devices like Qualcomm Gobi WWAN cards and other devices that support both CDMA/EVDO/LTE and/or GSM/UMTS/LTE simultaneously. To provide this support, the D-Bus API of ModemManager has changed, which may require updates in applications that interact with ModemManager to control WWAN devices.

Many devices will connect and authenticate using the NetworkManager GUI. `nm-cli` has added features to configure mobile connections. For more detailed usage information, consult http://fedoraproject.org/wiki/Features/MoreMobileBroadband .

firewalld

locking the firewall

Dynamic firewall configuration by application can now be locked down completely, or limited to a whitelist. The whitelist can contain commands, users, UIDs, and selinux contexts.

To lock down the firewall, set `Lockdown=yes` in `/etc/firewalld/firewalld.conf`

Whitelist definitions are kept in `/etc/firewalld/lockdown-whitelist.xml`. This example whitelist allows `firewall-cmd` to configure the firewall:

<whitelist>
<command name="/usr/bin/python /usr/bin/firewall-cmd"
</whitelist>

The firewall must be reloaded to refresh the whitelist:

firewall-cmd --reload

configuring the firewall

Configuring firewalld is now possible using high level, human readable language. firewalld's XML rule definitions make advanced configuration easy. For more information, read the feature page at http://fedoraproject.org/wiki/Features/FirewalldRichLanguage .

BIND10

The latest versions of the popular nameserver `bind` and dhcp server `dhcpd` server are now available for Fedora. The BIND10 suite features include a RESTful configuration API and sqlite database backend for `named` and SQL backend for `dhcpd`.

For more information, consult the `bind10` manual at http://bind10.isc.org/docs/bind10-guide.html .

stable network interface naming

The udevd service has a long history of providing predictable names for block devices and others. Fedora will now also use udev naming for network interfaces by default, providing more reliable interface names on systems with multiple network devices. Alternative naming schemes, such as custom udev rules or biosdevname, will override this default. Users upgrading from previous releases may need to update the device names referenced in `/etc/system/network-scripts`, although in most cases `biosdevname` will continue to manage naming.

For more information, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .