# Wireless access point from laptop HOWTO.

## How to create a wireless access point and router, from a laptop.

### Krastyo Komsalov

http://komsalov.homelinux.org/ http://ca.linkedin.com/in/kkomsalov

`<kkomsalov@gmail.NOSPAM.com>`

2012-04-15

Revision History
Revision 2.0 | 2012-06-29 | Revised by: Me
Changed the document title. Fixed a number of spelling mistakes.
Revision 1.1 | 2012-01-01 | Revised by: ME
Created first DocBooc version.
Revision 1.0 | 2011-10-09 | Revised by: ME
First UNofficial release.

This is as simple as I managed to made it instruction how to make wireless access point from a computer wit wireless adapter.

## About this document

### .1. Copyright and License

Copyright (c) 2012 by Krastyo Komsalov.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in Appendix A.

### .2. Translations

If you know of any translations for this document, or you are interested in translating it, please email me `<kkomsalov@gmail.com>`.

### .3. Preface

The main reason for writing this document is to share my surprise of how easy it is to convert a laptop into a wireless access point on Slackware.

### .4. Acknowledgments

I wish to express my gratitude towards my two sons Petko Komsalov and Viktor Komsalov who helped me with the countless hours of their time in the redaction of this guide. The finalized form of this guide would not have been publishable, if not for their advices and counseling during the rooting out of inconsistencies and mistakes.

### .5. Feedback

Find something wrong with this document? (Or perhaps something right?) I would love to hear from you. Please email me at `<kkomsalov@gmail.com>`.

### .6. Conventions used in this document

The following typographic and usage conventions occur in this text:

Table 1. Typographic and usage conventions

Text type | Meaning
--- | ---
"Quoted text" | Quotes from people, quoted computer output.

    terminal view

Literal computer input and output captured from the terminal.

command | Name of a command that can be entered on the command line.
`option` | Option to a command, as in "the `-a` option to the ls command".
`parameter` | Parameter to a command, as in "read man `ls`".
command `options` `arguments` | Command synopsis or general usage, on a separated line.
`filename` | Name of a file or directory, for example "Change to the `/usr/bin` directory."
Menu->Choice | Choice to select from a graphical menu, for instance: "Select Help->About Mozilla in your browser."
The author | Click-able link to an external web resource.

Thanks to Machtelt "Tille" Garrels for this list of conventions.

## 2. Introduction

The main reason for writing this document is to share my surprise of how easy it is to convert the Aspire One into a wireless access point on Slackware and how good the Aspire One hardware is for this. Accidentally, I happened to have some free time and one three year old Aspire in my hands so I decided to do something about my growing dissatisfaction with my home router. I live in a crowded Wi-Fi area with over 30 access points coming from the apartments around me and my router obviously has troubles with this. What I wanted was a wireless router over which I will have full control of all settings: log levels control, ability to install additional software for traffic analysis, a decent iptables firewall, RADIUS; in short a wireless router with full Linux installed on it.

1. I chose to use Free RADIUS, since I wanted not only support for WPA and the ability to append eventual access points with roaming, but also the extensibility to any user data base, from local flat files to LDAP. Hostapd has its own integrated RADIUS, but the freedom of having FreeRADIUS was so tempting; besides the setup with flat ASCII users file is really easy. In this configuration RADIUS is set up to use files.

2. Ipv6 and DNSSEC are here to stay and no embedded router has all the functionality which I have with Linux. Ipv6 and DNSSEC configuration is not included in this HOWTO guide, but the freedom to configure them is there.

3. I wanted to have not only a standard firewall, but the full power of iptables. A simple functionality like SSH tunnels that allows home access from school for my kids is tricky with my router and traffic shaping is simply not available. For this reason the Firewall Builder is included in this configuration with a basic rule set. I think it is by far the best firewall management solution on the market and it is free for Linux users.

4. I wanted to have at least two wireless networks "different ssid", to open safely one of them and share some of my bandwidth with my neighbours. This I hope will make me feel less ripped-off next time I pay my internet bill.

5. The other solution OpenWrt had two disadvantages: my router is too weak to support OpenWrt and any router that is powerful enough for everything that I want will cost nearly as much or more then the Aspire; which I already have.

## 3. Hardware description

My Acer Aspire One has a Model KAV10, which is one of Acer's oldest models. Since then Acer has produced many new models, but the only important part for this configuration is the model of the wireless adapter within it. From what I found Acer has been changing the adapter in nearly all newer models of Aspire. All the models I checked come with a different adapter made by Atheros (although its important to verify the producer). If you are thinking of buying the laptop, check in advance its wireless adapter. For mine, lspci and dmesg are giving this:

    bash-4.1# lspci
    01:00.0 Ethernet controller: Atheros Communications Inc. AR5001
            Wireless Network Adapter (rev 01)
    03:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114
            Gigabit or Fast Ethernet (rev b0)
    bash-4.1# dmesg |grep Atheros
    [   10.367156] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

This is really good news as it seems that Atheros is one of the best supported adapters on Linux (the people from The MadWifi project are doing excellent work).

Surprisingly Windows is giving different information:

If it turns out that your adapter is different from mine, you will have to investigate further in order to be sure it supports AP mode. To accomplish this you will need the "iw" command. You probably have it already, but for the source and some documentation go to: http://linuxwireless.org/en/users/Documentation/iw. The most informative syntax is:

