[SOLVED] Open WiFi setup: iwconfig, ok; But "Network is unreachable"

xtian · 2013-09-12 18:47:45

Following the Wireless Setup page has been fairly easy.

My setup has the (3) primary components: wireless interface, correct kernel driver for my hardware, and the kernel driver is loaded:

# ip link 
[...]
4: wlp2s2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 00:04:23:56:45:07 brd ff:ff:ff:ff:ff:ff
# lspci -k
[...]
02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
        Subsystem: Intel Corporation Device 2551
        Kernel driver in use: ipw2100
        Kernel modules: ipw2100
# dmesg | grep ipw2100
[   22.007615] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[   22.007626] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[   22.011114] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection

I'm following these (4) steps (#iw does not work with my card so I'm using #iwconfig):

# ip link set wlp2s2 up
# iwlist wlp2s2 scan
// EDIT, added this step back into my original list cuz if you can scan something's working, right?
# iwconfig wlp2s2 essid "[my router's open network SSID]"
# dhcpcd wlp2s2
dhcpcd[1570]: sending commands to master dhcpcd process

And to check the status of the wifi connection I'm following these (4) steps:

#iwconfig wlp2s2
wlp2s2    IEEE 802.11b  ESSID:"XtiansWiFi"  Nickname:"ipw2100"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 94:44:52:EA:5B:25   
          Bit Rate=11 Mb/s   Tx-Power:16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:00E4-D366-4C   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=-36 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
# journalctl -f
-- Logs begin at Fri 2013-08-30 16:09:25 EDT. --
Sep 12 10:02:29 frylock dhcpcd[278]: enp2s8: deleting route to 192.168.2.0/24
Sep 12 10:02:29 frylock dhcpcd[278]: enp2s8: deleting default route via 192.168.
Sep 12 10:02:29 frylock kernel: e100 0000:02:08.0 enp2s8: NIC Link is Down
Sep 12 10:04:23 frylock dhcpcd[278]: wlp2s2: carrier lost
Sep 12 10:04:24 frylock dhcpcd[278]: wlp2s2: carrier acquired
Sep 12 10:04:24 frylock dhcpcd[278]: wlp2s2: soliciting an IPv6 router
Sep 12 10:04:24 frylock dhcpcd[278]: wlp2s2: soliciting a DHCP lease
Sep 12 10:04:36 frylock dhcpcd[278]: wlp2s2: no IPv6 Routers available
Sep 12 10:05:16 frylock dhcpcd[1570]: sending commands to master dhcpcd process
Sep 12 10:05:16 frylock dhcpcd[278]: control command: dhcpcd wlp2s2
^C
#ip addr
// EDIT, added this step as per below comments
# ping 192.168.2.1
connect: Network is unreachable

Then, reconnecting the wired line you can see dhcpcd assign the ip to enp2s8 (wired lan),

# journalctl -f
-- Logs begin at Fri 2013-08-30 16:09:25 EDT. --
Sep 12 10:05:16 frylock dhcpcd[278]: control command: dhcpcd wlp2s2
Sep 12 10:07:35 frylock dhcpcd[278]: enp2s8: carrier acquired
Sep 12 10:07:35 frylock kernel: e100 0000:02:08.0 enp2s8: NIC Link is Up 10...ex
Sep 12 10:07:35 frylock dhcpcd[278]: enp2s8: soliciting an IPv6 router
Sep 12 10:07:35 frylock dhcpcd[278]: enp2s8: rebinding lease of 192.168.2.7
Sep 12 10:07:40 frylock dhcpcd[278]: enp2s8: leased 192.168.2.7 for infinity
Sep 12 10:07:40 frylock dhcpcd[278]: enp2s8: adding host route to 192.168.2....1
Sep 12 10:07:40 frylock dhcpcd[278]: enp2s8: adding route to 192.168.2.0/24
Sep 12 10:07:40 frylock dhcpcd[278]: enp2s8: adding default route via 192.1....1
Sep 12 10:07:47 frylock dhcpcd[278]: enp2s8: no IPv6 Routers available

The troubleshoot section notes to try the other dhcp tool (dhclient). If that doesn't work, and you have a working wired connection try:

# iwconfig wlan0 power off

And It still won't give me a route to host! What am I missing? I know this hardware is older and it could have just given up the ghost, I can't say. However it was working with the previous install of Fedora 17...

