Most webpages timing out

seth · 2018-02-15 20:29:36

He's not reaching the proxy IP ...

But do you maybe use https://wiki.archlinux.org/index.php/Ne … domization

lo1 · 2018-02-15 20:35:45

3:  be456.pr2.thlon.isp.sky.com                          78.866ms asymm  4 
 4:  lag-102.ear1.London1.Level3.net                      97.500ms

...or he's ridiculously close to the POP, perhaps?

This anyway has nothing to do with routing, this must be something wrong with how the network has been setup on the host or a crazy modem/router (and, I hate to say it: if it works in Windows, there's no need to go further than the specific host-to-gateway configuration)

Last edited by lo1 (2018-02-15 20:38:48)

Seraphic8X · 2018-02-15 20:35:53

lo1 wrote:

What network type (e.g. vpn or simple xdsl connection...) and which network manager (NetworkManager, netctl, wpa_supplicant + dhcp...), but also:
cat /etc/resolv.conf
cat /etc/nsswitch.conf
dig google.com
dig github.com
Note: to use dig you have to install bind.

I'm on an ADSL connection, I use NetworkManager, netctl, wpa_supplicant and dhcp. Maybe this is the problem, during set up I used multiple ones because I was struggling to get the Wireless working, maybe they are clashing? Should I just keep NetworkManager?

I have a feeling I'm probably doing something silly since I'm new to Arch and not that experienced with Linux yet.

cat /etc/resolv.conf:

cat /etc/resolv.conf
# Generated by resolvconf
search Home
nameserver 192.168.0.1
nameserver fdab:e51:29f8:0:7e4c:a5ff:fed3:4464

cat /etc/nsswitch.conf:

cat /etc/resolv.conf
# Generated by resolvconf
search Home
nameserver 192.168.0.1
nameserver fdab:e51:29f8:0:7e4c:a5ff:fed3:4464

dig google.com:

$ dig google.com

; <<>> DiG 9.12.0 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59898
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             290     IN      A       216.58.210.46

;; Query time: 83 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Feb 15 20:29:53 GMT 2018
;; MSG SIZE  rcvd: 44

dig github.com:

$ dig github.com

; <<>> DiG 9.12.0 <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55066
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.                    IN      A

;; ANSWER SECTION:
github.com.             53      IN      A       192.30.253.113
github.com.             53      IN      A       192.30.253.112

;; Query time: 213 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Feb 15 20:29:59 GMT 2018
;; MSG SIZE  rcvd: 60

loqs · 2018-02-15 20:40:29

Yes it is not a good idea to have multiple network management services running. Just having the packages installed however is fine.

$ systemctl list-unit-files --state enabled

Edit:
To try something even lighter than curl does the following time out as well?

$ openssl s_client -connect 192.30.253.112:443

Last edited by loqs (2018-02-15 20:41:55)

seth · 2018-02-15 20:41:32

You posteed /etc/resolv.conf twice

tracepath google.com

Seraphic8X · 2018-02-15 20:42:07

loqs wrote:

Yes it is not a good idea to have multiple network management services running. Just having the packages installed however is fine.
$ systemctl list-unit-files --state enabled
Edit:
To try something even lighter than curl does the following time out as well?
$ openssl s_client -connect 192.30.253.112:443

$ systemctl list-unit-files --state enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
bluetooth.service                           enabled
bumblebeed.service                          enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
getty@.service                              enabled
lm_sensors.service                          enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
systemd-timesyncd.service                   enabled
remote-fs.target                            enabled

Seraphic8X · 2018-02-15 20:43:26

seth wrote:

You posteed /etc/resolv.conf twice
tracepath google.com

Sorry!

$ cat /etc/nsswitch.conf
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files mymachines systemd
group: files mymachines systemd
shadow: files

publickey: files

hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

loqs · 2018-02-15 20:46:03

@seth perhaps nmap TCP SYN scan and TCP connect scan just targeted at ports 80 and 443?

lo1 · 2018-02-15 20:52:18

I use NetworkManager, netctl, wpa_supplicant and dhcp

If you use them together (@loqs, regardless of what's enabled I would have checked if OP has enabled one networkmanager while using another one post-boot...) stop doing it cause this is clearly a mess

loqs · 2018-02-15 20:56:02

Seraphic8X did you start netctl, wpa_supplicant or dhcp services this boot?

seth · 2018-02-15 21:02:00

systemctl list-units | grep -iE '(wicd|conn|net|dhcp|wpa)'
sudo nmap -sS -p443 github.com
sudo nmap -sA -p443 github.com

The weird part though is that only some (many but not all) IPs are affected and it works with windows™ ...

Seraphic8X · 2018-02-15 21:17:11

loqs wrote:

Seraphic8X did you start netctl, wpa_supplicant or dhcp services this boot?

I think this is probably not causing the main problem unfortunately as I remember installing netctl when I was trying to find a way around this problem unfortunately.

My WiFi relies on wpa_supplicant, and if I get rid of it, my WiFi drops. Also I cannot control my wireless network through the KDE system tray if I remove NetworkManager.

Sorry I'm so green with this guys, your help is really appreciated.

And as I speak I've found the culprit. WiFi repeater. If I connect to the main network I do not get these issues. Problem is I need to stand next to the wall as the AP is in my neighbours home (I am permitted access, I live in an annexe)

seth · 2018-02-15 21:22:41

ping github.com

(I want to see whether you get doubled packages)
The repeater however works for other devices/windows?
How does it relate to the target IP - is it still limited to the same domains or is the behavior rather random (and independent of the target IP)?

lo1 · 2018-02-15 21:30:25

My WiFi relies on wpa_supplicant, and if I get rid of it, my WiFi drops.

NetworkManager relies on wpa_supplicant (you don't ever need to manually enable or start it) so if it's just sitting there without your intervention this is fine.

However, why a WiFi repeater causes systematically for certain websites to experience a connection timeout while others to work just fine is out of my reach.

seth wrote:

The repeater however works for other devices/windows?

The only thing that comes to my mind is that wifi drivers with windows works fine out of the box (click next, install, next, next, I agree the Policy terms, install), and that we have been chasing ghosts until now.

Seraphic8X · 2018-02-15 21:33:39

The repeater is fine for Windows and other devices. I have some kind of funny feeling I could have configured it strangely when setting up Arch, and it's a problem on the laptops side. I used wifi-menu + wpa_supplicant when doing so.

$ ping github.com
PING github.com (192.30.253.113) 56(84) bytes of data.
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=1 ttl=49 time=138 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=2 ttl=49 time=161 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=3 ttl=49 time=149 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=4 ttl=49 time=151 ms
64 bytes from lb-192-30-253-113-iad.github.com (192.30.253.113): icmp_seq=5 ttl=49 time=169 ms
^C
--- github.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 138.754/154.049/169.425/10.496 ms

Weirdly this still happens even though I can access it fine now via https:

$ tracepath github.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  SkyRouter.Home                                        1.894ms 
 1:  SkyRouter.Home                                        1.471ms 
 2:  no reply
 3:  be456.pr2.thlon.isp.sky.com                         136.495ms asymm  4 
 4:  no reply
 5:  no reply
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

So far all http/s sites I mentioned before work, plus steam.

I'm going to try resetting the repeater and see if it still gives me grief then.

Seraphic8X · 2018-02-15 21:35:37

lo1 wrote:

My WiFi relies on wpa_supplicant, and if I get rid of it, my WiFi drops.
NetworkManager relies on wpa_supplicant (you don't ever need to manually enable or start it) so if it's just sitting there without your intervention this is fine.
However, why a WiFi repeater causes systematically for certain websites to experience a connection timeout while others to work just fine is out of my reach.
seth wrote:
The repeater however works for other devices/windows?
The only thing that comes to my mind is that wifi drivers with windows works fine out of the box (click next, install, next, next, I agree the Policy terms, install), and that we have been chasing ghosts until now.

It is a cheap repeater. I should have sussed this out way earlier myself, cheap repeaters are reknowned for doing stupid things like this. They just repeat on the same frequency and cause all sorts of network issues.

Thanks again so much for all your help, I'm sorry I didn't realise this sooner!

seth · 2018-02-15 21:49:40

Is that ping with or without the repeater?
(Though I've no idea left if this actually consistently affects only the same set of IPs...)

Arch Linux

#26 2018-02-15 20:29:36

Re: Most webpages timing out

#27 2018-02-15 20:35:45

Re: Most webpages timing out

#28 2018-02-15 20:35:53

Re: Most webpages timing out

#29 2018-02-15 20:40:29

Re: Most webpages timing out

#30 2018-02-15 20:41:32

Re: Most webpages timing out

#31 2018-02-15 20:42:07

Re: Most webpages timing out

#32 2018-02-15 20:43:26

Re: Most webpages timing out

#33 2018-02-15 20:46:03

Re: Most webpages timing out

#34 2018-02-15 20:52:18

Re: Most webpages timing out

#35 2018-02-15 20:56:02

Re: Most webpages timing out

#36 2018-02-15 21:02:00

Re: Most webpages timing out

#37 2018-02-15 21:17:11

Re: Most webpages timing out

#38 2018-02-15 21:22:41

Re: Most webpages timing out

#39 2018-02-15 21:30:25

Re: Most webpages timing out

#40 2018-02-15 21:33:39

Re: Most webpages timing out

#41 2018-02-15 21:35:37

Re: Most webpages timing out

#42 2018-02-15 21:49:40

Re: Most webpages timing out

Board footer