I connected to a new Wifi network 2 days ago. Worked well. All of a sudden, I did not have access to the internet anymore. I've got google google and have
temporary failure in name resolution. I pinged the mu gateway and I got no answer. A few hours later, I worked again. Then he stopped working again. I spent 2 hours trying solutions found online now. I have no idea what is causing this. Here is a starting point:
▶ iwconfig lo no wireless extensions. wlp2s0 IEEE 802.11 ESSID:"fisch" Mode:Managed Frequency:2.462 GHz Access Point: 78:54:2E:51:7C:7E Bit Rate=65 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=69/70 Signal level=-41 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:24 Missed beacon:0 ▶ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 lo-skami # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ▶ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 ▶ ip r default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.103 metric 600 ▶ ping www.google.com ping: www.google.com: Temporary failure in name resolution ▶ ping -c4 126.96.36.199 PING 188.8.131.52 (184.108.40.206) 56(84) bytes of data. --- 220.127.116.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 52ms ▶ ping -c3 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. --- 192.168.0.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 44ms ▶ ping -c3 1.1 PING 1.1 (18.104.22.168) 56(84) bytes of data. --- 1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 13ms
It is this Linux installation that is faulty. I had a parallel start for two distributions. The networking of the other distribution works well.
btw. networking for this faulty distribution has also worked in all other wifi networks on which I was. At least until 2 days ago. I have not checked with other networks since then.
Do you have any idea of the cause of this? Do you need other order outputs or newspapers?