|From:||Tony D'Amato <...>|
|To:||Gary Vollink <gmail>|
|Date:||May 30, 2006 6:48 AM (CDT)|
I've used your page above with great success. Yes, I upgraded to
unstable package wpasupplicant 0.4.8-4 the other day and my setup
broke. It seems that my /etc/wpa_supplicant.conf file was renamed to
/etc/wpa_supplicant.conf.dpkg-bak and the init script was removed.
After a bit of cursing, I read the documentation in
/usr/share/doc/wpasupplicant and found a workaround - they include a
replacement init script (unsupported, of course) here:
According to NEWS.Debian.gz in the main doc directory:
Copy the file into the /etc/init.d directory and make it executable:
cp /usr/share/doc/wpasupplicant/examples/wpasupplicant.roaming-daemon \ /etc/init.d/wparoamd chmod +x /etc/init.d/wparoamd
The init daemon must be altered to suit your persnal configuration. Edit the
script so that INTERFACE, CONFIG and DRIVER are defined, then make sure the
init daemon begins with the following commands:
update-rc.d wparoamd start 15 2 3 4 5 . stop 90 0 1 6 . invoke-rc.d wparoamd start
Please note to copy it as 'wparoamd' and NOT 'waproamd' !! The later
is a completely different package!
Once this was done, I was able to get my setup working again by
copying my wpa_supplicant.conf file into /etc/wpa_supplicant (a new
directory) and following the directions in the new wparoamd script.
I'm using an Atheros-based PC card, and here are the changes I made to
the wparoamd script:
--- /usr/share/doc/wpasupplicant/examples/wpasupplicant.roaming-daemon 2006-04-29 17:30:53.000000000 -0400 +++ /etc/init.d/wparoamd 2006-05-29 07:39:21.000000000 -0400 @@ -9,7 +9,7 @@ # To activate the wpasupplicant daemon, set ENABLE_ROAMING_MODE to 1 -ENABLE_ROAMING_MODE=0 +ENABLE_ROAMING_MODE=1 # Location of the wpa_supplicant.conf configuration file to be used # by the daemon. @@ -21,7 +21,7 @@ # Failure to set CONFIG to the full pathname of your configuration # file will cause the daemon to exit immediately. -CONFIG="" +CONFIG="/etc/wpa_supplicant/wpa_supplicant.conf" # Specify the network interface that the daemon will attach to. # @@ -31,7 +31,7 @@ # Failure to set INTERFACE to a valid network interface name will # cause the daemon to fail or exit immediately. -INTERFACE="" +INTERFACE="ath1" # DRIVER specifies the driver type of the interface defined above. # @@ -46,7 +46,7 @@ # ipw = Intel ipw2100/2200 driver (linux kernels 2.6.13 or older only) # wired = wpa_supplicant wired Ethernet driver -DRIVER="" +DRIVER="madwifi" # End user defined section
I hope this info helps someone else... if you want to credit me, just use my name please... thanks!
"Beer is living proof that God loves us and wants us to be happy."
-- Benjamin Franklin