--- 05_network.txt	2013-09-12 11:15:54.902830067 +0200
+++ 05_network_proposal.txt	2013-10-20 20:58:57.748640282 +0200
@@ -31,9 +31,12 @@
 `wicd-daemon`                       @-@popcon1@-@ @-@psize1@-@ , ,               wired and wireless network manager (daemon)
 `wicd-gtk`                          @-@popcon1@-@ @-@psize1@-@ , ,               wired and wireless network manager (GTK+ client)
 `iptables`                          @-@popcon1@-@ @-@psize1@-@ config::Netfilter administration tools for packet filtering and NAT (http://en.wikipedia.org/wiki/Netfilter[Netfilter])
+### HW: the link http://www.linuxfoundation.org/en/Net:Iproute2 in next line seems no longer active,
+### HW: redirection to http://www.linuxfoundation.org/collaborate/workgroups/networking
 `iproute`                           @-@popcon1@-@ @-@psize1@-@ config::iproute2  http://www.linuxfoundation.org/en/Net:Iproute2[iproute2], IPv6 and other advanced network configuration: `ip`(8), `tc`(8), etc
 `ifrename`                          @-@popcon1@-@ @-@psize1@-@ , ,               rename network interfaces based on various static criteria: `ifrename`(8)
 `ethtool`                           @-@popcon1@-@ @-@psize1@-@ , ,               display or change Ethernet device settings
+### HW: link in next line dead, see above
 `iputils-ping`                      @-@popcon1@-@ @-@psize1@-@ test::iproute2    test network reachability of a remote host by http://en.wikipedia.org/wiki/Hostname[hostname] or http://en.wikipedia.org/wiki/IP_address[IP address] (http://www.linuxfoundation.org/en/Net:Iproute2[iproute2])
 `iputils-arping`                    @-@popcon1@-@ @-@psize1@-@ , ,               test network reachability of a remote host specified by the http://en.wikipedia.org/wiki/Address_Resolution_Protocol[ARP] address
 `iputils-tracepath`                 @-@popcon1@-@ @-@psize1@-@ , ,               trace the network path to a remote host
@@ -127,6 +130,11 @@
 - The `libnss-mdns` plugin package provides host name resolution via mDNS for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc).
 - The "`/etc/nsswitch.conf`" file should have stanza like "`hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4`".
 - Host names ending with the http://en.wikipedia.org/wiki/.local[".local"] http://en.wikipedia.org/wiki/Pseudo-top-level_domain[pseudo-top-level domain] (TLD) are resolved.
+
+### HW: I'm unsure what the following line means. If that are examples for the 
+### HW: format of the IP address, you should use something like: 
+### HW: The format of the IP address is:
+### HW: "`224.0.0.251`" for IPv4 and "`ff02::fb`" for IPv6
 - IP address "`224.0.0.251`" for IPv4 and "`ff02::fb`" for IPv6 are used.
 
 The hostname resolution via deprecated http://en.wikipedia.org/wiki/NetBIOS_over_TCP/IP[NETBios over TCP/IP] used by the older Windows system can be provided by installing the `winbind` package.  The "`/etc/nsswitch.conf`" file should have stanza like "`hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 wins`" to enable this functionality.  (Modern Windows system usually use the `dns` method for the hostname resolution.)
@@ -153,7 +161,7 @@
 
 The network interface name, e.g. `eth0`, is assigned to each hardware in the Linux kernel through the user space configuration mechanism, `udev` (see <<_the_udev_system>>), as it is found.  The network interface name is referred as **physical interface** in `ifup`(8) and `interfaces`(5).
 
-In order to ensure each network interface to be named persistently for each reboot using http://en.wikipedia.org/wiki/MAC_address[MAC address] etc., there is a record file "`/etc/udev/rules.d/70-persistent-net.rules`".  This file is automatically generated by the "`/lib/udev/write_net_rules`" program, probably run by the "`persistent-net-generator.rules`" rules file. You can modify it to change naming rule.
+In order to ensure each network interface to be named persistently for each reboot using http://en.wikipedia.org/wiki/MAC_address[MAC address] etc., there is a rules file "`/etc/udev/rules.d/70-persistent-net.rules`".  This file is automatically generated by the "`/lib/udev/write_net_rules`" program, probably run by the "`persistent-net-generator.rules`" rules file. You can modify it to change naming rule.
 
 CAUTION: When editing the "`/etc/udev/rules.d/70-persistent-net.rules`" rules file, you must keep each rule on a single line and the http://en.wikipedia.org/wiki/MAC_address[MAC address] in lowercase. For example, if you find "FireWire device" and "PCI device" in this file, you probably want to name "PCI device" as `eth0` and configure it as the primary network interface.
 
