Re: [Dnsmasq-discuss] getting different responses from high traffic DNSmasq

On 18/02/2021 09:44, Boris Behrens wrote: This happened after the update from v2.76 to v2.80 Is there a way how I can debug that deeper. If you're in a position to compile Dnsmasq from source and have an easily reproducible failure case (it sounds like you do), you could perform a bisection

[Dnsmasq-discuss] [PATCH] Regression: dnsmasq replies to forwarded query too early when receiving REFUSED response from upstream server

as removed from the conditional, instead of "RCODE(header) != SERVFAIL". I've attached a patch against git master that fixes the (presumed) typo and provides the behaviour I'd expect. Cheers, Chris From 42804dafeadc2a16357f5683c7a1b8111f979241 Mon Sep 17 00:00:00 2001 From: Chri

[Dnsmasq-discuss] [PATCH] --dont-mirror-queries option

on of the --dns-loop-detect option that is only capable of detecting 1-hop loops. Kurt H Maier was the brains of this operation, helping me figure out the part of forward.c that needed patching. Cheers, Chris From bc963171d1a5d46566c3835e66145532b8269ac8 Mon Sep 17 00:00:00 2001 From: Chris Nova

Re: [Dnsmasq-discuss] [PATCH] --dont-mirror-queries option

corner cases that would lead to each dnsmasq giving a different response to the same query. I agree with you: the patch adds a weird option that's only useful if you have full control over the DNS-resolving hosts on a network, but for those who do and want this kind of behaviour, it's reall

Re: [Dnsmasq-discuss] [PATCH] --dont-mirror-queries option

On 13/02/2016 13:09, Simon Kelley wrote: > Will try and remember to reply to your other points, but on this one, > the way I'd do it (assuming you don't have problems with slow or > intermittent connectivity) is to have one (primary) dnsmasq which is the > DHCP server for all three networks. You de

Re: [Dnsmasq-discuss] Compile Error.