iw list

It will give you a pretty long output. In it look for the part that is similar to the following:

    Supported interface modes:
                     * IBSS
                     * managed
                     * AP
                     * AP/VLAN
                     * monitor
                     * mesh point
            Supported commands:

If there is a line "* AP" it is good news, you have the necessary AP support for hostapd.

If it turns out that your chipset is different from mine you can check if it is supported on the MadWifi website. The MadWifi website is also by far the best source of documentation I have found. This will be one of your primary sources of knowledge when you decide to adjust to your needs, experiment or simply improve the configuration given below.

If you do not have Linux already installed, you can boot it from Slackware or SystemRescueCd USB stick and do some investigation on your Aspire.

The model of my old router "Linksys SRX 200" shown as part of two of the three configurations is not important. You may use any wireless router if you have any or avoid using it at all if you decide to permanently dedicate the Aspire as your Wireless router.

## 4. Some possible network configurations

### 4.1. Keep your old router and append the Aspire inside, providing two additional wireless networks. Configuration (a.).

In this configuration the Ethernet port of the Aspire is connected directly to "SRX 200". This solves the problem of Aspire having only one Ethernet port. Two Ethernet ports required are one for the Internet link the other for the internal switch to provide Internet access to Ethernet connected computers. The two wireless networks are NAT'ed to the 192.168.1.55 IP address. The reason for this is not only to put ssid "Welcome" in a separate network and simplify firewalling, but also to resolve some NAT and routing problems. First the devices in 192.168.1.0/24 must have a route to 192.168.11.0/24. I had no problem adding routes within Linux and Solaris, but my network printer simply has no such thing as a routing table in its web interface. Second, appending the route in "SRX 200" is not a problem, but "SRX 200" refuses to NAT any other network than the one connected to its interface. This is probably solvable by sub-networking its network, but I think the next configurations (b.) and (c.) are better solutions. Even with all its disadvantages, I think this configuration is the best starting point as it will not cause any disruptions or changes in your current setup until all configurations on Aspire are done and tested; then it can easily be converted to any other.

### 4.2. Using only Aspire as AP. Configuration (b.).

This configuration is setting you free from any later worries and is the optimal variant, but there is a price to pay. Since the Aspire has only one Ethernet adapter you have to append a second one. There are two solutions. The first one "shown on the picture" is to use an intelligent or managed switch to VLAN the eth0. The second one is to use a USB to Ethernet adapter, to convert one of the USB ports to Ethernet. The drawback of the switch solution is that it is much more expensive, though it has the advantage of speed, stability and simplicity. The USB to Ethernet adapter is much cheaper, but it comes with a doubtful Linux driver support and uncertain speed and reliability. There is one more small detail to mention: depending what kind of Internet connection you have there will be different setups for the uplink adapter. If you use a cable connection than it simply has to be on DHCP. In the case of ADSL (my case) you will need to configure a PPPoE. On Slackware you simply have to run a pppoe-setup script.

### 4.3. Bridging between the two private networks and NATing only "Welcome" public network. Configuration (c.).

In this configuration the interfaces eth0 and wlan0 are bridged. The network 192.168.1.0/24 can be accessed either through "kristo" or "Acer_A1" ssid. The DHCP server on the Aspire is bind only to the wlan0_0 interface. NAT to 192.168.1.55 is only done for 172.17.0.0/16. The computers assessing the 192.168.1.0/24 network through ssid "Acer_A1" are getting IP addresses from the DHCP server on "SRX 200". Other solutions will be available if the DHCP server on "SRX 200" was more manageable. For example, instead of bridging the two parts of 192.168.1.0/24, it will be more elegant to subnet 192.168.1.0/24 and setup a DHCP helper for the part in ssid "Acer_A1".

This configuration has two advantages. The first is that it avoids both, the routing problem of the solution (a.) and the consequent NAT'ing of the "Acer_A1". Second, it allows the Aspire to be turned off while networking remains through your old router. If you can't afford to dedicate your Aspire as AP, this is the best configuration. It provides a stable network when you do not need the Aspire and allows you to disconnect the Aspire from the network for personal use, while preserving a functional network.

## 5. Initial Configuration (a.) - installation instructions for all the necessary software for all configurations.

I installed all the necessary programs from the source in /usr/local. I left some configuration files in `/usr/local/etc` and moved some in `/etc`/. There are Slackware packages on SlackBuilds.org or you can make your own if you decide it is worth the effort, considering that installing it from source is easier.

### 5.1. The easiest way of installing Slackware on Acer Aspire One

his chapter is probably unnecessary, but I love to preach about Slackware.

You need a Linux FTP server, to host a Slackware and a USB stick.

First you have to create a Slackware mirror by getting the script `mirror-slackware-current.sh` from Alien Pastures and running it. The script will put the mirror by default in the `/home/ftp` directory, which is exactly where you need it for the last step.

After this is done insert a USB stick, go to the directory

`/home/ftp/pub/Linux/Slackware/slackware-current/usb-and-pxe-installers`

unmount the USB if it is mounted and run the script to make a startup USB.

    /home/ftp/pub/Linux/Slackware/slackware-current/usb-and-pxe-installers
    dmesg |grep sd
    [86504.700524]  sdb: sdb1
    [86504.708517] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    umount /dev/sdb1
    sh usbimg2disk.sh -i usbboot.img -o /dev/sdb

