wpa_supplicant -u
dbus_bus_request_name[dbus]: Resource temporarily unavailable
Could not request DBus service name: org.freedesktop.DBus.Error.AccessDenied Connection ":1.7887" is not allowed to own the service "fi.epitest.hostap.WPASupplicant" due to security policies in the configuration file.
Failed to initialize wpa_supplicant
-----------------
./networking force-reload
Error : No address associated with hostname
Error : No address associated with hostname
Error : No address associated with hostname
Error : No address associated with hostname
Error : No address associated with hostname
Error : No address associated with hostname
Error : No address associated with hostname
eth0: unknown hardware address type 24
wifi0: unknown hardware address type 801
eth0: unknown hardware address type 24
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:11:f5:9c:e3:ea
Sending on LPF/ath0/00:11:f5:9c:e3:ea
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database.
This program is free software. You can distribute it
and/or modify it
under the terms of the GNU General Public License ve
rsion 2.
Alternatively, this software may be distributed unde
r the terms of the
BSD license. See README and COPYING for more details .
Interactive mode
> <2>CTRL-EVENT-DISCONNECTED - Disconnect event - re move keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remo ve keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remo ve keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remo ve keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remo ve keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remo ve keys
> <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
------------------------
x3dre - 10.10.2006, 22:15 Uhr Titel: FAQ-id_cat-140.html help :)
I have been working through . The section of
"A log of /sbin/wpa_action's actions is created at /var/log/wpa_action.log, please attach the log when reporting problems" there is no log file of this sort in the directory...
Is FAQ-id_cat-140.html upto date for RC 4 release or is it for Debian or earlier RC versions to follow though and work?
kelmo - 11.10.2006, 13:13 Uhr Titel: RE: FAQ-id_cat-140.html help :)
/usr/share/doc/wpasupplicant/README.modes.gz is the definitive document.
x3dre - 11.10.2006, 13:52 Uhr Titel: Re: RE: FAQ-id_cat-140.html help :)
kelmo hat folgendes geschrieben::
/usr/share/doc/wpasupplicant/README.modes.gz is the definitive document.
Is there an easy way to read this document, apart from untarring it manually and read it's contents ?
Many Thx
horo - 11.10.2006, 14:32 Uhr Titel: Re: RE: FAQ-id_cat-140.html help :)
F3 in mc (midnight commander) will do.
Ciao Martin
x3dre - 11.10.2006, 15:14 Uhr Titel: RE: Re: RE: FAQ-id_cat-140.html help :)
Thx Martin
x3dre - 11.10.2006, 23:36 Uhr Titel: RE: Re: RE: FAQ-id_cat-140.html help :)
I think something in the cvs tree for Madwifi, that has changed in the working RC3 release, that has changed in the RC4 release, which is screwing up the way netcardconfig configures the interfaces and wpa_supplicant.conf file. Even with the http://ftp.us.debian.org/debian/pool/no ... -1_all.deb applied it's made no difference to the getting the configuration to work.
kelmo - 12.10.2006, 01:01 Uhr Titel: RE: Re: RE: FAQ-id_cat-140.html help :)
x3dre, do you want to discuss this issue here? or privately via email? Makes _no_ sense to me to do both.
Having said that, its not sufficient to just install that package, you must replace your existing madwifi modules by making a new set of modules for your kernel. In my email to you, i pointed to the file that explains that process briefly, although I do not expect that it will be an easy process for those new to it.
x3dre - 12.10.2006, 12:12 Uhr Titel: Atheros Chip Set *SOLVED*
Here's what I had to do with the help of kelmo
1. Configure the networking in netcardconfig as per the router settings needed for the clients connecting to it.
ping router address & outside world. More than likely you will not be able to ping the outside world but may be you might be abled to ping the router intermittently... Though both may not work..
3. Do a : dpkg -l | grep module-ass to check if you have the module-assistant already installed : do; apt-get install module-assistant or it is possible to download http://ftp.us.debian.org/debian/pool/ma ... .6_all.deb
4. Do a : dpkg -i madwifi-source_
5. Do a : dpkg -i module-assistant
6. Do : su - and then m-a a-i madwifi this will do the modules needed for the kernel to build in the new madwifi wireless modules.
7. Reboot - when the rebooting is finished, in the bottom right hand corner there should be the two little red lights on. Therefore allowing router & world access to all protocol net bound.
This process worked for me, with great help from Kel & related documents...
Many Thx
DeepDayze - 12.10.2006, 14:57 Uhr Titel: RE: Atheros Chip Set *SOLVED*
Great that it worked out for you...hopefully will help others with the same card. Eventually there should be a fixed package released