On Thu, Jan 10, 2019 at 05:48:26PM +0530, Sandeep K M wrote:
> On Wed, Jan 9, 2019 at 10:33 PM Simon Kelley wrote:
> > On 04/01/2019 06:25, Sandeep K M wrote:
> > >
> > > Attached are the packet captures:
> > >
> > > 1. Packets exchanged between client and relay (client-relay.pcap)
> > > 2.
I had tried dbus-monitor but message sniffing was disabled on my system
and it gave me no useful information.
I also considered tcpdump/wireshark to watch for outbound traffic on
port 53 but I also wanted to know when queries were being resolved from
cache, not just when they were resolved
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
On Wed, Mar 29, 2017 at 09:43:33AM -0500, Joel Whitehouse wrote:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on 127.0.1.1.
> When I issue a dig query, dig informs me it's using 127.0.1.1 as its
> resolver:
>
> ;; Query time: 3 msec
> ;; SERVER: 127.0.1.1#53(127.0.1.1)
> ;;
On Wednesday 29 March 2017 09:43:33 Joel Whitehouse wrote:
> Both the file /var/run/NetworkManager/dnsmasq.conf and the directory
> /etc/NetworkManager/dnsmasq.d/ are empty, so it's likely that dnsmasq is
> receiving its resovlers from Network Manager over the dbus interface.
Right.
> Is there
Hi Joel,
Le Wed, 29 Mar 2017 09:43:33 -0500
Joel Whitehouse a écrit:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on
> 127.0.1.1. When I issue a dig query, dig informs me it's using
> 127.0.1.1 as its resolver:
>
> ;; Query time: 3 msec
> ;;
On Wed, Mar 29, 2017 at 09:43:33AM -0500, Joel Whitehouse wrote:
> I'm running ubuntu 14, which uses dnsmasq as a local resolver on 127.0.1.1.
> When I issue a dig query, dig informs me it's using 127.0.1.1 as its
> resolver:
>
> ;; Query time: 3 msec
> ;; SERVER: 127.0.1.1#53(127.0.1.1)
> ;;
I'm running ubuntu 14, which uses dnsmasq as a local resolver on
127.0.1.1. When I issue a dig query, dig informs me it's using
127.0.1.1 as its resolver:
;; Query time: 3 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Wed Mar 29 09:36:06 CDT 2017
;; MSG SIZE rcvd: 63
However, I would
Is there any way to get additonal debugging information out of dnsmasq?
I'm running into an issue where I'm seeing 'DHCPDISCOVER(eth0) X Y no
address available', but it's not particularly clear to me why this is
happening. Is there a way to log the contents of the DISCOVER packet?
I know I
On 11/02/14 15:12, Brian Rak wrote:
Is there any way to get additonal debugging information out of dnsmasq?
I'm running into an issue where I'm seeing 'DHCPDISCOVER(eth0) X Y no
address available', but it's not particularly clear to me why this is
happening. Is there a way to log the contents
Sorry, should have mentioned that I already have that enabled.
That gives me some extra info:
Feb 11 11:14:07 x dnsmasq-dhcp[2278]: 3227716451 DHCPDISCOVER(eth0)
00:25:90:d6:ac:25 no address available
Feb 11 11:14:08 x dnsmasq-dhcp[2278]: 467005255 available DHCP range:
10.x.10 -- 10.x.250
11 matches
Mail list logo