Servidor DNS não mais levado em consideração através do meu bluetooth Samsung Galaxy S7 tethring

0

Depois de tentar adicionar manualmente rotas no NetworkManager à minha conexão Bluetooth, parece que não consigo mais me conectar, mesmo excluindo essas rotas adicionais. Eu cavei um pouco para entender o que aconteceu e aqui está o que eu encontrei:

quando eu me conecto através do applet nm, tudo parece correto, mas a internet está inacessível:

   # ping www.google.com
   ping: www.google.com: Nom ou service inconnu

A Informação de conexão do NM mostra que o DNS Primário é dado corretamente pelo DHCP:

   Primary DNS:     192.168.44.1

Usando este endereço DNS através do nslookup interativo, posso resolver www.google.com Então eu adicionei manualmente este DNS ao resolvconf usando:    servidor de nomes echo 192.168.44.1 | sudo resolvconf -a bnep0 onde bnep0 é o nome do meu dispositivo bluetooth e a Internet ficou acessível novamente.

Então, tentei entender o que é anexado durante o processo de tethering e adicionei o nível de log DEBUG aos domínios MB, DNS e BT do NetworkManager e obtive o seguinte log:

Oct 28 22:43:27 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <info>  [1509223407.8541] device (94:7B:E7:8A:0F:65): Activation: (bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via PAN.
Oct 28 22:43:27 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223407.8586] dns-mgr: (device_ip6_config_changed): queueing DNS updates (1)
Oct 28 22:43:27 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223407.8586] dns-mgr: (device_ip6_config_changed): DNS configuration did not change
Oct 28 22:43:27 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223407.8587] dns-mgr: (device_ip6_config_changed): no DNS changes to commit (0)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.8968] dns-mgr: (device_ip4_config_changed): queueing DNS updates (1)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.8969] dns-mgr: (device_ip4_config_changed): DNS configuration did not change
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.8969] dns-mgr: (device_ip4_config_changed): no DNS changes to commit (0)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9115] dns-mgr: (device_state_changed): queueing DNS updates (1)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9116] dns-mgr: (update_routing_and_dns): queueing DNS updates (2)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9119] dns-mgr: (update_routing_and_dns): DNS configuration changed
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9120] dns-mgr: (update_routing_and_dns): no DNS changes to commit (1)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9120] dns-mgr: (device_state_changed): DNS configuration changed
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9120] dns-mgr: (device_state_changed): committing DNS changes (0)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9120] dns-mgr: update-dns: updating resolv.conf
    Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9121] dns-mgr: update-dns: updating plugin systemd-resolved
    Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: ((devices/nm-device.c:9799)): assertion '<dropped>' failed
    Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: ((devices/nm-device.c:9799)): assertion '<dropped>' failed
    Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9600] dns-mgr: (device_ip4_config_changed): queueing DNS updates (1)
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9601] dns-mgr: (device_ip4_config_changed): DNS configuration did not change
Oct 28 22:43:30 hbrazzi-ThinkPad-T450s NetworkManager[24463]: <debug> [1509223410.9601] dns-mgr: (device_ip4_config_changed): no DNS changes to commit (0)

Como você pode ver. Parece haver um problema no nm-device.c na linha 9799 seguido pela indicação de que a configuração do DNS não foi alterada. Agora estou um pouco grudado e a ajuda seria bem vinda.

Como solicitado por jeremy31, aqui estão os meus pacotes relacionados ao dns:

# dpkg -l|grep dns
rc  dnsmasq-base                                    2.76-5ubuntu0.1                               amd64        Small caching DNS proxy and DHCP/TFTP server
ii  dnsutils                                        1:9.10.3.dfsg.P4-10.1ubuntu5.2                amd64        Clients provided with BIND
ii  libdns-export162                                1:9.10.3.dfsg.P4-10.1ubuntu5.2                amd64        Exported DNS Shared Library
ii  libdns162:amd64                                 1:9.10.3.dfsg.P4-10.1ubuntu5.2                amd64        DNS Shared Library used by BIND
ii  libnet-dns-perl                                 1.07-1                                        all          Perform DNS queries from a Perl script
ii  libnss-mdns:amd64                               0.10-8ubuntu1                                 amd64        NSS module for Multicast DNS name resolution

considera

    
por hpotter40 29.10.2017 / 14:23

1 resposta

0

Eu percebi isso, é um bug no (pelo menos) network-manager 1.4.4-1ubuntu3.2

Não tenho certeza de quando foi introduzido ou resolvido, mas com a resolução de DNS do gerenciador de rede 1.8.2-1ubuntu1 também funciona corretamente no wwan / 3g.

Para o Ubuntu 17.04 eu usei a versão 1.8.2 da proposta artística: link

Você precisará atualizar tanto o libnm0 quanto o network-manager: link link

Faça o download e instale por:

sudo dpkg -i libnm0_1.8.2-1ubuntu1_amd64.deb network-manager_1.8.2-1ubuntu1_amd64.deb

Eu reiniciei o network-manager e o modem-manager, embora eu ache que o modem-manager não é necessário.

sudo service network-manager restart
sudo service modem-manager restart
    
por Oskar Stenman 23.12.2017 / 10:09