WiFi connects, but pages don't load

This problem is tied to one WiFi network only. I tested it using System Monitor's data activity measurement. After connecting, there is about 40 seconds of working connection, then it linearly decreases to almost zero within about 20 seconds, then there is a big spike in activity, then it goes dead. The computer is still ostensibly connected, but it claims signal strength is 0%. I tried "ping google.com":

ping: google.com: Name or service not known

All other devices connect to this WiFi without problems. When I create a WiFi bridge through my phone and connect to that, it works normally. The WiFi had previously worked fine for many months. I don't recall any particular change I could link to the problem.

All network issues I found on Ask Ubuntu were "unable to connect to network" problems, but my computer stays connected the entire time. The WiFi just eventually stops transmitting any information.

I had Ubuntu 18.04 and upgraded to 20.04. The problem persists.

EDIT: In response to johncli:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

etc.

Is the rest of your answer applicable in this situation?

3: The file clearly cannot be edited by hand:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search home

The output of ifconfig:

enp3s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether a8:1e:84:81:4b:4e txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 18233 bytes 1725789 (1.7 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 18233 bytes 1725789 (1.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.136 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::fbeb:d153:68ac:c2f1 prefixlen 64 scopeid 0x20<link> ether 3c:a0:67:af:bb:61 txqueuelen 1000 (Ethernet) RX packets 1161729 bytes 1493982625 (1.4 GB) RX errors 0 dropped 600 overruns 0 frame 0 TX packets 470115 bytes 91019517 (91.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

The output of route -n:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 600 0 0 wlp2s0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlp2s0
192.168.0.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp2s0

I checked this answer. It delays the problems for a while, but they reappear after half an hour or so. If it is any use, the log shows, several times,

Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

Edit 2: Reply to William Martens:

The output of sudo service network-manager status:

NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-10-08 17:44:44 CEST; 20h ago Docs: man:NetworkManager(8) Main PID: 35927 (NetworkManager) Tasks: 4 (limit: 9322) Memory: 7.8M CGroup: / └─35927 /usr/sbin/NetworkManager --no-daemon
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9406] dhcp4 (wlp2s0): option requested_rfc3442_classless_static_routes => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9406] dhcp4 (wlp2s0): option requested_root_path => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9406] dhcp4 (wlp2s0): option requested_routers => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9406] dhcp4 (wlp2s0): option requested_static_routes => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9406] dhcp4 (wlp2s0): option requested_subnet_mask => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9407] dhcp4 (wlp2s0): option requested_time_offset => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9407] dhcp4 (wlp2s0): option requested_wpad => '1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9407] dhcp4 (wlp2s0): option routers => '192.168.0.1'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9407] dhcp4 (wlp2s0): option subnet_mask => '255.255.255.0'
říj 09 14:15:48 matej-Aspire-E5-575 NetworkManager[35927]: <info> [1602245748.9407] dhcp4 (wlp2s0): state changed extended -> extended

(říj would presumably be oct in English)

EDIT 3:

There is nothing I did with any wireless settings that directly preceded this. All the answers to similar questions are either diagnostics or shots in the dark. The ones that seem to have worked are all restarts, but it isn't clear how the problem originated.

2 Answers

Try to ping 8.8.8.8 or any other ip to check internet access.
- you can ping any other public address that is "up" for sure
If the ping success then you have internet and the problem is on DNS configuration.
Exec the command sudo nano /etc/resolv.conf.
It is probably sets on "nameserver" as localhost ip (127.0.0.53).
If it is on 127.0.0.53 change the address to 1.1.1.1 or 8.8.8.8.
- you can change the address to any good Domain Name Server.
- i am using 1.1.1.1 as my favorite.
Save the resolv.conf file.
Exec the command sudo systemctl restart network-manager.service
Try to ping a domain address like google.com or just open the web and surf to a website to check if the change helped out.
Please comment the output or the settings that you find out for we can solve the issue togther.

If you haven't already, try this:

sudo service networking stop
sudo service networking start
sudo service networking reload
sudo service network-manager stop
sudo service network-manager start
sudo service network-manager reload

If you have Ethernet (working, that is) Connect to ethernet and:

sudo apt update
sudo apt upgrade
sudo apt autoremove

**If you have net-tools installed: **

sudo apt remove net-tools
sudo apt install net-tools

If you do not have net-tools installed

sudo apt install net-tools

EDIT:

Can you try the answer from here? It's exactly the same problem

Wifi apparently connected, but webpages won't load

And, if possible: can you try to run the diagnostic tool they are mentioning in the post?

" I found a thread that used a diagnostic tool (wireless-info on github), which might help you guys figure out if there's anything wrong with my current system/drivers. "

+EDIT 3:

original linkWiFi disconnects for few seconds and resumes

These lines, according to the problem you're facing, is in my opinion quite interesting: (I changed it slightly, look on the original link) But, I can't stress this enough; what I skipped is what I thought was not going to work, which is why I suggest you reading the link, with the original answer!

install or reinstall wpa_supplicant

sudo apt-get --reinstall install wpasupplicant

upgrade and install build-essential and linux-headers

sudo apt-get update
sudo apt upgrade
sudo apt-get install build-essential linux-headers-generic

and

sudo ifdown wlan0
sudo ifup wlan0

You can reboot

Small questions that could be worth looking into:

You don't have any VPN software installed, that is blocking it /disrupting ?
I thought of
You haven't used macchanger? (or, supplied wrong mac - or anything like that?) I thought of this from here; Ubuntu shows that it's connected to wifi, but will not load any pages
You have not tried something with airmon? from here:

Killing interfering processes

This command stops network managers then kill interfering processes left:

~# airmon-ng check kill
Killing these processes: PID Name 870 dhclient 1115 wpa_supplicant

Hope this can be useful! Good luck;

Regards.

Fame Burst

WiFi connects, but pages don't load

2 Answers

Can you try the answer from here? It's exactly the same problem

Your Answer

Sign up or log in

Post as a guest

You Might Also Like

How do I get wires in fallout 4 to connect them to my generators

User Tikolu - Arqade

Highest damage dealt in Pokemon?

How do you take a screenshot in Hearthstone?