[SOLVED] Wireless ralink on fresh install

Quicken2k · 06-06-2014, 10:11 AM

I can't seem to setup my wireless network I'm in console only (fresh install). I selected NetworkManger during the setup program, I have a router. wpa_supplicant just connects and disconnects. Any ideas?

My wpa_supplicant output when manually run

Code:

wlan0: Associated with 20:aa:4b:ff:6f:a7
wlan0: CTRL-EVENT-DISCONNECTED bssid=20:aa:4b:ff:6f:a7 reason=0
wlan0: Trying to associate with 20:aa:4b:ff:6f:a7 (SSID='dasilvam' freq=2437 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlan0: Association request to the driver failed
wlan0: Associated with 20:aa:4b:ff:6f:a7
wlan0: CTRL-EVENT-DISCONNECTED bssid=20:aa:4b:ff:6f:a7 reason=0
wlan0: Trying to associate with 20:aa:4b:ff:6f:a7 (SSID='dasilvam' freq=2437 MHz)

wpa_supplicant.conf

Code:

# wpa_supplicant.conf


ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
        ssid="dasilvam"
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=CCMP
        psk=5378156f5e124f4b120aa7d5b4fffa355f41383db7f49e9acde2775eab1d4c0d
}

pairwise and group and key_mgmt were added manually by me.

DHCPCD output

Code:

root@dasilvam:~# ping www.google.ca
ping: unknown host www.google.ca
root@dasilvam:~# dhcpcd wlan0
dhcpcd[967]: version 6.0.5 starting
dhcpcd[967]: wlan0: waiting for carrier
dhcpcd[967]: timed out
dhcpcd[967]: allowing 8 seconds for IPv4LL timeout
dhcpcd[967]: timed out
dhcpcd[967]: exited

Quicken2k
Mark

gmgf · 06-07-2014, 04:33 AM

wheel GROUP, isn't used in slackware.

Alien Bob · 06-07-2014, 04:55 AM

If you enabled networkmanager, then /etc/wpa_supplicant.conf is not used. Instead you need to configure your wireless parameters in a GUI. Either the network-manager-applet in XFCE (a Gnome application) or the networkmanager of KDE is available for that.

Quote:

Originally Posted by gmgf

wheel GROUP, isn't used in slackware.

I depend on it all the time. Does that count as "used in Slackware"?

Eric

gmgf · 06-07-2014, 08:24 AM

wheel GROUP, is present, on slackware, but it's no really used like in BSD, i think.

Quicken2k · 06-07-2014, 11:07 AM

Ok I Switch it use dhcpcd instead of NetworkManager as I don't want a GUI right now added wpa_supplicant command to rc.local.

Now I get this output when dhcpcd is run, but still no internet connection.

Code:

Successfully initialized wpa_supplicant
Polling for DHCP server on interface wlan0:
dhcpcd[691]: version 6.0.5 starting
dhcpcd[691]: wlan0: soliciting a DHCP lease
dhcpcd[691]: wlan0: offered 192.168.1.119 from 192.168.1.1 `ecosystem.home.cisco.com'
dhcpcd[691]: wlan0: leased 192.168.1.119 for 86400 seconds
dhcpcd[691]: wlan0: adding host route to 192.168.1.119 via 127.0.0.1
dhcpcd[691]: wlan0: adding route to 192.168.1.0/24
dhcpcd[691]: wlan0: adding default route via 192.168.1.1
dhcpcd[691]: forked to background, child pid 730

Quicken2k
Mark

Alien Bob · 06-07-2014, 12:56 PM

Quote:

Originally Posted by Quicken2k

Ok I Switch it use dhcpcd instead of NetworkManager as I don't want a GUI right now added wpa_supplicant command to rc.local.

Now I get this output when dhcpcd is run, but still no internet connection.

Code:

Successfully initialized wpa_supplicant
Polling for DHCP server on interface wlan0:
dhcpcd[691]: version 6.0.5 starting
dhcpcd[691]: wlan0: soliciting a DHCP lease
dhcpcd[691]: wlan0: offered 192.168.1.119 from 192.168.1.1 `ecosystem.home.cisco.com'
dhcpcd[691]: wlan0: leased 192.168.1.119 for 86400 seconds
dhcpcd[691]: wlan0: adding host route to 192.168.1.119 via 127.0.0.1
dhcpcd[691]: wlan0: adding route to 192.168.1.0/24
dhcpcd[691]: wlan0: adding default route via 192.168.1.1
dhcpcd[691]: forked to background, child pid 730

Quicken2k
Mark

Looks like the WPA association works. Otherwise dhcpcd would not be able to get an IP address.
If you can not resolve hostnames, then dhcpcd has not configured /etc/resolv.conf for you. Usually the DHCP server informs the DHCP client which IP addresses to use for hostname resolving - those IP addresses will be written to /etc/resolv.conf .

You can still test whether you have internet connectivity, using ping.

First, ping your local gateway, 192.168.1.1. That should answer for sure.
Then if you got replies, ping one of Google's public DNS servers, 8.8.8.8 .

If that works you can add these lines to /etc/resolv.conf manually:

Code:

nameserver 8.8.8.8
nameserver 8.8.4.4

This should get your Internet access working.

Eric