Boot from the USB and install the Slackware. Here is the how to do it: http://www.slackbook.org/html/installation.html. Use a network cable (makes things easier) to connect the laptop to the network, you will need it anyway to access the machine during the configuration of the access point, and after as your uplink.

### 5.2. Kernel configuration

It is a good idea to start by recompiling your kernel. Click on .config to download my configuration file in `/usr/src/linux`. This is not a fully optimized version and only the processor is set to Intel Atom and some obviously unnecessary stuff is removed. I chose not to put here a version that is too customized to my needs. I used the `-j 8` option since it makes bzImage and modules faster. It seems `-j 8` gives the best results, but on the first compilation you will not have this advantage. Anyway it will take forever to compile even with the `-j 8` option. It is important not to forget to reinstall the MadWifi drivers, if someday you decide to optimize your kernel.

In case you want to keep Windows and resize its partition, the best solution is SystemRescueCd. Follow the instructions for installing it on a USB stick from here http://www.sysresccd.org/Sysresccd-manual-en_How_to_install_SystemRescueCd_on_an_USB-stick. It is a good idea to archive the partitions of your Aspire, in case you decide to return it back to the current state someday; if you can afford the space to keep the images.

### 5.3. Remote access - XDMCP

Depending on how comfortable you feel with the small keyboard and monitor of Aspire, you may consider enabling XDMCP. Here is good guide of how to do it: http://alien.slackbook.org/blog/running-x-window-on-ms-windows/. If you have CygWin already installed you would not need to install X-Server, simply run

xwin `-query` `Aspire.IP.address`

from a CygWin terminal.

### 5.4. For consideration:

FreeRadius http://freeradius.org/ - Formally RADIUS support is necessary only if you want the following capabilities: having WPA Enterprise authentication, being able to append more access points or authentication against external user data bases like LDAP or Novell eDirectory. It is also important to consider the choice between the standalone RADIUS server and the hostapd integrated RADIUS support. With so many choices, I thought it is a good idea to explain my arguments for choosing FreeRadius. First of all WEP in its 128 bit version is acceptable for home security, but it is so easy to configure that it takes away all the fun from the task. In its most basic configuration FreeRadius is really easy to install and configure, which means that obtaining WPA requires only a modest amount of effort. Configuring RADIUS is certainly not easy (it requires a lot of patience) and it may take days to set it up as a DAP gateway, but it is a five minutes work in the simplest scenario as in the example here with flat ASCII files. I suspect that using the hostapd integrated RADIUS allows for a lower CPU load than a separate RADIUS server and this has to be considered for small embedded routers. FreeRadius though has low processing requirements so the dedicated Aspire can easily run it.

If you opt for FreeRadius, you can download the latest version from http://freeradius.org/download.html. I used the freeradius-server-2.1.11 version. The installation is as simple as typing the command ./configure, make, make install. The following instructions can be used to configure RADIUS http://wiki.freeradius.org/Basic-configuration-HOWTO. If you used `./configure` without additional options the "`users`" file will be created in "`/usr/local/etc/raddb`".

- First, create some users, simply by appending at the end of the "user" file something like: `User1 Cleartext-Password := "password1" Second, change the "secret=12345:-)"`

- Second, change the "secret=12345:-)" statement in the `clients.conf.` No further actions are needed since all communications in this configuration are going through the looback address that is configured by default.

- Third, copy the `rc.radiusd` script from the `freeradius-server-2.1.11/scripts` to `/etc/rc.d/`. Run the first tests of your newly installed RADIUS server with "radiusd -X". Once you are satisfied, insert the line "/etc/rc.d/rc.radiusd start" in the `"/etc/rc.d/rc.local"` file. Create the file `"/etc/rc.d/rc.local_shutdown"`, make it executable and put the corresponding "/etc/rc.d/rc.radiusd stop" in it. From now on, if there are problems with RADIUS you will look in `/usr/local/var/log/radius`. There is also a lot of authentication related information in `/usr/local/var/log/radius/radacct/127.0.0.1`.

- Finally, the default self-signed certificates generated during the installation in `"/usr/local/etc/raddb/certs"` are good, but if you want your self-signed certificates to show something different you can generate your own. All of the certificates are located in the RADIUS sub-directory `"certs"`.

### 5.5. Necessary:

- MadWifi project

  http://madwifi-project.org/

- hostapd: IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator

  http://hostap.epitest.fi/hostapd/.

I used hostapd-0.7.3 and madwifi-0.9.4-r4167-20110827.

First, I installed MadWifi since there is a remark about hostapd in `README-WPS` mentioning that hostapd needs specifications about the location of the MadWifi libraries. All the instructions for installing MadWifi are found within the `INSTALL` file of the source. Look in the `README` file in the source for the necessary kernel configuration. Make the necessary changes in your kernel or simply use my kernel .config. The only thing not mentioned that I thought necessary to do is to enter "make install" at the end, simply to be sure all is on place.