Last edited by xtian (2013-09-17 21:24:34)

Active Build · 2013-09-12 18:55:02

Why don't you use wpa_supplicant?

/etc/wpa_supplicant/custom.conf

network={
    ssid="YOUR-ROUTER-SSID"
    psk="PASSWORD"
}

systemctl start dhcpcd

wpa_supplicant -Dwext -iwlp2s2 -c/etc/wpa_supplicant/custom.conf -B

I haven't had any problems since I started to practice it this way.

ewaller · 2013-09-12 19:14:37

Well, you are associated with your access point (XtiansWiFi). For an open network, you don't need wpa_supplicant.

You seem have an ip address. Verify that with ip addr , but the address looks to be 192.168.2.7.
Therefore, I think you are having DNS problems. Verify this by trying to ping 192.168.2.1. I think that is going to be the address of your router.
You might even try browsing to 192.168.2.1 and see if you can see your router's web page (if it has one)

xtian · 2013-09-12 23:07:08

AB: I was thinking of using netcfg for autoconfiguration. If I understand you correctly (and the wiki) you have a bash script somewhere and manually connect?

EW: Thanks for the #ip addr command, that was a big help. I wasn't sure I had an IP using only #journalctl.

Now its working.
I didn't do anything but logout (all the way to tty) and walk away. Maybe my wireless card is shy. (>_<)

I would add two points of note:
The #journalctl command output is asymmetric -- it does not show the same data for a connected WiFi as it does for connected ethernet. This is performed connected via WiFi:

# journalctl -f
-- Logs begin at Fri 2013-08-30 16:09:25 EDT. --
Sep 12 14:21:15 frylock dhcpcd[273]: wlp2s2: no IPv6 Routers available
Sep 12 14:21:23 frylock dhcpcd[1838]: sending commands to master dhcpcd process
Sep 12 14:21:23 frylock dhcpcd[273]: control command: dhcpcd wlp2s2
Sep 12 14:23:23 frylock dhcpcd[273]: enp2s8: carrier lost
Sep 12 14:23:23 frylock dhcpcd[273]: enp2s8: deleting host route to 192.168....1
Sep 12 14:23:23 frylock dhcpcd[273]: enp2s8: deleting route to 192.168.2.0/24
Sep 12 14:23:23 frylock dhcpcd[273]: enp2s8: deleting default route via 192....1
Sep 12 14:23:23 frylock kernel: e100 0000:02:08.0 enp2s8: NIC Link is Down
Sep 12 14:23:54 frylock dhcpcd[1886]: sending commands to master dhcpcd process
Sep 12 14:23:54 frylock dhcpcd[273]: control command: dhcpcd wlp2s2

Testing my connection using "#ping 192.168.2.1" (the router's address), I got "100% packet loss". I got a clue something was different because the output from the previous state was "unreachable". Fortunately I've memorized a real world IP (my old DSL's DNS server from 1998!) and this went through. In other words, for some reason my wifi router is closed to my ping even though it is working. If I didn't have an outside IP to test, I would likely have been looking for more answers while it was already fixed. This is also performed with WiFi connected:

# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
^C
--- 192.168.2.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms

[root@frylock ~]# ping 206.13.31.12
PING 206.13.31.12 (206.13.31.12) 56(84) bytes of data.
64 bytes from 206.13.31.12: icmp_seq=1 ttl=239 time=98.5 ms
64 bytes from 206.13.31.12: icmp_seq=2 ttl=239 time=82.3 ms
^C
--- 206.13.31.12 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms

I would like to add I'm psyched ethernet dhcp is sorted automatically whenever I connect or disconnect. I'm new to Arch and I'm really into the minimal install. Its great there are some things that don't need to be setup to work automatically. Woot!

//EDIT. added last comment...

Last edited by xtian (2013-09-12 23:34:10)

Arch Linux

#1 2013-09-12 18:47:45

[SOLVED] Open WiFi setup: iwconfig, ok; But "Network is unreachable"

#2 2013-09-12 18:55:02

Re: [SOLVED] Open WiFi setup: iwconfig, ok; But "Network is unreachable"

#3 2013-09-12 19:14:37

Re: [SOLVED] Open WiFi setup: iwconfig, ok; But "Network is unreachable"

#4 2013-09-12 23:07:08

Re: [SOLVED] Open WiFi setup: iwconfig, ok; But "Network is unreachable"

Board footer