commit 48ac13adae0ef9ce87038f0eff967dd854162644 Author: Petr Bokoc pbokoc@redhat.com Date: Tue Nov 11 16:34:25 2014 +0100
Adding the rest of NetworkSpoke
en-US/NetworkSpoke.xml | 70 ++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 68 insertions(+), 2 deletions(-) --- diff --git a/en-US/NetworkSpoke.xml b/en-US/NetworkSpoke.xml index 3568b6d..9c7d202 100644 --- a/en-US/NetworkSpoke.xml +++ b/en-US/NetworkSpoke.xml @@ -29,7 +29,7 @@ Use the <guilabel>ON</guilabel>/<guilabel>OFF</guilabel> switch in the top right corner to enable or disable the currently selected interface. </para> <para> - Below the list of connections, enter a host name for this computer in the <guilabel>Hostname</guilabel> input field. The host name can be either a <firstterm>fully-qualified domain name</firstterm> (FQDN) in the format <replaceable>hostname</replaceable>.<replaceable>domainname</replaceable>, or a short host name with no domain name. Many networks have a <firstterm>Dynamic Host Configuration Protocol</firstterm> (<systemitem class="protocol">DHCP</systemitem>) service that automatically supplies connected systems with a domain name. To allow the <systemitem class="protocol">DHCP</systemitem> service to assign the domain name to this machine, only specify the short host name. + Below the list of connections, enter a host name for this computer in the <guilabel>Hostname</guilabel> input field. The host name can be either a <firstterm>fully-qualified domain name</firstterm> (FQDN) in the format <replaceable>hostname</replaceable>.<replaceable>domainname</replaceable>, or a short host name with no domain name. Many networks have a <firstterm>Dynamic Host Configuration Protocol</firstterm> (<systemitem class="protocol">DHCP</systemitem>) service that automatically supplies connected systems with a domain name; to allow the <systemitem class="protocol">DHCP</systemitem> service to assign the domain name to this machine, only specify the short host name. </para> <section id="sect-installation-gui-network-configuration-virtual-interface"> @@ -67,7 +67,73 @@ <section id="sect-installation-gui-network-configuration-advanced"> <title>Editing Network Interface Configuration</title> <para> - text + This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the <citetitle>&PRODUCT; Networking Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/">&PRODUCT; Documentation</ulink>. + </para> + <para> + To configure a network connection manually, select that connection in the list on the left side of the screen, and click the <guilabel>Configure</guilabel> button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in <xref linkend="sect-installation-gui-network-configuration-virtual-interface" />.. A full description of all configuration settings for all connection types is beyond the scope of this document; see the <citetitle>Networking Guide</citetitle> for details. + </para> + <para> + The most common and useful options in the configuration dialog are: + </para> + <variablelist> + <varlistentry> + <term>Enable or disable the connection by default</term> + <listitem> + <para> + In the <guilabel>General</guilabel> tab of the configuration dialog, you can select or unselect the <guilabel>Automatically connect to this network when it is available</guilabel> check box to allow or disallow this connection to connect by default. When enabled on a wired connection, this means the system will typically connect during startup (unless you unplug the network cable); on a wireless connection, it means that the interface will attempt to connect to any known wireless networks in range. + </para> + <para> + Additionally, you can allow or disallow all users on the system from connecting to this network using the <guilabel>All users may connect to this network</guilabel> tab. If you disable this option, only <systemitem class="username">root</systemitem> will be able to connect to this network. + </para> + <note> + <para> + It is not possible to only allow a specific user other than <systemitem class="username">root</systemitem> to use this interface, because no other users are created at this point during the installation. If you need a connection for a different user, you must configure it after the installation. + </para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term>Set up static IPv4 or IPv6 settings</term> + <listitem> + <para> + By default, both <systemitem class="protocol">IPv4</systemitem> and <systemitem class="protocol">IPv6</systemitem> are set to automatic configuration depending on current network settings. This means that addresses such as the local IP address, DNS address, and other settings will be detected automatically each time the interface connects to a network. In many cases, this is sufficient, but you can also provide static configuration in the <guilabel>IPv4 Settings</guilabel> and <guilabel>IPv6</guilabel> settings, respectively. + </para> + <para> + To set static network configuration, navigate to one of the settings tabs and select a method other than <guilabel>Automatic</guilabel> (for example, <guilabel>Manual</guilabel>) from the <guilabel>Method</guilabel> drop-down menu. This will enable the <guilabel>Addresses</guilabel> field below. + </para> + <note> + <para> + In the <guilabel>IPv6 Settings</guilabel> tab, you can also set the method to <guilabel>Ignore</guilabel> to disable <systemitem class="protocol">IPv6</systemitem> on this interface. + </para> + </note> + <para> + Then, click <guilabel>Add</guilabel> on the right side and add a set of settings: <guilabel>Address</guilabel>, <guilabel>Netmask</guilabel> (for <systemitem class="protocol">IPv4</systemitem>), <guilabel>Prefix</guilabel> (for <systemitem class="protocol">IPv6</systemitem>), and <guilabel>Gateway</guilabel>. + </para> + <para> + The <guilabel>DNS servers</guilabel> field accepts one or more IP addresses of DNS servers - for example, <literal>10.0.0.1,10.0.0.8</literal>. + </para> + <para> + The final option in both tabs is <guilabel>Require IPv<replaceable>X</replaceable> addressing for this connection to complete</guilabel>. Select this option in the <systemitem class="protocol">IPv4</systemitem> tab to only allow this connection if <systemitem class="protocol">IPv4</systemitem> was successful; the same principle applies to this setting in the <systemitem class="protocol">IPv6</systemitem> tab. If this option remains disabled for both <systemitem class="protocol">IPv4</systemitem> and <systemitem class="protocol">IPv6</systemitem>, the interface will be able to connect if configuration succeeds on either IP protocol. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Configure routes</term> + <listitem> + <para> + In the <guilabel>IPv4 Settings</guilabel> and <guilabel>IPv4 Settings</guilabel> tabs, click the <guilabel>Routes</guilabel> button in the bottom right corner to configure routing settings for a specific IP protocol on an interface. A new dialog will open, allowing you to <guilabel>Add</guilabel> a specific route. + </para> + <para> + If you confire at least one static route, you can disallow all other ones by enabling the <guilabel>Ignore automatically obtained routes</guilabel>. + </para> + <para> + You can also check the <guilabel>Use this connection only for resources on this network</guilabel>; this option does not require any static routes to be set. This setting is useful if you are configuring more than one interface. By enabling it for one interface and disabling it for others, you can ensure that the interface which has this option enabled will only be used to access resources unavailable to other interfaces (such as your internal network with restricted access), and the other ones will be used to access normally avaibable data (such as the internet). + </para> + </listitem> + </varlistentry> + </variablelist> + <para> + Once you finish configuring the interface, click <guilabel>Save</guilabel> in the configuration window's bottom right corner to save your settings and return to the <guilabel>Network & Hostname</guilabel> screen. </para> </section>
docs-commits@lists.fedoraproject.org