--- xml/htdocs/doc/en/handbook/hb-net-advanced.xml 2005/12/21 11:49:14 1.9 +++ xml/htdocs/doc/en/handbook/hb-net-advanced.xml 2005/12/21 12:20:43 1.10 @@ -4,7 +4,7 @@ - + @@ -16,10 +16,10 @@

-The config_eth0 variable is the heart of an interface's configuration. -It's a high level instruction list for configuring the interface (eth0 in -this case). Each command in the instruction list is performed sequentially. -The interface is deemed OK if at least one command works. +The config_eth0 variable is the heart of an interface's configuration. It's a +high level instruction list for configuring the interface (eth0 in this case). +Each command in the instruction list is performed sequentially. The interface is +deemed OK if at least one command works.

@@ -51,9 +51,9 @@ dhcp, adsl or apipa (or a custom command from a 3rd party module) - Run the module which provides the command. For example "dhcp" will - run a module that provides dhcp which can be one of either dhcpcd, - udhcpc, dhclient or pump. + Run the module which provides the command. For example "dhcp" will run a + module that provides dhcp which can be one of either dhcpcd, udhcpc, + dhclient or pump. @@ -98,9 +98,9 @@ When using the ifconfig module and adding more than one address, interface aliases are created for each extra address. So with the above two examples you -will get interfaces eth0, eth0:1 and eth0:2. -You cannot do anything special with these interfaces as the kernel and other -programs will just treat eth0:1 and eth0:2 as eth0. +will get interfaces eth0, eth0:1 and eth0:2. You cannot do anything special with +these interfaces as the kernel and other programs will just treat eth0:1 and +eth0:2 as eth0. @@ -109,8 +109,8 @@ -APIPA and -DHCP are discussed later. +APIPA and DHCP are discussed later. @@ -137,35 +137,33 @@ no - This basically means that at least one net.* service besides net.lo - must be up. This can be used by notebook users that have a wifi and - a static nic, and only wants one up at any given time to have the - net service seen as up. + This basically means that at least one net.* service besides net.lo must be + up. This can be used by notebook users that have a wifi and a static nic, + and only wants one up at any given time to have the net service seen as up. lo - This is the same as the 'no' option, but net.lo is also counted. - This should be useful to people that do not care about any specific - interface being up at boot. + This is the same as the 'no' option, but net.lo is also counted. This should + be useful to people that do not care about any specific interface being up + at boot. yes - For this ALL network interfaces MUST be up for the 'net' service to - be considered up. + For this ALL network interfaces MUST be up for the 'net' service to be + considered up.

-But what about net.br0 depending on net.eth0 and net.eth1? -net.eth1 may be a wireless or ppp device that needs configuration before it -can be added to the bridge. -This cannot be done in /etc/init.d/net.br0 as that's a symbolic -link to net.lo +But what about net.br0 depending on net.eth0 and net.eth1? net.eth1 may be a +wireless or ppp device that needs configuration before it can be added to the +bridge. This cannot be done in /etc/init.d/net.br0 as that's a +symbolic link to net.lo

@@ -180,10 +178,9 @@

-For a more detailed discussion about dependency, consult the section -Writing -Init Scripts in the Gentoo Handbook. +For a more detailed discussion about dependency, consult the section Writing Init Scripts in the Gentoo +Handbook.