Re: [Dnsmasq-discuss] Debugging dnsmasq on Ubuntu

Hi Joel, 2017-03-29 17:43 UTC+03.00, Joel Whitehouse : > > Is there any way to get dnsmasq to log when it issues a new query to a > resolver? > You can run tcpdump on upstream interface and port 53. Risto ___ Dnsmasq-discuss

Re: [Dnsmasq-discuss] No more random source port

Hi Simon, 2017-03-23 0:04 UTC+02.00, Simon Kelley : > > This indicates that dnsmasq has been configured to force the packets to > the upstream server via eth0. To do that requires an operation on the > socket which can only be done as root, so the socket has to be >

Re: [Dnsmasq-discuss] No more random source port

Hi Albert, 2017-03-21 22:47 UTC+02.00, Albert ARIBAUD : > > I can't see why your dnsmasq would only use one port. This would be the > behavior for -Q0 (or -Q45807, but your dnsmasq does not have this option > in its command line. > I took in the source package and added

Re: [Dnsmasq-discuss] No more random source port

Hi, 2017-03-21 16:23 UTC+02.00, /dev/rob0 : > > Did you ever show us the contents of this --conf-dir? It could have > a file with "query-port". > -- Good point. I forgot. I did check it, though, and the directory was empty. Risto ___

Re: [Dnsmasq-discuss] No more random source port

Zyxel doesn't have a problem with same source port: https://www.dropbox.com/s/wxdl480hwr39j12/dns-03.pcap?dl=1 Same commands as in pcap-01. Risto ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk

Re: [Dnsmasq-discuss] No more random source port

Hi Albert, 2017-03-21 0:03 UTC+02.00, Albert ARIBAUD : > > Source IP is not the same in both pcaps. 1st pcap queries 8.8.8.8 and > 192.168.1.1 from 192.168.1.33, while 2nd pcap queries are from > 192.168.1.100. Can you clarify your network setup? > IP is differerent, but

Re: [Dnsmasq-discuss] No more random source port

Ok, no pcap attachments, here is a link, I hope it gets through: https://www.dropbox.com/s/3nfx2kr2kxsw0ud/dns-01.pcap?dl=1 Risto ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk

Re: [Dnsmasq-discuss] No more random source port

Hi Albert, Thanks for your help so far. 2017-03-20 22:18 UTC+02.00, Albert ARIBAUD : > > So, back to the basics: let's start with a capture of DNS traffic. Can > you run wireshark or tcpdump on your Lubuntu and capture a few requests > for resolution? > Attached a small

Re: [Dnsmasq-discuss] No more random source port

This is the pcap against TP-link: https://www.dropbox.com/s/c1edxlpmar8euvi/dns-02.pcap?dl=1 This time I only did: 1) 'host google.com 192.168.1.1' 2) 'host google.fi 192.168.1.1' The rest of the requests came through dnsmasq, and received no answer. They are repeated forever. Risto

Re: [Dnsmasq-discuss] No more random source port

2017-03-20 21:05 UTC+02.00, Albert ARIBAUD : > > (I don't see the point of this restruction but hey, that's TP-Link's > choice.) > I might use the word 'bug' instead of 'choice'. > > Ok, so the OS is not limiting the ports per se. > > You said the command line did not

Re: [Dnsmasq-discuss] No more random source port

Hi Albert, 2017-03-20 20:30 UTC+02.00, Albert ARIBAUD : > > I don't kow about dnsmasq per se, but the range of ports an application > can use is controlled by the kernel -- on my 16.04 Xubuntu, that is > defined by /proc/sys/net/ipv4/ip_local_port_range. Does your system >

[Dnsmasq-discuss] No more random source port

Hi, I'm running Lubuntu 16.04 with dnsmasq 2.75-1ubuntu0.16.04.1 under NetworkManager's control. When forwarding DNS requests, dnsmasq uses same source port (per interface) every time. Compared to Ubuntu 14.04 with dnsmasq 2.68-1ubuntu0.1, which used different ports. The command line options