zero3k/xsupplicant

Mirror of the XSupplicant (Open1X) Project on SourceForge

xsupplicant's Issues

Dynamic WEP key

Originally posted by Andrew Torry on the Bug Tracker for it on Sourceforge:

The current development version 2.2.1 does not support a wireless connection to an SSID that provides a dynamic WEP key.
Cisco WISM controlled WiFi networks that are 802.1x enabled require the use of a dynamic WEP key.
This WEP key is unknown to the end user and so cannot use XSupplicant to connect to the SSID since XSupplicant demands the
user enter the WEP (40 HEX digits) key.
Microsoft built-in supplicants report 'WEP key is provided' but XSupplicant is not honoring this.

No wireless adapters found x64 2.2.2.504

Originally posted by Mark Holmes on the Bug Tracker for it on Sourceforge:

Supplicant installs on Windows 7 x64 (with all latest OS updates and latest drivers for Intel WiFiLink 1000BGN wireless card)

Installed from xsupplicant-setup-v2.2.2.504.x64.exe

Reports 'no network adapters found'

XSupplicant Trouble Ticket.zip

Scanning error

Originally posted by Nicholas Hughes on the Bug Tracker for it on Sourceforge:

I set the NetworkManager with 'Enable Network' and without the 'Enable Wireless'.
Then when trying to scan I got the following in a window:

QT disconnect() API failed
From class: Emitter
SLOT: '2signalScanCompleteMessage(const QString &)
To class: SSIDListDlg
SIGNAL: '1wirelessScanComplete(const QString &)'

and:

QT disconnect() API failed
From class: WirelessScanDlg
SLOT: '2scanCancelled()
To class: SSIDListDlg
SIGNAL: '1cancelScan()'

but it still detected the networks. When I scanned again I didn't get this messages anymore.
I'm sending the file 'log output 1' which has the logfile output but I don't know if it's useful.

log output 1.txt

eap_types/md5/md5.c:169: bad call to memset ?

Originally posted by dcb on the Bug Tracker for it on Sourceforge:

eap_types/md5/md5.c:169:23: warning: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to dereference it? [-Wsizeof-pointer-memaccess]

memset(ctx, 0, sizeof(ctx)); /* In case it's sensitive */

Maybe better code

memset(ctx, 0, sizeof(ctx)); / In case it's sensitive */

Tray icon doesn't work correctly

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

On Linux, the tray icon will change to green when the authentication is a success. However, it never changes back to any of the earlier colors when an authentication fails, or is disconnected.

Help doesn't work in Mac OS X UI

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

When clicking the "Help" button in the UI, the following error pops up:

The help file '/Users/terry/Desktop/SeaMonkey/xsupplicant-ui/build-debug/XSupplicantUI.app/Contents/MacOS/Docs/xsupphelp.html' was not found. You may need to reinstall the application.

certificate files directory

Originally posted by Ludovic on the Bug Tracker for it on Sourceforge:

Where do I have to put the two files called cert.cer and key.pem
that contain the certificate in DER format and key in PEM format
repsectively.
I didn't find anything in README.certificates

Best regards,
Ludovic

UI can leave configuration bits behind

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

If you have an EAP-TLS connection already configured, then edit it and change it to a TTLS connection, and rename that connection to something else the profile and trusted server blocks remain in the configuration. This doesn't cause any real issues, but it does leave a bit of a mess in the configuration file.

Linux build DHCP failure

Originally posted by w1relessm0nkey on the Bug Tracker for it on Sourceforge:

Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

XSupplicant svn 634

The supplicant authenticates properly w/ WPA, PEAP /MSCHAPv2, but does not appear to ask for a DHCP lease. Manually running dhclient on the interface, after association and authentication, appears to work and I am able to access the network. UI does not change status from "Connecting" to "Authenticated" or "Connected", despite being authenticated and connected.

Debug logs contain no useful data, repeating only "[DOT1X_STATE] Tue Apr 28 14:57:06 2009 - Clock tick for 'wlan0'! authWhile=0 heldWhile=0 startWhen=0 curState=AUTHENTICATED"
Once per second.

