Bugzilla – Bug 130256
XSupplicant is exiting after authentication
Last modified: 2005-11-07 15:02:16 UTC
Hello I have configured Xsupplicant (the one, that comes with SuSe 10). I am not sure, what is wrong, but I can't get it working. This is how I do : floyd:/var/log # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:"test" Nickname:"test" Mode:Managed Frequency:2.437 GHz Access Point: xx:xx:xx:xx:xx:xx Bit Rate=11 Mb/s Tx-Power:25 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Security mode:open Power Management:off Link Quality:100/100 Signal level:-46 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:11 Invalid misc:24461 Missed beacon:0 floyd:/var/log # ifconfig wlan0 up floyd:/var/log # ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx UP BROADCAST NOTRAILERS RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:742 errors:0 dropped:0 overruns:0 frame:0 TX packets:685 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:64131 (62.6 Kb) TX bytes:81575 (79.6 Kb) Memory:fcfec000-fcfedfff floyd:/var/log # xsupplicant Starting XSupplicant v. 1.0.1! floyd:/var/log # cat xsupplicant.log Interface wlan0 initalized! Connection established, authenticating... Authenticated! floyd:/var/log # ps -aef | grep xsupplicant root 11544 6656 0 11:50 pts/0 00:00:00 grep xsupplicant floyd:/var/log # xsupplicant You can only run one instance of XSupplicant! If you are sure that no other copy of XSupplicant is running, please delete /var/run/xsupplicant! floyd:/var/log # cat /var/run/xsupplicant 11583 floyd:/var/log # ps -fp 11583 UID PID PPID C STIME TTY TIME CMD floyd:/var/log # It looks like xsupplicant is not running after authentication. Is it how it should be ? I can't get DHCP working after xsupplicant confirmed authentication. What's wrong ? Strace for xsupplicant (child process) ends : write(1, "Authenticated!\n", 15) = 15 munmap(0x40019000, 4096) = 0 munmap(0x40017000, 4096) = 0 exit_group(0) = ? Looks like it stops after authentication, thus my DHCPCD can't get an IP address. With best regards Martynas
Any particular reason for not using wpa_supplicant?
Hello I was used to configure Xsupplicant for PEAP-MSCHAPv2 authentication. It is working well with latest Xsupplicant version. I expected it to work with default for Suse Xsupplicant installation if it is available as part of package. Why it should exist if it is not working ?... But Xsupplicant is definetly not mandatory. Probably I need to check how to configure WPA supplicant for PEAP-MSCHAPv2 type authentication and switch to this this software. With best regards Martynas
Maybe the old version of xsupplicant didn't work properly (at least, with the configuration you need). I did update xsupplicant for openSUSE, but I don't think an xsupplicant YaST Online Update is necessary as xsupplicant does not get used often imho. So I'm closing this as wontfix. wpa_supplicant should support PEAP. Maybe even the configuration generated when configured the interface with YaST works. If not, also custom wpa_supplicant configurations are supported by ifup (see 'man ifcfg-wireless').