[SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

dlin · 2016-03-23 21:16:31

I use wif-menu to connect my WPA wireless network.
It connected and get an IP address '192.168.0.104'.
The /ec/resolved.conf point to the gateway 192.168.0.1.

Here is the '''ip addr''' result

2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:23:54:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.105/24 brd 192.168.0.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::223:54ff:fe88:d3b9/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:22:43:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.104/24 brd 192.168.0.255 scope global wlp1s0
       valid_lft forever preferred_lft forever
    inet6 fe80::222:43ff:fe4c:4e23/64 scope link 
       valid_lft forever preferred_lft forever

/etc/resolv.conf

# Generated by resolvconf
nameserver 192.168.0.1

if I turn off the 'dhcp' static ethernet and only turn on wifi, it still can not work

sudo netctl stop dhcp  # for enp2s0
ping 192.168.0.1 # failed

1. tried to type every command line of iw/ip.
2. reload the ath9k module.
3. reinstall iw & wpa_supplicant

It works. But I will try it tomorrow again..

Last edited by dlin (2016-03-24 15:45:53)

dlin · 2016-03-24 10:43:26

Update, I found it works, if I setup my access point as 'Open' instead of 'WPA2'.

jeremy31 · 2016-03-24 11:15:29

Did the /etc/resolv.conf change also?

dlin · 2016-03-24 16:13:06

jeremy31 wrote:

Did the /etc/resolv.conf change also?

I think the resolve.conf is ok. So the dhcpcd work well.
But the problem is it can not ping gateway, and dns can not work.
My other machine work fine on the same wireless network.

I guess this problem may cause by the ath9k module should remove and reload.
Or, the wpa_supplicant and iw command should re-install.

I'll try tomorrow.

jeremy31 · 2016-03-24 17:11:27

Every Linux machine I have has

nameserver 127.0.1.1

in resolv.conf. I did change it to my routers address and DNS fails

dlin · 2016-03-27 12:46:57

jeremy31 wrote:

Every Linux machine I have has
nameserver 127.0.1.1
in resolv.conf. I did change it to my routers address and DNS fails

Jeremy, Thank you for your time to answer this question.

But, in fact it is solved.
I don't think it is caused by /etc/resolv.conf.

It is caused by strange reason. Just fix it by reinstall related packages.

Arch Linux

#1 2016-03-23 21:16:31

[SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

#2 2016-03-24 10:43:26

Re: [SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

#3 2016-03-24 11:15:29

Re: [SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

#4 2016-03-24 16:13:06

Re: [SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

#5 2016-03-24 17:11:27

Re: [SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

#6 2016-03-27 12:46:57

Re: [SOLVED] wifi-menu connected, but can not ping out on EEE PC S101

Board footer