jf

Windows build fails to handle interface disable/re-enable

Originally posted by Bob Ziuchkovski on the Bug Tracker for it on Sourceforge:

The Windows build of xsupplicant fails to handle situations where a wireless interface is disabled while connected and then subsequently re-enabled. After this sequence, the UI still shows the wireless interface as connected, even though the connection is not established and is lacking an IP. If you then click "Disconnect", two error dialogues appear:

1. Error: Failed to set the SSID for interface Intel(R) PRO/Wireless 2200BG Network Connection - Teefer2 Miniport.
2. Error: Failed to set the 802.11 infrastructure mode for interface Intel(R) PRO/Wireless 2200BG Network Connection - Teefer2 Miniport. Please be sure that your wireless card drivers are current.

All subsequent attempts to connect to the wireless network show additional copies of the error dialogues above. If you then quit out of xsupplicant, agreeing to terminate connections, and re-open the application, these error messages display again. The problem is resolved after rebooting Windows.

Additional information:

• Versions of xsupplicant tested: 2.0.1 / 2.1.9
• Windows version: XP SP3, all MS updates applied as of 2009/12/11
• Wireless adapter: Intel(R) PRO/Wireless 2200BG
• Wireless network configuration: WPA2-Enterprise, AES, PEAP/MSCHAPv2
• Reason for disabling/re-enabling wireless: We use the NicSwitch util (http://www.netswitcher.com/NicSwitch/nicswitch.htm) to ensure only one physical connection is active at any given time. This is needed to allow transparent switching between wired/wireless while maintaining a single IP address assigned by DHCP.

Wrong outer identity

Originally posted by Jeff Fern on the Bug Tracker for it on Sourceforge:

I'm configuring a WPA2 enterprise connection with EAP-PEAP. What I want is for the outer identity to be exactly the same as my credentials username, however I want to be able to enter this at connect-time (not confiuration time).

If I leave the outer-identity blank and select 'prompt for credentials', I get the popup box when I try and connect however the outer identity is set as anonymous.
If I leave the outer-identity blank, select 'store credentials and enter my username/password at configration time', the outer-identity is populated with the stored username.
If I enter my username in the outer-identity and select 'prompt for credentials' then I get the popup box when I connect, and everything works.

Should there not be an option to say 'prompt for credentials and use that username as my outer-identity'?

eduroam connection

Originally posted by Nicholas Hughes on the Bug Tracker for it on Sourceforge:

After I created a profile for the eduroam I tried to connect and got an error saying that the network was not found. When I tried to edit the profile to check the network's name it was saying that the network was in use, even thought the main window had nothing indicating a connection.

FAST anonymous provisioning is weird

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

In order to get FAST anonymous provisioning to work with ACS you need to configure the supplicant to use FAST-GTC. Technically, GTC shouldn't be allowed during provisioning, but for some reason it is. :-/ Need to fix this.

Machine auth doesn't always kick in

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

It has been reported that there are cases that the machine authentication doesn't connect as expected.

Can't configure 802.1X with WEP

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

There doesn't seem to be a way to configure 802.1X with WEP anymore.

PEAP/EAP-GTC x EAP-FAST/EAP-GTC

Originally posted by an anonymous user on the Bug Tracker for it on Sourceforge:

At my radius server I have configured it to work with PEAP/EAP-GTC, each user has a user name and password. On other supplicants like NetworkManager, I'm able to successfuly authenticate. When using Xsupplicant, I try two different settings:

EAP-PEAP/EAP-GTC
-> This won't work because xSupplicant doesn't allow me to set a user password, only username. I don't know why this happens.

EAP-FAST/EAP-GTC
-> Even though I can specify the username and password, this authentication type isn't supported by the radius server because I have configured there EAP-PEAP/EAP-GTC.

Concluding, it seems that the implementation of EAP-PEAP/EAP-GTC isn't correct at XSupplicant, mainly because I can't specify username and password. On other supplicants it is allowed and the authentication works as expected.

Mac OS X interface names should print pretty

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

Interfaces for Mac OS X currently show up in the UI in raw *NIX format (en0, en1, etc).

It would be better to show these interface names in a format that Mac OS X users are familiar with, such as in the Network System Preference pane.

See attached screenshots of both the XSupplicant UI configuration window and of the network preference pane for details.

• Terry

WPA encryption type can't be changed

Originally posted by Aaron Smith on the Bug Tracker for it on Sourceforge:

I added a wireless network connection, and selected "Other" instead of a visible network. On the next screen, where I specify the SSID and encryption configuration, I chose WPA2-Enterprise (and other WPA selections). The encryption type is greyed out and hard-set to TKIP. I like AES :~). BTW -- client is Windows XP SP3.

Crashes on Mac OS X

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

Steps to reproduce:

Remove configuration file.
Open UI.
Open supplicant.
sudo chmod 777 /tmp/xsupplicant.sock

A dialog pops up about /etc/xsupplicant.conf not being readable, and asks if the user has permission, then the UI crashes.

xsupplicant.log
xsupplicant_crash_macosx.log

Issue with using it on Windows Server 2003

I am running into an issue with using it on Windows Server 2003. Both the wired and wireless connections are being detected after being installed. After rebooting, only the wired connection is being detected by it.

ReactOS support

It would be nice if you all helped get it working on ReactOS (http://www.reactos.org) and also possibly add it to its source and have it be used as the default wireless manager in it.

EAP-FAST anonymous provisioning with Hostapd can break

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

EAP-FAST authentication with hostapd will fail after the PAC has expired. (Still need to gather more details on what is wrong.)

New gcc in Fedora does not permit implicit DSO linking

Originally posted by Tom 'spot' Callaway on the Bug Tracker for it on Sourceforge:

Hi,

In Fedora 13, gcc no longer does "indirect" linking of required
objects/libraries by default. As a result of this, XSupplicant failed to
build with the new gcc. I have attached a basic patch that gets things
working again.

For more information about this issue, please see:

https://fedoraproject.org/wiki/UnderstandingDSOLinkChange

Here's a patch which fixes the issue that he also included:

xsupplicant-2.2.0-implicit-DSO.patch.zip

Some well-known unusable devices need blacklisting

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

Some interfaces which we'll never be able to use for 802.1X should probably be blacklisted.

This includes interfaces such as gif0, and stf0 on Mac OS X (and possibly others. fw0?)

There are likely other interfaces on Linux (and Windows?) that should be blacklisted.

It might be best to try and call an IOCTL on each platform and key off of the interface type and/or capabilities.

• Terry

Generated date is missing from Mac OS X configuration file

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

This is probably due to some stubbed in function in Mac OS X (and possibly Linux) which needs to be properly implemented.

Mac OS X skin directory placement is broken

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

Currently Mac OS X requires that the skins be placed in:

XSupplicantUI.app/Contents/MacOS

This is incorrect behavior on the platform.

The correct place would be in /Library/Application Support or perhaps in the same directory as XSupplicantUI.app

• Terry

Login window button text is truncated in Mac OS X

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

The login window button text is truncated in Mac OS X.

vista 32 : no connection to wpa2 enterprise

Originally posted by Alain Bonis on the Bug Tracker for it on Sourceforge:

Hello,
Xsupplicant fails to connect to a eduroam wpa2 ccmp eap-ttls/pap network. The aruba nas logs show no assoc request coming from the laptop wireless card mac address. I can connect to our un-encrypted network through Xsupplicant UI.
On this laptop ( dell vostro 1510), I connect fine to eduroam on Linux with wpa_supplicant, as well as on win vista using Intel wireless tools.
I Hope you find some clue in the attached trouble ticket.
Regards.
Alain Bonis,
Junior network administrator
Université Paris Ouest Nanterre La Défense.

XSupplicant Trouble Ticket3.zip

BSOD in usbehci.sys after transferring lots of data

When running XSupplicant 2.2.3.553 and transferring lots of data in a Windows XP VM ran via VirtualBox, I get a IRQL_NOT_LESS_OR_EQUAL BSOD caused by usbehci.sys. I am attaching the minidump that was made when it crashed.

Mini070220-01.zip

OPen 1x protocol layer not installing

Originally posted by Chris Wiseman on the Bug Tracker for it on Sourceforge:

I have installed XSupplicant 2.2.3.553 on a Dell Lattitude E5420 running Windows 7 Enterprise 64 bit. The wireless card installed in the machine is the DW1530 Wireless-N WLAN Half-Mini Card (Broadcomm). When I try to connect with xSupplicant, I receive an error “Unable to locate any network adapters in the system. You will not be able to connect to any networks.” In the network properties for the DW1530 I have found that the Open1x 802.1x Protocol Layer is not listed. I have uninstalled and reinstalled xSupplicant several times.

I have attached the Troubleticket.

XSupplicant Trouble Ticket.zip

error starting a scan

Originally posted by Alain Bonis on the Bug Tracker for it on Sourceforge:

Hello,
I installed xsupplicant 2.2.1.487 on a Dell vostro 1510 laptop running vista 32 bits sp2 home premium ed.
Right after the install the U.I is displaying the different ssid's within reach of the laptop. This enabled me to configure the wpa2 ttls/pap connection to the eduroam network we use in our university.
Though, when I hit connect, nothing happens, and the radius server doesn't see any access request coming in.
Moreover, after a reboot, the U.I doesn't display no networks, and hitting browse and refresh doesn't make any good.
I've tried with various versions of the Intel wireless driver, but the results are the same.
I' m ready to provide more info and to do more testing, and I hope we can overcome this problem, as there is a real need for a vista/7 free supplicant.
Thank you for your work.
Regards.

XSupplicant Trouble Ticket.zip

support EAP-TLS client wired on embedded system based FreeRtos + Lwip

Originally posted by Leonid Shigris on the Bug Tracker for it on Sourceforge:

Hello,

We should support EAP-TLS client side wired.
Our system based FreeRtos V.10 + LWIP 2.1.2 .
MCU: NXP IMXRT-1060.

I'm new in this topic.

Pls advise.

Kind Regards,

Leon.

UI can't connect to IPC on Mac OS X

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

The UI can't connect to the IPC channel on Mac OS X by default.

Mac OS X uses root/wheel for the user/group when creating the socket, but the UI apparently doesn't start up with the wheel group.

A quick workaround to bypass this for testing purposes is to sudo chmod 777 /tmp/xsupplicant.sock

• Terry

UI pegs CPU and leaks memory, then crashes in some cases

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

If the supplicant disappears out from underneath the UI in Mac OS X, then the UI will peg the CPU and leak memory until eventually crashing.

Need better error messages on soft sims

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

If the SoftSIMs fail, the error messages that are returned are non-sense. This needs to be fixed to return something useful.

Windows 10 support

It would be nice if it worked properly on Windows 10 x64. It installs without any errors but its UI is reporting that it cannot detect any network adapters.

Direct RADIUS mode doesn't work

Originally posted by Chris Hessing on the Bug Tracker for it on Sourceforge:

Direct RADIUS mode won't build and work.

Please ship a larger icon and a one line summary for XSupplicantUI

Originally posted by Richard Hughes on the Bug Tracker for it on Sourceforge:

Hi, my name is Richard Hughes and I work at Red Hat. I'm trying to build a distro-neutral framework to make installing applications easier. At the moment I'm trying to contact various upstream authors asking them to do things to make their software show up. I've got support from a number of distros, KDE, XFCE and GNOME, but I also need some degree of maintainer buy-in. Already there are over 1000 applications listed in the metadata, and over 25% of them supply the nice-to-have AppData file with screenshots.

XSupplicantUI does have a few of small issues. It currently ships a very small application icon, which is too small to be padded to 64x64. It also doesn't have a "Comment=" one line description in the .desktop file.

Would you perhaps consider shipping a larger icon and adding the one-line "Comment"? To be included your application needs to ship an icon of at least 48x48px, and ideally 64x64px with an alpha channel. Additionally, please consider writing and installing an AppData file with the application description and some screenshots, otherwise your application will look kinda bare in the GNOME and KDE Software Centers. We'd also love to showcase more applications, but without the extra data file we can't.

See http://people.freedesktop.org/~hughsient/appdata/ for details about AppData and AppStream, or if you have any other questions please don't hesitate to ask; thanks!

Richard

Xsupplicant and ThinClient

Originally posted by Stefan Pavlov on the Bug Tracker for it on Sourceforge:

First of all I need to import System Event Notification (SENS) registry from normal Windows XP (they are missing from embedded windows).
Then after install xsupplicant (and on every uninstall/install) I need to import and xsupplicant registry too, which is not full.
Reboot. On making new connection xsupplicant try to save xsupplicant.user.conf on Z:\ drive which is RAM Drive for ThinClient (Need to be C:). Then on reboot I need to make new connection again because this.

============
Wired (EAP-MD5)
HP ThinClient
WinXP Embedded
version: xsupplicant-setup-v2.1.nightly.578.exe

Panda antivirus drivers

Originally posted by Ismael Rodriguez Espigares on the Bug Tracker for it on Sourceforge:

It seems there's trouble with Panda's NDIS drivers. The supplicant recognizes them as an adapter instead of the real adapter or something, and program prompted that this device can't be configured and that is not available.

XSupplicant Trouble Ticket.zip

Default linux install directory is missing version

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

When installing the Linux version the BitRock installer's default install location is "/opt/xsupplicant-". It seems like this should be "/opt/xsupplicant-2.2.0" or some such.

UI text output looks hideous on Mac OS X.

Originally posted by Terry Simons on the Bug Tracker for it on Sourceforge:

The UI log window output looks really bad on Mac OS X - pretty much unreadable.

This is probably due to the window being set up to use a font that is not available on Mac OS X. May affect other platforms as well.

• Terry

Open1X 802.1X Protocol Layer not bound to interface

Originally posted by Graeme Lawes on the Bug Tracker for it on Sourceforge:

The problem was first evident when I opened the xsupplicant program and recieved the error "Unable to locate any network adapters on the system".

I followed the steps in the mailing list conversation here: https://sourceforge.net/mailarchive/message.php?msg_id=26723606
Here is the output of "sc query open1x" from step one:
SERVICE_NAME: open1x
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

I then checked for the Open1X 802.1x Protocol Layer in the device properties of my wireless card, it was not present (not present on wired either).

My machine is an Alienware M15x running Windows 7 x64 Professional.

My wireless card is Intel WiFi Link 5300 AGN using the intel drivers provided by dell at (sorry for huge URL):
open http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R213215&SystemID=ALW_LP_M15X&servicetag=&os=WV64&osl=en&deviceid=15758&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=0&libid=5&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=304444

attached is the trouble ticket generated by xsupplicant

GUI crash upon auth failure

Originally posted by Aaron Smith on the Bug Tracker for it on Sourceforge:

Configured for EAP-TTLS/PAP/WPA2 authentication to a FreeRADIUS server with OpenLDAP database. I misconfigured FreeRADIUS when testing LDAP failover, which resulted in an auth rejection from FreeRADIUS. When all retries were exhausted, the GUI closed and the tray icon disappeared. If I fired it back up, everything appeared to be running, and still trying to authenticate. Open1x debug and FreeRADIUS output attached. BTW -- client is Windows XP SP3.

XSupplicant Trouble Ticket.zip
freeradius_dbg.zip

Wireless connection; subsequent crash

Originally posted by Zack Greywolf on the Bug Tracker for it on Sourceforge:

Attempted to create a wireless connection using wpaeap with TTLS protocol. Could not create a wireless network that would successfully connect. Attempted to create a second wireless connection using wpa2eap, however there was still no connectivity. Attempted to use Wireshark to check authentication process, but no authentication occurred. After attempting to re-connect multiple times with wpa2eap configuration, UI subsequently crashed.

Unsecure network

Originally posted by Nicholas Hughes on the Bug Tracker for it on Sourceforge:

I tried to connect to an insecure network and, after double clicking on it, I go to the main window where nothing happens (at least in the foreground). This is similar with what happens when I try to connect to the eduroam.