@@ -171,7 +179,7 @@
 C     192.168.0.x -- 192.168.255.x 255.255.255.0 /24            256          
 -----------------------------------------------------------------------------
 
-NOTE: If one of these addresses is assigned to a host, then that host must not access the Internet directly but must access it through a gateway that acts as a proxy for individual services or else does http://en.wikipedia.org/wiki/Network_address_translation[Network Address Translation(NAT)].  The broadband router usually performs NAT for the consumer LAN environment.
+NOTE: If one of these addresses is assigned to a host, then that host must not access the Internet directly but must access it through a gateway that acts as a proxy for individual services or else does http://en.wikipedia.org/wiki/Network_address_translation[Network Address Translation (NAT)].  The broadband router usually performs NAT for the consumer LAN environment.
 
 ==== The network device support
 
@@ -179,7 +187,10 @@
 
 === The modern network configuration for desktop
 
-Debian `squeeze` systems can manage the network connection via management http://en.wikipedia.org/wiki/Daemon_(computer_software)[daemon] software such as http://en.wikipedia.org/wiki/NetworkManager[NetworkManager (NM)] (network-manager and associated packages) or http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)[Wicd] (wicd and associated packages).
+### HW: There are several parts in the d-r where "squeeze" is hardcoded. 
+### HW: Probably this can or should be changed, to have the d-r not only capable
+### HW: for one release? In the following line the sentence can savely be changed.
+Debian `squeeze` and newer can manage the network connection via management http://en.wikipedia.org/wiki/Daemon_(computer_software)[daemon] software such as http://en.wikipedia.org/wiki/NetworkManager[NetworkManager (NM)] (network-manager and associated packages) or http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)[Wicd] (wicd and associated packages).
 
 - They come with their own http://en.wikipedia.org/wiki/Graphical_user_interface[GUI] and command-line programs as their user interfaces.
 - They come with their own http://en.wikipedia.org/wiki/Daemon_(computer_software)[daemon] as their backend system.
@@ -204,7 +215,7 @@
 --------------------
 $ sudo adduser foo netdev
 --------------------
-2. Keep configuration of "`/etc/network/interfaces`" as simple as the the following.
+2. Keep configuration of "`/etc/network/interfaces`" as simple as in the following.
 +
 --------------------
 auto lo
@@ -221,7 +232,8 @@
 --------------------
 4. Configure your network via GUI.
 
-NOTE: Only interfaces which are **not** listed in "`/etc/network/interfaces`" or which have been configured with "`auto ...`" or "`allow-hotplug ...`" and "`iface ... inet dhcp`" (with no other options) are managed by NM to avoid conflict with `ifupdown`.
+### HW: is the following limitation not also true for Wicd?
+NOTE: Only interfaces which are **not** listed in "`/etc/network/interfaces`" or which have been configured with "`auto ...`" or "`allow-hotplug ...`" and "`iface ... inet dhcp`" (with no other options) are managed by NM or Wicd to avoid conflict with `ifupdown`.
 
 TIP: If you wish to extend network configuration capabilities of NM, please seek appropriate plug-in modules and supplemental packages such as `network-manager-openconnect`, `network-manager-openvpn-gnome`, `network-manager-pptp-gnome`, `mobile-broadband-provider-info`, `gnome-bluetooth`, etc.   The same goes for those of Wicd.
 
@@ -236,6 +248,7 @@
 There are 2 types of programs for the low level network configuration on Linux (see <<_iproute2_commands>>).
 
 - Old http://www.linuxfoundation.org/en/Net:Net-tools[net-tools] programs (`ifconfig`(8), ...) are from the Linux NET-3 networking system. Most of these are obsolete now.
