You are not logged in.

Pages: 1

#1 2016-05-27 04:54:03

mischka
Member
From: Milwaukee, WI
Registered: 2015-04-26
Posts: 12
Website

Wifi receives IP address, Destination Host Unreachable afterward

I have an Acer E5-574G with an ath10k QCA9377 network adapter. I'm using Linux 4.6 from testing currently, though I've had this problem using stable and mainline kernels since I got this laptop a few months ago.

My wifi works fine on my personal network at my apartment, a wireless hotspot from my phone, my mother's personal network at her home, and a public network, so in general it works, but I can't get it to work on my network at work. I am able to connect to the network using other devices, including another laptop running Arch.

The network in question is wpa2 personal, just like the ones that worked. I'm able to get an IP address with DHCP and connect to the access point, but I'm unable to connect to any ip addresses after doing so, receiving "Destination Host Unreachable" when I try, even with addresses on my local network, including my default gateway.

I work at a hospital, so I wouldn't be surprised if they use some kind of archaic security measures that are perhaps causing a problem. I've received minimal support when trying to troubleshoot other non-Linux issues with the network, so I would like to make sure I'm not doing something wrong before I ask for support from them.

The problem occurs both when using NetworkManager and when using wpa_supplicant and dhcpcd manually.

# ip a
...
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 30:f7:72:03:5c:53 brd ff:ff:ff:ff:ff:ff
    inet 172.19.207.90/22 brd 172.19.207.255 scope global wlp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::32f7:72ff:fe03:5c53/64 scope link 
       valid_lft forever preferred_lft forever
$ ip route
default via 172.19.204.1 dev wlp3s0  src 172.19.207.90  metric 303 
172.19.204.0/22 dev wlp3s0  proto kernel  scope link  src 172.19.207.90  metric 303
# journalctl -r | grep NetworkManager
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.4240] device (wlp3s0): Activation: successful, device activated.
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3912] dns-mgr: Writing DNS information to /usr/bin/resolvconf
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3911] policy: set 'REPLACED_SSID' (wlp3s0) as default for IPv4 routing and DNS
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3905] manager: NetworkManager state is now CONNECTED_GLOBAL
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3871] manager: NetworkManager state is now CONNECTED_LOCAL
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3865] device (wlp3s0): state change: secondaries -> activated (reason 'none') [90 100 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3846] device (wlp3s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3838] device (wlp3s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3782] dhcp4 (wlp3s0): state changed unknown -> bound
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3781]   gateway 172.19.204.1
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3780]   domain name 'REPLACED_DOMAIN'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3780]   nameserver '192.227.56.198'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3780]   nameserver '192.227.32.62'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3780]   expires in 14400 seconds
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3780]   plen 22
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3779]   address 172.19.207.25
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3602] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3599] device (wlp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3595] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'REPLACED_SSID'.
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3595] device (wlp3s0): supplicant interface state: associated -> completed
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3594] device (wlp3s0): supplicant interface state: associating -> associated
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3593] device (wlp3s0): supplicant interface state: authenticating -> associating
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.3577] device (wlp3s0): supplicant interface state: inactive -> authenticating
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2718] sup-iface[0x26daf70,wlp3s0]: config: set interface ap_scan to 1
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2496] Config: added 'psk' value '<omitted>'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2496] Config: added 'key_mgmt' value 'WPA-PSK'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2496] Config: added 'bssid' value 'B4:14:89:D0:63:BD'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2496] Config: added 'scan_ssid' value '1'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2495] Config: added 'ssid' value 'REPLACED_SSID'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2495] device (wlp3s0): Activation: (wifi) connection 'REPLACED_SSID' has security, and secrets exist.  No new secrets needed.
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2493] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2490] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2452] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2452] device (wlp3s0): Activation: (wifi) access point 'REPLACED_SSID' has security, but secrets are required.
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2450] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2446] manager: NetworkManager state is now CONNECTING
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2444] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2443] device (wlp3s0): Activation: starting connection 'REPLACED_SSID' (1811f509-4b30-4da0-a97c-79101a5dbf83)
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.2432] policy: auto-activating connection 'REPLACED_SSID'
May 24 10:34:43 mischka-laptop NetworkManager[447]: <info>  [1464104083.1722] device (wlp3s0): supplicant interface state: ready -> inactive
May 24 10:34:38 mischka-laptop NetworkManager[447]: <info>  [1464104078.4527] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 24 10:34:38 mischka-laptop NetworkManager[447]: <info>  [1464104078.4526] device (wlp3s0): supplicant interface state: starting -> ready
May 24 10:34:38 mischka-laptop NetworkManager[447]: <info>  [1464104078.4516] sup-iface[0x26daf70,wlp3s0]: supports 5 scan SSIDs
May 24 10:34:38 mischka-laptop NetworkManager[447]: <info>  [1464104078.3932] manager: NetworkManager state is now DISCONNECTED
May 24 10:34:36 mischka-laptop NetworkManager[447]: <info>  [1464104076.4876] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 24 10:34:36 mischka-laptop NetworkManager[447]: <info>  [1464104076.4218] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 24 10:34:36 mischka-laptop NetworkManager[447]: <info>  [1464104076.4215] manager: waking up...
May 24 10:34:36 mischka-laptop NetworkManager[447]: <info>  [1464104076.4215] manager: wake requested (sleeping: yes  enabled: yes)

Please let me know what other information or logs I can give, thank you for your help.

Offline

#2 2016-05-27 12:20:46

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,910

Re: Wifi receives IP address, Destination Host Unreachable afterward

metric 303

That's a very high number for any route,especially a default one.
what is the output of traceroute 172.19.204.1 ?

Other possibilities that come to mind :

- the network only accepts validated systems, like those that are members of a domain ?
- dhcp server and nameserver could have different ip-adresses (SHOULD be covered by dhcp getting correct resolve info)
- the network uses a proxy server

If the traceroute doesn't give clues, easiest way to answer those questions is probably to check setting/behaviour on supported devices .
( phone/tablet  using wifi, laptop running windows etc )

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2016-05-27 12:39:49

mischka
Member
From: Milwaukee, WI
Registered: 2015-04-26
Posts: 12
Website

Re: Wifi receives IP address, Destination Host Unreachable afterward

Is 303 high? I'm getting 600 for the metric at my apartment apparently, where it works. Odd.

It accepts all systems, my phone and my last Linux laptop both work fine out of the box. I'm not too worried about the nameserver, I can use Google's if it comes to it. I don't believe it uses a proxy server, how can I check that?

I'll try traceroute on both the laptop and my phone when I get to work, should be less than an hour.

Offline

#4 2016-05-27 13:38:23

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,514
Website

Re: Wifi receives IP address, Destination Host Unreachable afterward

I have no idea what it means, but FWIW, I also have metric 303 and my connection is fine.

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2016-05-27 13:44:52

mischka
Member
From: Milwaukee, WI
Registered: 2015-04-26
Posts: 12
Website

Re: Wifi receives IP address, Destination Host Unreachable afterward

Traceroute just times out at the first hop, which I expected. And I'm getting 600 today for the metric at my workplace as well.

Regular MAC:

[mischka@mischka-laptop ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:ab:3a:4b:71:8f brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 30:f7:72:03:5c:53 brd ff:ff:ff:ff:ff:ff
    inet 172.19.205.104/22 brd 172.19.207.255 scope global dynamic wlp3s0
       valid_lft 3589sec preferred_lft 3589sec
    inet6 fe80::32f7:72ff:fe03:5c53/64 scope link 
       valid_lft forever preferred_lft forever

[mischka@mischka-laptop ~]$ sudo ip route
[sudo] password for mischka: 
default via 172.19.204.1 dev wlp3s0  proto static  metric 600 
172.19.204.0/22 dev wlp3s0  proto kernel  scope link  src 172.19.205.104  metric 600 

[mischka@mischka-laptop ~]$ traceroute 172.19.204.1
traceroute to 172.19.204.1 (172.19.204.1), 30 hops max, 60 byte packets
 1  mischka-laptop (172.19.205.104)  2584.495 ms !H  2584.450 ms !H  2584.434 ms !H

Phone's MAC:

[mischka@mischka-laptop ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:ab:3a:4b:71:8f brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 64:bc:0c:43:7f:37 brd ff:ff:ff:ff:ff:ff
    inet 172.19.79.94/22 brd 172.19.79.255 scope global dynamic wlp3s0
       valid_lft 3591sec preferred_lft 3591sec
    inet6 fe80::66bc:cff:fe43:7f37/64 scope link 
       valid_lft forever preferred_lft forever

[mischka@mischka-laptop ~]$ ip route
default via 172.19.76.1 dev wlp3s0  proto static  metric 600 
172.19.76.0/22 dev wlp3s0  proto kernel  scope link  src 172.19.79.94  metric 600 

[mischka@mischka-laptop ~]$ traceroute 172.19.76.1
traceroute to 172.19.76.1 (172.19.76.1), 30 hops max, 60 byte packets
 1  mischka-laptop (172.19.79.94)  1930.329 ms !H  1930.296 ms !H  1930.218 ms !H

I tried spoofing the MAC address of my phone to get an IP that I was sure worked, but I still was unable to ping or connect to anything.

I brought my Windows drive with me to work and a USB3 adapter, if there's something I can try in Windows on the same machine that might shed some light please let me know what that would be.

Edit: Formatting, output for spoofed MAC connection.
Edit: Phone's connection information: https://goo.gl/photos/GRafJvaXXtGQzYKs8

Last edited by mischka (2016-05-27 13:52:38)

Offline

#6 2016-05-27 23:21:32

mischka
Member
From: Milwaukee, WI
Registered: 2015-04-26
Posts: 12
Website

Re: Wifi receives IP address, Destination Host Unreachable afterward

I spent half the day looking at wireshark and searching for everything I could think of, I'm about to start blaming the qca9377 firmware. I see a fair amount of network activity, gratuitous arp replies for others, but my arp requests for my gateway never receive a response.

Offline

#7 2016-05-28 02:16:06

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Wifi receives IP address, Destination Host Unreachable afterward

Moving to Networking as per request...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

Pages: 1

Board footer

Powered by FluxBB