Connecting to the Internet
It is still under construction and content may change. Do not rely on the information on this page. This is the chapter Connecting to the Internet written for the UG. Fill free to suggest ideas, suggestions, improvements, corrections. TY
The Network Manager Applet Icon
Network Manager is the application that, since Fedora 11, the GNOME Desktop uses to handle a wide variety of network devices and connections, that allows you to access the Internet. Network Manager is used to configure all your network connections from wired to wireless network, mobile broadband to xDSL network and VPN, too. And if you don't know about DNS, DHCP or pppoe, Network Manager does it all for you. If you use your computer at home, and have an xDSL connection, it is already up, you dont need to configure anything. With a wireless or broadband connection, the steps needed to setup them are simple and easy to do, just a fiew clicks and fill in your personal informations.
Network Manager executes automatically when you start your session and it is visible as an applet Icon, on the top right of the desktop. If you move the mouse over it, it views the active connection. Left-clicking on it, appears a menu divided in three sections:
- The first section regards the actual connection active which you can eventually Disconnect
- The second section views the other available connections configured: you can switch to one of them by a simple click and the previous one closes automatically.
- VPN Connections: this item allows to configure or disconnect a VPN connection.
Right clicking on the applet, appears another little menu, that allows to
- Enable Networking
- Enable Notifications
- view the Connection Information: a window pops up with informations about the active connection.
- Edit Connections...: it pops up the Network Manager window, in which you configure the network devices and connections.
- About: it pops up the About Network Manager Applet, with information about the project and the people that created the application, with a link to the Project Web-Site.
Mobile Broadband
In Fedora 13, once inserted your card, you can easily create a Mobile Broadband connection, as indicated below. For many mobile broadband cards, Network Manager can visualize in NM applet icon, cellular signal strength and technology, and listen for signal strength changes, or poll modem-manager for such changes while connected. In this way, you are able to know when the device has a signal and if it is roaming or not.
Network Manager in Fedora 13, uses the gnome-bluetooth plugin to help to configure your Mobile Broadband with the service provider. Also, if you have a Bluetooth adapter and a mobile phone (GPRS) that supports Bluetooth DUN, you can pair the phone with the computer, and let Network Manager recognize your mobile phone; at the end of the pairing process you'll see a screen with checkbox that says Access the Internet using your mobile phone. Checking that box, a progress indicator will appear and say Detecting phone configuration
For a list of supported devices, look at NetworkManager - Mobile Broadband, on the gnome.org site. If your device is not supported, please contact us in the mailing list, with informations on your device.
Create a Mobile Broadband network connection
Right-click on the Network Manager applet Icon and select Edit Connections.... Then select the Mobile Broadbandtab, and click on the Add button. A wizard will open that will assist you in the configuration, questioning some information about your provider; specifically, you should know:
- Broadband Provider's name
- Broadband Billing Plan name
- Broadband Billing Plan APN (Access Point Name)
The wizard displays:
- An information page, that let you choose, if more than one, the Mobile device to configure.
- A page where you select the Provider's Country
- A page where you select your Provider
- A summary page of your selections.
Then you need to setup your Mobile connection.
If your Service Provider, or plan (ie, APN) is not listed, you can contact us in Bugzilla, or at Bugzilla Gnome and tell us your provider name, your country, the common name of your plan, and the APN you use, helping us to make the things work better.
Setup a Mobile Broadband connection
Enter your information for the Mobile Broadband connection in following tabs.
Mobile Broadband Tab
- Number: Number to dial when establishing a PPP data session with the GSM-based mobile broadband network. In most cases, leave the number blank and a number selecting the APN will be used automatically when required.
- Username: Username used to authenticate with the network, if required. Note that many providers do not require a username or accept any username.
Password: Password used to authenticate with the network, if required. Note that many providers do not require a password or accept any password.
PPP-Settings Tab
(default values)
Mobile Broadband-IPv4
- Automatic (PPP): Specifing this method, then the O.S. does it all for you (default)
- Automatic (PPP) addresses only: Specifing this method, then only automatic DHCP is used and at least one IP address must be given in the DNS servers entry.
- Manual: Specifing this method, static IP addressing is used and at least one IP address must be given in the DNS servers entry.
Access to Network Manager window
To acceed to Network Manager window for setup your network devices & connections:
- Right-click on the Network Manage applet Icon
- Select Edit Connections...
Before creating your new configuration, the O.S. pops up a window to confirm your operation, asking you the root password.
Some items in the Network Manager window
When editing, in the Network Manager window, you find this items:
- Connection name: User-readable connection identifier/name
- Connect automaticaly: If checked, Network Manager will activate this connection when its network resources are available. If unchecked, the connection must be manually activated by you.
- Available to all users: If checked, Network Manager gets access to this network connection to all users
Setup a wired connection
In this section a common user, generally, doesn't need to do any configuration.
Wired Tab
- Mac Address: The HW address of your network card. When the system boots, it recognizes the network card and its HW address. If you need to know the Mac Address of an interface, open a terminal and run ifconfig | grep HWaddr.
ifconfig | grep HWaddr eth0 Link encap:Ethernet HWaddr 00:21:D0:1F:C3:29
MTU (Maximun Transmission Unit): If non-zero, the card transmits packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames. You could set this to Automatic and the O.S. does it for you.
<section id="sect-User_Guide-Wired_Security"> <title>802.1x Tab</title> <para>If you want cipher your Ethernet communications (defualt is unset) </para> </section>
<section id="sect-User_Guide-Connecting_to_the_Internet-Items_Editing_IPv4"> <title>IPv4 Tab</title> <itemizedlist> <listitem> <para> <guilabel>Automatic (DHCP)</guilabel>: Specifing this method, then the O.S. does it all for you (default) </para> </listitem> <listitem> <para> <guilabel>Automatic (DHCP) addresses only</guilabel>: Specifing this method, then only automatic DHCP is used and at least one IP address must be given in the <guilabel>DNS servers</guilabel> entry. </para> </listitem> <listitem> <para> <guilabel>Manual</guilabel>: Specifing this method, static IP addressing is used and at least one IP address must be given in the <guilabel>DNS servers</guilabel> entry. </para> </listitem> <listitem> <para> <guilabel>Link-Local Only</guilabel>: Specifing this method, a link-local address in the 169.254/16 range will be assigned to the interface. </para> </listitem> <listitem> <para> <guilabel>Shared to other computers</guilabel>: Specifing this method, (indicating that this connection will provide network access to other computers) then the interface is assigned an address in the 10.42.x.1/24 range and a DHCP and forwarding DNS server are started, and the interface is NAT-ed to the current default network connection. </para> </listitem> <listitem> <para> <guilabel>DNS Servers</guilabel>: List of DNS servers. For the <guilabel>Automatic (DHCP)</guilabel> method, these DNS servers are appended to those (if any) returned by automatic configuration. DNS servers cannot be used with the <guilabel>Shared to other computers</guilabel> or <guilabel>Link-Local Only</guilabel> methods as there is no usptream network. In <guilabel>Automatic (DHCP) addresses only</guilabel> and <guilabel>Manual</guilabel> methods, these DNS servers are used as the only DNS servers for this connection. </para> </listitem> <listitem> <para> <guilabel>Search domains</guilabel>: List of DNS search domains. For the <guilabel>Automatic (DHCP)</guilabel> method, these search domains are appended to those returned by automatic configuration. Search domains cannot be used with the <guilabel>Shared to other computers</guilabel> or <guilabel>Link-Local Only</guilabel> methods as there is no upstream network. In <guilabel>Automatic (DHCP) addresses only</guilabel> and <guilabel>Manual</guilabel> methods, these search domains are used as the only search domains for this connection. </para> </listitem> <listitem> <para> <guilabel>Routes...</guilabel>: Fowarding table or routing table. Each IPv4 route structure is composed of 4 32-bit values; the first, <guilabel>Address</guilabel> being the destination IPv4 network; the second, <guilabel>Netmask</guilabel> the destination network, the third, <guilabel>Gateway</guilabel> being the next-hop if any, and the fourth, <guilabel>Metric</guilabel> being the route metric. For the <guilabel>Automatic (DHCP)</guilabel> method, given IP routes are appended to those returned by automatic configuration. Routes cannot be used with the <guilabel>Shared to other computers</guilabel> or <guilabel>Link-Local Only</guilabel> methods as there is no upstream network. </para> </listitem> <listitem> <para> <guilabel>DHCP client ID</guilabel>: The local machine which the DHCP server may use to customize the DHCP lease and options. </para> </listitem> </itemizedlist> </section> </section>
<section id="sect-User_Guide-Connecting_to_the_Internet-Wireless-Setup">
<title>Setup a Wireless connection</title>
<para>Most common items you should fill in, when using a Wireless connection: </para>
<section id="sect-User_Guide-Connecting_to_the_Internet-Items_Editing-Wireless"> <title>Wireless Tab</title> <itemizedlist> <listitem> <para> <guilabel>SSID</guilabel>: The SSID of the WiFi network </para> </listitem> <listitem> <para> <guilabel>Mode</guilabel> The available mode are: <guilabel>Infrastructure</guilabel> (default), <guilabel>Ad Hoc</guilabel> </para> </listitem> <listitem> <para> <guilabel>BSSID</guilabel>: If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. <citetitle>Note: this property does not control the BSSID used when creating an <guilabel>Ad Hoc</guilabel> network.</citetitle> </para> </listitem> </itemizedlist> </section>
<section id="sect-User_Guide-Connecting_to_the_Internet-Items_Editing-Wirelees_Security"> <title> Wireless Security Tab</title> <itemizedlist> <listitem> <para> <guilabel>WEP 40/128-bit Key</guilabel>: Your WEP personal key </para> </listitem> <listitem> <para> <guilabel>WEP 128-bit Passphrase</guilabel>: The passphrase to decipher your WEP </para> </listitem> <listitem> <para> <guilabel>LEAP</guilabel>: </para> </listitem> <listitem> <para> <guilabel>Dynamic WEAP (802.1x)</guilabel>: </para> </listitem> <listitem> <para> <guilabel>WPA & WPA2 Personal</guilabel>: Your WPA personal key </para> </listitem> <listitem> <para> <guilabel>WPA & WPA2 Enterprise</guilabel>: </para> </listitem> </itemizedlist> </section>
<section id="sect-User_Guide-Items_Editing-Wireless-IPv4"> <title>IPv4-Settings Tab</title> <para> <guilabel>IPv4-Settings</guilabel> tab: View <xref linkend="sect-User_Guide-Connecting_to_the_Internet-Items_Editing_IPv4" /> </para> </section> </section>
<section id="sect-User_Guide-Setup_VPN"> <title>Setup a VPN connection</title> <para>Here are some items, depending on the VPN connection type, founded when configuring a VPN connections:</para>
<section id="sect-User_Guide-VPN_VPN_Tab"> <title>VPN Tab</title> <itemizedlist> <listitem> <para> <guilabel>Gateway</guilabel> </para> </listitem> <listitem> <para> <guilabel>Type</guilabel> </para> </listitem> <listitem> <para> <guilabel>Username</guilabel> </para> </listitem> <listitem> <para> <guilabel>CA Certificate</guilabel> </para> </listitem> </itemizedlist> </section>
<section id="sect-User_Guide-VPN_IPv4"> <title>VNP-IPv4 Settings Tab</title> <itemizedlist> <listitem> <para> <guilabel>Automatic (VPN)</guilabel>: Specifing this method, then the O.S. does it all for you (default) </para> </listitem> <listitem> <para> <guilabel>Automatic (VPN) addresses only</guilabel>: Specifing this method, then only automatic DHCP is used and at least one IP address must be given in the <guilabel>DNS servers</guilabel> entry. </para> </listitem> </itemizedlist> </section> </section>
<section id="sect-User_Guide-Setup_xDSL"> <title>Setup an xDSL connection</title> <para>Here are the items generally used in the xDSL connections</para>
<section id="sect-User_Guide-DSL_DSL_Tab"> <title>xDSL Tab</title> <itemizedlist> <listitem> <para> <guilabel>Username</guilabel>: Username used to authenticate with the Service Provider. </para> </listitem> <listitem> <para> <guilabel>Service</guilabel>: For most providers, this should be left blank. </para> </listitem> <listitem> <para> <guilabel>Password</guilabel>: Password (if needed,) used to authenticate with the Service Provider. </para> </listitem> </itemizedlist> </section>
<section id="sect-User_Guide-DSL_PPP_WIRED"> <title>Wired & PPP-Settings Tabs</title> <itemizedlist> <listitem> <para> <guilabel>PPP-Settings</guilabel> tab: default values. </para> </listitem> <listitem> <para> <guilabel>Wired</guilabel> tab: View <xref linkend="sect-User_Guide-Connecting_to_the_Internet-Items_Editing_Wired" /> </para> </listitem> </itemizedlist> </section>
<section id="sect-User_Guide-DSL_IPv4"> <title>xDSL-IPv4 Tab</title> <itemizedlist> <listitem> <para> <guilabel>Automatic (PPPoE)</guilabel>: Specifing this method, then the O.S. does it all for you (default) </para> </listitem> <listitem> <para> <guilabel>Automatic (PPPoE) addresses only</guilabel>: Specifing this method, then only automatic DHCP is used and at least one IP address must be given in the <guilabel>DNS servers</guilabel> entry. </para> </listitem> <listitem> <para> <guilabel>Manual</guilabel>: Specifing this method, static IP addressing is used and at least one IP address must be given in the <guilabel>DNS servers</guilabel> entry. </para> </listitem> </itemizedlist> </section> </section>
<section id="sect-User_Guide-NM-References">
<title>References</title>
<para>
For more information on <application>Network Manager</application>, you can refer to:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url="http://live.gnome.org/NetworkManager/">Project Web-Site</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://live.gnome.org/DarrenAlbers/NetworkManagerFAQ">Network Manager FQA</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://docs.fedoraproject.org/">Fedora 13 Release Notes</ulink>
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section id="sect-User_Guide-Connecting_to_the_Internet-NM_CLI">
<title>nmcli: Network Manager in a CLI</title>
<para>
<command>nmcli</command>, is the console command that makes <application>Network Manager</application> available in a console. <command>nmcli</command> has the following format: nmcli [OPTIONS] OBJECT { COMMAND | help }.
</para>
<itemizedlist>
<listitem>
<para>
OPTIONS: allows you to view the output in terse <command>-t</command> or pretty <command>-p</command> mode.
</para>
</listitem>
<listitem>
<para>
OBJECT: can be <command>nm</command> (NetworkManager status), <command>con</command> (NetworkManager connections) or <command>dev</command> (devices managed by NetworkManager)
</para>
</listitem>
<listitem>
<para>
COMMAND: is the action on OBJECT
</para>
</listitem>
</itemizedlist>
<para>
Type <command>nmcli</command> OBJECT <command>help</command> to see a list of the available actions. For example when OBJECT is <command>nm</command>, the COMMAND are:
</para>
<para> <screen> nmcli nm help Usage: nmcli nm { COMMAND | help }
COMMAND := { status | sleep | wakeup | wifi | wwan }
status sleep wakeup wifi [on|off] wwan [on|off]
</screen> </para>
<para> So, running <command>nmcli nm status</command>, we have: </para>
<para> <screen> NM running: running NM state: connected NM wireless hardware: enabled NM wireless: enabled NM WWAN hardware: enabled NM WWAN: enabled </screen> </para>
<para>
Refer to <command>man NetwkorManager</command> for more informations.
</para>
<section id="sect-User_Guide-Connecting_to_the_Internet-NM-nm-tools"> <title>nm-tools</title> <para> The <command>nm-tool</command> utility provides information about NetworkManager, device, and wireless networks. For example: </para>
<para> <screen> $ nm-tool NetworkManager Tool
State: connected
- Device: eth0 [System eth0] --------------------------------------------------
Type: Wired Driver: 8139too State: connected Default: yes HW Address: 00:21:C0:C1:B3:29
Capabilities: Carrier Detect: yes Speed: 100 Mb/s
Wired Properties
Carrier: on
IPv4 Settings: Address: 192.137.1.2 Prefix: 24 (255.255.255.0) Gateway: 192.137.1.1
DNS: 192.137.1.1
$ </screen> </para> </section> </section>
<section id="sect-User_Guide-Connecting_to_the_Internet-Other-Tools">
<title>Other Networking Tools</title>
<para>
In Fedora 13, <application>Network Manager</application> is the default GUI of the GNOME Desktop, handling the network devices and connections. Though there is another tool, (<command>system-config-network</command> or <menuchoice><guilabel>System > Administration > Network</guilabel></menuchoice>) used to network setup. Probably in next releases of Fedora it will be removed. As seen, <application>Network Manager</application> is cool!
</para>
</section>
<section id="sect-User_Guide-Connecting_to_the_Internet-Remote_Server"> <title>To Access a Remote Server</title> <para> In Fedora 13, the GNOME Desktop has a tool that allows you to access to a Remote Server using its file manager, Nautilus. In the menu-bar select <menuchoice><guilabel>Places > Connect to Server...</guilabel></menuchoice>. Once filled in the necessary connection informations, for quick selection, you can <guilabel>(Add) Bookmark</guilabel> the Server, in Nautilus and in the first section of your Places menu. </para> </section>
</chapter>