+### HW: link in next line dead, see above.
 - New http://www.linuxfoundation.org/en/Net:Iproute2[Linux iproute2] programs (`ip`(8), ...) are the current Linux networking system.
 
 Although these low level networking programs are powerful, they are cumbersome to use.  So high level network configuration systems have been created.
@@ -258,7 +271,11 @@
 
 === The network connection method (legacy)
 
-CAUTION: The connection test method described in this section are meant for testing purposes.  It is not meant to be used directly for the daily network connection.  You are advised to use them via NM, Wicd, or the `ifupdown` package (see <<_the_modern_network_configuration_for_desktop>> and <<_the_basic_network_configuration_with_ifupdown_legacy>>).
+### HW: "You are advised to use them via NM, Wicd, or the `ifupdown` package" has a
+### HW: problem with wrong reference: I read it like "You are advised to use the wvdial 
+### HW: test command via NM, Wicd, or the `ifupdown` package". But that's not meant here,
+### HW: I think. 
+CAUTION: The connection test methods described in this section are meant for testing purposes.  It is not meant to be used directly for the daily network connection.  You are advised to use NM, Wicd, or the `ifupdown` package instead (see <<_the_modern_network_configuration_for_desktop>> and <<_the_basic_network_configuration_with_ifupdown_legacy>>).
 
 // FIXME: Since my MacBook has no build-in modem, and I use the broadband-modem via Ethernet, all POTS-related description needs to be tested with the recent system.
 
@@ -274,7 +291,7 @@
 Ethernet port (`eth0`) DHCP/Static       <=> LAN <=> BB-router with http://en.wikipedia.org/wiki/Network_address_translation[network address translation (NAT)] (<=> BB-modem ...)
 ------------------------------------------------------------------------------------------------------------------------------------------
 
-Here is the summary of configuration script for each connection method.
+Here is the summary of configuration scripts for each connection method.
 
 .List of network connection configurations
 [grid="all"]
@@ -285,7 +302,7 @@
 PPP (alternative) `wvdialconf` to create heuristic chat     `ppp`, `wvdial`
 PPPoE             `pppoeconf` to create deterministic chat  `pppoeconf`, `ppp`
 DHCP              described in "`/etc/dhcp/dhclient.conf`"  `isc-dhcp-client`
-static IP (IPv4)  described in "`/etc/network/interfaces`"  `net-tools`
+static IP (IPv4)  described in "`/etc/network/interfaces`"  `iproute` or `net-tools` (obsolete)
 static IP (IPv6)  described in "`/etc/network/interfaces`"  `iproute`
 -------------------------------------------------------------------------------
 
@@ -314,7 +331,7 @@
 
 ==== The DHCP connection with the Ethernet
 
-The typical modern home and small business network, i.e. LAN, are connected to the WAN(Internet) using some consumer grade broadband router.  The LAN behind this router is usually served by the http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol[dynamic host configuration protocol (DHCP)] server running on the router.
+The typical modern home and small business network, i.e. LAN, are connected to the WAN (Internet) using some consumer grade broadband router.  The LAN behind this router is usually served by the http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol[dynamic host configuration protocol (DHCP)] server running on the router.
 
 Just install the `isc-dhcp-client` package for the Ethernet served by the http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol[dynamic host configuration protocol (DHCP)].
 
@@ -429,7 +446,9 @@
 - For **dynamic IP** system such as mobile PCs, you should setup TCP/IP network **with** the `resolvconf` package and enable you to switch your network configuration easily (see <<_the_network_interface_served_by_the_dhcp>>).
 - For **static IP** system such as servers, you should setup TCP/IP network **without** the `resolvconf` package and keep your system simple (see <<_the_network_interface_with_the_static_ip>>).
 
-These traditional setup methods are quite useful if you wish to set up advanced configuration (see <<_the_basic_network_configuration_with_ifupdown_legacy>>).
+### HW: The link in the following line is quite senseless, since it links to itself
+### HW: (the link is in chapter 5.5 and it links to chapter 5.5). So better delete it.
+These traditional setup methods are quite useful if you wish to set up advanced configuration; find details in the following.
 
 The `ifupdown` package provides the standardized framework for the high level network configuration in the Debian system. In this section, we learn the basic network configuration with `ifupdown` with simplified introduction and many typical examples.
 
