Intel Wifi Card not connecting to internet through home Network

General system Kernel, boot, graphics & hardware
1

Hi everyone, I have come across a strange issue

I am not able to connect to the internet via my home network directly through my computer, however I can connect just fine when I hotspot the very same network through my (google pixel) phone

Hardware: Acer laptop, Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20), using i3wm, updated a couple of days ago

I can ping 8.8.8.8 just fine but if i try to ping google.com the network hangs

Happy to post any more information (not sure what is relevant, which is part of my problem sadly). Any help is very much appreciated!

2

Check

dig google.com

and/or

nslookup google.com
3

I get this result:

;; communications error to 10.140.2.5#53: timed out

4

You don’t reach your DNS.

Try setting up a public one.

5

That sounds reasonable, may I ask exactly how one does this

6

Visit this website and fill in the numbers at the network settings.
Right click on the network icon in your system tray and click on configure, head over to the IPv4 tab and click on the drop down arrow, next click on the second option and fill in the numbers , do the same thing on the IPv6 tab apply the settings. Next disconnected the internet connection and enable the connection again. It would look something like this (don’t forget the comma).
DNS-servers : 9.9.9.9,149.112.112.112

7

Thank you very much for these instructions. I followed them unfortunately and the problem is persisting. I added both IPv4 and IPv6 DNS servers.

I should mention that I use nordvpn, but I have disabled that in case it was causing the issue and there is still no difference. It’s very strange, I’ve been connecting to the internet through my home network for years without issue on this computer.

It seems like the issue has now followed me to my workplace as well. The very same computer that had no issues connecting to my work wifi is also now unable to connect. I am once again having to hotspot the very same network through my phone to connect. It’s very strange.

8

If I understand correctly, you’re using the same OS across multiple networks, and having the same problem on both? However, you are able to use your wifi card to connect to the hotspot on your phone?

Can you give us a little more information for troubleshooting?

hwinfo --network
inxi -Na
uname -r

I know that when I tried using NordVPN I also had this issue (I think I was using the nordvpn-bin package). Does the issue persist if you uninstall nordVPN, or if you boot from the liveCD?

9

That’s right, I am using the same OS, for the last few years, across multiple networks, and only a couple of days ago it stopped being able to connect to the internet through them directly, but could do so without issue if I hotspot those networks through my phone.

I have uninstalled NordVPN and the problem is persisting. However, it seems like I can connect to the internet through my home network fine when I boot from a live USB.

uname -r:

6.16.8-arch3-1

Inxi -Na

Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: N/A modules: r8169 port: 3000
bus-ID: 0000:01:00.0 chip-ID: 10ec:8168 class-ID: 0200

hwinfo --network

42: None 00.0: 10700 Loopback
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: “Loopback network interface”
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

43: None 00.0: 1070a WLAN
[Created at net.126]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.sYIoCXLiMP6
SysFS ID: /class/net/wlan0
SysFS Device Link: /devices/pci0000:00/0000:00:14.3
Hardware Class: network interface
Model: “WLAN network interface”
Driver: “iwlwifi”Driver Modules: “iwlwifi”
Device File: wlan0
HW Address: 8c:55:4a:e5:70:45
Permanent HW Address: 8c:55:4a:e5:70:45
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Network controller)
10

Great! That means that this likely isn’t a hardware issue!

Just to eliminate your wireless router itself can you please try turning off your access point, waiting 30 seconds, and turning it back on?

Also, can you post the output of the following files? /etc/hosts, /etc/rc.conf, and /etc/resolve.conf? Additionally, if you try to join your router and run and ifconfig I just want to see if you’re retrieving an address.

Once that’s all done I would also like to see the output of a route to your gateway and to 8.8.8.8.

11

Yes, I tried restarting the wireless router and that did not solve the issue, unfortunately.

/etc/host:

# Standard host addresses
127.0.0.1  localhost
::1        localhost ip6-localhost ip6-loopback
ff02::1    ip6-allnodes
ff02::2    ip6-allrouters
# This host address
127.0.1.1  epicene

/etc/resolv.conf

# Generated by NetworkManager
nameserver 10.140.2.5

/etc/rc.conf does not have an output.