On 24/08/16 16:31, Tony White wrote: > inotify.c:92: error: ‘IN_NONBLOCK’ undeclared (first use in this function) > inotify.c:92: error: (Each undeclared identifier is reported only once > inotify.c:92: error: for each function it appears in.) > inotify.c:92: error: ‘IN_CLOEXEC’ undeclared (first u

Re: [Dnsmasq-discuss] Bug forward upstream SERVFAIL

On 22/11/16 15:03, Martin Wetterwald wrote: > We found what we think is a bug (at least a not wanted behaviour), but > it seems it's actually a feature, when looking at commits 4ace25c5 and > 51967f980 (pasted at the end of this email). 4ace25c5 is a red herring: that provides REFUSED responses wi

Re: [Dnsmasq-discuss] returns REFUSED when first response comes from non-recursive server

On 27/02/17 10:04, Daniel Pocock wrote: > > I've observed the following problem: > > - dnsmasq is sending queries to 5 servers, one of them is not recursive > and only answers for a private domain > > - if the first response dnsmasq receives comes from the non-recursive > server (REFUSED), then

Re: [Dnsmasq-discuss] [PATCH] Delay DHCP replies for Raspberry Pi clients

On 29/03/2017 18:13, Kurt H Maier wrote: > On Wed, Mar 29, 2017 at 02:48:48PM +0200, Floris Bos wrote: >> The PXE boot firmware implementation of the Raspberry Pi 3 >> has a bug causing it to fail if it receives replies >> instantly. >> >> As a workaround ensure there is a minimum delay of one >> s

Re: [Dnsmasq-discuss] Dnsmasq, multiple subnets/gateways and option 82

On 11/05/2017 01:40, Keith Lyons wrote: > Currently I have dhcp-option=3,10.192.4.1 set for the active subnet, I > will need to add 10.192.5.1 and 10.192.6.1 for the others as they come > online. I have seen some other posts about utilizing multiple nics, each > assigned to one of the subnet, is t

[Dnsmasq-discuss] [PATCH] Fix logic of appending "." to PXE basename

;t contain a ".", the "." suffix is erroneously omitted. A patch against the git HEAD is attached that inverts this logic and restores the expected behaviour of --pxe-service. >From 38a119885b1a2a16c515ba65681d0a9a97bb7cd0 Mon Sep 17 00:00:00 2001 From: Chris Novakovic Date: Mo

Re: [Dnsmasq-discuss] Dnsmasq-2.77 pxelinux.0 question

On 05/06/17 12:38, Steven Shiau wrote: > I have a question about using dnsmasq 2.77 as the PXE booting service. > This is running on Debian Sid amd64 version, the package is from Debian > repository: > > root@debian:~# dpkg -l dnsmasq > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/In

Re: [Dnsmasq-discuss] [PATCH] --dont-mirror-queries option - updated for 2.77

solution >> anywhere? >> >> Thanks, >> khm >> >> > No draft code yet. No version of dnsmasq has ever removed EDNS0 from > queries, and note that queries are all we're concerned about here. The > EDNS0 options should not be included in replies. Packet s

Re: [Dnsmasq-discuss] Tag from interface name?

On 03/07/2017 15:53, Brian Rak wrote: > I'd like to be able to classify DHCP requests based on the interface > they come in on. I'd like to have a tag based on the interface name > (so, if the request came in over br0, I'd have a br0 tag to match on). > > Is there any way of accomplishing this wi

Re: [Dnsmasq-discuss] Tag from interface name?

On 08/07/2017 20:46, Simon Kelley wrote: > On 04/07/17 09:06, Chris Novakovic wrote: >> On 03/07/2017 15:53, Brian Rak wrote: >>> I'd like to be able to classify DHCP requests based on the interface >>> they come in on. I'd like to have a tag based on the i

Re: [Dnsmasq-discuss] Funny came behaviour

On 09/07/2017 09:17, Gareth Howell wrote: > I have dnsmasq serving IP addresses. I also have domain=agdon.net > and a couple of cname= lines > (see https://pastebin.com/aGLrWa5K for more detail) > > However, if you look at the transcript > at https://pastebin.com/YdVpx7y1 you

Re: [Dnsmasq-discuss] [PATCH] Fix broken translations after commit 730c6745

On 17/07/2017 18:50, Chris Novakovic wrote: > Commit 730c6745 makes a number of fixes to typos, among them the > messages reporting that asynchronous logging is unavailable in Solaris > and Android in src/dnsmasq.c. This is a gettext-localised string, and > the corresponding msgids in

[Dnsmasq-discuss] [PATCH] Fix broken translations after commit 730c6745

typo fixes, breaking these two translations for all localisations. This commit ports the typo fixes to the affected msgids in po/*.po, fixing all translations for these strings. From 93cc62dabb33bd141741684fa7e95303966506c5 Mon Sep 17 00:00:00 2001 From: Chris Novakovic Date: Mon, 17 Jul 2017 18:

Re: [Dnsmasq-discuss] ProxyDHCP with dnsmasq 2.77 - wrong suffix

On 31/08/2017 08:39, Aaron Salwat wrote: > I've noticed what seems to be a bug with the NBP suffix for BIOS > clients in version 2.77 for dnsmasq, which was working fine in 2.76. > > I have not confirmed if the issue occurs within a normal DHCP/PXE > environment, only for proxyDHCP. > > > Along

Re: [Dnsmasq-discuss] pxe booti: dnsmasq 2.76 not sending dhcp-force-option 66

On 02/09/2017 13:46, Floris Bos wrote: > Pi 3 does not like instant replies. > > Add to dnsmasq.conf: > > dhcp-reply-delay=1 Just a warning, however: Floris's patch that adds this feature [1] was committed between 2.76 and 2.77, so you'll either have to upgrade to 2.77 or recompile 2.76 with tha

Re: [Dnsmasq-discuss] Source IP address of forwarded DNS queries

On 05/09/2017 10:00, Steffen Heil (Mailinglisten) wrote: > We are using dnsmasq as a dns proxy. We serve some local entries but most > entries are forwarded to another dns server. > Is there a way to specify the ip address the outgoing (forwarded) dns > requests are send with? The --server optio

Re: [Dnsmasq-discuss] DHCP Relay across VLANs

On 15/09/2017 01:26, Ray Ramadorai wrote: > Software versions working case: > > Kernel:  Linux Openwrt 3.18.23 #1 SMP Sun Jan 31 15:32:38 CET 2016 > x86_64 GNU/Linux > > DNSMasq:  Dnsmasq version 2.73  Copyright (c) 2000-2015 Simon Kelley > > Compile time options: IPv6 GNU-getopt no-DBus no-i18n

Re: [Dnsmasq-discuss] dnsmasq on FreeBSD not listening on specified interfaces

On 21/09/2017 12:19, Jason Mann wrote: > I have tried to configure dnsmasq to listen only on 'lan' and 'lan.129' > (plus the implicit 'lo0') with the following directives: > > interface=lan > interface=lan.129 > > However, after a restart, dnsmasq is still listening on all interfaces (*) >From t

Re: [Dnsmasq-discuss] DNSMASQ Not Sending ACK?

On 21/09/2017 14:15, Jason Kary (jkary) wrote: > I’m working on getting DNSMASQ to work with IP RELAY in a VxLAN environment. > Using tcpdump we were able to trace a DHCP relay request to the ‘request’ > message. It appears the server is not sending an DHCP ACK message. Which version of dnsm

Re: [Dnsmasq-discuss] DNSMASQ Not Sending ACK?

On 22/09/2017 13:42, Chris Novakovic wrote: > If you're using 2.76, It's implied by my later comment, but I should also clarify that this bug affects 2.77 as well as 2.76. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelley

Re: [Dnsmasq-discuss] DNSMASQ Not Sending ACK?

On 22/09/2017 19:24, Jason Kary (jkary) wrote: > Thank you for the update. We are running version 2.66 2.66 is four and a half years old now, and those parts of the codebase have been overhauled quite a lot since then --- is there any way you can test your setup with 2.77 plus the patch in [2] fr

Re: [Dnsmasq-discuss] doc issue: dhcp on multiple interfaces

On 26/04/2018 11:24, Harald Dunkel wrote: > maybe I am too blind to see, but apparently something like > > dhcp-range=em1,10.0.0.10,10.0.0.254,12h > dhcp-range=em2,10.0.1.10,10.0.1.254,12h > > is not mentioned in the man page. Is it possible that the > interface part was lost? If you're

Re: [Dnsmasq-discuss] doc issue: dhcp on multiple interfaces

On 26/04/2018 12:52, Harald Dunkel wrote: > So it should be > >     dhcp-range=tag:em1,10.0.0.10,10.0.0.254,12h >     dhcp-range=tag:em2,10.0.1.10,10.0.1.254,12h > > Or is it > >     dhcp-range=set:em1,10.0.0.10,10.0.0.254,12h >     dhcp-range=set:em2,10.0.1.10,10.0.1.254,12h Assuming your inte

Re: [Dnsmasq-discuss] doc issue: dhcp on multiple interfaces

On 26/04/2018 12:52, Harald Dunkel wrote: > So it should be > >     dhcp-range=tag:em1,10.0.0.10,10.0.0.254,12h >     dhcp-range=tag:em2,10.0.1.10,10.0.1.254,12h > > Or is it > >     dhcp-range=set:em1,10.0.0.10,10.0.0.254,12h >     dhcp-range=set:em2,10.0.1.10,10.0.1.254,12h Assuming your inte

Re: [Dnsmasq-discuss] [PATCH] Enable netboot of raspberry pi (DHCP)

On 03/01/2025 10:40, Lluís Batlle i Rossell wrote: here is a patch I used to be able to netboot Raspberry Pi (2B in my case). Their bootcode.bin expects a proxy DHCP like for PXE, but it doesn't want a filename+sname/tftp_name to fetch a file, but instead it requests DHCP Option 66 (TFTP Server)