From Fedora Project Wiki

m (Closed this beat)
Line 1: Line 1:
{{Admon/warning | F13 | Beat owner should begin placing Fedora 13 content in this beat. }}
===[[Features/NetworkManagerBluetoothDUN |NetworkManager Bluetooth DUN ]]===
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.
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 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.
===[[Features/NetworkManagerCmdline |NetworkManager Command Line ]]===
NetworkManager Command Line allows a user to control the NetworkManager without using a GUI.
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.
NetworkManager Command Line tools will benefit the Fedora user by making the NetworkManager more suitable to the server enviroment and consolidating network configuration.
===[[Features/NetworkManagerMobileStatus |NetworkManager Mobile Status]]===
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.
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 [ 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]]

Revision as of 01:25, 29 April 2010

Warning - Beat Converted

Beat has already been converted to XML
Be sure to set Wiki Good to * and In Publican to 0 if this beat is modified


The contents of this beat have been converted to Publican and sent for translation. The official Fedora 25 documentation now contains the information that was on this page.

If you have changes or corrections please file a bug. Use the product Fedora Documentation, component release-notes.

For the official copy of this beat, refer to the Fedora 25 Documentation.