You are not logged in.
Hi,
Just fresh installed Arch on my xps 9500 2020.
After wifi setup with NetworkManager, I found that some website can not be opened in chromium or firefox, for example nytimes.com. But google and archlinux site are Ok.
On cable connection everything works.
Ping to those urls are ok. DNS resolution seems ok with dig.
I've other machines in Arch and there's no problem.
Any idea what could be wrong?
Last edited by darkjh (2020-08-04 17:22:31)
Offline
What happens instead? Timeout?
Can you open "links nytimes.com" (CLI browser, https://www.archlinux.org/packages/core/x86_64/links/ )?
Are wifi and wired connection to the same router?
Sanity check:
nmap -p80 nytimes.com
Offline
What happens instead? Timeout?
Can you open "links nytimes.com" (CLI browser, https://www.archlinux.org/packages/core/x86_64/links/ )?
Are wifi and wired connection to the same router?Sanity check:
nmap -p80 nytimes.com
Yes it's timeout.
I tried `curl -v www.lemonde.fr` for example
~ $ curl -v www.lemonde.fr
* Trying 151.101.122.217:80...
* connect to 151.101.122.217 port 80 failed: Connection timed out
* Failed to connect to www.lemonde.fr port 80: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to www.lemonde.fr port 80: Connection timed out
and for nmap
nmap -p80 -Pn nytimes.com
Starting Nmap 7.80 ( https://nmap.org ) at 2020-08-03 10:21 CEST
Nmap scan report for nytimes.com (151.101.129.164)
Host is up.
Other addresses for nytimes.com (not scanned): 151.101.65.164 151.101.193.164 151.101.1.164PORT STATE SERVICE
80/tcp filtered httpNmap done: 1 IP address (1 host up) scanned in 2.21 seconds
Maybe it could be a ipv6 problem? If I ping url that I can visit, it's always an ipv6 ip. But if I ping the url I cannot visit, it's always an ipv4 ip.
Offline
I also try disable NetworkManager and use wpa_supplicant and dhclient directly to connect to wifi. Same problem.
Offline
Maybe it could be a ipv6 problem? If I ping url that I can visit, it's always an ipv6 ip. But if I ping the url I cannot visit, it's always an ipv4 ip.
Maybe.
What's the output of "ip a; ip r" in the wired and the wifi case?
I assume you ran "nmap -Pn" because the host didn't respond at all?
Offline
Maybe it could be a ipv6 problem? If I ping url that I can visit, it's always an ipv6 ip. But if I ping the url I cannot visit, it's always an ipv4 ip.
Maybe.
What's the output of "ip a; ip r" in the wired and the wifi case?I assume you ran "nmap -Pn" because the host didn't respond at all?
On wifi
ip a;ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether cc:f9:e4:9c:5a:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.37/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
valid_lft 43169sec preferred_lft 43169sec
inet6 2a01:e35:243b:e80:1ea2:e3ba:a857:46d4/64 scope global dynamic noprefixroute
valid_lft 86371sec preferred_lft 86371sec
inet6 fe80::f77f:3243:47df:690c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
default via 192.168.1.254 dev wlp0s20f3 proto dhcp metric 20600
192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.37 metric 600
wired
ip a;ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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: wlp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether ba:64:8c:f8:36:b9 brd ff:ff:ff:ff:ff:ff permaddr cc:f9:e4:9c:5a:0e
3: enp56s0u1u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 34:29:8f:99:0e:72 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/24 brd 192.168.1.255 scope global dynamic noprefixroute enp56s0u1u3
valid_lft 43177sec preferred_lft 43177sec
inet6 2a01:e35:243b:e80:5938:c44a:cdf5:d6fa/64 scope global dynamic noprefixroute
valid_lft 86379sec preferred_lft 86379sec
inet6 fe80::291a:2fc9:72f8:7e42/64 scope link noprefixroute
valid_lft forever preferred_lft forever
default via 192.168.1.254 dev enp56s0u1u3 proto dhcp metric 100
192.168.1.0/24 dev enp56s0u1u3 proto kernel scope link src 192.168.1.5 metric 100
Yes nmap tells me the host seems down.
Offline
Hmm very strange that if I switch to a wifi 2.4G it works. But 5G has the above problem. On the same router.
What could be wrong? Wireless card driver?
Last edited by darkjh (2020-08-03 17:24:27)
Offline
Ok finally it's not the same router. The connection in 5G band I connect to is from a tp link repeater. I restart the repeater and the problem just go away.
Thanks seth for your help!
Offline
Well, the problem solved itself with your help - I didn't do a lot.
I like that kind of problem
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline