Re: Buster 10 - Labtop Mobilfunk Verbindungsproblem
Am 08.09.20 um 17:55 schrieb Harald Weidner:
Hallo,
Ich habe hier einen Labtop mit LTE-Mobilkarte. Damit bin ich bis dato auch
gut ins I-Net gekommen. Verbindung in Networkmanager eingerichtet, die IP's
usw. auf Automatik gestellt und los ging es.
Per LAN/ WLAN funktioniert alles nur per mobil-WWAN wird zwar die IP, DNS
und Route korrekt abgerufen bzw. eingetragen (mit Networkmanager), aber ich
bekomme dennoch keine Namensauflösung! Weder mit "nslookup" noch in
irgendeinem Programm bekomme ich eine Auflösung...auch "traceroute" liefert
mir keine erhellende Ergebnisse (mit URI keine Auflösung, mit IP nur die "3
Sterne").
Die Konfiguration sieht auf den ersten Blick okay aus.
root@dorsy1:~# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 139.7.30.126
nameserver 139.7.30.125
Sind das hier sinnvolle DNS-Server vom Provider? Kannst du sie explizit
benutzen, z.B. mit "dig @139.7.30.125 www.google.de"?
Ich würde mal die DNS Konfiguration im NetworkManager auf "manuell" stellen
und öffentlich verfügbare DNS Server eintragen, z.B. 8.8.8.8 von Google oder
9.9.9.9 (Quad9).
Warum habe ich 33 "ge-drop-te" Packete (aus ifconfig)?
Wie kann ich das herausfinden woran das liegt?
Sind vielleicht Paketfilterregeln aktiv? Was sagt "iptables -nvL"?
Ansonsten blockt der Kernel auch einige Pakete, die ihm verdächtig
erscheinen. Das steht dann i.d.R. im Kernel-Log (/var/log/kern.log).
Gruß, Harald
Hallo,
Ich habe das alles mal ausprobiert. Ich kann da noch nichts erkennen.
Auch mit festen DNS-Servern im Networkmanager ändert sich nichts...
Hier sind die Ausgaben:
-------------------------------------------------------------
root@dorsy1:~# journalctl -f
Sep 08 23:11:11 dorsy1 NetworkManager[519]: <info> [1599599471.6248]
device (wlp3s0): set-hw-addr: set MAC address to 82:0A:DE:58:A5:28
(scanning)
Sep 08 23:11:11 dorsy1 NetworkManager[519]: <info> [1599599471.7195]
device (wlp3s0): supplicant interface state: inactive -> disconnected
Sep 08 23:11:11 dorsy1 NetworkManager[519]: <info> [1599599471.7226]
device (wlp3s0): supplicant interface state: disconnected -> inactive
Sep 08 23:11:11 dorsy1 wpa_supplicant[530]: wlp3s0: Reject scan trigger
since one is already pending
Sep 08 23:11:16 dorsy1 NetworkManager[519]: <info> [1599599476.1434]
device (ttyUSB2): Activation: starting connection 'Vodafone'
(5d78b994-8d2d-4dff-a0f5-b1bddca3bae9)
Sep 08 23:11:16 dorsy1 NetworkManager[519]: <info> [1599599476.1436]
audit: op="connection-activate"
uuid="5d78b994-8d2d-4dff-a0f5-b1bddca3bae9" name="Vodafone" pid=814
uid=10000 result="success"
Sep 08 23:11:16 dorsy1 NetworkManager[519]: <info> [1599599476.1438]
device (ttyUSB2): state change: disconnected -> prepare (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:16 dorsy1 NetworkManager[519]: <info> [1599599476.1503]
manager: NetworkManager state is now CONNECTING
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] simple
connect started...
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] simple
connect state (4/8): wait to get fully enabled
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] simple
connect state (5/8): register
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] simple
connect state (6/8): bearer
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] simple
connect state (7/8): connect
Sep 08 23:11:16 dorsy1 ModemManager[562]: <info> [modem0] state changed
(registered -> connecting)
Sep 08 23:11:16 dorsy1 NetworkManager[519]: <info> [1599599476.1675]
modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting'
(reason: user-requested)
Sep 08 23:11:17 dorsy1 ModemManager[562]: <info> [modem0] state changed
(connecting -> connected)
Sep 08 23:11:17 dorsy1 ModemManager[562]: <info> [modem0] simple
connect state (8/8): all done
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1900]
modem["ttyUSB2"]: modem state changed, 'connecting' --> 'connected'
(reason: user-requested)
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1942]
device (ttyUSB2): state change: prepare -> config (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:17 dorsy1 avahi-daemon[515]: Joining mDNS multicast group
on interface enx021e101f0000.IPv4 with address 100.74.83.192.
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1948]
device (ttyUSB2): state change: config -> ip-config (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:17 dorsy1 avahi-daemon[515]: New relevant interface
enx021e101f0000.IPv4 for mDNS.
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1953]
modem-broadband[ttyUSB2]: IPv4 static configuration:
Sep 08 23:11:17 dorsy1 avahi-daemon[515]: Registering new address record
for 100.74.83.192 on enx021e101f0000.IPv4.
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1953]
modem-broadband[ttyUSB2]: address 100.74.83.192/25
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1953]
modem-broadband[ttyUSB2]: gateway 100.74.83.129
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1953]
modem-broadband[ttyUSB2]: DNS 139.7.30.126
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1954]
modem-broadband[ttyUSB2]: DNS 139.7.30.125
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1968]
device (ttyUSB2): state change: ip-config -> ip-check (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1979]
device (ttyUSB2): state change: ip-check -> secondaries (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1982]
device (ttyUSB2): state change: secondaries -> activated (reason 'none',
sys-iface-state: 'managed')
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.1992]
manager: NetworkManager state is now CONNECTED_LOCAL
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.2257]
manager: NetworkManager state is now CONNECTED_SITE
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.2259]
policy: set 'Vodafone' (enx021e101f0000) as default for IPv4 routing and DNS
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.2331]
device (ttyUSB2): Activation: successful, device activated.
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.2339]
manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 08 23:11:17 dorsy1 dbus-daemon[518]: [system] Activating via
systemd: service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7'
(uid=0 pid=519 comm="/usr/sbin/NetworkManager --no-daemon ")
Sep 08 23:11:17 dorsy1 systemd[1]: Starting Network Manager Script
Dispatcher Service...
Sep 08 23:11:17 dorsy1 dbus-daemon[518]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Sep 08 23:11:17 dorsy1 systemd[1]: Started Network Manager Script
Dispatcher Service.
Sep 08 23:11:17 dorsy1 nm-dispatcher[1836]: req:1 'up'
[enx021e101f0000]: new request (1 scripts)
Sep 08 23:11:17 dorsy1 nm-dispatcher[1836]: req:1 'up'
[enx021e101f0000]: start running ordered scripts...
Sep 08 23:11:17 dorsy1 nm-dispatcher[1836]: req:2 'connectivity-change':
new request (1 scripts)
Sep 08 23:11:17 dorsy1 NetworkManager[519]: <info> [1599599477.5152]
audit: op="statistics" arg="refresh-rate-ms" pid=814 uid=10000
result="success"
Sep 08 23:11:19 dorsy1 PackageKit[1206]: get-updates transaction
/3375_aeabbcbc from uid 10000 finished with success after 1238ms
Sep 08 23:11:27 dorsy1 nm-dispatcher[1836]: req:2 'connectivity-change':
start running ordered scripts...
Sep 08 23:11:35 dorsy1 kernel: perf: interrupt took too long (3954 >
3950), lowering kernel.perf_event_max_sample_rate to 50500
Sep 08 23:11:37 dorsy1 systemd[1]: NetworkManager-dispatcher.service:
Succeeded.
Sep 08 23:11:40 dorsy1 NetworkManager[519]: <info> [1599599500.4346]
audit: op="statistics" arg="refresh-rate-ms" pid=814 uid=10000
result="success"
Sep 08 23:13:44 dorsy1 NetworkManager[519]: <info> [1599599624.5248]
audit: op="statistics" arg="refresh-rate-ms" pid=814 uid=10000
result="success"
Sep 08 23:13:52 dorsy1 NetworkManager[519]: <info> [1599599632.3776]
audit: op="statistics" arg="refresh-rate-ms" pid=814 uid=10000
result="success"
Sep 08 23:14:13 dorsy1 kernel: perf: interrupt took too long (4973 >
4942), lowering kernel.perf_event_max_sample_rate to 40000
-------------------------------------------------------------
root@dorsy1:~# dig @139.7.30.125 www.google.de
; <<>> DiG 9.16.6-Debian <<>> @139.7.30.125 www.google.de
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@dorsy1:~# dig @9.9.9.9 www.google.de
; <<>> DiG 9.16.6-Debian <<>> @9.9.9.9 www.google.de
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@dorsy1:~# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 8.8.8.8
root@dorsy1:~# ifconfig
...
enx021e101f0000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 100.74.83.192 netmask 255.255.255.128 broadcast
100.74.83.255
ether 02:1e:10:1f:00:00 txqueuelen 1000 (Ethernet)
RX packets 87 bytes 9306 (9.0 KiB)
RX errors 0 dropped 80 overruns 0 frame 0
TX packets 141 bytes 18043 (17.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
....
-------------------------------------------------------------
root@dorsy1:~# nslookup debian.org
;; connection timed out; no servers could be reached
root@dorsy1:~# ping -c3 130.89.148.77
PING 130.89.148.77 (130.89.148.77) 56(84) bytes of data.
--- 130.89.148.77 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 53ms
root@dorsy1:~# dig @9.9.9.9 www.google.de
; <<>> DiG 9.16.6-Debian <<>> @9.9.9.9 www.google.de
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
-------------------------------------------------------------
root@dorsy1:~# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
-------------------------------------------------------------
--
Mit freundlichen Grüßen
Sebastian Reinhardt
Reply to: