2. Linux From Scratch 12.2
3. chapter09_network
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Linux From Scratch 12.2/chapter09_network — Spanish	General Network Configuration
	Linux From Scratch 12.2/chapter09_network — Spanish	network
	Linux From Scratch 12.2/chapter09_network — Spanish	configuring
	Linux From Scratch 12.2/chapter09_network — Spanish	Creating Network Interface Configuration Files
	Linux From Scratch 12.2/chapter09_network — Spanish	The files in <filename class="directory">/etc/sysconfig/</filename> usually determine which interfaces are brought up and down by the network script. This directory should contain a file for each interface to be configured, such as <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> describes the network card. The interface name (e.g. eth0) is usually appropriate. Each file contains the attributes of one interface, such as its IP address(es), subnet masks, and so forth. The stem of the filename must be <emphasis>ifconfig</emphasis>.
	Linux From Scratch 12.2/chapter09_network — Spanish	If the procedure in the previous section was not used, udev will assign network card interface names based on system physical characteristics such as enp2s1. If you are not sure what your interface name is, you can always run <command>ip link</command> or <command>ls /sys/class/net</command> after you have booted your system.
	Linux From Scratch 12.2/chapter09_network — Chinese (Simplified Han script)	The interface names depend on the implementation and configuration of the udev daemon running on the system. The udev daemon for LFS (installed in <xref linkend="ch-system-udev"/>) will not run until the LFS system is booted. So the interface names in the LFS system cannot always be determined by running those commands on the host distro, <emphasis>even in the chroot environment</emphasis>.
	Linux From Scratch 12.2/chapter09_network — Spanish	The interface names depend on the implementation and configuration of the udev daemon running on the system. The udev daemon for LFS (installed in <xref linkend="ch-system-udev"/>) will not run until the LFS system is booted. So the interface names in the LFS system cannot always be determined by running those commands on the host distro, <emphasis>even in the chroot environment</emphasis>.
	Linux From Scratch 12.2/chapter09_network — Spanish	The following command creates a sample file for the <emphasis>eth0</emphasis> device with a static IP address:
	Linux From Scratch 12.2/chapter09_network — Spanish	<userinput>cd /etc/sysconfig/ cat &gt; ifconfig.<replaceable>eth0</replaceable> &lt;&lt; "EOF" <literal>ONBOOT=<replaceable>yes</replaceable> IFACE=<replaceable>eth0</replaceable> SERVICE=<replaceable>ipv4-static</replaceable> IP=<replaceable>192.168.1.2</replaceable> GATEWAY=<replaceable>192.168.1.1</replaceable> PREFIX=<replaceable>24</replaceable> BROADCAST=<replaceable>192.168.1.255</replaceable></literal> EOF</userinput>
	Linux From Scratch 12.2/chapter09_network — Spanish	The values in italics must be changed in each file, to set the interfaces up correctly.
	Linux From Scratch 12.2/chapter09_network — Spanish	If the <envar>ONBOOT</envar> variable is set to <literal>yes</literal> the System V network script will bring up the Network Interface Card (NIC) during the system boot process. If set to anything besides <literal>yes</literal>, the NIC will be ignored by the network script and will not be started automatically. Interfaces can be manually started or stopped with the <command>ifup</command> and <command>ifdown</command> commands.
	Linux From Scratch 12.2/chapter09_network — Spanish	The <envar>IFACE</envar> variable defines the interface name, for example, eth0. It is required for all network device configuration files. The filename extension must match this value.
	Linux From Scratch 12.2/chapter09_network — Spanish	The <envar>SERVICE</envar> variable defines the method used for obtaining the IP address. The LFS-Bootscripts package has a modular IP assignment format, and creating additional files in the <filename class="directory">/lib/services/</filename> directory allows other IP assignment methods. This is commonly used for Dynamic Host Configuration Protocol (DHCP), which is addressed in the BLFS book.
	Linux From Scratch 12.2/chapter09_network — Spanish	The <envar>GATEWAY</envar> variable should contain the default gateway IP address, if one is present. If not, then comment out the variable entirely.
	Linux From Scratch 12.2/chapter09_network — Spanish	The <envar>PREFIX</envar> variable specifies the number of bits used in the subnet. Each segment of an IP address is 8 bits. If the subnet's netmask is 255.255.255.0, then it is using the first three segments (24 bits) to specify the network number. If the netmask is 255.255.255.240, the subnet is using the first 28 bits. Prefixes longer than 24 bits are commonly used by DSL and cable-based Internet Service Providers (ISPs). In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the <envar>PREFIX</envar> variable according to your specific subnet. If omitted, the PREFIX defaults to 24.
	Linux From Scratch 12.2/chapter09_network — Spanish	For more information see the <command>ifup</command> man page.
	Linux From Scratch 12.2/chapter09_network — Spanish	Creating the /etc/resolv.conf File
	Linux From Scratch 12.2/chapter09_network — Spanish	/etc/resolv.conf
	Linux From Scratch 12.2/chapter09_network — Spanish	The system will need some means of obtaining Domain Name Service (DNS) name resolution to resolve Internet domain names to IP addresses, and vice versa. This is best achieved by placing the IP address of the DNS server, available from the ISP or network administrator, into <filename>/etc/resolv.conf</filename>. Create the file by running the following:
	Linux From Scratch 12.2/chapter09_network — Spanish	<userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF" <literal># Begin /etc/resolv.conf domain <replaceable>&lt;Your Domain Name&gt;</replaceable> nameserver <replaceable>&lt;IP address of your primary nameserver&gt;</replaceable> nameserver <replaceable>&lt;IP address of your secondary nameserver&gt;</replaceable> # End /etc/resolv.conf</literal> EOF</userinput>
	Linux From Scratch 12.2/chapter09_network — Spanish	The <varname>domain</varname> statement can be omitted or replaced with a <varname>search</varname> statement. See the man page for resolv.conf for more details.
	Linux From Scratch 12.2/chapter09_network — Spanish	Replace <replaceable>&lt;IP address of the nameserver&gt;</replaceable> with the IP address of the DNS most appropriate for the setup. There will often be more than one entry (requirements demand secondary servers for fallback capability). If you only need or want one DNS server, remove the second <emphasis>nameserver</emphasis> line from the file. The IP address may also be a router on the local network.
	Linux From Scratch 12.2/chapter09_network — Spanish	The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.
	Linux From Scratch 12.2/chapter09_network — Spanish	Configuring the System Hostname
	Linux From Scratch 12.2/chapter09_network — Spanish	hostname
	Linux From Scratch 12.2/chapter09_network — Spanish	During the boot process, the file <filename>/etc/hostname</filename> is used for establishing the system's hostname.
	Linux From Scratch 12.2/chapter09_network — Spanish	Create the <filename>/etc/hostname</filename> file and enter a hostname by running:
	Linux From Scratch 12.2/chapter09_network — Spanish	<userinput>echo "<replaceable>&lt;lfs&gt;</replaceable>" &gt; /etc/hostname</userinput>
	Linux From Scratch 12.2/chapter09_network — Spanish	<replaceable>&lt;lfs&gt;</replaceable> needs to be replaced with the name given to the computer. Do not enter the Fully Qualified Domain Name (FQDN) here. That information goes in the <filename>/etc/hosts</filename> file.
	Linux From Scratch 12.2/chapter09_network — Spanish	Customizing the /etc/hosts File
	Linux From Scratch 12.2/chapter09_network — Spanish	/etc/hosts
	Linux From Scratch 12.2/chapter09_network — Spanish	localnet
	Linux From Scratch 12.2/chapter09_network — Spanish	Decide on a fully-qualified domain name (FQDN), and possible aliases for use in the <filename>/etc/hosts</filename> file. If using static IP addresses, you'll also need to decide on an IP address. The syntax for a hosts file entry is:
	Linux From Scratch 12.2/chapter09_network — Spanish	<literal>IP_address myhost.example.org aliases</literal>
	Linux From Scratch 12.2/chapter09_network — Spanish	Unless the computer is to be visible to the Internet (i.e., there is a registered domain and a valid block of assigned IP addresses&mdash;most users do not have this), make sure that the IP address is in the private network IP address range. Valid ranges are:
	Linux From Scratch 12.2/chapter09_network — Spanish	<literal>Private Network Address Range Normal Prefix 10.0.0.1 - 10.255.255.254 8 172.x.0.1 - 172.x.255.254 16 192.168.y.1 - 192.168.y.254 24</literal>
	Linux From Scratch 12.2/chapter09_network — Spanish	x can be any number in the range 16-31. y can be any number in the range 0-255.
	Linux From Scratch 12.2/chapter09_network — Spanish	A valid private IP address could be 192.168.1.1.
	Linux From Scratch 12.2/chapter09_network — Chinese (Simplified Han script)	If the computer is to be visible to the Internet, a valid FQDN can be the domain name itself, or a string resulted by concatenating a prefix (often the hostname) and the domain name with a <quote>.</quote> character. And, you need to contact the domain provider to resolve the FQDN to your public IP address.
	Linux From Scratch 12.2/chapter09_network — Spanish	If the computer is to be visible to the Internet, a valid FQDN can be the domain name itself, or a string resulted by concatenating a prefix (often the hostname) and the domain name with a <quote>.</quote> character. And, you need to contact the domain provider to resolve the FQDN to your public IP address.
	Linux From Scratch 12.2/chapter09_network — Chinese (Simplified Han script)	Even if the computer is not visible to the Internet, a FQDN is still needed for certain programs, such as MTAs, to operate properly. A special FQDN, <literal>localhost.localdomain</literal>, can be used for this purpose.
	Linux From Scratch 12.2/chapter09_network — Spanish	Even if the computer is not visible to the Internet, a FQDN is still needed for certain programs, such as MTAs, to operate properly. A special FQDN, <literal>localhost.localdomain</literal>, can be used for this purpose.
	Linux From Scratch 12.2/chapter09_network — Spanish	Create the <filename>/etc/hosts</filename> file by running:
	Linux From Scratch 12.2/chapter09_network — Spanish	<userinput>cat &gt; /etc/hosts &lt;&lt; "EOF" <literal># Begin /etc/hosts 127.0.0.1 localhost.localdomain localhost 127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>&lt;192.168.1.1&gt;</replaceable> <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>[alias1] [alias2 ...]</replaceable> ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # End /etc/hosts</literal> EOF</userinput>
	Linux From Scratch 12.2/chapter09_network — Spanish	The <replaceable>&lt;192.168.1.1&gt;</replaceable>, <replaceable>&lt;FQDN&gt;</replaceable>, and <replaceable>&lt;HOSTNAME&gt;</replaceable> values need to be changed for specific uses or requirements (if assigned an IP address by a network/system administrator and the machine will be connected to an existing network). The optional alias name(s) can be omitted.