WIFI acts wierdly on RP4 Raspbian OS

Sudo It

Active Member
Joined
May 21, 2021
Messages
172
Reaction score
123
Credits
1,328
I have a raspberry pi 4 8GB model and it worked perfectly fine until few hours ago. Now it connects to my wifi router but internet doesn't work. Weird part is, telegram works though web browsers and other apps don't:rolleyes:. Does anyome have any idea why this happened?
I ran ifconfig and this is the result.

Code:
$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e4:5f:01:1b:ac:b2  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

ipv6leakintrf0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 1500
        inet 169.254.105.31  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::ca21:7ae5:ea73:c13d  prefixlen 64  scopeid 0x20<link>
        inet6 fdeb:446c:912d:8da::  prefixlen 64  scopeid 0x0<global>
        ether 46:51:0c:bc:d1:ee  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 73  bytes 21024 (20.5 KiB)
        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 10138  bytes 1138988 (1.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10138  bytes 1138988 (1.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.100  netmask 255.255.255.0  broadcast 192.168.0.255
        ether c2:09:c6:e3:92:9c  txqueuelen 1000  (Ethernet)
        RX packets 66  bytes 9664 (9.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 275  bytes 38075 (37.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Thanks in advance
 


2022-02-04_09-43.png



PS: I used a different internet connection too, but still the same.
 

Attachments

  • 2022-02-04_19-23.png
    2022-02-04_19-23.png
    88.9 KB · Views: 218
Looks like your Wireless LAN adapter is obtaining an IP address, in your case it is the 192.168.0.100. Have you tried pinging a domain name through the terminal? for example, what happens if you ping google.com? If that does not work, try pining an IP address after, for example, try pining 1.1.1.1. With these tests, I am trying to see if your DNS is the issue?
 
Looks like your Wireless LAN adapter is obtaining an IP address, in your case it is the 192.168.0.100. Have you tried pinging a domain name through the terminal? for example, what happens if you ping google.com? If that does not work, try pining an IP address after, for example, try pining 1.1.1.1. With these tests, I am trying to see if your DNS is the issue?
yes I think this is a dns issue.
20220204_205103.jpg
 
Ok, so can you edit your network config and add 1.1.1.1 or 8.8.8.8 as a DNS IP? Then you can either reboot, or restart the network stack for it to take effect. Then try pinging the DNS name again and see if it works.
 
Edit /etc/systemd/resolved.conf and add the DNS server you want at:
#DNS=
#FallbackDNS=

Save. Then reboot, that should fix it.
 
I was so much confused bcz of what happened suddenly. so instead of fixing what's wrong, I installed os again:D:D. Thank u very much for the help tho
 

Members online


Top