Eu tenho uma situação semelhante à explicada em: Configuração de DNS de banda larga móvel
Se eu tentar usar meu adaptador USB de banda larga sem fio para acessar a internet, por algum tempo (não sei exatamente quanto tempo eu uso apenas irregularmente - eu penso em 2 semanas ou mais), ele se conecta com sucesso, mas eu Não consigo navegar ou receber e-mails, pois não tenho nenhuma configuração de DNS em funcionamento. minhas conexões Wi-Fi ou LAN estão funcionando bem.
o que eu encontrei até agora / porque eu acho que é apenas o problema do DNS:
my /etc/resolv.conf tem esta aparência:
$ cat /etc/resolv.conf
# 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
então eu sei que o serviço systemd-resolve manipula dns.
se eu tiver uma conexão sem fio ativa, obtenho:
$ systemd-resolve --status
Global
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 6 (ppp0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp3s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 80.69.96.12
81.210.129.4
Link 2 (eno1)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
tudo bem - há DNS Servers atribuídos.
se eu desativar a conexão sem fio e ativar minha banda larga móvel, obtenho:
$ systemd-resolve --status
Global
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 6 (ppp0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp3s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (eno1)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
parece que não há nenhuma configuração de dns acontecendo. se eu verificar a conexão de rede com nmcli eu vejo que existem endereços de DNS atribuídos automaticamente no perfil:
$ nmcli device show
GENERAL.DEVICE: ttyUSB2
GENERAL.TYPE: gsm
GENERAL.HWADDR: (unknown)
GENERAL.MTU: 0
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: 1&1
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/6
IP4.ADDRESS[1]: 10.222.91.51/32
IP4.GATEWAY: 0.0.0.0
IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]: 139.7.30.125
IP4.DNS[2]: 139.7.30.126
GENERAL.DEVICE: wlp3s0
GENERAL.TYPE: wifi
GENERAL.HWADDR: 4E:D3:55:95:9D:9F
GENERAL.MTU: 0
GENERAL.STATE: 30 (disconnected)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
GENERAL.DEVICE: eno1
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 5C:26:0A:01:41:05
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: off
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY:
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY:
e se eu tentar verificar com o status do systemd eu recebo:
$ systemctl status wpa_supplicant.service NetworkManager.service systemd-resolved
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2017-11-19 14:14:51 CET; 4h 4min ago
Main PID: 1275 (wpa_supplicant)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/wpa_supplicant.service
└─1275 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
Nov 19 18:01:15 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 92:5c:14:74:dc:ca completed [id=0 id_str=]
Nov 19 18:01:15 stefan-Latitude-E6510 wpa_supplicant[1275]: EAPOL: Received IEEE 802.1X EAPOL-Key even though this was not accepted - ignoring this packet
Nov 19 18:01:15 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-69 noise=9999 txrate=1000
Nov 19 18:01:18 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 19 18:03:58 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=28900
Nov 19 18:12:07 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=26000
Nov 19 18:12:08 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-71 noise=9999 txrate=26000
Nov 19 18:12:09 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-78 noise=9999 txrate=26000
Nov 19 18:14:22 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=92:5c:14:74:dc:ca reason=3 locally_generated=1
Nov 19 18:14:22 stefan-Latitude-E6510 wpa_supplicant[1275]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2017-11-19 14:14:49 CET; 4h 4min ago
Docs: man:NetworkManager(8)
Main PID: 1098 (NetworkManager)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
├─1098 /usr/sbin/NetworkManager --no-daemon
└─6631 /usr/sbin/pppd nodetach lock nodefaultroute ipv6 , user D2 ttyUSB2 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 idle 0 ipparam /org/freedesktop/NetworkManager/PPP/2 plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.1267] dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 7487
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.1267] dhcp4 (wlp3s0): state changed bound -> done
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.1424] device (wlp3s0): set-hw-addr: set MAC address to F6:15:2A:E4:71:5F (scanning)
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.4753] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.4755] policy: set '1&1' (ppp0) as default for IPv4 routing and DNS
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: ((devices/nm-device.c:9799)): assertion '<dropped>' failed
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <warn> [1511111662.4861] sup-iface[0x5617361c71f0,wlp3s0]: connection disconnected (reason -3)
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.4862] device (wlp3s0): supplicant interface state: completed -> disconnected
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.4969] device (wlp3s0): supplicant interface state: disconnected -> disabled
Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager[1098]: <info> [1511111662.4973] device (wlp3s0): supplicant interface state: disabled -> disconnected
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-resolved.service.d
└─resolvconf.conf
Active: active (running) since Sun 2017-11-19 14:14:49 CET; 4h 4min ago
Docs: man:systemd-resolved.service(8)
http://www.freedesktop.org/wiki/Software/systemd/resolved
http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 1195 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-resolved.service
└─1195 /lib/systemd/systemd-resolved
Nov 19 14:14:49 stefan-Latitude-E6510 systemd[1]: Started Network Name Resolution.
Nov 19 17:23:06 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
Nov 19 17:27:53 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 81.210.129.4 for interface wlp3s0.
Nov 19 17:42:30 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
Nov 19 18:04:14 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 81.210.129.4 for interface wlp3s0.
Nov 19 18:04:14 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
Nov 19 18:04:14 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 81.210.129.4 for interface wlp3s0.
Nov 19 18:04:15 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
Nov 19 18:04:16 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 81.210.129.4 for interface wlp3s0.
Nov 19 18:04:17 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
o que me chamou a atenção é: Nov 19 18:14:22 stefan-Latitude-E6510 NetworkManager [1098]: [1511111662.4755] política: definir '1 & amp; 1' (ppp0) como padrão para roteamento IPv4 e DNS
'1 & amp; 1' é o nome da minha conexão - então ok - é ativado e agora é o padrão para o dns.
mas a última entrada no log de status de systemd-resolved é
Nov 19 18:04:17 stefan-Latitude-E6510 systemd-resolved[1195]: Switching to DNS server 80.69.96.12 for interface wlp3s0.
de modo que é da última vez que mudei para a conexão sem fio - e não há atualização no switch para a conexão de banda larga ...
Se eu mudar de volta para wireless, eu posso ver o ... set as default ... ao mesmo tempo que uma entrada com ... Switching to DNS ...
Então, para mim, parece que a ativação da configuração de banda larga falha para ativar as novas configurações de DNS.
se eu tiver ativado a conexão de banda larga eu sei que é online porque eu posso pingar o ip diretamente (inclusive os endereços de DNS fornecidos de ambas as configurações ...)
Eu também tentei configurar a conexão com um servidor dns definido pelo usuário e configurá-lo para o modo automatic only IPs - mas isso não mudou o comportamento. (pude ver os endereços definidos manualmente na saída do comando nmcli device show )
espero que alguém tenha uma ideia do que posso testar / tentar que isso funcione novamente. (Eu não acho que é a maneira correta de contornar isso, desativando o sistema de resolução de dns padrão, como sugerido na pergunta vinculada.)