[dundee] eee bygum

[jamie]

Hi all, been looking at hooking the Asus EEE to a WPA enterprise secured
network. (I don't have one but was asked and looked into it --cause i
might). There are two problems --According to eeeuser
wpa_supplicant.conf is rewritten every restart by the GUI wireless
handler. This would need disabled or rewritten to suit our needs or in
hacker fashion by passed by scripting a program to re-write the file
post boot to what we need.
The wifi chipset in use is the bang up to date AR5007EF lovely except
the usual delay in getting out drivers -- currently supported by latest
madwifi driver but the latest AR5K(opensource) isn't yet advised. Posts
indicate Asus has modified its code for this driver but others report
working links after reflashing with UBUNTU and FEDORA so i suspect it is
just a pre-release image that worked and the latest driver is OK.
Another 'Feature' wpa enterprise is present but as mentioned above the
wpa_sup.conf file needs re-writ every start. Another convenience ASUS
provided was the lack of MSCHAPV2 second level authentication compiled
into wpa_supplicant. This is an old version (circa2005) and may not have
it as an option anyway, Cvs 5.5/5.6 had MSCHAP in their later guises but
very flaky. it would probably advisable to compile a new wpa_supplicant
v 6.X. 


Except ASUS has not provided a complete set of kernel headers much less
kernel sources. This would have to be attempted using standard ones and
crossed fingers? Apparently there are a few different minor kernel
versions in use which may make things interesting. 

Hope this of use to someone with small parts. Sorry its a bit dry but
hey ho

The regex presentation could inform the basis of a shell script to
rewrite wpa_supplicant.conf after start up so this will make the next
meeting more interesting.