Re: [Dnsmasq-discuss] (no subject)
On Sat, Aug 06, 2022 at 08:16:26PM +1000, Michelangelo Lauria via Dnsmasq-discuss wrote: > How can I find a topic in the discussion list for DNSMASQ ? I am having > issues enabling DNSSEC for Centos7 and I am unable to read the archives > unless I download and unzip each file. https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/thread.html ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq not re-reading resolv file
On Thu, Jul 21, 2022 at 12:13:38PM +0100, Tom Cook wrote: > I have a hard-to-reproduce situation where dnsmasq doesn't re-read the > configured resolv conf when it changes. I'm running dnsmasq 2.79. I > realise that this is rather behind the times but upgrading it on the > platform in question is non-trivial; could someone suggest whether > updating is likely to fix this problem please? > Recent monthly posting: https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016468.html ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Possible to reuse Cache over restats?
On Sat, Jul 02, 2022 at 08:29:32PM +, Dan Schaper wrote: > From: "Bottom Post Request via Dnsmasq-discuss" > > > > > Visit website that is NOT ours > > > Nice, very helpful. > > > > ... By staying on GitHub, established FOSS communities bring > > newcomers to this proprietary platform — expanding GitHub's > > reach. and limiting the imaginations of the next generation of > > FOSS developers. > > > > See the whole text at website of one of ours: > > https://sfconservancy.org/GiveUpGitHub/ > > > > Geert, > > Can you keep the political holy war crap off this list? The words "holy" and "political" triggered me to retrieve what Gandhi said about those two: Those who say religion has nothing to do with politics do not know what religion is. While doing that I stubbled upon another Gandhi quote My religion is based on truth and non-violence. Truth is my God. Non-violence is the means of realising him. > Thanks! It is probably for not yet having seen: } } Acknowledge on "I'm still stuck", but what about: } } * Reread the manual page and in particular --log-queries option } } ??? } } Three questionmarks, okay I did something wrong? } I reread the man page and figure out some misunderstands about } --no-daemon mode, and I think Geert Stappers, wanted to have my } configuration file? Nope. In https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016453.html was already the "read the fine manual" worded as "Reread the manual page and in particular --log-queries option" and in https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016457.html was the "Read The Fantastic Manual" repeated because there was no proof of that it had been done. Is was good to see that https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016460.html does has proof that RTFM has been done. Groeten Geert Stappers -- Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Valid and Preferred lifetimes are not decreasing in RA's(captures)
On Wed, Jun 22, 2022 at 10:22:13AM +0530, Jagadeesh M wrote: > Hi, > > Wanted your suggestion regarding a problem we are seeing with dnsmasq > configuration. > > At first, we had an issue where we did have dnsmasq sending RA's with > multiple prefixes as we had multiple ipv6 addresses(with different > prefixes) on the interface. > So, as per our requirement we made dnsmasq to send only one prefix (clients > should configure ipv6 address with only that prefix), we changed dhcp-range > config in dnsmasq. > > from > *a. dhcp-range=::,constructor:eth0,ra-stateless,24*h (with this config, > lifetimes are decrementing in clients properly) > > to > *b. dhcp-range=eth0,1234::,ra-stateless,24h* > > But,* after changing configuration to type 'b'*, we observed that whenever > the clients receive a new RA, the clients are updating lifetimes values > back to 86400 seconds(valid and preferred lifetime values which we gave) > I mean to say, always the valid and preferred lifetimes in RA(seen through > captures) is *constant at 86400*. It is not decrementing and it is becoming > a protocol violation. > > Overall, our aim is to send only 1 ipv6 prefix in RA, even though we have > multiple ipv6 addresses(with multiple prefixes) on the interface. > Also, another question: Is there any dhcp-range configuration with which we > can exclude sending ULA prefixes in RA ? > > I tried to configure dhcp-range with other alternative ways, but nothing is > working out. > > Any help/suggestions would be highly helpful and appreciated. Suggestion: Try harder to explain the "problem". -- Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dhcp-ignore=tag:!known questions
On Thu, Jun 09, 2022 at 06:02:42PM -0400, B. Cook wrote: > I have a conf-file setting to include dhcp settings vs dnsmasq settings.. > > listen-address, user, group, logfacility, no-hosts, no-poll, no-resolv > (dnsmasq settings) > > then for dhcp settings.. > > dhcp-ignore=tag:!known > dhcp-authorative > dhcp-no-override > dhcp-generate-names > dhcp-fqdn > > (other global dhcp options) > dhcp-option=option:ntp-server,0.0.0.0 > dhcp-option=option:tzdb-timezone,"America/New_York" > dhcp-option=option:log-server,10.20.0.16 > dhcp-option=option:dns-server,10.20.0.43,10.20.32.100 > > then conf-file entries for defined ranges > > (for example) > conf-file=/etc/dnsmasq.d/dnsmasq.red.dhcp # 10.20.32/20 > conf-file=/etc/dnsmasq.d/dnsmasq.blue.dhcp # 10.20.16/20 > > dnsmasq.red.dhcp then defines global defaults for the red range.. > > domain=red.dns,10.20.0.0/20 > dhcp-range=red,10.20.12.1,10.20.14.254,255.255.240.0,4h > dhcp-option=red,option:router,10.20.0.1 # Gateway > dhcp-option=red,option:domain-name,red.dns # Domain > > dnsmasq.blue.dhcp defines options for the blue range.. > > domain=blue.dns,10.20.16.0/20 > dhcp-range=blue,10.20.28.1,10.20.30.254,255.255.240.0,4h > dhcp-option=blue,option:router,10.20.16.1 # Gateway > dhcp-option=blue,option:domain-name,blue.dns # Domain > > etc.. > > in each red, orange, yellow, green, blue, etc range (buildings) there > are hosts defined to allow dhcp.. because of the initial > dhcp-ignore=tag:!known definition at the top of the include.. > > Defining a host in red does not give them access to blue building, > etc.. all of this is fine and working; and if the above is clear below > is my problem to which I am looking for a possible solution.. > > We are adding a bunch of new Netgate devices at each building, > apparently pfsense 2.6.0 does not do dhcpd and dhcp-relay on the same > device it is one or the other.. > > Netgate 6100 fwiw, pfsense+ > DHCP Relay is currently enabled. DHCP Server canot be enabled while > the DHCP Relay is enabled on any interface. > > So just now hitting this wall; and the only (quick solution) pfsense > option is to dhcp-relay all vlans from buildings, red, orange, yellow, > etc.. so this main single dnsmasq with the dhcp-ignore=tag:!known > defined.. > > Is there a way to define another range and "dis-inherit" the !known tag? > > (for example) > conf-file=/etc/dnsmasq.d/dnsmasq.red.clear.dhcp # 10.120.36/24 > > domain=red-clear.dns,10.120.36.0/24 > dhcp-range=red-clear,10.120.36.100,10.120.36.200,255.255.240.0,4h > dhcp-option=red-clear,option:router,10.120.36.254 # Gateway > dhcp-option=red-clear,option:domain-name,red-clear.dns # Domain > > and then *not* have to manually assign each host I want to allow in this > range? > > Is that possible? } Is that possible with minimal effort by me? > > From the man page which talks about the --dhcp-ignore=tag:!known, I > cannot figure out how to 'undo it' for a range.. > > (as I have not defined it for red, orange, yellow, etc.. I cannot seem > to undefine or not define it for red-clear, orange-clear, etc.. ) > > Or is the answer to have a new entry: > > dhcp-ignore=red,orange,yellow,tag:!known > > Thank you in advance for taking the time to read this.. Acknowledge on "What is configured". Please add "What is wanted / What is desired" and "What is the actual result". See also https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016423.html (monthly posting) Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Disable dhcp-option for a single host
On Sun, Jun 05, 2022 at 07:41:03AM -0400, Brian Rossa wrote:
> Hello,
>
> I'm doing some firmware-related work and am using a --dhcp-hostsdir setup
> to test several devices on my LAN. This is working fine, but I appear to
> have hit the limits of my dnsmasq-fu when attempting to *toggle* the DHCP
> options for a particular end host.
>
> Namely, (1) the global config sets enable-tftp and (2) the hostsdir config
> for the target device starts as "{mac},{ip},set:green". During my test I
> (3) update it asynchronously to "{mac},{ip},set:red" and (4) hit dnsmasq
> with SIGHUP. According to my understanding, this will cause dnsmasq to
> clear its host cache and reload the hostsdir configs.
>
> The only remaining question, then, is how to specify individual dhcp-option
> disablement for the target. Specifically, for "red" tags, I tried the
> following configuration to override the global tftp-enable setting:
>
> dhcp-option=tag:red,option:tftp-server,""
> dhcp-option=tag:red,option:tftp-server-address,""
> dhcp-option=tag:red,option:boot-file-size,""
> dhcp-option=tag:red,option:bootfile-name,""
>
> Unfortunately, this approach seems to be flawed as the service complains
> that empty string is an invalid option and never comes up.
>
> Is there a common "disable" flag for scenarios like this? If so, I could
> not find it in the docs. If not, what approach is recommended for these
> kinds of per-host override situations?
https://duckduckgo.com/?q=scapy+dhcp
> Thanks!
Silence is hard to parse
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
