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.