[SOLVED] Wireless issue | Works in X

Alstare · 08-15-2012, 10:57 PM

I know, I know... Not another Slackware wireless thread. But I am truly stumped here.

Now let me start out this thread by saying my wireless works perfect IF I start KDE and just sign in using the wireless manger. Flawlessly, no hiccups, nice and fast, etc...

Now for some reason, possibly sadistic. I want to have my wireless setup in the traditional fashion, and dont feel like starting X every time I want an internet connection. This is for a desktop workstation, that will only connect to this 1 wireless network 24/7 for the rest of its life. Also this is a Wireless network with WPA2 security on it.

I have a clean fresh slack 14rc install, with 1 wired interface not configured or needed, and 1 wireless "wlan0" interface that uses the ath9k driver.

I have it setup using Aliens Bob's guide step for step exactly.

Here is my "rc.inet1.conf" pertanint sections only of course, the rest left default.

Code:

## Example config information for wlan0.  Uncomment the lines you need and fill
## in your data.  (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
IPADDR[4]=""  
NETMASK[4]=""
USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]=""
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[4]=Bondy2ghz
WLAN_MODE[4]=Managed
#WLAN_RATE[4]="54M auto"
#WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]="D5A31F54ACF0487C2D0B1C10D2"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
#WLAN_WPAWAIT[4]=30

Also my wpa_supplicant.conf file

Code:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=1
eapol_version=1
ap_scan=1
fast_reauth=1

network={
        scan_ssid=0
        ssid="Bondy2ghz"
        proto=WPA RSN
        key_mgmt=WPA-PSK WPA-EAP
        pairwise=CCMP TKIP
        group=CCMP TKIP
        psk=083eb1ec7a73b1e9abddf81d9a1de0f49c299bb6cffbe36acf52840cd6b0aff0
}

Alstare · 08-15-2012, 11:03 PM

Now when I try to start the interface, I get this which takes a solid 2-3mins to complete...

Code:

bash-4.2# ./rc.inet1 wlan0 start
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan0 ; Operation not supported.
Polling for DHCP server on interface wlan0:
dhcpcd[3661]: version 5.5.6 starting
dhcpcd[3661]: wlan0: waiting for carrier
dhcpcd[3661]: timed out
dhcpcd[3661]: allowing 8 seconds for IPv4LL timeout
dhcpcd[3661]: timed out

The output from running "wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf"

Code:

bash-4.2# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
wlan0: Trying to associate with 5c:d9:98:20:11:0d (SSID='Bondy2ghz' freq=2462 MHz)
wlan0: Associated with 5c:d9:98:20:11:0d
wlan0: WPA: No SSID info found (msg 1 of 4)
wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:d9:98:20:11:0d reason=0
wlan0: Trying to associate with 5c:d9:98:20:11:0d (SSID='Bondy2ghz' freq=2462 MHz)
wlan0: Associated with 5c:d9:98:20:11:0d
wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:d9:98:20:11:0d reason=0
wlan0: Trying to associate with 5c:d9:98:20:11:0d (SSID='Bondy2ghz' freq=2462 MHz)
wlan0: Associated with 00:00:00:00:00:00
wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:d9:98:20:11:0d reason=0
wlan0: Trying to associate with 5c:d9:98:20:11:0d (SSID='Bondy2ghz' freq=2462 MHz)
wlan0: Associated with 5c:d9:98:20:11:0d

Alstare · 08-15-2012, 11:49 PM

Also running "wpa_cli" gives me a similar output...

Code:

<3>WPS-AP-AVAILABLE 
<3>Trying to associate with 5c:d9:98:20:11:0d (SSID='Bondy2ghz' freq=2462 MHz)
<3>Associated with 00:00:00:00:00:00
<3>CTRL-EVENT-DISCONNECTED bssid=5c:d9:98:20:11:0d reason=0

volkerdi · 08-16-2012, 12:55 AM

Quote:

Originally Posted by Alstare

Now let me start out this thread by saying my wireless works perfect IF I start KDE and just sign in using the wireless manger. Flawlessly, no hiccups, nice and fast, etc...

If that's true, I think you might be running NetworkManager, which would fight with any traditional rc.inet1.conf configuration that you might have. Is /etc/rc.d/rc.networkmanager chmod 755? If so, change the perms to mode 644 and see if things work any better.

Alstare · 08-16-2012, 01:11 AM

Wow... I can't even begin to express my thanks!

I removed the executable permission from "/etc/rc.d/rc.networkmanger" restarted it and BAM instant gratification...

I have spent the last several hours going over everything top to bottom, searching Google, trying fixes, all to no avail and pulling out most of my hair. I wondered about "rc.networkmanager" running in the /etc/rc.d directory, but wasn't sure if it was used for basic networking as well so I didn't try removing it. I had disabled it from running well in X well testing but I guess that wasn't enough.

Thanks again... The drinks are on me!