... 1 oder 2 Minuten sehr langsames Internet, dann wieder ewig keine Verbindung. Auch nach Neustart unverändert.
Wie stellst Du fest, dass das "Internet" langsam ist bzw. das es keine Verbindung(ins Internet) gibt?
DNS_PROBE_FINISHED_NO_INTERNET aber auf komisch
|
Anmeldungsdatum: Beiträge: 13293 |
|
|
(Themenstarter)
Anmeldungsdatum: Beiträge: Zähle... |
es ist so dass eine Seite sich langsam aufbaut oder es gibt die Meldung DNS_PROBE_FINISHED_NO_INTERNET im Browser. Meist keine Verbindung und DNS_PROBE_FINISHED_NO_INTERNET. |
|
Anmeldungsdatum: Beiträge: 13293 |
|
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
Es bleibt leider alles beim alten, fast keine bis gar keine Verbindung ins Internet. (Wie oben schon beschrieben.) Hier was ich gemacht habe mit Ausgabe: ~$ cat /etc/systemd/resolved.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] #DNS= #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=no-negative #DNSStubListener=yes #ReadEtcHosts=yes $ sudo find /etc -iname '*resolv*' [sudo] password for XXXXXXXX: /etc/resolvconf /etc/dhcp/dhclient-enter-hooks.d/resolved /etc/ppp/resolv /etc/resolv.conf /etc/openvpn/update-resolv-conf /etc/systemd/system/dbus-org.freedesktop.resolve1.service /etc/systemd/system/multi-user.target.wants/systemd-resolved.service /etc/systemd/resolved.conf $ ip r g 1.1.1.1
1.1.1.1 dev lo table 55555 src 192.168.XXX.XXX uid 1000
cache <local> $ ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 39 mai 20 2022 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf |
|
Supporter, Wikiteam
Anmeldungsdatum: Beiträge: 16818 |
cat /etc/resolv.conf resolvectl |
|
Anmeldungsdatum: Beiträge: 13293 |
|
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
~$ ip a
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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 28:d2:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a4:4e:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet 192.168.XX.XX/24 brd 192.168.XX.XX scope global dynamic noprefixroute wlp3s0
valid_lft 863894sec preferred_lft 863894sec
inet6 XXXX::XXXX:XXXX:XXXX:XXad/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: vpn: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default
link/none ~$ ip r default via 192.168.XX.XX dev wlp3s0 proto dhcp metric 600 169.254.XX.XX/16 dev wlp3s0 scope link metric 1000 192.168.XX.XX/24 dev wlp3s0 proto kernel scope link src 192.168.XX.XX metric 600 ~$ ip n s 192.168.XXXX dev wlp3s0 lladdr 3c:a6:XX:XX:XX:XX REACHABLE |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
cat /etc/resolv.conf resolvectl ~$ 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.XXX.XXX options edns0 trust-ad search XXXXX ~$ resolvectl
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 5 (vpn)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp3s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.XXX.XXX
DNS Servers: 192.168.XXX.XXX
DNS Domain: ~.
XXXXXX
Link 2 (enp0s25)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
lines 42-64/64 (END)
DNSSEC supported: no
Link 3 (wlp3s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.XXX.XXX
DNS Servers: 192.168.XXX.XXX
DNS Domain: ~.
XXXXXX
Link 2 (enp0s25)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 42-64/64 (END)
DNSSEC supported: no
Link 3 (wlp3s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.XXX.XXX
DNS Servers: 192.168.XXX.XXX
DNS Domain: ~.
XXXXXXX
Link 2 (enp0s25)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 42-64/64 (END)
|
|
Anmeldungsdatum: Beiträge: 13293 |
~$ ip r default via 192.168.XX.XX dev wlp3s0 proto dhcp metric 600 169.254.XX.XX/16 dev wlp3s0 scope link metric 1000 192.168.XX.XX/24 dev wlp3s0 proto kernel scope link src 192.168.XX.XX metric 600 ~$ ip n s 192.168.XXXX dev wlp3s0 lladdr 3c:a6:XX:XX:XX:XX REACHABLE Hattest Du evtl. eine VPN-Verbindung aktiv? "ip r g 1.1.1.1" müsste als gateway die "192.168.XX.XX" und als src-IP die IP-Adresse vom Interface wlp3s0 anzeigen. |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
~$ ip r default via 192.168.XX.XX dev wlp3s0 proto dhcp metric 600 169.254.XX.XX/16 dev wlp3s0 scope link metric 1000 192.168.XX.XX/24 dev wlp3s0 proto kernel scope link src 192.168.XX.XX metric 600 ~$ ip n s 192.168.XXXX dev wlp3s0 lladdr 3c:a6:XX:XX:XX:XX REACHABLE Ja ich hatte versucht ein VPN zu installieren, wie am Anfang geschrieben: curl -L https:// website des Anbieters/download/linux-amd64 | tar -xJ && sudo ./install.sh seitdem geht es nicht mehr. |
|
Anmeldungsdatum: Beiträge: 13293 |
