Netcfg2 + wpa_supplicant
i have a problem... i have a problem with me not knowing how to set up netcfg2 with wpa_supplicant...
netcfg2 profile:
CONNECTION="wireless"
DESCRIPTION="fer wlan"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa-config"
ESSID="FERwlan"
WPA_OPTS="-Dwext"
WPA_CONF="/etc/wpa_confs/fer.conf"
IP="dhcp"
my wpa_supplicant conf:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="FERwlan"
key_mgmt=IEEE8021X
eap=PEAP
phase2="auth=MSCHAPV2"
identity="asdf"
password="asdf"
when i start it with arch assistant, it detects the network but says something is wrong with my wpa_supplicant configuration...
wpa_supplicant works perfectly on its own, but i cant seem to use it with netcfg2.
i have a broadcom4311 wifi card, using b43 module...
plz help
with netcfg2 I don't need to set the wpa_supplicant.conf file...
I've only the profile file /etc/network.d/wireless (you can name this file however you want), and I can activate that profile with netcfg2 like this:
# netcfg2 wireless
where wireless is the name of my configuration file.
you can find many examples in /etc/network.d/examples
here the /etc/network.d/examples/wpa.example file
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="mynetwork"
KEY="SomePasskey"
IP="dhcp"
TIMEOUT=20
I've just replaced wlan0 with my interface, mynetwork with my essid, SomePasskey with my wpa password and saved it as /etc/network.d/wireless
After that, # netcfg2 wireless and I'm connected with my wifi router...
pretty simple, isn't it?
Last edited by gain (2008-05-21 23:36:21)
Similar Messages
-
Problems conecting to WPA security access point [solved]
I am trying to set up a wireless in my university (to the access point). I have IBM ThinkPad R61 notebook with Intel ipw4965 wireless card. I have installed ipw4965, iwlwifi, netcfg2, wpa_supplicant by pacman and I have succsesfully configured my home wireless with WPA security. Has anybody any suggestions what is wrong with my configuration?
University gives this information:
The example of .config:
CONFIG_IEEE8021X_EAPOL = y
CONFIG_EAP_MD5 = y
CONFIG_MSCHAPV2 = y
CONFIG_EAP_TLS = y
CONFIG_EAP_PEAP = y
The example of wpa_supplicant.conf:
network={
ssid="MIF"
eap=PEAP
key_mgmt=WPA-EAP
identity="my user name"
password="my password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
My configuration:
My wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="MIF"
eap=PEAP
key_mgmt=WPA-EAP
identity="my username"
password="my password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
My [mifwifi] (wireless profile in /etc/network.d/mifwifi):
DESCRIPTION="MIF wireless"
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="MIF"
USEWPA="yes"
IP="dhcp"
TIMEOUT=20
WPAOPTS=""
When I try to run [netcfg2 mifwifi] to set up university wireless I get the error similar to this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
Passprase must be between 8..63 characters
P.S. Sorry for my language mistakes, I just learning English.
Last edited by Edd (2008-02-07 07:56:10)Hello,
If you want to use your wpa_supplicant.conf file, you should set SECURITY="wpa-config" in your netcfg2 profile, and add WPA_CONF=/path/to/wpa_supplicant.conf (in the same file). The passphrase error is probably caused by the fact that netcfg2 is not reading your wpa_supplicant conf file, and there is no password defined anywhere else. -
Iwl4965, netcfg2 lease attempt failed
I'm trying to get my iwl4965 running with netcfg2, but i keep getting stuck on the actual connection/dhcp process. These are the packages i have installed:
core/wireless_tools 29-2 [installed]
Wireless Tools
core/iwlwifi-4965-ucode 228.57.2.21-1 [installed]
Intel wireless firmware for IPW4965 (iwlwifi driver)
core/wpa_supplicant 0.5.10-1 [installed]
A utility providing key negotiation for WPA wireless networks
core/netcfg 2.0.6-1 [installed]
Network configuration and profile scripts
test.profile:
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="no"
SECURITY="wpa"
ESSID="Meow"
KEY="mypasswd"
IP="dhcp"
TIMEOUT=20
iwlist wlan0 scan:
Cell 02 - Address: 00:19:CB:09:35:EE
ESSID:"Meow"
Mode:Master
Channel:7
Frequency:2.442 GHz (Channel 7)
Quality=85/100 Signal level=-48 dBm Noise level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=0000000c3c85d01a
when i issue a netcfg2 test.profile, it's status says BUSY and stays like that indefinitely. when i then press control-c i get an extra line saying the DHCP lease failed:
:: Meow up [BUSY]
^C - DHCP IP lease attempt failed [FAIL]
dmesg:
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:19:cb:09:35:ee
wlan0: RX authentication from 00:19:cb:09:35:ee (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:19:cb:09:35:ee
wlan0: RX AssocResp from 00:19:cb:09:35:ee (capab=0x51 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: deauthenticate(reason=3)
could it be something trivial i'm missing? i've used wireless without problems before using networkmanager, but i really would like to use netcfg2 instead.Hello, there seems to problems with this iwl4965-driver.
Those guys have similar problems:
http://bbs.archlinux.org/viewtopic.php?id=53300
and here is another problem with this driver described:
http://bbs.archlinux.org/viewtopic.php? … 42#p396142
So, it seems as these problems are related, so just try to use an older driver version. -
Wifi configuration (netcfg2/rc.conf) fails to "auto work on boot"
Hey :- ) ,
I have been trying to figure out how to configure my laptop to get associated AND receive its static ip "on boot". In short i have tried various configurations and different methods, but seems like with some of them i manage to get my wifi card an ip but let in the "not-associated-land" , while with others i get it associated with my wireless router but the interface cant get brought up, so i cant ping anything.Lets get the details here:
First of all, laptop's wifi card is the Intel Wireless Pro 4965 one, and the module used is the corresponding iwl4965.
Under simple manual editing of rc.conf the way described in the wiki wlan0 interface succesfully gets configured with the desired static IP plus the interface gets brought up succesfully on boot.Unfortunately though it is let in the "Cell: not associated" status.
Here you can see ifconfig wlan0 and iwconfig wlan0 after booting is completed:
ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:5A:4B:63
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"<myessid>"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Simply issuing :
iwconfig wlan0 mode managed essid <myessid>
gets everything working , but i need zero configuration connection on boot.So no joy.
and ifconfig wlan0 , iwconfig wlan0 looks like
ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:5A:4B:63
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::21d:e0ff:fe5a:4b63/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1609 (1.5 Kb) TX bytes:1897 (1.8 Kb)
iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"<myessid>"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:7F:84:8D:67
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality=100/100 Signal level=-44 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Under netcfg2 , using an edited version of the "complete.example" my wifi card gets associated with my AP on boot , but unfortunately it doesnt get brought up (according to man ifconfig , this happens when it fails to get an IP). In this case issuing :
ifconfig wlan0 up
iwconfig wlan0 essid <myessid>
gets everything working again .But still its not 100% automated.
Here i am posting my files.Some parts of it are commented/disabled to swap among netcfg2 configuration and manual rc.conf edited configuration.
here is my /etc/rc.conf network part file
HOSTNAME="robonoobs"
lo="lo 127.0.0.1"
#WLAN_INTERFACE=(wlan0)
#eth0="eth0 10.0.0.12 netmask 255.255.255.0 broadcast 10.0.0.255"
#wlan0="wlan0 10.0.0.12 netmask 255.255.255.0 broadcast 10.0.0.255"
#wlan_wlan0="wlan0 mode managed essid <myessid>"
#following /bin/sleep 5 is there just to get a chance to see messages without searching logs during #testing period
#echo "SLEEP 5"
#/bin/sleep 5
#WIFI_WAIT = 10
INTERFACES=(lo !eth0 !wlan0)
gateway="default gw 10.0.0.1"
ROUTES=(gateway)
# Network profiles are found in /etc/network-profiles
NET_PROFILES=(!wifi_init)
#complete found at /etc/network.d/
NETWORKS=(complete !wifi_init)
# DAEMONS
DAEMONS=(syslog-ng netfs !crond alsa !fam hal network net-profiles kdm)
here comes my netcfg2 profile named "complete"
CONNECTION="wireless"
DESCRIPTION="Very verbose complete wireless example"
INTERFACE=wlan0
HOSTNAME=robonoobs
# Interface Settings (use IFOPTS="dhcp" for DHCP)
IP="static"
IFOPTS="inet 10.0.0.12 netmask 255.255.255.0 broadcast 10.0.0.255"
GATEWAY=10.0.0.1
# DHCP Example
#IFOPTS=dhcp
#DHCP_TIMEOUT=20 # Default is 10.
#DHCP_OPTIONS="" # Extra arguments for dhcpcd
# DNS Settings (optional)
DOMAIN=robonoobs.domain.org
DNS1=10.0.0.1
DNS2=
SEARCH=
# Standard Wireless Settings
ESSID=<myessid>
SECURITY=none # One of wep, wpa, wpa-config, none
#KEY="SomePasskey"
# Scans to see if network is available before connecting (reccomended)
SCAN="NO"
#tried with this one set to "YES" with the same result, gets associated but is not brought up
# Time to wait to connect to a network. Default 15.
TIMEOUT=15
# Pass *custom* options to iwconfig. Usually not needed (optional)
IWOPTS="wlan0 mode managed essid $ESSID"
# Any extra arguments for wpa_supplicant
WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config
WPA_CONF=
# Commands to run at various stages of configuration
PRE_UP=
POST_UP=
PRE_DOWN=
POST_DOWN="some command"
here follows "iwconfig wlan0" right after booting is completed, which shows wlan0 associated with the AP in question:
wlan0 IEEE 802.11g ESSID:"<myessid>"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:7F:84:8D:67
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality=88/100 Signal level=-45 dBm Noise level=-127 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
here is ifconfig wlan0 right after booting up:
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:5A:4B:63
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
At this part i am only able to ping 10.0.0.12 .
Here ere are both of them after issuing ifconfig wlan0 up and iwconfig wlan0 essid <myessid>
ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:1D:E0:5A:4B:63
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::21d:e0ff:fe5a:4b63/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2072 (2.0 Kb) TX bytes:2160 (2.1 Kb)
iwconfig wlan0 essid <myessid>
wlan0 IEEE 802.11g ESSID:"<myessid>"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:7F:84:8D:67
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality=100/100 Signal level=-40 dBm Noise level=-92 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
At this point i can ping all my local network devices , such as my gateway at 10.0.0.1. but no internet "connect: Network is unreachable" after issuing
/etc/rc.d/network restart
everything is up and running and i have access to the net.This seems quite a puzzle to me, since restarting network should reset everything and i should be able to ping only 10.0.0.12 , no?
Thats it, unfortunately i didnt manage to get a workaround on that alone ...propably i am overlooking something obvious badly.
Any suggestions on how to fix this, or any other way on geting wifi completely working on boot without touching my laptop will be greatly appreciated.
IMGWell , since this issue got seriously on my nervers and took me a day trying things out with no luck, i studied a bit of shell programming and wrote a script to configure my net on boot, copied it with the correct permissions in /etc/rc.d/ , added it in my daemons at rc.conf, and there you go! Net on boot finally : -).
#!/bin/sh
echo "sleeping to ensure network is up"
/bin/sleep 2
until [ "$(ifconfig wlan0 | grep -c "UP")" != "0" ]
do
echo "waiting for wlan0 interface to get UP"
/bin/sleep 2
done
echo "checking if wlan0 is associated "
while [ "$(iwconfig wlan0 | grep -c "Access Point: Not-Associated")" != "0" ]
do
$(iwconfig wlan0 essid Virus_Home)
echo "sleeping for 20 seconds to give hardware some time to associate "
/bin/sleep 20
done
exit 0
However i dont concider my solution elegant , so if anyone can figure out why net doesnt get configured correctly on boot without my script i would love to know as well.
enjoy,
IMG -
Wpa_supplicant in wired network [SOLVED AGAIN]
Hi to all!
Here is a problem with using wpa_supplicant in wired network. My internet provider uses IEEE8021X EAP MD5 for authentication. Recently I used wpa_supplicant with another Linux and it worked. Here is my wpa_supplicant.conf:
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=MD5
identity="login"
password="password"
I used wired driver and all was working. Now in Arch I cant get internet connection. What I have to do to fix it?
Here is the problem solvation in Ubuntu. But in Arch there is no such directory /etc/network/ and file 'interfaces' in it. And I suppose that in Arch it must be different. Who did face same problem?
Thanks.
PROBLEM IS SOLVED. Internet connection works. I cant show files now, when I setup something with browser I'll show how I solved this problem. Now I must use MS XP for posting here [
Last edited by vennen (2008-04-02 09:46:33)My previous configuration did not work well, often I had to run wpa_supplicant and dhcp client manually (maybe always - it's possible it never worked ). After slight inspection of netcfg2 code, it seems that wired 802.1x is not yet supported natively, and I also realized why my config could not work. The following network profile is now working well for me. Someone might find it helpful.
# this is /etc/network.d/my8021x
CONNECTION="ethernet"
DESCRIPTION="My 802.1x wired connection"
INTERFACE=eth0
IP="dhcp"
DHCP_TIMEOUT=10
_WPA_CONF=/etc/wpa_supplicant_my8021x.conf
_WPA_TIMEOUT=5
PRE_UP="wpa_supplicant -Dwired -i$INTERFACE -c$_WPA_CONF -B; wpa_cli logon; sleep $_WPA_TIMEOUT"
POST_DOWN="wpa_cli -i$INTERFACE logoff; wpa_cli terminate"
.. and my /etc/rc.conf:
DAEMONS=(... ... net-profiles ... ...)
NETWORKS=(my8021x) -
Can't connect to my WPA AP using wpa_supplicant
Hi!
I've got a problem. I've been playing around with Archlinux trying to set up a small server using my laptop. Everything's been working fine and I've been able to get past any problems I've come across using the wonderful wiki. However, my wireless internet connection all of a sudden stopped working today. I've been messing some config files and I think I might have changed something I shouldn't. So I tried to start at square one again following the steps described in the wpa_supplicant wikipost. However, something's not working. After issuing the following command:
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
I still can't get an IP using dcphcd wlan0, it just says "timed out". Output:
[ola@stashbox wpa_supplicant]$ sudo wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf -d
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=wheel'
Priority group 0
id=0 ssid='porncave2'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:16:44:90:77:9a
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): b5 23 79 9f cb 59 5e 92 b2 8e 10 4f f7 27 8a 30
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Using existing control interface directory.
ctrl_interface_group=10 (from group name 'wheel')
Added interface wlan0
Daemonize..
[ola@stashbox wpa_supplicant]$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:16:44:90:77:9A
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[ola@stashbox wpa_supplicant]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
I'd be thankful if anyone could take the time to give me a few ideas as to how to proceed.AurosGamma wrote:
The process that i use every time that i want to get connected using wpa_supplicant:
# ifconfig eth0 down && ifconfig wlan0 up
You have to shutdown eth0 connection to avoid conflicts
# wpa_passphrase ESSID "PASSWORD" > /etc/wpa_supplicant.conf
Where ESSID is your wireless network name, and PASSWORD your router password
# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
-B to run as daemon, -D driver parameter using "wext" driver.-i interface "wlan0", -c specify configuration file /etc/wpa_supplicant.conf
For dhcp:
# dhcpcd wlan0
For static ip (you should try this one, maybe your router has dhcp option disabled)
# ifconfig wlan0 XXX.XXX.XXX.XXX
# route add default gw XXX.XXX.XXX.XXX
# echo "nameserver XXX.XXX.XXX.XXX" > /etc/resolv.conf
note: XXX.XXX.XXX.XXX must be the numbers (obviously) corresponding to your router configuration(for IP,GW,DNS), e.g. 192.168.3.110
The first command sets your ip
the second one sets your gateway
the third command sets the primary DNS
Try your connection, this procedure always work for me (on connections with WPA and WPA2 security protocols)
note: In your output says that wlan0 has no acces point associated, maybe a wrong router password? Try to reconfigure /etc/wpa_supplicant.conf
Thank you! Your post along with some tinkering made everything work the way they should -
Edit- As it turns out, even though I see a message stating that my WG311V3 supports WPA2 via ndiswrapper, that doesn't appear to be the case in practice. I guess WPA and a 20+ character random passworrd will do.
After bring down then up wlan0, I associate it w/ my AP and use wpa_supplicant. When I try to reconnect, I always timeout. W/ my router, I have WPA2 selected, using PSK and whatever passphase. There's a part for cipher type, and I've tried leaving it blank as well as selecting TKIP. Does anyone see anything wrong w/ the wpa_supplicant output/config, or anything else I'm missing? I'm totally in the dark w/ configuring this stuff.
#wpa_supplicant -dd -B -Dwext -i wlan0 -c/etc/wpa_supplicant.conf
Initializing interface 'wlan0' conf
'/etc/wpa_supplicant.conf' driver 'wext'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf'
-> '/etc/wpa_supplicant.conf'
Reading configuration file
'/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=5):
64 6c 69 6e 6b
dlink
proto: 0x2
key_mgmt: 0x2
pairwise: 0x18
group: 0x18
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='dlink'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for
the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18
enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:18:4d:70:43:04
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address -
hexdump(len=16): f4 d2 ce 7e 1d 74 52 56 a9 8b
8b 47 79 c1 7f 7b
WPS: Build Beacon and Probe Response IEs
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Response Type (2)
WPS: * UUID-E
WPS: * Manufacturer
WPS: * Model Name
WPS: * Model Number
WPS: * Serial Number
WPS: * Primary Device Type
WPS: * Device Name
WPS: * Config Methods (0)
WPS: * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
Daemonize..
Last edited by omgwtfbyobbq (2009-12-07 05:52:32)With the URL of the feed one can check it in iTunes and submit it to FeedValidator as a first-line method of locating problems. It's nearly impossible to read right through a long feed's text looking for the one tiny error which may have borked it. With both URLs it's much easier to check things - including whether iTunes is using the feed the originator thinks it is (not always the case).
If you've been getting quick updates in the Store you've been lucky; the Store checks feeds in some sort of rotation and so it depends where you happen to be in the cycle when you upload a change. -
Short wifi sessions with netcfg (was "Freeze due to netcfg2") [Solved]
Hey guys and girls,
I'm experiencing some problems with netcfg. This is kind of urgent since that's my parents' computer and I have to leave tomorrow (actually I already delayed my departure from today because of that).
Here is the problem :
[- I have to boot at least ten times for the computer to boot successfully, otherwise the boot process stops at "Wifi up" ("wifi" being the name of my profile).][doesn't seem true anymore with ndiswrapper]
- When it works, the network randomly stops working after a few minutes.
- After it worked (and fell), trying to stop net-profiles won't work : it will just print "Wifi down [BUSY]" up to nowhen, then any attempt to sudo anything (even vi) will fail (the prompt will just hang on), and shutting down process will also fail on this "Wifi down [BUSY]" thing.
The computer is up to date (that's actually part of the problem, no upgrade since at least six months and I didn't want to, but finally did because of mis-diagnosis…) with only stable repositories. Here are some useful config files and output :
rc.conf:
wlan0="wlan0 192.168.0.2"
INTERFACES=(lo wlan0)
ROUTES=(!gateway)
NETWORKS=(wifi)
network.d/wifi:
CONNECTION="wireless"
DESCRIPTION="wifi"
INTERFACE=wlan0
SCAN="no"
SECURITY="wep"
ESSID="whocares"
KEY="loose key"
IP="static"
IFOPTS="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
GATEWAY="192.168.0.254"
TIMEOUT=60
DHCP_TIMEOUT=60
(the timeouts don't work as the system freezes)
The router is a french "freebox" configured in dhcp, with a permanent 192.168.0.2 address dedicated to the MAC address of the computer, its address is 192.168.0.254 and it works well.
The wifi card is a Zyxel one with Realtek's RTL8185L chipset. It worked fine before the switch to netcfg, and I use ndiswrapper [it is worst if I use the "new" rtl8180 driver, see edit3].
So, any idea ? Thanks.
Edit : Oh, and logs are empty…
Edit2 : In case it could be related, I use pci=routeirq and edd=off at boot.
Edit3 : Additional problem I had with rtl8180 : "If I remove net-profiles from rc.conf' daemons list, starting manually netcfg2, netcfg-auto-wireless or net-profiles freezes the computer, forcing me to hard reboot]
Last edited by Skippy le Grand Gourou (2008-08-22 10:13:18)Still no idea ? I figured out that iwlist cannot scan anything [edit: well, not everytime…] (while the network is working):
$ iwlist wlan0 scan
wlan0 Failed to read scan data : Resource temporarily unavailable
And maybe this might help some guru :
$ iwpriv wlan0
wlan0 Available private ioctls :
ndis_reset (8BF0) : set 0 & get 0
power_profile (8BF1) : set 1 int & get 0
deauthenticate (8BF3) : set 0 & get 0
network_type (8BF2) : set 1 char & get 0
media_stream (8BF4) : set 1 int & get 0
reload_defaults (8BF7) : set 0 & get 0
I'm really hoping to hear from anybody soon… Thanks.
Last edited by Skippy le Grand Gourou (2008-08-21 19:58:30) -
Problem with wpa_supplicant unstable
Hello, I have some problems using wpa_supplicant. I didn't really noticed since when, because my router wasn't working for some time, but I suspect it was the upgrade to the kernel 2.6.32.
Anyway, my connection is too unstable, very slow most of times, but sometimes fast(between 0k/s to 1500k/s), and drop after a minute.
At the beginning, the connection is obtained slower than usual.
And after around a minute(sometimes more), I have in wpa_supplicant logs this message:
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b19 len=16
Received 799 bytes of scan results (2 BSSes)
New scan results available
Selecting BSS from priority group 1
Try to find WPA-enabled AP
0: 00:18:39:32:c5:81 ssid='linksys' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
selected based on RSN IE
selected WPA AP 00:18:39:32:c5:81 ssid='linksys'
Already associated with the selected AP.
In general, when I got this message after the connection(somtimes it's after the second time), the internet doesn't work anymore, even if the interface is still there, and iwconfig and iwlist scan shows the right information. There's no message in the logs, no error, no nothing. And I have to kill wpa_supplicant to reconnect.
I wonder if anyone have the same problem, or knows why I have this "wireless event".
My configuration is a Linux64, atheros card(DLink DWA547), using WPA2 security
In wpa_supplicant.conf:
network={
ssid="linksys"
proto=RSN
psk=xxxxxxx
priority=1
Here's the log of the connection
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
eapol_version=1
ap_scan=1
fast_reauth=0
Line: 509 - start of a new network block
ssid - hexdump_ascii(len=7):
6c 69 6e 6b 73 79 73 linksys
proto: 0x2
PSK - hexdump(len=32): [REMOVED]
priority=1 (0x1)
Priority group 1
id=0 ssid='linksys'
Initializing interface (2) 'ath0'
Interface ath0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1c:f0:5b:d8:0a
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): f7 e2 2f 2e e3 9d 51 47 9a e6 b8 17 a9 14 0e 90
WPS: Build Beacon and Probe Response IEs
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Response Type (2)
WPS: * UUID-E
WPS: * Manufacturer
WPS: * Model Name
WPS: * Model Number
WPS: * Serial Number
WPS: * Primary Device Type
WPS: * Device Name
WPS: * Config Methods (0)
WPS: * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface ath0
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Ignore event for foreign ifindex 3
Ignore event for foreign ifindex 3
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 440 bytes of scan results (1 BSSes)
New scan results available
Selecting BSS from priority group 1
Try to find WPA-enabled AP
0: 00:18:39:32:c5:81 ssid='linksys' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
selected based on RSN IE
selected WPA AP 00:18:39:32:c5:81 ssid='linksys'
Trying to associate with 00:18:39:32:c5:81 (SSID='linksys' freq=2462 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 2
WPA: set AP WPA IE - hexdump(len=28): dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00
WPA: using GTK TKIP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b04 len=16
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b19 len=16
Received 799 bytes of scan results (2 BSSes)
New scan results available
Selecting BSS from priority group 1
Try to find WPA-enabled AP
0: 00:18:39:32:c5:81 ssid='linksys' wpa_ie_len=26 rsn_ie_len=24 caps=0x11
selected based on RSN IE
selected WPA AP 00:18:39:32:c5:81 ssid='linksys'
Already associated with the selected AP.
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Wireless event: cmd=0x8b15 len=24
Wireless event: new AP: 00:18:39:32:c5:81
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:18:39:32:c5:81
No keys have been configured - skip key clearing
Associated with 00:18:39:32:c5:81
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:18:39:32:c5:81
RX EAPOL - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=2 type=3 length=95
EAPOL-Key type=2
key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
key_length=16 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 02 03 00 5f 02 00 8a 00 10 00 00 00 00 00 00 00 01 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:18:39:32:c5:81 (ver=2)
RSN: msg 1/4 key data - hexdump(len=0):
WPA: Renewed SNonce - hexdump(len=32): 69 01 18 59 3a c2 52 d7 26 3c db 92 51 7e 4b 97 d3 3e 0a a7 cf 32 9c 82 58 2f 8a eb 3d b6 6a af
WPA: PTK derivation - A1=00:1c:f0:5b:d8:0a A2=00:18:39:32:c5:81
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=48): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=121): 01 03 00 75 02 01 0a 00 00 00 00 00 00 00 00 00 01 69 01 18 59 3a c2 52 d7 26 3c db 92 51 7e 4b 97 d3 3e 0a a7 cf 32 9c 82 58 2f 8a eb 3d b6 6a af 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 a1 cc 03 76 20 64 f4 a5 77 2a b9 59 3d 52 d9 00 16 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
RX EAPOL from 00:18:39:32:c5:81
RX EAPOL - hexdump(len=203): 02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 02 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 41 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14 30 dc 3f 93 b3 15 ac 51 70 cb 6c c6 19 1c 79 00 68 c0 46 a1 2c f7 e0 e6 9b b6 b0 25 b1 7f 9b ac cc de 1f a4 ab 28 29 22 82 16 bd 12 4e 0d 12 c1 54 d4 58 9c 2d cc f1 f2 c2 f3 81 b7 0b f4 92 c2 69 73 31 d5 5b d6 7f 35 d1 40 1a 71 4d dc 58 b9 43 e7 69 d7 25 25 48 da ad 5c 2f 70 96 32 f2 24 ba 2f b6 9c 97 dc 34 f6 e4 37 4a 3d 41 ad 00 7c 6d 46 07 9f b6 c3 3f 9c a9
IEEE 802.1X RX: version=2 type=3 length=199
EAPOL-Key type=2
key_info 0x13ca (ver=2 keyidx=0 rsvd=0 Pairwise Install Ack MIC Secure Encr)
key_length=16 key_data_length=104
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 41 02 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 14 30 dc 3f 93 b3 15 ac 51 70 cb 6c c6 19 1c 79
WPA: RX EAPOL-Key - hexdump(len=203): 02 03 00 c7 02 13 ca 00 10 00 00 00 00 00 00 00 02 86 e5 80 cf 87 fc 5f 82 84 78 23 70 57 61 ae 6b da 1d 82 cc 29 0d a0 1c ea 55 f2 7d 30 4e 5f 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 41 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14 30 dc 3f 93 b3 15 ac 51 70 cb 6c c6 19 1c 79 00 68 c0 46 a1 2c f7 e0 e6 9b b6 b0 25 b1 7f 9b ac cc de 1f a4 ab 28 29 22 82 16 bd 12 4e 0d 12 c1 54 d4 58 9c 2d cc f1 f2 c2 f3 81 b7 0b f4 92 c2 69 73 31 d5 5b d6 7f 35 d1 40 1a 71 4d dc 58 b9 43 e7 69 d7 25 25 48 da ad 5c 2f 70 96 32 f2 24 ba 2f b6 9c 97 dc 34 f6 e4 37 4a 3d 41 ad 00 7c 6d 46 07 9f b6 c3 3f 9c a9
RSN: encrypted key data - hexdump(len=104): c0 46 a1 2c f7 e0 e6 9b b6 b0 25 b1 7f 9b ac cc de 1f a4 ab 28 29 22 82 16 bd 12 4e 0d 12 c1 54 d4 58 9c 2d cc f1 f2 c2 f3 81 b7 0b f4 92 c2 69 73 31 d5 5b d6 7f 35 d1 40 1a 71 4d dc 58 b9 43 e7 69 d7 25 25 48 da ad 5c 2f 70 96 32 f2 24 ba 2f b6 9c 97 dc 34 f6 e4 37 4a 3d 41 ad 00 7c 6d 46 07 9f b6 c3 3f 9c a9
WPA: decrypted EAPOL-Key key data - hexdump(len=96): [REMOVED]
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:18:39:32:c5:81 (ver=2)
WPA: IE KeyData - hexdump(len=96): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00 dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 dd 26 00 0f ac 01 02 00 61 5d c5 e9 0c 67 2d ad 05 07 6d 9d 42 5a 0a 52 ff 0b 0f 1e 05 63 1a 6c 57 53 c0 54 2b 20 2e 44 dd 00
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f 02 03 0a 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 77 12 f7 83 4a fc 6a 7d 57 b3 2d 50 cf e7 5f 9d 00 00
WPA: Installing PTK to the driver.
wpa_driver_wext_set_key: alg=3 key_idx=0 set_tx=1 seq_len=6 key_len=16
EAPOL: External notification - portValid=1
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RSN: received GTK in pairwise handshake - hexdump(len=34): [REMOVED]
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=2 tx=0 len=32).
WPA: RSC - hexdump(len=6): 41 02 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=2 set_tx=0 seq_len=6 key_len=32
WPA: Key negotiation completed with 00:18:39:32:c5:81 [PTK=CCMP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:18:39:32:c5:81 completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUP
Last edited by ondo (2010-03-16 22:09:08)Not solved, but my workaround was to downgrade to kernel 2.6.31+madwifi0.9.4096. Apparently there was nothing special to the suspicious message from the logs, as it was already there and it still works.
-
hey guys, I can't get netcfg2 to work on my machine... really annoying upgrade check this:
[network.d]% diff examples/wpa.example home
1,2c1,2
< CONNECTION="wireless"
< INTERFACE=wlan0
> CONNECTION="home"
> INTERFACE=eth1
5,6c5,6
< ESSID="mynetwork"
< KEY="SomePasskey"
> ESSID="Lebowski"
> KEY="foobar"
[network.d]% sudo netcfg2 home
> home is not a valid connection, check spelling or look at examples
Any ideas? Also, why do I have to specify CONNECTION="foo"? the filename is enough to get the name, no?
chris
Last edited by delmonico (2008-03-28 17:54:41)I can't get work netcfg2...
if I run
iwconfig wlan0 essid SpeedTouch5F3851 enc open s:LesPiTTareL
it works great, I can connect to my wireless network but...
if I configure my /etc/network.d/celadina in this way:
CONNECTION="wireless"
DESCRIPTION="Connessione wireless casa Bergamo"
INTERFACE=wlan0
ESSID=SpeedTouch5F3851
KEY=LesPiTTareL
SECURITY=wep
IP="static"
IFOPTS="192.168.1.70 netmask 255.255.255.0"
GATEWAY=192.168.1.254
and running
netcfg2 celadina
I get this error message
:: celadina up - Could not set wireless configuration [FAIL]
[root@Arials skioppetto]# "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.
I think the error is in SECURITY but I can0t find a solution... I've tried also with IWOPTS and if I don't
define SECURITY it doesn't give any errors but it can't connect becouse key remains off
I use rt61 wireless module; when I connect trough the first way I don't get any wep modules loaded even if it works...
I think the problem could be the kernel module.
What do you think about? -
I've written a script to support bash completion for netcfg2.
Here it is:
http://fatcat.ftj.agh.edu.pl/~sitarzm/A … on/netcfg2
Just download it and place it in /etc/bash_completion.d, log out and login again and give it a try.MAC!EK wrote:
Since the script was quite old I replaced it with a new version on that site:
http://fatcat.ftj.agh.edu.pl/~sitarzm/A … ion/netcfg
or
http://fatcat.ftj.agh.edu.pl/~sitarzm/A … on/netcfg2
uastasi if you want the completion to work with 'n' command add a line at the end:
complete -F _netcfg n
Awesome, thank you :) -
Wicd = Bad password, but wpa_supplicant connects fine
Hello.
I have a working wireless connection using wpa_supplicant and the network daemon, it comes up at boot fine. I'd like to use wicd instead but it won't connect. The config file that wicd generates differs from my working wpa_supplicant.conf but I don't see any way to override what it uses.
I'm running Arch64 and wicd-1.6.0-2.
My working wpa_supplicant setup:
$ cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
network={
ssid="mywireless"
scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk="this is secret"
priority=5
$ cat /etc/rc.conf
NETWORKS=(!dhcp_wired wireless)
DAEMONS=(syslog-ng hal network !wicd net-profiles netfs crond alsa)
The config that wicd generates when using WPA 1/2 (Preshared Key):
$ cat /var/lib/wicd/configurations/001d7eff6a78
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="<hidden>"
scan_ssid=0
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="this is secret"
$ cat /etc/rc.conf
NETWORKS=(!dhcp_wired !wireless)
DAEMONS=(syslog-ng hal !network wicd net-profiles netfs crond alsa)
Using WPA 1/2 (Passphrase) results in an unquoted hexidecimal psk, and still doesn't work.
Running wicd-client just gives a list of detected ssids in the logging, including:
ESSID : <hidden>
Any ideas how to get wicd connecting?
Thanks
UBobPlease file a bug report on the project site of wicd. It seems that this is an upstream issue. You can find a similar problem on the wicd forum here: http://wicd.net/punbb/viewtopic.php?id=591
Answer from one of the developers (the network card driver was a ath5k):
I think this is an issue with your wireless card drivers. Most do not deal well with hidden ESSIDs. Since hiding the ESSID gives you no advantage, you should just make the access point visible. That will solve the problem.
Daniel -
Hello, I am new to the forums and have run into a problem with wpa_supplicant and netcfg (though I believe the problem resides with wpa_supplicant).
A bit about me - This is my first "intermediate" linux distro (I tried fedora back when it was version 6 but didn't get terribly far with it). I have mostly been using Ubuntu (because it is out of the box and easy), but I ran out of use for an old laptop I had around and chose to install a minimalist distro on it (hence arch). The learning curve was a bit steep, but it is intersting and makes for a nice learning experience at the very least.
The problem:
I updated my system (which I do each time there is an available update on linux because it normally fixes things) on the 11th and everything was working great. However, my ip lease expired over the weekend (apparently) and as I am mostly a windows user (sorry, but it is true) I didn't notice it until today (when I went to check pacman for any updates and no longer had an internet connection).
It appears that the last round of updates I installed included updates for wpa_supplicant in them and changed the way things are supposed to be done in the /etc/wpa_supplicant.conf file. It looked like so beforehand (and still does though I have attempted to rewrite with the new format - sadly that hasn't worked out and I am here as a result):
network={
ssid="zelda"
psk=<... long key here> # note - Like I said, this was working before, I removed the key on purpose.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
And here is what I have attempted with my new wpa_supplicant.conf file:
network={
ssid="zelda"
psk=<... long key here>
scan_ssid=1
priority=1
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
Here are the steps I am taking to attempt and access the internet (manually):
sudo ifconfig wlan0 up
sudo wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
<wait a bit>
sudo dhcpcd wlan0
dhcpcd[2281]: version 5.2.12 starting
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquited
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: boradcasting for a lease
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquired
dhcpcd[2281]: wlan0: rebinding lease of <IP>
dhcpcd[2281]: wlan0: broadcasting for a lease
dhcpcd[2281]: wlan0: carrier lost
dhcpcd[2281]: wlan0: carrier acquired
dhcpcd[2281]: wlan0: rebinding lease for <IP>
dhcpcd[2281]: timed out
And if I attempt to use netcfg (in code because it uses spaces):
sudo netcfg zelda
:: zelda up [BUSY]
> WPA Authentication/Association Failed
[FAIL]
Here is my /etc/network.d/zelda file (like I said, this used to work. I haven't modified this file though):
CONNECTION='wireless'
DESCRIPTION='Home network'
INTERFACE='wlan0'
SECURITY='wpa-config'
WPA_CONF='/etc/wpa_supplicant.conf'
IP='dhcp'
Any help would be appreciated.
<edit>
Well, this is what I like to see. Apparently it wasn't as difficult as I was making it out to be, and the second wpa_supplicant.conf file I posted (the new one) works. I just had to do a reboot for it to notice the changes (though this does lead me to wonder if a daemon caches the wpa_supplicant entries...). It is all working now.
</edit>
Last edited by BetaWar (2011-05-18 23:55:22)trixrabbit wrote:
Then I use netcfg-menu to connect to the netowork.
My problem is I tried doing this again and I get : Please install 'dialog' to use netcfg-menu
You are trying to use netcfg-menu.
The error message is telling you that you need to install the "dialog" package to use netcfg-menu.
Solution: install the "dialog" package (pacman -S dialog).
edit: You can also use netcfg without the dialog package. For example, "netcfg -u <profile>", "netcfg -l". See "netcfg --help" for more options.
10PinkPanther wrote:Wiki says that dialog is needed in some cases.Do you see your network when you run wifi-menu?
Last edited by Xyne (2012-12-02 19:12:18) -
[SOLVED] systemd+wpa_supplicant, but the name of interfaces changes
Hello,
I'm following instructions here for having the wireless connection ready at boot on my machine.
I needed to setup two different daemons since sometimes my wireless interfaces is wlp3s0 and sometimes is wlan0.
When the name of the interface is wlp3s0 everything works fine and I'm correctly given an IP address.
It doesn't happen the same when the name is wlan0.
Here's some output
$ systemctl status [email protected] -l
● [email protected] - Wireless network connectivity (wlan0)
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead)
Jun 22 16:10:19 banzi systemd[1]: Dependency failed for Wireless network connectivity (wlan0).
$ cat /etc/conf.d/network-wireless@wlan0
address=192.168.1.10
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/conf.d/network-wireless@wlp3s0
address=192.168.1.8
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/systemd/system/[email protected]
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
ExecStart=/usr/bin/ip route add default via ${gateway}
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
What more info do you need?, what's wrong?
Thanks,
Giuseppe
Last edited by giuscri (2014-06-28 19:53:35)Check your journal for messages relating to wlan0 and wlp3s0. I think you may find some kind of error message -- maybe having to do with firmware. I've seen thing like that break predicatible device names
If you've just one wlan interface, you could turn off predicable device names and just go with wlan0 -
Need a volunteer to correct WPA_supplicant page
As the title suggests.
The existing wiki article is woefully out-of-date, and I have no experience with wpa, or I would do it me-self.
I'd greatly appreciate it if anyone is feeling up to modernizing and cleaning it up, as it is quite wordy at this point.
Thanks!
http://wiki.archlinux.org/index.php/Wpa … This_FirstMisfit, I do use WPA a lot, since I have a doble-bridge and router WL-network arrangement at home (with that, I got 500 mts. of range with 90% of the signal). I must clarify that I'm not an expert with WPA, but I know how to handle most of the problems. I got an athereos, a ralink and a few dlink cards, so I know to make my way along the different drivers that wpa_supplicant handles. Also, I created a tiny patch to solve a few of the most common wicd issues.
The problem, probably, is that the english isn't my "default" language. If you wish, I can write a little bit about the WPA and it's configuration, but I'm going to need some help with the language itself.
ok. That's all, I hope my help might be useful.
Maybe you are looking for
-
Hi, I have a sequece for a table value. I have the following code to retrieve the sequence value. protected void create(AttributeList attributeList) { ApplicationModule am = getDBTransaction().getRootApplicationModule(); DBSequence dS = new DBSequenc
-
I DON'T WANT TO UPGRADE OR HAVE AN ADD ON EVER, DISABLING UPDATES DOES NOT WORK, HOW DO I KILL ALL MESSAGES FOR UP GRADES AND ADD ON'S FOR EVER, ONCE AND FOR ALL, COMPLETELY, THE END AND NEVER BE BOTHERED AGAIN EVER! ALSO IF I KILL MYSELF I WILL HOLD
-
How to fetch the correct netprice based on contract item conditions
Hi, When you display a contract using ME33K and you click on a item and view its conditions(shift+F6), there might be 2 validity periods for a given item. and each period will have different netprice in it. Let me describe the same. Suppose the PO cr
-
Human Task service not working
Hi helping hands, I recently stepped into BPEL world. I created a human task for approve & reject, when I try to run this in BPEL engine, its giving me orabpel-10561 error and the msg: creator is empty. I tried to find this error code,however I wasnt
-
Airport Express problems solved
My first post so excuse any stuff ups. I have spent three days reading through a myriad of problems on various forums that AX users are having. My three week old MacBookPro 15inch Duo core has worked well until a few days ago when the wireless connec