@@ -634,7 +653,7 @@
 
 ==== The network configuration state of ifupdown
 
-The "`/etc/network/run/ifstate`" file stores the **intended** network configuration states for all the currently active network interfaces managed by the `ifupdown` package are listed. Unfortunately, even if the `ifupdown` system fails to bring up the interface as intended, the "`/etc/network/run/ifstate`" file lists it active.
+The "`/etc/network/run/ifstate`" file stores the **intended** network configuration states for all the currently active network interfaces managed by the `ifupdown` package. Unfortunately, even if the `ifupdown` system fails to bring up the interface as intended, the "`/etc/network/run/ifstate`" file lists it active.
 
 Unless the output of the `ifconfig`(8) command for an interface does not have a line like following example, it can not be used as a part of http://en.wikipedia.org/wiki/IPv4[IPV4 network].
 
@@ -663,7 +682,7 @@
 
 The `network-test` command frees you from the execution of cumbersome low level commands to analyze the network problem.
 
-The automatic scripts are installed in "`/etc/network/\*/`" and performs the following.
+The automatic scripts are installed in "`/etc/network/\*/`" and perform the following.
 
 - Check the network cable connection
 - Check duplicate use of IP address
@@ -685,9 +704,9 @@
 
 ==== The ifplugd package
 
-The `ifplugd` package is older automatic network configuration tool which can manage only Ethernet connections. This solves unplugged/replugged Ethernet cable issues for mobile PC etc.   If you have http://en.wikipedia.org/wiki/NetworkManager[NetworkManager] or http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)[Wicd] (see <<_the_modern_network_configuration_for_desktop>>) installed, you do not need this package.
+The `ifplugd` package is an older automatic network configuration tool which can manage only Ethernet connections. This solves unplugged/replugged Ethernet cable issues for mobile PC etc.   If you have http://en.wikipedia.org/wiki/NetworkManager[NetworkManager] or http://en.wikipedia.org/wiki/Wicd_(Linux_Network_Manager)[Wicd] (see <<_the_modern_network_configuration_for_desktop>>) installed, you do not need this package.
 
-This package runs http://en.wikipedia.org/wiki/Daemon_(computer_software)[daemon] and replaces **auto** or **allow-hotplug** functionalities (see <<list-of-stanzas-in-eni>>) and starts interfaces upon their connection to the network.  
+This package runs a http://en.wikipedia.org/wiki/Daemon_(computer_software)[daemon] and replaces **auto** or **allow-hotplug** functionalities (see <<list-of-stanzas-in-eni>>) and starts interfaces upon their connection to the network.  
 
 Here is how to use the `ifplugd` package for the internal Ethernet port, e.g. `eth0`.
 
@@ -718,8 +737,9 @@
 The following sets the `eth0` interface to be preferred over the `wlan0` interface.
 
 1. Install the `ifmetric` package.
-2. Add an option line with "`metric 0`" just below the "`iface eth0 inet dhcp`" line.
-3. Add an option line with "`metric 1`" just below the "`iface wlan0 inet dhcp`" line.
+### HW: Say in which file the following changings should be performed?
+2. Add an option line with "`metric 0`" just below the "`iface eth0 inet dhcp`" line in "`/etc/network/interfaces`".
+3. Add an option line with "`metric 1`" just below the "`iface wlan0 inet dhcp`" line in "`/etc/network/interfaces`".
 
 The metric 0 means the highest priority route and is the default one.  The larger metric value means lower priority routes. The IP address of the active interface with the lowest metric value becomes the originating one. See `ifmetric`(8).
 
@@ -751,7 +771,7 @@
 
 ==== The advanced command syntax
 
-The `ifupdown` package offers advanced network configuration using the  **network configuration** name and the **network interface** name.  I use slightly different terminology from one used in `ifup`(8) and `interfaces`(5).
+The `ifupdown` package offers advanced network configuration using the  **network configuration** name and the **network interface** name.  I use a terminology being slightly different from the one used in `ifup`(8) and `interfaces`(5).
 
 
 .List of terminology for network devices
@@ -790,7 +810,7 @@
  map ...
 --------------------
 