Second I installed hostapd. Here comes the most sophisticated part of the whole installation. Within the source directory (wherever you extracted it), there is a subdirectory `hostapd`. You need a `.config` file in order to compile the file. Copy the `defconfig` file to the `.config` file in the same directory and then edit the `.config` file. Its editing depends on the configuration that you want to build and types of authentication that you plan to support. There are many important options that need consideration when editing the `.congif` file. For example, do you want RADIUS and if yes with what kind of support etc. These are the changes I made to my .config:

    CONFIG_DRIVER_MADWIFI=y
    CFLAGS += -I/tmp/2/madwifi-0.9.4-r4167-20110827 # change to the madwifi source directory
    CONFIG_DRIVER_NL80211=y
    CONFIG_WPS=y
    CONFIG_WPS_UPNP=y
    CONFIG_RADIUS_SERVER=y
    CONFIG_IEEE80211R=y
    CONFIG_DRIVER_RADIUS_ACL=y
    CONFIG_IEEE80211N=y

And here is the link to get my `.config` which I called "hostapd.config" to avoid confusion with the kernel `.config`. Copy it in the `hostapd` subdirectory and rename it `.config` and then "make", "make install". Change the path to the MadWifi libraries depending on your installation location choice.

    CFLAGS += -I/tmp/2/madwifi-0.9.4-r4167-20110827

I strongly recommend reading my file and also the `README` and `README-WPS` that are in the same directory even if you simply decide to use my configuration file. This will give you better understanding and may also spark ideas for interesting experiments. If you decide to dig deeper, check the dependencies between the variables in the `Makefile` "ifdef constructions". Follow the "Matrix" movie's advice and "Go to the source".

Create the `/etc/hostapd/` directory and copy in it at least the `hostapd.conf` file (do not confuse it with my `hostapd.config` it is a copy of my `.config` for `hostapd`) from the source directory. This is the changes for configuration (a.):

    #driver=madwifi
    #ctrl_interface_group=0
    #ssid=test
    ssid=Acer_A1
    hw_mode=g
    channel=11
    ieee8021x=1
    eapol_key_index_workaround=1
    nas_identifier=komsalov.homelinux.org
    auth_server_addr=127.0.0.1
    auth_server_port=1812
    auth_server_shared_secret=12345:-)
    acct_server_addr=127.0.0.1
    acct_server_port=1813
    acct_server_shared_secret=12345:-)
    wpa=1
    wpa_key_mgmt=WPA-EAP
    wpa_pairwise=TKIP
    wpa_group_rekey=300
    wpa_gmk_rekey=640
    bss=wlan0_0
    ssid=Welcome

You may need to copy some other files and eventually create some if you decide to change the configuration and of course fix the path to them in `hostapd.conf`. Here is my `hosapd.conf` for the network configuration (a.). It can be used as it is, the only absolutely necessary change is to put your RADIUS secret.

    auth_server_shared_secret=12345:-)
    acct_server_shared_secret=12345:-)

At first run hostapd in the terminal, like that:

    /usr/local/bin/hostapd -dd /etc/hostapd/hostapd.conf

You can either start directly with my file or with the example file from the source directory first. The example file will create one open network with ssid=test, giving you some confidence. It is a good idea to begin like this before setting up the DHCP server and eventually masquerading with the firewall. This will help you pinpoint the problems that need to be fixed. If you start two or more encrypted ssid's, DHCP, DNS and the firewall at once, it will be harder to identify the source of the eventual problems. It will also be good to test the configuration with any wireless client, but Windows, even a simple iPod would be better. Configuring Windows to work with RADIUS self-signed keys for WPA is a bit tricky and it is hard to pinpoint what gives you the problem, the client or the AP. There are two things you may consider here: to use CCMP instead of TKIP and to switch from WPA to WPA2. I decided to leave this decision for configuration (c.), because this is the one I will keep until I can afford to dedicate my Aspire to configuration (b.).

You can get the `rc.hostapd` from http://slackbuilds.org/repository/13.0/network/hostapd/, after you get bored looking on the hostapd in a terminal and running it manually. Put the `rc.hostpd` in the `/etc/rc.d` directory, fix the paths in it, call it from `/etc/rc.d/rc.local` and stop it from `rc.local_shutdown`.

At this state your rc.local should look like this:

    #!/bin/sh
    #
    # /etc/rc.d/rc.local:  Local system initialization script.
    #
    # Put any local startup commands in here.  Also, if you have
    # anything that needs to be run at shutdown time you can
    # make an /etc/rc.d/rc.local_shutdown script and put those
    # commands in there.

    /etc/rc.d/rc.radiusd start

    /sbin/ifconfig wlan0 up
    /sbin/iwconfig wlan0 channel auto

    route add default gw 192.168.1.1

    /sbin/ifconfig wlan0 192.168.11.1

    /etc/rc.d/rc.hostapd start

    /sbin/ifconfig wlan0_0 172.17.0.1

    /usr/sbin/dhcpd wlan0 wlan0_0

    #EOF

And your rc.local_shutdown:

    #!/bin/sh
    #

    /etc/rc.d/rc.hostapd stop

    /etc/rc.d/rc.radiusd start

    #EOF

The "/sbin/ifconfig wlan0 up ; /sbin/iwconfig wlan0 channel auto" commands in `rc.local` should not be necessary, but if you do not give them you will get an error when hostapd sets the channel.

