802.1x PEAP protected authentication problems

Dimitime · 09-21-2008, 12:52 AM

Ok so, I'm at the University of Florida and they use an 802.1x authentication for their wired (and I'm assuming wireless) internet connection. I can't get this to work on anything save Ubunutu.

On Ubuntu, the university provides instructions on editing files and such, but some of the files are ubuntu-specific files that aren't on other distro's (for example, they tell me to edit /etc/NetworkManager/dispatcher.d/01ifupdown). I have a slew of other problems with ubuntu and would really prefer not to use it.

I tried installing xsupplicant but i keep having issues installing it, and I'm pretty sure you can do it with wpa supplicant but i have no idea.

I really want to be able to connect to the internet using slackware or openSUSE or Fedora, or really anything other than Ubuntu.

Sorry if i didn't provide enough information, this is my first post =/

Dimitime · 09-23-2008, 04:23 AM

Ok... so no replies. Here's my wpa_supplicant.conf file, along with what happens when i run it in the terminal...

wpa_supplicant.conf :

Code:

# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample
# for many more options that you can use in this file.

# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant

ap_scan=0
network={
  key_mgmt=IEEE8021X
  eap=PEAP
  identity="username"
  password="password"
  phase1="peaplabel=0"
  phase2="auth=MSCHAPV2"
}

terminal stuff:

Code:

root@darkstar:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant.conf -d
Initializing interface 'eth0' 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'
ap_scan=0
Priority group 0
   id=0 ssid=''
Initializing interface (2) 'eth0'
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
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Operation not supported
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1d:72:64:17:69
wpa_driver_wext_set_wpa
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
Added interface eth0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added
ioctl[SIOCGIWESSID]: Operation not supported
Could not read SSID from driver.
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth0' added

I honestly have no clue what's going on. I see something about drivers not being supported, but it seems to me that that's not the only issue..

I'm running Slamd64 12.1 (64 bit port of Slackware).

Dimitime · 10-06-2008, 02:56 AM

...Ok do apparantly this is the most impossible thing to do in the world?

Also, I'm not sure why it got moved to the wireless section, since I'm trying to set up an 802.1x wired connection.

Ok, so since no one's posted any sort of answer, I'm gonna spew out more information that may or may not help anyone help me with this, I'm just kinda getting desperate here.

So this is how you're supposed to do it, according to my school.

Code:

Step 1

Edit /etc/rc.local to remove any line mentioning wpa_supplicant or dhclient if a previous tutorial was used.



Step 2

Paste the following into /etc/wpa_supplicant/wpa_supplicant.wired.conf, correctly replacing the username and password.



ctrl_interface=/var/run/wpa_supplicant

ap_scan=0

network={

key_mgmt=IEEE8021X

eap=PEAP

identity="gatorlink username"

password="gatorlink password"

phase1="peaplabel=0"

phase2="auth=MSCHAPV2"

}



Where it says identity="gatorlink username" please add your Gatorlink user name between the quotes. Where it says password="gatorlink password" please add you Gatorlink password between the quotes. Save the file and close gedit.



Step 3

Run sudo chmod 600 /etc/wpa_supplicant/wpa_supplicant.wired.conf



Step 4
Edit /etc/NetworkManager/dispatcher.d/01ifupdown and add the following after the line 'export VERBOSITY="0"'.

IEEE8021X_INTERFACE="eth0"
if [ $IFACE = $IEEE8021X_INTERFACE ] ; then
 export  IF_WPA_DRIVER="wired"
 export  IF_WPA_CONF="/etc/wpa_supplicant/wpa_supplicant.wired.conf"
fi



Step 5

Reboot the computer.

That's what it says to do for Ubuntu Gutsy and below. It looks like the same steps should work for other linux distros, except that /etc/NetworkManager/dispatcher.d/01ifupdown isn't in any other distro that i've used, so does anyone know what the equivalent file would be in Slackware?

Hangdog42 · 10-06-2008, 08:27 AM

Quote:

It looks like the same steps should work for other linux distros, except that /etc/NetworkManager/dispatcher.d/01ifupdown isn't in any other distro that i've used, so does anyone know what the equivalent file would be in Slackware?

For Slackware, I think the first step might be to start up wpa_supplicant and then use dhcpcd to request an IP address. I'm not sure that anything more than that would be required.

If you're looking for a more GUI route, take a look at wicd, which I believe will handle this sort of stuff. There is a script to build it at Slackbuilds.org that works exceedingly well.

Dimitime · 10-30-2008, 07:08 PM

Well, it fails epically at the run wpa_supplicant phase, which leads me to believe that getting an IP address using dhclient won't work, since running wpa_supplicant doesn't work. As for wicd, I can't for the life of me figure out how exactly to install or use it. All the "installation instructions" kinda just say "Install it." Which isn't horribly helpful.

Hangdog42 · 10-31-2008, 08:29 AM

Quote:

Well, it fails epically at the run wpa_supplicant phase, which leads me to believe that getting an IP address using dhclient won't work, since running wpa_supplicant doesn't work.

You're assumption about getting an IP address is right. Care to enlighten us as to the details of the epic fail?

Quote:

As for wicd, I can't for the life of me figure out how exactly to install or use it. All the "installation instructions" kinda just say "Install it." Which isn't horribly helpful.

If you're using Slackware, download the Slackbuild script and the source code from Slackbuilds.org. When you unpack the Slacbuild tarball, it will create a directory. Move the wicd source code into that and then as root, run wicd.Slackbuild. That will compile the program and create a Slackware package in /tmp that you can install with installpkg. An even easier route is to download sbopkg which is an ncurses front end for Slackbuilds.org and makes compiling Slackware packages a breeze. Once you have wicd installed, you have to start the daemon (in Slackware you should get /etc/rc.d/rc.wicd that starts the daemon) and then when you start your gui, run wicd-cient to get the GUI interface.

Dimitime · 11-04-2008, 12:16 AM

All right so I kinda sorta got it to work.

What I figured out was that in my command that I used to run wpa_supplicant I didn't tell it that I was using a wired connection (by adding -D wired at the end). So when I ran:

Code:

wpa_supplicant -B -ieth0 -c/etc/wpa_supplicant.conf -D wired

and then

Code:

dhclient eth0

That worked. For some reason though it won't work again... and I'm not sure why.

Hangdog42 · 11-04-2008, 08:15 AM

For Slackware, try use dhcpcd instead of dhclient. In my experience dhcpcd is a MUCH better DHCP client that dhclient.

Dimitime · 11-05-2008, 09:23 PM

Awesome dhcpcd worked. Thank you so much guys!