-This provides advanced feature to the "`/etc/network/interfaces`" file by automating the choice of the configuration with the mapping script specified by `<script_name>`.
+This provides advanced features to the "`/etc/network/interfaces`" file by automating the choice of the configuration with the mapping script specified by `<script_name>`.
 
 Let@@@sq@@@s follow the execution of the following.
 
@@ -812,7 +832,12 @@
 
 Here is how to switch manually among several network configurations without rewriting the "`/etc/network/interfaces`" file as in <<_the_basic_network_reconfiguration>> .
 
-For all the network configuration you need to access, you create a single "`/etc/network/interfaces`" file as the following.
+### HW: The following sentence is misleading IMHO. While reading it the first
+### HW: time, I understood it as:
+### HW: For all the different network configurations you create a separate
+### HW: /etc/network/interfaces file, naming them like /etc/network/interfaces.home,
+### HW: /etc/network/interfaces.office, /etc/network/interfaces.hotel etc.
+For all the network configuration you need to access, you create a separate stanza in "`/etc/network/interfaces`" file as the following.
 
 --------------------
 auto lo
@@ -926,7 +951,7 @@
 "`$IFACE`"           physical name (interface name) of the interface being processed
 "`$LOGICAL`"         logical name (configuration name) of the interface being processed
 "`$ADDRFAM`"         <address_family> of the interface
-"`$METHOD`"          <method_name> of the interface. (e.g., "static")
+"`$METHOD`"          <method_name> of the interface (e.g., "static")
 "`$MODE`"            "start" if run from `ifup`, "stop" if run from `ifdown`
 "`$PHASE`"           as per "`$MODE`", but with finer granularity, distinguishing the `pre-up`, `post-up`, `pre-down` and `post-down` phases
 "`$VERBOSITY`"       indicates whether "`--verbose`" was used; set to 1 if so, 0 if not
@@ -959,6 +984,7 @@
 
 ==== Iproute2 commands
 
+### HW: two links in next line dead, see above.
 http://www.linuxfoundation.org/en/Net:Iproute2[Iproute2] commands offer complete low-level network configuration capabilities. Here is a translation table from obsolete http://www.linuxfoundation.org/en/Net:Net-tools[net-tools] commands to new http://www.linuxfoundation.org/en/Net:Iproute2[iproute2] etc. commands.
 
 .Translation table from obsolete `net-tools` commands to new `iproute2` commands
@@ -1072,7 +1098,7 @@
 Dial-up link (IP: PPP)                                        576                   standard
 Ethernet link (IP: DHCP or fixed)                             1500                  standard and default
 Ethernet link (IP: PPPoE)                                     1492 (=1500-8)        2 bytes for PPP header and 6 bytes for PPPoE header
-Ethernet link (ISP@@@sq@@@s backbone: ATM, IP: DHCP or fixed) 1462 (=48\*31-18-8)   author@@@sq@@@s speculation: 18 for Ethernet header, 8 for SAR trailer
+Ethernet link (ISP@@@sq@@@s backbone: ATM, IP: DHCP or fixed) 1462 (=48\*31-18-8)   author@@@sq@@@s speculation: 18 bytes for Ethernet header, 8 bytes for SAR trailer
 Ethernet link (ISP@@@sq@@@s backbone: ATM, IP: PPPoE)         1454 (=48\*31-8-18-8) see "http://www.mynetwatchman.com/kb/ADSL/pppoemtu.htm[Optimal MTU configuration for PPPoE ADSL Connections]" for rationale
 ------------------------------------------------------------------------------------------------------------------------------------------
 
@@ -1151,5 +1177,5 @@
 - http://www.netfilter.org/documentation/HOWTO/packet-filtering-HOWTO.html[Linux 2.4 Packet Filtering HOWTO]
 - http://www.netfilter.org/documentation/HOWTO/NAT-HOWTO.html[Linux 2.4 NAT HOWTO]
 
-TIP: Although these were written for Linux **2.4**, both `iptables`(8) command and netfilter kernel function apply for current Linux **2.6**.
+TIP: Although these were written for Linux **2.4**, both `iptables`(8) command and netfilter kernel function apply for Linux **2.6** and **3.x** kernel series.
 