Here is my simple dhcpd.conf file:

    authoritative;
    ddns-update-style none;

    default-lease-time 604800;
    # 7 days 7*86400

    max-lease-time 2592000;
    # 30 days 30*86400

    subnet 192.168.11.0 netmask 255.255.255.0 {
       range 192.168.11.10 192.168.11.100;
       range 192.168.11.150 192.168.11.200;

    option domain-name "mydomain.org";
    option broadcast-address 192.168.11.255;
    option routers 192.168.11.1;
    option domain-name-servers 192.168.11.1, 207.164.234.193, 207.164.234.129;

        }

    subnet 172.17.0.0 netmask 255.255.0.0 {
       range 172.17.0.10 172.17.255.250;

    option domain-name "mydomain.org";
    option broadcast-address 172.17.255.255;
    option routers 172.17.0.1;
    option domain-name-servers 172.17.0.1, 207.164.234.193, 207.164.234.129;

        }

    #log-facility local7;

I decided to have a caching DNS server on the Aspire; it is not mandatory, but it is necessary to put your DNS servers in the `dhcpd.conf`.

### 5.6. Optional programs:

Firewall builder by NetCitadel http://www.fwbuilder.org/ Having a firewall is not exactly an option, but you will have to do some NAT with iptables anyway. Of course you may do it manually but I strongly recommend Firewall Builder. It is from my point of view by far the best firewall management solution on the market and is free on Linux. Here is a simple script acerap.fw generated with it for the configuration (a.), as an example. On Slackware, download the source and compile it and then run ldconfig after using "make install".

Wireshark - http://www.wireshark.org/ Wireshark is unnecessary for the current configuration, but at some moment you certainly will want to know what is going on. As you are anyway in the process of downloading and compiling, install it to have it on hand when necessary. I recommend that you put at least "./configure --enable-threads" if no other option. It improves performance and the program remains stable.

## 6. Configuration (b.) - VLAN's and switches

For this configuration I used a Cisco Catalyst 2900 XL switch. I am on Bell Sympatico ADSL with SpeedStream 5360 Ethernet ADSL modem, which is actually only a bridge. It turned out that it does not matter how I configured the port of the Cisco Catalyst, it did not detect the SpeedStream. Finally, I gave up and used one small 5 port TrendNet TE100-SS/CA switch in between them. Since all SpeedStream 5360's are gone nowadays, you probably will not have this problem. DSL modems nowadays are actually routers and have integrated PPPoE support and for this configuration it is only necessary to VLAN the switch and eth0. I used a Cisco Catalyst (which is actually not so bad) only because this is what I managed to borrow, but if you are thinking of buying a switch look for something better.

I configured two additional VLAN's on it:

    I configured two additional VLAN's on it:
    VLAN Name                             Status    Ports
    ---- -------------------------------- --------- -------------------------------
    1    default                          active    Fa0/2, Fa0/3, Fa0/4, Fa0/5,
                                                    Fa0/6, Fa0/7, Fa0/8, Fa0/13,
                                                    Fa0/14, Fa0/15, Fa0/16, Fa0/20,
                                                    Fa0/21, Fa0/22, Fa0/23, Fa0/24
    2    VLAN0002                         active    Fa0/9, Fa0/10, Fa0/11, Fa0/12
    3    VLAN0003                         active    Fa0/17, Fa0/18, Fa0/19

Port FA01 is a tagged port. I am not giving the detailed commands to set it up, since they will depend on whatever switch model you have.

From the side of Linux it is really easy; type the commands:

    ifconfig eth0 0.0.0.0

(to remove the IP address from eth0)

    ip link add link eth0 name eth0.1 type vlan id 1
    ip link add link eth0 name eth0.2 type vlan id 2
    ifconfig eth0.1 up
    ifconfig eth0.2 up

Of course in "vlan id NN" the NN will have to be replaced with your VlanID. In my case the new IP addresses are set back like this:

    ifconfig eth0.1 0.0.0.0
    ifconfig eth0.2 192.168.1.55 netmask 255.255.255.0

If you like you can go with something more traditional like 192.168.1.1 for your future default gateway. I used eth0.1 as the uplink. If you want your physical wireless and wired networks to be in the same network, to mimic the behavior of the commercial routers, you can bridge eth0.2 and wlan0. Check configuration (c.) below for help with bridging. The only real reason you may want this is to use Microsoft ™workgroup network, though in this case you should consider installing Samba as a master browser on the Aspire.

In my case I had to setup PPPoE by running the `pppoe-setup` script. This will not be necessary for most people, but if it is for you than pay attention to the last question (asked by the `pppoe-setup` script) and answer it depending on the firewall management you choose. You may encounter additional MTU auto discovery problems with Internet providers such as Bell Sympatico. If it turns out that you are able to ping external machines, but browsing barely works if at all, you will have to use some commands like the next one in your firewall script:

    iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

In case you decide to use the Firewall Builder, it is only a matter of checking the check box "Clamp MSS to MTU" in firewall settings. If you want to know more about this problem check "Linux Advanced Routing & Traffic Control HOWTO".

I implemented the configuration with a manageable switch rather than the one with the USB to Ethernet converter, since to start with I have no such device. The second problem with such devices is actually making them work. Finally I have difficulties believing the advertised speeds of all USB to Ethernet converters that the manufacturers claim.

## 7. Configuration (c.) - bridging

I chose to stay with this configuration for now, since it allows me to pull my Aspire out of the network from time to time without loosing Internet connectivity. When travelling, I use my Aspire as a GPS device in combination with a USB connected satellite antenna.

