Funtoo Linux Networking - Revision history

24.184.214.10: /* Interface Renaming */

2013-02-12T03:06:39Z

‎Interface Renaming

Drobbins: refer people to networkmanager and the install docs for Wi-Fi.

2012-12-31T04:04:59Z

refer people to networkmanager and the install docs for Wi-Fi.

Drobbins: /* Basic VLAN Configuration */

2012-12-31T03:59:12Z

‎Basic VLAN Configuration

Drobbins: /* Basic VLAN Configuration */

2012-12-31T03:58:14Z

‎Basic VLAN Configuration

Drobbins: console formatting

2012-12-31T03:57:43Z

console formatting

Show changes

178.26.44.217: /* Broadcast Address */

2012-12-30T11:56:22Z

‎Broadcast Address

Drobbins at 20:43, 23 November 2012

2012-11-23T20:43:26Z

Drobbins: /* General Variables */

2012-11-21T20:27:43Z

‎General Variables

Judge at 15:25, 21 November 2012

2012-11-21T15:25:46Z

109.91.51.186: /* Interface Variables */

2012-11-20T22:41:59Z

‎Interface Variables

@@ Line 172: / Line 172: @@
 === Interface Renaming ===
-Funtoo network scripts now support interface renaming, so you can create an interface called <tt>lan</tt> if you would like. To so this, simply specify the MAC address of the interface you would like to rename using the <tt>macaddr</tt> variable:
+Funtoo network scripts now support interface renaming, so you can create an interface called <tt>lan</tt> if you would like. To do this, simply specify the MAC address of the interface you would like to rename using the <tt>macaddr</tt> variable:
 <pre>macaddr=&quot;00:15:17:19:b6:a3&quot;</pre>If this MAC address is part of the <tt>netif.lan</tt> configuration file, then when this interface starts, whatever interface currently has the MAC address of 00:15:17:19:b6:a3 (i.e. <tt>eth5</tt>) will be renamed to <tt>lan</tt> prior to the interface being brought up, and will show up in <tt>ifconfig</tt> and <tt>ip</tt> commands as being an interface named <tt>lan</tt>.

@@ Line 407: / Line 407: @@
 == Wireless Configuration ==