ifconfig:

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 64  bytes 4476 (4.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 64  bytes 4476 (4.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.72  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::6ff3:860:d941:d180  prefixlen 64  scopeid 0x20<link>
        inet6 2607:fea8:12e9:2e00::76ed  prefixlen 128  scopeid 0x0<global>
        inet6 2607:fea8:12e9:2e00:13e:cd4a:e9e1:18aa  prefixlen 64  scopeid 0x0<global>
        ether 8c:55:4a:e5:70:45  txqueuelen 1000  (Ethernet)
        RX packets 88840  bytes 96491997 (92.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 31581  bytes 13080015 (12.4 MiB)
        TX errors 0  dropped 10 overruns 0  carrier 0  collisions 0

Unfortunately I am not sure what you mean by seeing the output of a route to the gateway or 8.8.8.8, happy to follow whatever instructions you may have! Thank you for all the help so far.

12

Thanks for sharing that. My apologies for my last message being unclear. I was replying on my phone while helping my sick wife.

/etc/resolv.conf

# Generated by NetworkManager
nameserver 10.140.2.5

I can see that your DNS is configured for 10.140.2.5, but I’m not sure what this is it doesn’t really look related to the network you’re currently on. Are you able to edit this? Here is some documentation: https://man.archlinux.org/man/resolvconf.8.en and https://wiki.archlinux.org/title/Resolv.conf

I would recommend editing this in your network manager, not sure which DE you use, but usually you just edit by clicking/right-clicking on the network icon in your system tray. If that doesn’t work (as I can see you tried this before) try using nmcli.

nmcli connection show  # Find your connection name
nmcli connection modify "<your-connection-name>" ipv4.dns "8.8.8.8 8.8.4.4"
nmcli connection modify "<your-connection-name>" ipv4.ignore-auto-dns yes
nmcli connection up "<your-connection-name>"

Doing this would likely break any intranet or internal hosts you try to resolve, so you may need to adjust to suit your needs.

By “seeing the output of a route” I meant using traceroute to see the path you take. I don’t think traceroute is installed on EOS by default so you may need to do the following.

pacman -S traceroute #install the traceroute tool
traceroute 8.8.8.8 #shows the route the packet takes to google's public DNS
traceroute google.com #shows the route taken to google by DNS

The beauty of using traceroute is we can see at what point the connection fails.

To try and ping the gateway you might know what this is or you can try the following

ip r #should show the routes

Then you can ping the gateway as an example:

[user@computername ~]$ ip r
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.29 metric 600 
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.29 metric 600 
[user@computername ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.66 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.59 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.40 ms
^C
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 2.403/3.217/4.593/0.978 ms

If you’re unable to ping your gateway, your connection is broken on the LAN side, if you can ping your gateway but not 8.8.8.8 your connection is broken on the WAN side. If you can ping 8.8.8.8 but not google.com your DNS is borked.

Sorry for the super long response. I’ve been fixing broken networks over a decade now.

13

Please don’t apologize, I really appreciate the help!

Ok, I edited the dns using nmcli but the problem persists.

Output for ip r:

default via 10.0.0.1 dev wlan0 proto dhcp src 10.0.0.72 metric 20600 
10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.72 metric 600 

ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=4.04 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=3.81 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.78 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=2.42 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=4.09 ms
^C
--- 10.0.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.782/3.228/4.094/0.946 ms

Output for traceroute 8.8.8.8:

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.1)  4.133 ms  4.928 ms  4.913 ms
 2  99.225.128.1 (99.225.128.1)  15.790 ms  22.849 ms  23.173 ms

Output for google.com :

google.com: Temporary failure in name resolution
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)

It looks like the issue is with resolving DNS. Hopefully I don’t have to a fresh install of EOS (though I am glad to see that it is not a network issue). Hope your wife is better!

14

My wife is much better today thank you! She’s recovering from a surgery, so there have been a few times she’s been sick.

image
image550Ă—707 104 KB

Can you try resolvconf -u ? That might reset your DNS to something that makes sense. 10.140.2.5 is likely not able to resolve as you’re on 10.0.0.0/24.

15

Glad to hear she is better

I tried resolvconf -u:

Switch -u ignored.

16

Okay that’s strange I’m getting the same error on my end, but in hindsight I’ve never had to use this on an arch-based system.

I did some searching on the forums and found the following: I killed the internet... Resolv.conf empty - #2 by BluishHumility

I’m fairly certain that the entry stuck in resolv.conf if the problem.

17

Yeah I think you’re right that the entry is the problem

I tried to follow the instructions on that post (thanks for finding that btw!) and I wasn’t able to unlink:

~]$ sudo unlink /etc/resolv.conf
unlink: cannot unlink '/etc/resolv.conf': Operation not permitted

Edit: nvm

I was able to look up how to change the immutability status of the file and unlink it. That fixed the issue, thank you very much!

1 Like
18

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.