These are the commands given in the necessary order placed inside the `/etc/rc.d/rc.local` file:

    #!/bin/sh
    #
    # /etc/rc.d/rc.local:  Local system initialization script.
    #
    # Put any local startup commands in here.  Also, if you have
    # anything that needs to be run at shutdown time you can
    # make an /etc/rc.d/rc.local_shutdown script and put those
    # commands in there.

    /etc/rc.d/rc.radiusd start

    /sbin/ifconfig wlan0 up
    /sbin/iwconfig wlan0 channel auto

    /etc/rc.d/rc.hostapd start

    /sbin/ifconfig wlan0_0 172.17.0.1

    /sbin/ifconfig eth0 up
    /sbin/ifconfig wlan0 up

    /usr/sbin/brctl addbr br0
    /sbin/ifconfig br0 up
    /usr/sbin/brctl addif br0 eth0
    /usr/sbin/brctl addif br0 wlan0

    /sbin/ifconfig br0 192.168.1.55

    /sbin/route add default gw 192.168.1.1

    /usr/sbin/dhcpd wlan0_0

    /etc/rc.d/firewall/acerap_br.fw
    /etc/rc.d/rc.traffic_shaping start

    /etc/rc.d/rc.bind restart

    #EOF

The part that concerns bridging is in bold. Bridging on Linux is really easy and it should not cause you any troubles. The spanning tree should be off as it is by default. Turn it on only if you really know what you are doing. The dhcpd is bound only to the wlan0 to serve 172.17.0.0/16 addresses to the Welcome network. The network with the Acer_A1 ssid is getting its IP addresses from the "Linksys SRX 200" DHCP server trough the bridge (it transfers broadcasts transparently). The `rc.traffic_shaping` script is for traffic shaping which turned out to be necessary, because some of the clients in Welcome misbehaved (see 6. Additional administrative tasks).

Of course you will need a firewall as well, so here is the acerap_br.fwb file created with the FWbuilder project and the script acerap_br.fw it generated, really basic, but a good starting point. I decided to switch to WPA2 after using this configuration for about one month. This required only a change of `wpa=1` in `/etc/hostapd.conf` to `wpa=2` and a restart of the hostapd. I was worried about the amount of work necessary to reconfigure all clients, but it turned out that only some small changes to the Windows clients are required.

## 8. Clients setup - WPA and WPA2 with self-signed certificates.

### 8.1. Linux.

Slackware comes with Wicd in `/Slackware/slackware-current/extra/wicd` directory and it works fine, so simply install it. Most other collections seem to be using NetworkManager, but anyway there are no problems.

### 8.2. Mac OS X 10.7.2

When I first tried to connect it showed a message stating that the certificate is not from a known authority and offered me a check box to accept it permanently, then it asked for the `username` and `password` and worked fine after. There is a key management program in Mac OS's utilities called Key Chain Access. Here I marked the certificate as trusted and it became green. I am not sure if this was necessary, but I wanted to be on the safe side. I found an instruction that recommended installing manually and in advance the certificate, but it turned out that Mac does it for you. When you decide to use WPA2 there will be no need to even touch a Mac. It detects the change in the access point and reacts accordingly by readjusting its settings and even reusing the `username` and `password` from the previous configuration.

### 8.3. Itouch.

I asked my son to do it, since I only have second hand experience with those devices. Besides I did not want to look for my glasses. It behaved the same way as the Mac, it asked me to accept the certificate and then asked me for the `username` and `password`.

### 8.4. Windows 7

Do not expect to get a question about the certificate at this point. You will have to install the certificate in advance by yourself. Go to `/usr/local/etc/raddb/certs/` to get it, I used a USB stick. The instructions, I found online, are to create the connection manually and install the certificate as soon as the network connection setuping wizard reaches the point of asking you for them. This did not help and Windows continued to complain about the certificate. I installed it through the Internet options section within the Control Panel, but this did not help either. I played with the check boxes "the best Windows approach isn't it?", and did some googling. Suddenly it worked and when I tried to connect asked me to accept the certificate (the same one which I installed and marked in advance as trusted in all the possible places!!!) This is the picture with the certificate's options.

As if this is not enough you need to do the same for all the users on each Windows machine, even with the same laptop the procedure for each user will be similar but unique. The only advice I have is to be persistent and it will work. If you google the problem you will find that some people simply got around the problem by buying certificates obviously it comes cheaper for big number of laptops, but maybe quitting Windows is better.

If you decide to use WPA2 Windows 7 will work fine, but it will not detect the change automatically. The properties change shown on the the picture above will work. The encryption should remain TKIP. Windows 7 will ask for the `username` and `password` and then it should work fine.

## 9. Additional administrative tasks you may consider necessary.

### 9.1. Limit bad clients - bit torrent.

It did not take more than a couple of days for around thirty of my neighbors to start using the open "Welcome" network. Most of them turned to being modest doing mostly mail and some surfing, but two or three bittorrent fans turned out to be a problem. If you decide to provide some Internet for your neighbors you certainly should do something about this problem.

You have at least two options: l7-filter from http://l7-filter.clearfoundation.com/ and ipp2p from http://www.ipp2p.org/. During one time or another I used both of them and the results are relatively similar. I still prefer ipp2p as I believe it is less CPU consuming. The project web page claims that the project is discontinued. This is not exactly true, it is only discontinued as a separate project for the external module. It was moved to patch-o-matic which is today defunct. Nowadays after netfilter.org discontinued patch-o-matic, it was moved to xtables-addons and netfilter.org is still support it. First, do not forget to install libmnl from http://www.netfilter.org/projects/xtables-addons/index.html and then the xtables-addons. Then you will need something like this:

        $IPTABLES -N Bittorrent
    $IPTABLES -t mangle -N Bittorrent
    $IPTABLES -t mangle -A PREROUTING -s 172.17.0.0/16 -m ipp2p --bit -j Bittorrent
    $IPTABLES -A INPUT  -s 172.17.0.0/16 -m ipp2p --bit -j Bittorrent
    $IPTABLES -A OUTPUT  -s 172.17.0.0/16 -m ipp2p --bit -j Bittorrent
    $IPTABLES -A FORWARD  -s 172.17.0.0/16 -m ipp2p --bit -j Bittorrent
    $IPTABLES -A Bittorrent  -j LOG  --log-level info --log-prefix "Bittorrent "
    $IPTABLES -t mangle -A Bittorrent  -j LOG  --log-level info --log-prefix "Bittorrent m "
    $IPTABLES -A Bittorrent  -j DROP
    $IPTABLES -t mangle -A Bittorrent  -j DROP

Most of these commands are unnecessary, just doing:

    iptables -t mangle -A PREROUTING -s 172.17.0.0/16 -m ipp2p --bit -j DROP

will do most of the job. You simply put it before the line

    iptables -A XXXXX -m state --state ESTABLISHED,RELATED -j ACCEPT

to get it working.

Anyway, do not expect too much from it, or from l7-filter for that matter. They will slow down bittorrent clients significantly, but both have problems recognizing encrypted connections. At least the bittorrent clients for sure will not be able to kill anymore all other connections. If you are not satisfied with the results of the solution just described you should combine it with traffic shaping (next paragraph).

### 9.2. Traffic shaping

The decision to spend time to setting up and fine tuning traffic shaping depends on: the type of Internet connection used, the number of clients you have, their behavior and most important, will you provide some Internet for your neighbors.

If you have a relatively fast and symmetric connection you have nothing to worry about, but if you are on something like ADSL and your provider has an illicit behavior than moving the queue to your machine makes a real difference. You can read about the reasons for getting control over your queue here "The Ultimate Traffic Conditioner".

It is important to mention that since "Linux Advanced Routing & Traffic Control HOWTO" was written, lots of things have changed, though probably the most important new thing in the field of traffic shaping is the "Intermediate Functional Block device". A lot of work has been done in the field and you have to be really careful when you are doing your own research since many of the online documentations and examples are outdated. Most examples will still work fine, but often better solutions have been developed.

My traffic shaping script had the following goals:

1. Move the queue to my machine.

2. Provide fairness between both my family clients and guests in the "Welcome" network.

3. Give a warranted advantage to my own clients, leaving the clients in "Welcome" with what is left, while at the same time warranting some bandwidth for Welcome even in moments of heavy load. My Internet connection is actually 99% unused anyway, but I did not want to listen to complaints from my family.

4. Have a method to separate clients that misbehave from the crowd.

Here is the resulting script rc.traffic_shaping. It does what I wanted it to, but is certainly not perfect and will require additional fine-tuning. Anyway you will have to readjust it to your conditions.

One important thing that needs to be mentioned is that limiting the outgoing traffic from a specific source, does not lead to proportional limitation to the incoming traffic. Most streaming protocols require small amounts of outgoing requests in order to get real floods of incoming video. As a result even class 1:13 (this is where baddies go), can seem too restrictive with its "rate 10kbit burst 15kbit", but it actually gives them around 600kbits of download speed. This demonstrates that in order to have precise control you need to shape incoming connections as well.

Next is the chart of outgoing traffic shaping.

The traffic goes as follow:

From Acer_A1 ->1:11
From Welcome -> 1:12
Bad clients -> 1:13
Between may cable clients and Acer_A1 -> 1:2

For example the traffic is classified by iptables with rules like this:

iptables -t mangle -A POSTROUTING -s 192.168.1.0/24 -d 192.168.1.0/24 -j CLASSIFY --set-class 1:2

You can see how I set the classes in "Policy: Traffic_Control" in `acer_br.pdf` or check the detailed syntax inside the `acerap_br.fw` script.

The next picture represents the chart of incoming traffic shaping.

The traffic goes as follow:

To Acer_A1 ->1:31
From Welcome -> 1:32
Bad clients -> 1:33 - nobody is there yet, but it is ready:-).
Between may cable clients and Acer_A1 -> 1:4

The first step in shaping the outgoing traffic is to get the ifb0 Intermediate Functional Block device" working. It turned out that the module does not load automatically, but I rather loaded it in the `rc.traffic_shaping` script by:

    /sbin/modprobe ifb
    ifconfig ifb0 up

The next problem is really interesting look at the part of the rc.traffic_shaping script pasted below:

    ##############################
    # It is necessary to mirror both eth0 and br0 to ifb0 in order to have both traffics
    # with destinations 172.17.0.0/16 and 192.168.1.0/24,
    # because each of them sees only one destination as outgoing.
    # You may check it by remarking one of the mirrors and the running WireShark on ifb0.

    tc filter add dev $DEV parent ffff: protocol ip prio 10 u32 \
     match ip dst 0.0.0.0/0 flowid 1: \
     action mirred egress redirect dev ifb0

    tc filter add dev br0 parent ffff: protocol ip prio 10 u32 \
     match ip dst 0.0.0.0/0 flowid 1: \
     action mirred egress redirect dev ifb0
    ##############################