-Wireless network configuration requires additional steps to the ones outlined above.
+The recommended approach for setting up Wi-Fi under Funtoo Linux is to use NetworkManager. Steps are provided in the [[Funtoo Linux Installation#Wi-Fi|Wi-Fi section of the Funtoo Linux Installation Guide]].
-−
-For wireless networks, you will need to enable wireless extensions in your kernel, the appropriate wireless modules, and emerge <tt>wireless-tools</tt>:
-−
-<pre># emerge wireless-tools</pre>
-I also recommend you <tt>emerge wpa_supplicant</tt>. wpa_supplicant implements modern WPA/WPA2 wireless link-layer encryption, which is necessary for connecting to most modern password-protected wireless networks. After emerging, add to your default runlevel as follows:
-<pre># emerge wpa_supplicant
-# rc-update add wpa_supplicant default</pre>
-−
-=== 802.11 Passphrases ===
-−
-The only remaining step is to use the <tt>wpa_passphrase</tt> utility to store hashed keys (passwords) that <tt>wpa_supplicant</tt> can use to connect to your favorite wireless networks. This is done as follows:
-−
-<pre># wpa_passphrase jims-netgear &gt;&gt; /etc/wpa_supplicant/wpa_supplicant.conf
-&lt;enter your passphrase&gt;</pre>
-Now, when <tt>wpa_supplicant</tt> encounters an SSID of <tt>jims-netgear</tt>, it will use the password you entered to authenticate with this access point.
-−
-If your wireless network is hidden, you will likely need to modify <tt>/etc/wpa_supplicant/wpa_supplicant.conf</tt> and add <tt>scan_ssid=1</tt> to the entry, like this, in order for <tt>wpa_supplicant</tt> to connect to the wireless network automatically:
-−
-<pre>
-network={
-        ssid="jims-netgear"
-        scan_ssid=1
-        psk=asdf;lkajsdf;laksfj;alskdf
-−
-</pre>
-−
-This is also a good time to remove comments containing your plain-text passphrases, added by <tt>wpa_passphrase</tt>.
-−
-At this point, ensure that <tt>dhcpcd</tt> has been enabled in your current runlevel and type <tt>rc</tt> to start everything up:
-−
-<console>
-# ##i##rc
-</console>
-−
-<tt>wpa_supplicant</tt> should be able to automatically associate with SSIDs in its config file, at which point <tt>dhcpcd</tt> will take over and acquire an IP address from a DHCP server. This should all happen seamlessly. Use the <tt>iwconfig</tt> command to see if you have successfully associated with an access point.
-−
-=== Wireless Firmware ===
-−
-Many wireless adapters will now have everything they need to work. However, if you have an Intel wireless adapter, then you may need to install the proper microcode for your device in addition to ensuring that the proper Intel Wireless kernel drivers are available. For my <tt>Intel Corporation PRO/Wireless AGN [Shiloh] Network Connection</tt>, I need to do the following:
-−
-<pre># emerge net-wireless/iwl5000-ucode</pre>
-<tt>udev</tt> (running by default) and the Linux kernel firmware loader support (<tt>CONFIG_FW_LOADER</tt>) will automatically load the microcode when needed.
-−
-The version of microcode you need will depend on the kernel you are using. For my RHEL5-based kernel, I had emerge an older version of the microcode to match what my kernel wireless driver was expecting by typing:
-−
-<pre># emerge =net-wireless/iwl5000-ucode-5.4.0.11</pre>
-This installed this file <tt>iwlwifi-5000-1.ucode</tt> which was required by my RHEL5-based kernel. Just typing <tt>emerge net-wireless-iwl5000-ucode</tt> installed <tt>iwlwifi-500-2.ucode</tt>, which my kernel could not use. Before I had the right version of the microcode, I saw an error like this when I viewed the kernel messages by typing <tt>dmesg</tt>:
-−
-<pre>iwl5000: iwlwifi-5000-1.ucode firmware file req failed: Reason -2</pre>
-This error message generally means &quot;I can't find this file ''<tt>iwlwifi-5000-1.ucode</tt> that I'm looking for in <tt>/lib/firmware</tt>.&quot;'' With the proper firmware in place, then the wireless driver will be happy and wpa-supplicant can then bring the wireless interface up.
 == Other Network Configurations ==

@@ Line 195: / Line 195: @@
 # ##i##ln -s netif.tmpl netif.eth1
 # ##i##rc-update add netif.eth1 default
-</pre>
+</console>
 Now, assuming you wanted to configure a VLAN of 32, you would create a config file named <tt>/etc/conf.d/netif.eth1.32</tt> that looks something like this:

@@ Line 179: / Line 179: @@
 The standard <tt>interface</tt> template supports VLANs. To use VLAN support, first ensure that your kernel was compiled with VLAN support (the module name is <tt>8021q</tt>) :
-<pre>
+<console>
-# grep CONFIG_VLAN /usr/src/linux/.config
+# ##i##grep CONFIG_VLAN /usr/src/linux/.config
 CONFIG_VLAN_8021Q=m
 CONFIG_VLAN_8021Q_GVRP=y
-</pre>
+</console>
 Then, configure the trunk interface using the <tt>interface-noip</tt> template. Assuming <tt>eth1</tt> is trunked, you would create the file <tt>/etc/conf.d/netif.eth1</tt> with the following contents:

@@ Line 101: / Line 101: @@
 <pre>
-ipaddrs="10.0.0.1/24;broadcast=1.0.1.255 10.0.0.2/24"
+ipaddrs="10.0.0.1/24;broadcast=10.0.1.255 10.0.0.2/24"
 </pre>

@@ Line 116: / Line 116: @@
 The following variables are enabled by default for all network scripts, and if specified will trigger a corresponding configuration action:
-;<tt>nameservers</tt>: Set DNS nameservers using OpenResolv. Specify multiple IPv4 or IPv6 nameservers like this: &quot;1.2.3.4 1.2.3.5 1.2.3.6&quot;. Please do not use &quot;127.0.0.1&quot; in this list, since this makes this to be the only nameserver which will show up in resolv.conf. Note that this appears to be due to OpenResolv treating localhost specially and is being tracked in [http://bugs.funtoo.org/browse/FL-229 Funtoo Bug FL-229].
+;<tt>nameservers</tt>: Set DNS nameservers using OpenResolv. Specify multiple IPv4 or IPv6 nameservers like this: &quot;1.2.3.4 1.2.3.5 1.2.3.6&quot;. Please note that OpenResolv treats <tt>127.0.0.1</tt> specially, and it indicates that you are running a local name resolver like <tt>dnsmasq</tt> or <tt>bind</tt>. OpenResolv will ignore all other name servers specified alongside <tt>127.0.0.1</tt>. See <tt>man resolvconf</tt> and <tt>man resolvconf.conf</tt> for additional setup information.
 ;<tt>search</tt>: Set DNS search information using OpenResolv.
 ;<tt>domain</tt>: Set DNS domain using OpenResolv.

@@ Line 92: / Line 92: @@
 ==== Interface Variables ====
-The <tt>ipaddr</tt> and <tt>ipaddrs</tt> variables are supported by the <tt>interface</tt> and <tt>bridge</tt> templates, and are used to specify a single or multiple  IPv4 or IPv6 address(es) for the interface. IP addresses should be specified in 'IP/netmask' format, such as <tt>10.0.0.1/24</tt>. Multiple IP addresses can be specified delimited by whitespace:</p>
+The <tt>ipaddr</tt> and <tt>ipaddrs</tt> variables are supported by the <tt>interface</tt> and <tt>bridge</tt> templates, and are used to specify a single or multiple  IPv4 or IPv6 address(es) for the interface. IP addresses should be specified in 'IP/netmask' format, such as <tt>10.0.0.1/24</tt>. Multiple IP addresses can be specified delimited by whitespace:
 <pre>ipaddrs=&quot;10.0.0.1/24 10.0.0.2/24&quot;</pre>