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.
Successfully initialized wpa_supplicant
Polling for DHCP server on interface wlan0:
dhcpcd: version 6.0.5 starting
dhcpcd: wlan0: soliciting a DHCP lease
dhcpcd: wlan0: offered 192.168.1.119 from 192.168.1.1 `ecosystem.home.cisco.com'
dhcpcd: wlan0: leased 192.168.1.119 for 86400 seconds
dhcpcd: wlan0: adding host route to 192.168.1.119 via 127.0.0.1
dhcpcd: wlan0: adding route to 192.168.1.0/24
dhcpcd: wlan0: adding default route via 192.168.1.1
dhcpcd: forked to background, child pid 730
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, 220.127.116.11 .
If that works you can add these lines to /etc/resolv.conf manually:
This should get your Internet access working.