The $DEV=eth0 is set at the beginning of the script. There is probably a better way of directing traffic to ifb0, but this is the only way that works for me. You will need the following commands, to investigate and adjust the script to your own needs:

    tc class ls dev eth0

    tc class ls dev ifb0

    tc -s -d qdisc show dev eth0

    tc -s -d qdisc show dev ifb0

    tc -s class show dev eth0

### 9.3. Cache DNS server.

Having a cache DNS server was a great advantage in the time when everyone thought that a 28'800 modem is lighting fast. With today's speed the percentage of economized bandwidth is close to zero, but it is so easy to install, and besides old habits die hard. Just make `/etc/rc.d/rc.bind` executable. Slackware has a `/etc/named.conf` pre-ready. It is a good idea to setup regular updates of named.root by simply creating the script `/etc/cron.monthly/named.root` and putting the following two commands in it:

    #!/bin/sh
    #
    /usr/bin/wget --user=ftp --password=ftp \
            http://www.internic.net/zones/named.root \
            -O /var/named/caching-example/named.root
    /etc/rc.d/rc.bind restart

### 9.4. Log configuration.

The dhcpd log can be moved to separate files by three simple steps:

Putting the next line at the end of the `dhcpd.conf`

    log-facility local7;

Append at the end of `/etc/syslog.conf` the line

    local7.*                   -/var/log/dhcpd.log

Create an empty dhcpd.log by:

    :> /var/log/dhcpd.log

Of course dhcpd and syslogd need to be restarted.

iptables log. It is a tempting idea to move the iptables log in a separate file if you use Firewall Builder or just enjoy having extensive logs from your firewall. The complication here comes from the limited choice of "`--log-level X`" available. As a result, the kernel (and not the iptables) is in reality doing all the filtering thus all logs go in log facility "kern.*". The choice for * is limited between those levels "0 emerg, 1 alert, 2 crit, 3 err, 4 warning, 5 notice, 6 info, 7 debug". Besides "crit" is the default level for `klogd` to send messages to the console so whatever goes on this level inevitably goes on the console as well. You may experiment with other levels or try changing "klogd -c 3" to something else.

Everything else is simple after these difficult choices are made.

First either change the log level setting in Firewall Builder, or if you wrote your own script set it to something like "`-j LOG --log-level warn --log-prefix "my log text"`".

After this is done, append at the end of `/etc/syslog.conf` the line:

    kern.=warn                  -/var/log/fwbuilder.log

and exclude it from

    *.warn;kern.!=warn;\
            authpriv.none;cron.none;mail.none;news.none        -/var/log/syslog

If you decide to experiment with other levels, for example "notice", change the line like this:

    kern.=notice                   /var/log/fwbuilder.log

But in the case of "notice" you will also have to exclude "kern.notice" from `/var/log/messages` by editing the related line in `syslog.conf` in a similar way yielding the line:

    *.info;*.!warn;kern.!=notice;\
            authpriv.none;cron.none;mail.none;news.none        -/var/log/messages

There is no perfect choice and some of your boot messages will always go to `fwbuilder.log` instead of going in to the messages or syslog files. The biggest problem are the eventual error messages generated during the normal course of work, which will be buried in the `fwbuilder.log`.

If you want see what else goes on in the /var/log/fwbuilder.log and iptables logs, the next command will help you:

    cat /var/log/fwbuilder.log |grep RULE -v

## 10. Some final words.

Over a month passed, since I started writing this document, while creating the access point took me only three days.

During the time being the AP did not drop one connection, while providing coverage over almost a 100 meter diameter. No timeout error messages occurred, which was so common for the "Linksys SRX 200" router.

Over 30 of my neighbors started using it more or less heavily and some really heavily.

For example, while writing this:

    root@acer:/var/log# cat /proc/net/ip_conntrack |grep tcp -c
    565
    root@acer:/var/log# cat /proc/net/ip_conntrack |grep udp -c
    76

And even in a moment of heavy load, like below, not only does the network remain stable, but it also provides a descent speed for everyone.

Now I have comprehensive log files like:

    Nov 21 21:29:49 acer kernel: [420579.216945] RULE 3 -- CONTINUE IN=wlan0_0 OUT=br0
           SRC=172.17.128.154 DST=173.194.31.138 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=58669
           DF PROTO=TCP SPT=49604 DPT=80 WINDOW=0 RES=0x00 RST URGP=0

All in all I am satisfied with the outcome. It was worth the effort, and the result surpassed the best of all my expectations.

# A. GNU Free Documentation License

## A.1. GNU Free Documentation License

Version 1.1, March 2000

> Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

## A.2. PREAMBLE

The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

## A.3. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you".

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

## A.4. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

## A.5. COPYING IN QUANTITY

If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

## A.6. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).

3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

4. Preserve all the copyright notices of the Document.

5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

8. Include an unaltered copy of this License.

9. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

11. In any section entitled "Acknowledgements" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

13. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version.

14. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

## A.7. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements."

## A.8. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

## A.9. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.

## A.10. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.

## A.11. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

## A.12. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

## A.13. HOW TO USE THIS LICENSE FOR YOUR DOCUMENTS

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

> Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License".

If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.