[Dnsmasq-discuss] Bluetooth networking issue

Thu Jan 26 21:22:14 GMT 2017

Simon,

Thanks.  dnsmasq is getting the queries, you can see them in the log:

Jan 18 16:56:07 datasoft-travel dnsmasq[7973]: query[A] www.cnn.com from 
127.0.0.1

But there is neither a reply nor an error message after the query is 
received.  "dig www.cnn.com" shows "status: REFUSED".  To be clear, the 
queries are originating from the laptop and should be routed through the 
bluetooth network connection.  The network connection is there and I can 
ping the nameserver over the bluetooth network, but it's having trouble 
with the DNS.  I don't think the bluetooth part of it is exactly 
relevant, but I'm assuming that somehow disconnecting and reconnecting a 
bluetooth network does something different than disconnecting and 
reconnecting a wifi network.

Aaron

On 01/26/2017 11:25 AM, Simon Kelley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Make sure you're not getting confused between "connection refused" and
> a DNS reply with a REFUSED return code. The former means there's
> nothing listening on port 53 at the address you're sending the query
> to, which is possible if the bluetooth interface is new and network
> manager hasn't prodded dnsmasq suitably. The later means the the query
> is getting to dnsmasq and it's replying, which as you say, it only
> does when it has no upstream servers. The log you posted doesn't seem
> to show that dnsmasq has no servers, or that it's getting queries from
> any address which could plausibly be a bluetooth device, so the
> connection refused option looks quite likely, but it's important to
> work which it is.
>
>
>
> Cheers,
>
> Simon.
>
>
> On 26/01/17 17:26, Aaron Brice wrote:
>> So, to summarize: after disconnecting and reconnecting the network
>> device, DNS queries are returning REFUSED, with no error messages
>> showing in the logs.  Is there any option to increase verbosity?  I
>> read somewhere that the only reason dnsmasq returns REFUSED is if
>> there are no nameservers or one of the nameservers returns REFUSED
>> status. However there are several "using nameserver" entries in the
>> logs, and no traffic occurs to those nameservers.
>>
>> Thanks, Aaron
>>
>> On 01/23/2017 02:47 PM, Aaron Brice wrote:
>>> I am testing a bluetooth networking (bnep0) device on an Ubuntu
>>> 16.04 laptop.  Everything works fine if I comment out dns=dnsmasq
>>> from the NetworkManager.conf.  With dnsmasq on, everything works
>>> fine the first time I connect my bluetooth network device.  When
>>> I disconnect it and reconnect it, DNS lookups fail immediately
>>> with a REFUSED status. When I restart the NetworkManager service
>>> everything works again.
>>>
>>> I turned on log-queries, and it shows the query is received, but
>>> no response is shown in the logs and also no error messages.  The
>>> logs show that on the reconnect the DHCP succeeded, and dnsmasq
>>> received the upstream nameservers from the DHCP response, but
>>> tcpdump does not show any DNS traffic to those nameservers when I
>>> use dig.  Is there a verbosity setting that might show some more
>>> information on why the DNS queries are being refused?
>>>
>>> Logs:
>>>
>>> Jan 18 16:56:02 datasoft-travel dnsmasq[7973]: setting upstream
>>> servers from DBus Jan 18 16:56:02 datasoft-travel dnsmasq[7973]:
>>> using nameserver 192.168.10.2#53(via bnep0) Jan 18 16:56:02
>>> datasoft-travel dnsmasq[7973]: using nameserver
>>> 68.105.29.16#53(via bnep0) Jan 18 16:56:02 datasoft-travel
>>> dnsmasq[7973]: using nameserver 68.105.28.16#53(via bnep0) Jan 18
>>> 16:56:02 datasoft-travel dnsmasq[7973]: query[A] daisy.ubuntu.com
>>> from 127.0.0.1 Jan 18 16:56:02 datasoft-travel whoopsie[883]:
>>> [16:56:02] Cannot reach: https://daisy.ubuntu.com Jan 18 16:56:02
>>> datasoft-travel dnsmasq[7973]: query[SOA] local from 127.0.0.1
>>> Jan 18 16:56:02 datasoft-travel NetworkManager[7926]: <info>
>>> [1484783762.2180] device (5C:31:3E:EC:71:B3): Activation:
>>> successful, device activated. Jan 18 16:56:02 datasoft-travel
>>> nm-dispatcher: req:2 'up' [bnep0]: new request (1 scripts) Jan 18
>>> 16:56:02 datasoft-travel nm-dispatcher: req:2 'up' [bnep0]: start
>>> running ordered scripts... Jan 18 16:56:02 datasoft-travel
>>> whoopsie[883]: [16:56:02] The default IPv4 route is:
>>> /org/freedesktop/NetworkManager/ActiveConnection/2 Jan 18
>>> 16:56:02 datasoft-travel deja-dup-monito[3334]: Source ID 948 was
>>> not found when attempting to remove it Jan 18 16:56:02
>>> datasoft-travel whoopsie[883]: [16:56:02] Network connection may
>>> be a paid data plan: /org/freedesktop/NetworkManager/Devices/3
>>> Jan 18 16:56:02 datasoft-travel dnsmasq[7973]: query[A]
>>> daisy.ubuntu.com from 127.0.0.1 Jan 18 16:56:02 datasoft-travel
>>> whoopsie[883]: [16:56:02] Cannot reach: https://daisy.ubuntu.com
>>> Jan 18 16:56:02 datasoft-travel dnsmasq[7973]: query[SOA] local
>>> from 127.0.0.1 Jan 18 16:56:02 datasoft-travel systemd[1]:
>>> Reloading. Jan 18 16:56:02 datasoft-travel systemd[1]:
>>> snapd.refresh.timer: Adding 4h 43min 19.514615s random time. Jan
>>> 18 16:56:02 datasoft-travel systemd[1]: apt-daily.timer: Adding
>>> 2h 3min 35.943181s random time. Jan 18 16:56:02 datasoft-travel
>>> dnsmasq[7973]: query[SOA] local from 127.0.0.1 Jan 18 16:56:02
>>> datasoft-travel systemd[1]: Reloading. Jan 18 16:56:02
>>> datasoft-travel systemd[1]: snapd.refresh.timer: Adding 1h 9min
>>> 9.603579s random time. Jan 18 16:56:02 datasoft-travel
>>> systemd[1]: apt-daily.timer: Adding 6h 19min 48.788489s random
>>> time. Jan 18 16:56:03 datasoft-travel dnsmasq[7973]: query[A]
>>> fsodqcsvqrxnlyy.corp.datasoft.com from 127.0.0.1 Jan 18 16:56:03
>>> datasoft-travel dnsmasq[7973]: query[A] xasqjyv.corp.datasoft.com
>>> from 127.0.0.1 Jan 18 16:56:03 datasoft-travel dnsmasq[7973]:
>>> query[A] ftmkaipfpi.corp.datasoft.com from 127.0.0.1 Jan 18
>>> 16:56:03 datasoft-travel dnsmasq[7973]: query[A] daisy.ubuntu.com
>>> from 127.0.0.1 Jan 18 16:56:03 datasoft-travel whoopsie[883]:
>>> [16:56:03] Cannot reach: https://daisy.ubuntu.com Jan 18 16:56:03
>>> datasoft-travel avahi-daemon[903]: Joining mDNS multicast group
>>> on interface bnep0.IPv6 with address fe80::cf57:5122:c1f0:43cd.
>>> Jan 18 16:56:03 datasoft-travel avahi-daemon[903]: New relevant
>>> interface bnep0.IPv6 for mDNS. Jan 18 16:56:03 datasoft-travel
>>> avahi-daemon[903]: Registering new address record for
>>> fe80::cf57:5122:c1f0:43cd on bnep0.*. Jan 18 16:56:03
>>> datasoft-travel dnsmasq[7973]: query[A] daisy.ubuntu.com from
>>> 127.0.0.1 Jan 18 16:56:03 datasoft-travel whoopsie[883]:
>>> [16:56:03] Cannot reach: https://daisy.ubuntu.com Jan 18 16:56:03
>>> datasoft-travel NetworkManager[7926]: <info> [1484783763.4104]
>>> policy: set 'SIDEBRIDGE_002020 Network' (bnep0) as default for
>>> IPv6 routing and DNS Jan 18 16:56:03 datasoft-travel
>>> dnsmasq[7973]: query[A] daisy.ubuntu.com from 127.0.0.1 Jan 18
>>> 16:56:03 datasoft-travel whoopsie[883]: [16:56:03] Cannot reach:
>>> https://daisy.ubuntu.com Jan 18 16:56:04 datasoft-travel
>>> dnsmasq[7973]: query[A] hmtddsov.corp.datasoft.com from
>>> 127.0.0.1 Jan 18 16:56:04 datasoft-travel dnsmasq[7973]:
>>> query[A] bigsooxchvptr.corp.datasoft.com from 127.0.0.1 Jan 18
>>> 16:56:04 datasoft-travel dnsmasq[7973]: query[A]
>>> ecbamrdeizxzc.corp.datasoft.com from 127.0.0.1 Jan 18 16:56:04
>>> datasoft-travel dnsmasq[7973]: query[A] daisy.ubuntu.com from
>>> 127.0.0.1 Jan 18 16:56:04 datasoft-travel whoopsie[883]:
>>> [16:56:04] Cannot reach: https://daisy.ubuntu.com Jan 18 16:56:04
>>> datasoft-travel ModemManager[898]: <info> Couldn't check support
>>> for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5':
>>> not supported by any plugin Jan 18 16:56:05 datasoft-travel
>>> dnsmasq[7973]: query[A] www.google.com from 127.0.0.1 Jan 18
>>> 16:56:06 datasoft-travel dnsmasq[7973]: query[A] www.google.com
>>> from 127.0.0.1 Jan 18 16:56:07 datasoft-travel dnsmasq[7973]:
>>> query[A] www.cnn.com from 127.0.0.1
>>>
>>> Thanks, Aaron
>>>
>>>
>>> _______________________________________________ Dnsmasq-discuss
>>> mailing list Dnsmasq-discuss at lists.thekelleys.org.uk
>>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>>
>>>
>>
>> _______________________________________________ Dnsmasq-discuss
>> mailing list Dnsmasq-discuss at lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBCAAGBQJYij8xAAoJEBXN2mrhkTWi/awP/jiXcWFKh4pq3gT9LYT15a40
> NDhP37WOFhd71SpBh484nLQ44cY00pWYqbTt/3AdrsnN3eDf2MKg1jmiS2+OL+bn
> +b8n+1qOtgkZqWQCA72ogxZzwigXGWdsf0njaS4I3CwQc88FZeq2qHm0tTWpSWqd
> Q6RBC/Ndwk8AKF5CgaKxPZrr/BRqtB+t3feNe9kw/N4oAllSM+gXfd8I3uisKuIa
> VRXu70qNerpqJv1rPAVfw7EY2D9uY352UGaCoxAwac4N7mWymOGBS8uGeEBPyJgL
> /ituq4KzlQclbiR6TWPsBpGMhgDkYXvSStwfvFlSdGqVTgzugk+FP4iS7d3nO2Xj
> MfA0FilELW6Qnr1dVSOPzEsQ+aMJWIo7EIDQp4oGLI32+CNVrc3xTM/pxiQoPMeB
> qZaiGdpTHCayzq8+YIrmfGu5OE2r8mT04J7tm+I0bG/3AkG8o7//VeLYOJ73qidH
> 0Zs6fPV70s6Ta8koWEIz9ea8uAfyxv3HaNOcG3PLQZ4KK7euoJ1NCNeAofKxlZ39
> xvx8aFJPQj2YtCPthz8GpNB8A71KvquiXoKEMbhW++kHqWzVu4e2/Ny65QvM67SK
> NqK7+I+XhaMBijtA8X923xWsvuUI1N+GdKfmH9TX/CmQimXNHdLeXmDf2Kw1/yHz
> 4kyj6AWQ+d7UxFAZqFI1
> =oOo9
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20170126/447016ea/attachment-0001.html>