WPA help please :)

pinniped · 09-25-2008, 09:02 AM

Well, I can't see "wlan_tkip" in your list of loaded modules. Stop wpa_supplicant (wpa_action ath0 stop), load 'wlan_tkip' (modprobe wlan_tkip), then restart the ath0 interface and see if it connects.

I also noticed you have another 80211 stack and Broadcom drivers loaded - do you have multiple wireless devices? If not, you should prevent unnecessary drivers from loading; usually they are harmless but sometimes they interfere with other drivers.

okos · 09-25-2008, 10:19 PM

Guys, thank you for your patience:
Still not working

Quote:

root@# wpa_action ath0 stop
bash: wpa_action: command not found
root@# modprobe wlan_tkip
root@# /etc/rc.d/rc.inet1 ath0_restart
/sbin/dhcpcd: not running
Polling for DHCP server on interface ath0:
Broadcasting DHCP_DISCOVER
timed out waiting for a valid DHCP server response

I get an error when checking the status:

Quote:

root@# wpa_cli -i ath0 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

Please excuse my ignorance but am I missing something here?

What is wpa_ctrl?

Quote:

I also noticed you have another 80211 stack and Broadcom drivers loaded - do you have multiple wireless devices? If not, you should prevent unnecessary drivers from loading; usually they are harmless but sometimes they interfere with other drivers.

I thought I had blacklisted the broadcom. It seemed to cause problems in the past. I added the following to the /etc/modprob.d/blacklist:

Quote:

# Deprecated BCM43xx driver. List it here so it won't conflict with
# b43 or b43legacy drivers.
# Blacklisting bcm4309, b43, ath5k for madwifi and ssb are my doing
blacklist bcm43xx
blacklist bcm4309
blacklist b43
blacklist ath5k
blacklist ssb

okos · 09-25-2008, 10:24 PM

I will see if my wife's computer will connect wireless this weekend and let you know the results. She uses xp

Alien Bob · 09-26-2008, 02:35 AM

Quote:

Originally Posted by okos

I get an error when checking the status:

Quote:

root@# wpa_cli -i ath0 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

Please excuse my ignorance but am I missing something here?

What is wpa_ctrl?

It appears that wpa_supplicant is not even running. The "wpa_ctrl" is the communication socket over which it is possible for the wpa_cli program to talk to the wpa_supplicant daemon. The error indicates that wpa_supplicant is not operational, which could mean an error in your /etc/wpa_supplicant.conf file.

Or, if you are still using

Code:

WLAN_WPADRIVER[1]="madwifi"

in your /etc/rc.d/rc.inet1.conf, you should change it now to

Code:

WLAN_WPADRIVER[1]="wext"

Eric

pinniped · 09-26-2008, 04:29 AM

Well, your lsmod shows that the bc* drivers are loaded - can you unload them and move them somewhere where the system can't find them so that they don't load?

One post I read claimed that wlan_tkip and wlan_xauth should both be loaded; perhaps you should try what you did before but load wlan_xauth again (I have no idea if that will work because I don't know if wlan_auth is used by clients or only by an Access Point).

Alien Bob pointed out that you might not have wpa_supplicant running either - I don't know how Slack has that all set up (I use Debian and it's all run without user intervention via the networking scripts). So you might have to start wpa_supplicant directly (as in a previous post).

okos · 09-26-2008, 08:21 PM

Alien Bob,

Thanks for the reply. I changed as shown in a previous post.

Quote:

# Config information for ath0:
IFNAME[1]="ath0"
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
WLAN_WPA[1]="wpa_supplicant"
WLAN_WPADRIVER[1]="wext"
WLAN_WPAWAIT[1]=50
#DHCP_HOSTNAME[1]="netgear"
DHCP_TIMEOUT[1]=50

Quote:

which could mean an error in your /etc/wpa_supplicant.conf file.

As posted earlier, I am not shure if there are any errors with the wpa_supplicant.conf.

Quote:

# 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
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

# WPA protected network, supply your own ESSID and WPAPSK here:
network={
proto=WPA
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
#pairwise=CCMP TKIP
#group=CCMP TKIP WEP104 WEP40
ssid="my ssid"
psk=my psk
}

# Plaintext connection (no WPA, no IEEE 802.1X),
# nice for hotel/airport types of WiFi network.
network={
key_mgmt=NONE
priority=0
}

One thought, should I put in my ssid or bssid? Isnt the bssid the same as the mac address for the router?

pinniped,
I just blacklisted the b43legacy

I did not quite understand,

Quote:

One post I read claimed that wlan_tkip and wlan_xauth should both be loaded; perhaps you should try what you did before but load wlan_xauth again (I have no idea if that will work because I don't know if wlan_auth is used by clients or only by an Access Point).

What do you suggest I do?

okos · 09-26-2008, 11:39 PM

Hi
I was not able to acquire an ip address with my wife's xp either.

However, I changed the encryption to wep and was able to connect using wicd.

I was not sure how to setup wep in slackware.

pinniped · 09-27-2008, 02:33 AM

How strange - it sounds like some setting on the wireless router isn't right.

okos · 04-22-2009, 06:35 PM

I bought a D-Link router and was able to configure wpa2 perfectly.

Here is a guide
http://alien.slackbook.org/dokuwiki/...ckware:network

My configurations are as follows.

/etc/rc.d/inet1.conf

Code:

# Config information for eth0:
FNAME[1]="eth0"
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

# Config information for ath0 (using dhcp):
IFNAME[1]="ath0"
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]="bt"
WLAN_WPA[1]="wpa_supplicant"
WLAN_WPADRIVER[1]="wext"

rc.wireless.conf

Code:

my mac address separated by colons)
      INFO="Netgear WG511T"
      ESSID="my essid"
      CHANNEL="1"
      KEY="my psk key"
     ;;

my /etc/wpa_supplicant.conf settings:

Code:

# WPA protected network, supply your own ESSID and WPAPSK here:
  network={
        scan_ssid=0
        ssid="my essid"
        proto=WPA RSN
        key_mgmt=WPA-PSK WPA-EAP
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk=my psk key
}