If you set the log-dhcp option in the dnsmasq config, it will log all
the options being sent to the client, which should include a copy of the
vendor-class received from the client.
Cheers,
Simon.
On 09/02/2023 20:54, Carl Karsten wrote:
I want to gather stats on how often I don't get a
Luckily, we have the complete data being added by the relay
option: 82 agent-id 01:04:00:64:00:02:02:06:5c:f4:ab:af:6f:9c
That's at circuit-ID (01) of length four (04) value 00:64:00:02
and a remote-id (02) length six (06) value 5c:f4:ab:af:6f:9c
So you can either match against the remote-id
On 31/01/2023 12:01, Petr Menšík wrote:
On 19. 01. 23 11:57, Simon Kelley wrote:
Addendum.
I just looked at the latest draft (11) rather than draft zero whixh
was linked here. That makes it clear that the additional processing is
optional, so simply caching SVCB recpords might be a usable
I just released dnsmasq 2.89.
This is a small update on 2.88, mainly to fix a problem introduced in
that release. It's in theory a nasty problem, but rather difficult to
reproduce, and has only turned up "in the wild" in one report, so that
rather reduces the priority.
Nevertheless, I'd lik
It's a long time since I visited FOSDEM. I won't be there this year, but
I'd consider a trip next year.
Cheers,
Simon.
On 30/01/2023 18:25, Petr Menšík wrote:
Dear developers and users,
Already this weekend will be FOSDEM conference. I will be there, because
also DNS dev room [2] would be p
2023-01-16 at 22:46 +0000, Simon Kelley wrote:
The patch moves the relevant code to after processing of command-line
arguments, but not reading configuration file(s). I can't think of any
reason why you wouldn't want to put
no-ident
into /etc/dnsmasq.conf
Have I missed something?
On 19/01/2023 10:53, Simon Kelley wrote:
From a quick scan of the draft, this is not trivial.
It looks like one form of the record is effectively a re-implementation
of CNAME, and all replies have lots of extra processing. It's not simply
a case of adding the ability to store a new R
From a quick scan of the draft, this is not trivial.
It looks like one form of the record is effectively a re-implementation
of CNAME, and all replies have lots of extra processing. It's not simply
a case of adding the ability to store a new RRtype in the cache; replies
to queries for that typ
The patch moves the relevant code to after processing of command-line
arguments, but not reading configuration file(s). I can't think of any
reason why you wouldn't want to put
no-ident
into /etc/dnsmasq.conf
Have I missed something?
Cheers,
Simon.
On 15/01/2023 08:01, Dominik Derigs wr
I've just resolved a problem that's been reported to me off-list. It
turns out that
1) This is a bug introduced in 2.88
2) If it's triggered, it's bad: dnsmasq logs about cache internal error
and the DNS subsystem becomes broken.
3) Actually triggering the bug is pretty unlikely: I've only seen
That's not supported. Multiple processes is the best way to go.
Simon.
On 06/12/2022 18:51, Gordon Shawn wrote:
can dnsmasq listen on different ports(e.g. 53, 5353,5354,5355) in the
same time with a single process running? each port can have its own
configuration. so far I invoke multiple dn
I just released dnsmasq version 2.88
CHANGELOG below.
Cheers,
Simon.
Fix bug in --dynamic-host when an interface has /16 IPv4
address. Thanks to Mark Dietzer for spotting this.
Add --fast-dns-retry option. This gives dnsmasq the ability
to originate retries fo
On 29/11/2022 23:11, Joe Pfeiffer wrote:
Thanks -- the particular phrase in the man page that confused me (I
actually had read it) was
The set of option-names known by dnsmasq can be discovered by
running "dnsmasq --help dhcp". For example, to set the default
route option to 192.1
On 29/11/2022 23:11, Joe Pfeiffer wrote:
Thanks -- the particular phrase in the man page that confused me (I
actually had read it) was
The set of option-names known by dnsmasq can be discovered by
running "dnsmasq --help dhcp". For example, to set the default
route option to 192.1
second to be answered [1]. This
gets worse with the number of requests.
Are there any tunables which could improve this?
Regards
Jan
[1]
root@8cb67b32dabb:/# dnsmasq --version
Dnsmasq version 2.86 Copyright (c) 2000-2021 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP
On 24/11/2022 02:40, zhangjiangyu via Dnsmasq-discuss wrote:
Hi,
On 24/11/2022 06:22, Simon via Dnsmasq-discuss wrote:
On 23/11/2022 02:56, zhangjiangyu via Dnsmasq-discuss wrote:
Hi,
On 23/11/2022 07:21, Simon via Dnsmasq-discuss wrote:
The main argument for this seems to be a security
Does the openwrt config use --hostsdir to read all the files in a
directory automatically when they change? The inotify code has explicit
handling for the case that an argument to --hostdir is a symlink, so
there's a chance that's botched somewhere.
Note that's a symlink in the path to the dir
On 24/11/2022 19:22, Dominik Derigs wrote:
Hey Simon,
We observed a few cache oddities with the current release-
candidate of dnsmasq and have been able to pin this down to the
use of the new use-stale-cache option. The issue happens with
cached content being served when the actual domain dat
rk_servers() cleanup
of local_domains is using serv->next after it has freed serv. Use
additional variable just like in cleanup_servers().
Patch attached.
On 11/21/22 23:22, Simon Kelley wrote:
Thanks for this. It was in my mind that vary large number of domains
would be --local=/domain/
On 23/11/2022 02:56, zhangjiangyu via Dnsmasq-discuss wrote:
Hi,
On 23/11/2022 07:21, Simon via Dnsmasq-discuss wrote:
The main argument for this seems to be a security one: the client may
not handle a malformed packet, and a suitably crafted malformed packet
may compromise the client with
On 22/11/2022 06:47, zhangjiangyu via Dnsmasq-discuss wrote:
Hi,
On 22/11/2022 07:00:26; Simon Kelley via Dnsmasq-discuss wrote:
This behaviour arises from the way dnsmasq works. It doesn't attempt to
completely parse the reply packet, it just sends it bit-for-bit to the
original requ
11/16/22 18:23, Simon Kelley wrote:
On 10/11/2022 17:02, Petr Menšík wrote:
Hi!
I were testing my builds on rootcanary.org test, where dnsmasq is the
only one failing with DNSSEC validation enabled. I am not sure why, I
think gost crypto algorithm might be broken intentionally on Fedora
or RHE
This behaviour arises from the way dnsmasq works. It doesn't attempt to
completely parse the reply packet, it just sends it bit-for-bit to the
original requestor. This has the advantage dnsmasq as a DNS forwarder is
transparent: new packet formats or data types that it doesn't understand
are st
Thanks for this. It was in my mind that vary large number of domains
would be --local=/domain/ or --address=/domain/, not forwarding to servers.
I've applied something that looks very like your patch, but with
cosmetic code changes.
Cheers,
Simon.
On 20/11/2022 05:50, Ye Zhou wrote:
Hi al
Thanks for testing these builds. That's a genuine problem.
Fixed in 2.88rc3, in git now.
Cheers,
Simon.
On 17/11/2022 18:26, Johnny S. Lee via Dnsmasq-discuss wrote:
"local=//" means "Do not forward unqualified names to any upstream
servers", right?
It has not generated any kind of error unt
Thanks.
Testing on BSD revealed a bug in that new code on all platforms (It
calls freeaddrinfo(NULL) ) but on BSD that crashes.
2.88rc should fix all of this.
Cheers,
Simon.
On 16/11/2022 23:56, Johnny S. Lee via Dnsmasq-discuss wrote:
Adding 'sdetails->' to all three of them se
On 10/11/2022 17:02, Petr Menšík wrote:
Hi!
I were testing my builds on rootcanary.org test, where dnsmasq is the
only one failing with DNSSEC validation enabled. I am not sure why, I
think gost crypto algorithm might be broken intentionally on Fedora or
RHEL for legal reason. But I have te
substituted an o for 0 or something similar.
Too late now, it is what it is.
Simon.
-Rich
On Thu, Oct 27, 2022 at 6:49 AM Simon Kelley <mailto:si...@thekelleys.org.uk>> wrote:
On 27/10/2022 01:34, Rich Otero wrote:
> Thanks for the reply.
>
> My firs
On 21/10/2022 22:23, Michael Traxler wrote:
Hello,
dnsmasq-2.87:
It took me quite some time to figure this out :-)
When you disable the DNS-server via
port=0
the /etc/hosts file is ignored and also the
addn-hosts=
is ignored.
This then results in the problem, that the
DHCP-server still wo
On 31/10/2022 14:59, Matus UHLAR - fantomas via Dnsmasq-discuss wrote:
Hello,
I have upgraded my router which included upgrading dnsmasq 2.80 to 2.86.
(Turris OS 5.4.4 based on openwrt 19 to 6.0.1 based on OpenWrt 21.02.05)
in the current version, dnsmasq returns REFUSED for external lookups
On 31/10/2022 14:15, Rich Otero via Dnsmasq-discuss wrote:
My dnsmasq server provides DHCP for more than one hundred subnets like this:
dhcp-range=set:172.18.14.0-24,172.18.14.0,static,255.255.255.0
dhcp-option=tag:172.18.14.0-24,option:router,172.18.14.1
dhcp-range=set:172.18.15
On 27/10/2022 11:49, Simon Kelley wrote:
When I first tried this, I had the dhcp-rapid-commit option set, and
strange things were happening, which I'll look into now, so make sure
you don't have that. (I might have found a bug for my efforts).
I did indeed find a bug, and if
who has [172.18.15.1]" and
there will be no answer, because [172.18.15.1] is no longer on that
network segment, it's been moved "upstream".
But 172.18.15.1 /is/ in the same segment. It's the address of the VLAN
199 interface of usb-ms01. Hosts at the bottom of the diagr
On 25/10/2022 19:14, Rich Otero via Dnsmasq-discuss wrote:
We have an Ubuntu v16.04.5 server with dnsmasq v2.75. The server acts as
a router for approximately 140 IP subnets and dnsmasq provides DHCP and
DNS for those subnets. The server has two network interfaces, which are
basically an "ups
#x27;m not sure if it's
the IPv6 address or the number of nameservers, but the problem only
happens when lan.example.net has both IPv4 and IPv6 nameservers.
Hopefully, this will help you track down the issue. Thanks for your help.
On 10/13/22 09:36, Simon Kelley wrote:
On 10/10/2022 00:2
Forwarded Message
From: Dominik Derigs
To: dnsmasq-discuss@lists.thekelleys.org.uk
, Simon Kelley
Subject: Fwd: [PATCH] Addressing hostsdir shortcomings
Date: Sat, 02 Apr 2022 21:32:30 +0200
Dear Simon,
Second resubmission of my patches.
They still apply cleanly to current
On 10/10/2022 00:21, Christopher J. Madsen wrote:
I have configured dnsmasq and openresolv as described in
https://unix.stackexchange.com/a/575449/2421 so that the DNS servers
provided by the VPN are only used for the domains on that network.
With dnsmasq 2.86 and openresolv 3.12.0 this was
On 09/10/2022 06:12, Mark Dietzer wrote:
Disregard that previous reply, for some reason it spuriously worked (maybe
keepalived temporarily lost my /32 addresses on the interface I am using).
Either way, something is broken.
My full setup, in case it matters, is that I have interfaces with a
I just pushed the long-awaited 2.87 release.
Release notes below.
Enjoy!
Simon.
version 2.87
Allow arbitrary prefix lengths in --rev-server and
--domain=,local
Replace --address=/#/. functionality which got
missed in the 2.86 domain search rewrite.
On 23/09/2022 13:20, Zeta Cloud wrote:
Hi.
I'm running dnsmasq as the local DHCP server in a container/VM/jail
intended to serve as a router for multiple VMs, and the router VM is set
up with multiple vnics, each on a different subnet.
vnic1: Subnet A -> 192.168.11.0 (external)
vnic2: Sub
On 20/09/2022 23:54, Glenn Fowler wrote:
Hi,
I am caching positive responses for 40 minutes (min-cache-ttl), but want
negative responses cached for only 1 minute. If the forward zone server
is down momentarily, all of the queries during that time could result in
an erroneous negative respon
On 20/09/2022 15:32, bru red wrote:
dnsmasq version: 2.86
OS, distro: linux, slackware 15.0
i use dnsmasq to provide dhcp for a tap interface. When i wake the
computer up from sleep state, 80% or 90% chances are that it will spin
at 100% cpu. I've heard that it might be related to the fact t
On 18/09/2022 17:21, Bryan Walton (dnsmasq) via Dnsmasq-discuss wrote:
I'm having trouble with Dnsmasq forwarding requests for some local
domains, even when I have them configured in my dnsmasq.conf. Here is
what I have in my config:
# Add local-only domains here, queries in these domains a
27.0.0.1
dnsmasq[1484740]: 103 127.0.0.1/35249 <http://127.0.0.1/35249>
forwarded example.COM to 127.0.0.1
On Thu, Sep 15, 2022 at 10:59 AM Simon Kelley
mailto:si...@thekelleys.org.uk>> wrote:
On 14/09/2022 22:32, Dmitry Pasiukevich via Dnsmas
On 14/09/2022 22:32, Dmitry Pasiukevich via Dnsmasq-discuss wrote:
Hi,
TLDR: DNS request to dnsmasq with upper-case domain is handled
differently if request is sent over TCP vs UDP
I run a server to forward "cluster.local" queries to another process:
/usr/sbin/dnsmasq-k--cache-size=1000--no
master, origin/master, origin/HEAD)'
' (tag: v2.87rc1)'
''
''
''
''
''
''
''
' (tag: v2.87test9)'
$ git log -10 --format="'%(describe)'"
'v2.87rc1-1-gc4b9bc6'
'v2.87rc1'
On 13/09/2022 09:10, Johnny S. Lee via Dnsmasq-discuss wrote:
How about something like the following?
diff --git a/VERSION b/VERSION
index 998eb1f..29a22f8 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-$Format:%d$
+$Format:%d;%(describe)$
diff --git a/bld/get-version b/bld/get-version
index
The current format is %d, which is
"ref names, like the --decorate option of git-log[1]"
according to git help log.
I'm not clear what the difference between that and %(describe) is. The
substituted value is used subtly in get-version as part of the
build-process, so we need to be a little
On 05/09/2022 20:07, Chris Green wrote:
I am running dnsmasq version 2.86 on xubuntu 22.04. Just recently (i.e. in
the past few weeks) it has started crashing with a segfault. The syslog has
the following:-
Sep 5 19:43:14 t470 dnsmasq[13183]: no servers found in
/run/NetworkManager/n
On 07/09/2022 10:10, Luis Thomas wrote:
On Tue, 2022-09-06 at 13:24 +0100, Simon Kelley wrote:
CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the
sender > and know the content is safe.
On 02/09/2022 14:03, L
On 08/09/2022 07:08, Hamish Moffatt wrote:
So, I got the suggestion off-list to set the DHCP client-id uniquely for
each connection. This fixed IPv4, even without matching on the client ID
in the config, because dnsmasq is tracking both separately in the leases
file. Leases (just IPv4) sho
I propose to begin the process to release the current development code
as 2.87.
As list-members may be aware, I've been somewhat absent from post for
the past six months, and I'm aware that there are known bugs and pending
patches which I've not attended to, and some I may even have forgotten
On 06/09/2022 17:23, Taylor Fox wrote:
Hello,
I am trying to write a script for logging & notification whenever
a new DHCP lease is issued, and I currently have a script that uses the
`dnsmasq_client_id` environment variable to get the MAC address of the
device that the lease was issue
On 02/09/2022 14:03, Luis Thomas wrote:
Hi everyone,
We are using both dnsmasq and isc dhcrelay as dhcp-relays for dhcpv6
only.
we launch dnsmasq like this:
dnsmasq -d \
--conf-file=/dev/null \
--dhcp-relay fd12:3456::b6e3:f9ff:fea5:fa5b,2020:abcd::1 \
--excep
We've been here before.
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016324.html
Simon.
On 24/08/2022 23:42, Felipe Polanco wrote:
Hello,
We are using dnsmasq as DNS server for our public VPN server and today
we found a rare issue where DNSMasq filled the entire send buf
On 14/08/2022 19:36, Geert Stappers via Dnsmasq-discuss wrote:
On Fri, Aug 12, 2022 at 06:46:14PM +0100, Simon Kelley wrote:
... Does your compiler still complain?
Nope
OK. Problem solved. Looks like gcc only generates false positives from
free(), not free() called by realloc
Interesting. I think this is a false positive, as the "use" is pointer
arithmetic to derive an integer offset, not a dereference. If you're
going to complain about using "buff" like that, you should equally
complain of using p, which just the value of buff that's just been freed
incremented a f
On 08/07/2022 21:26, Petr Menšík wrote:
Hi!
I have already described similar problem back in year 2021 [1]. There
exists race condition when higher count of clients starts at similar
time and requests DHCP(v4). First two patches were already sent. I think
I have sent also following patches
Patch applied, and a subsequent one to simplify poll.c that it suggested.
Simon.
On 18/07/2022 16:47, Petr Menšík wrote:
Hi,
After reading the code creating servers.bind reply, I made a change to
use realloc call instead. It should allow saving some memory copying
when it is possible to ju
=dnsmasq.git;a=commit;h=f4b281381853df6b275332d4cd0ec1d150bffa86
Fixes this.
Simon.
On 08/08/2022 11:27, Simon Kelley wrote:
I'm not sure what you are trying to do here.
the /#/ domain is only defined in the man page for --address and it
states that it matches any domain which doesn't h
I'm not sure what you are trying to do here.
the /#/ domain is only defined in the man page for --address and it
states that it matches any domain which doesn't have a more specific match.
Even though,
server=/#/
is not defined in the documentation; by extension it is exactly the same as
se
I think this is fixed in the development code:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=f4c87b504b444efb05892b8c7fc295e886f70789
Simon.
On 26/07/2022 16:09, ryt 51V wrote:
Hi,
I am running into a bug in the following circumstances.
When the config has a mix of the below (e
I wouldn't expect the dnsmasq DHCP server to return these hostnames at
all, so something unexpected is happening. Are sure the clients aren't
doing a reverse-DNS lookup on their assigned address, or something similar?
Setting --log-queries and --log-dhcp and posting the results (or sending
th
rship information to the
original author of the respective commit.
Cheers,
Jasper
Am 21.07.22 um 00:06 schrieb Simon Kelley:
Jasper,
The patch looks fine, and I'm happy to commit it. Geert's point is a
good one; please could you supply a suitable commit message which
describes c
This is a bug, for sure.
I can see exactly why this would happen with
address=/Computer1.example.org/10.0.0.10
but not with
host-record=Computer1.example.org,10.0.0.10,3600
Please could you recheck that you are seeing the problem with
--host-record? If you are, I've gone down the wrong track
For better or worse, dnsmasq operates by overlaying locally configured
data on the global DNS: if the local configuration doesn't include a
particular record type, dnsmasq continues to return the data in the
global DNS for that record type. That's what's happening here: you've
not defined an A
Jasper,
The patch looks fine, and I'm happy to commit it. Geert's point is a
good one; please could you supply a suitable commit message which
describes clearly what the patch does, and includes this attribution
information directly and not as links: the git commit will be around
forever, the
tion.c/read_opts":
#ifndef NO_ID
add_txt("version.bind", "dnsmasq-" VERSION, 0 );
add_txt("authors.bind", "Simon Kelley", 0);
.
The call to cache_reload calls make_non_terminals:
for (txt = daemon->txt; txt; txt = txt->next)
{
On 13/06/2022 08:16, John Gilmour via Dnsmasq-discuss wrote:
Hello,
First time user so please bear with me.
I have some quite specific in-house code that relies on the "cache->ttd"
value. I have noticed that the function "cache_reload" in "src/cache.c"
defines the following variable:
stru
The patch looks good to me. Applied.
Cheers,
Simon.
On 19/05/2022 10:43, Beniamino Galvani wrote:
On Wed, May 18, 2022 at 04:10:52PM +0200, Geert Stappers via Dnsmasq-discuss
wrote:
There new lines and one old line
+ if (rta->rta_type == IFA_LOCAL)
+
On 21/04/2022 23:46, Chris via Dnsmasq-discuss wrote:
From: Chris Staite
Fixes the case where a CNAME is valid and unsigned and the target of the
CNAME is returned with the CNAME but with no RRSIG (due to the CNAME not
being in a signed zone).
Since the CNAME is unsigned, there is no additi
I have a theory:
In the logs, it takes between 7 and 9 seconds after carrier detect on
eth0 (I guess that's when you plug the RTMU86 in?) before eth0 is
allocated IP address 192.168.6.1. Until the address is allocated,
dnsmasq will ignore DHCP requests and log
"DHCP packet received on eth0
his scenario. It's a soak
test with a large variety of clients all doing busy work like video
streaming etc.
On Fri, May 13, 2022 at 12:48 PM Simon Kelley <mailto:si...@thekelleys.org.uk>> wrote:
On 10/05/2022 16:40, Tom Keddie via Dnsmasq-discuss wrote:
>
On 16/05/2022 17:27, Brad Silva wrote:
I ran into an issue with DHCP on DNSmsaq 2.85.
It's running on a host with two IP addresses on the same network. The
primary IP is .12 and the secondary is .10. DNSmasq was put in place to
replace a missing server (long story), so it was setup to list
On 15/05/2022 15:40, Kamil via Dnsmasq-discuss wrote:
PS. I've read in FAQ about 255.255.255.255 broadcast and invalid
firewall rules, but I don't have any firewall rules and I'm not changing
network config files when switching to isc-dhcp-server (which I use as a
benchmark)
ISC dhcpd b
On 10/05/2022 16:40, Tom Keddie via Dnsmasq-discuss wrote:
Hi All,
I think you're saying that it's not surprising that dnsmasq is not
reading from the socket because the send queue is also full.
As per this thread on netdev
(https://lore.kernel.org/netdev/cabuuw65r3or9hehsmt_isvx1f-
Set the configuration --log-queries.
That will allow you to see if the queries are getting to dnsmasq, and it
will give you a full dump of the DNS cache (including DHCP derived
names) if you send the dnsmasq process SIGUSR1.
Both of these will help in diagnosing the problem.
Cheers,
Simon.
On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
Hi!
I've configured Dnsmasq with the following config:
interface=eth0
bind-interfaces
dhcp-option=3,192.168.6.1
dhcp-option=6,8.8.8.8
set long-lasting records.
dhcp-range=192.168.6.11,192.168.6.20,255.255.255.0,12h
On 16/04/2022 18:13, Анна Тихомирова via Dnsmasq-discuss wrote:
Hello.
I'm using dnsmasq version 2.86.
I've found that address option works incorrectly if the target domain is
a cname.
Here is an example:
1) Add a domain to dnsmasq configuration:
address=/api.ott.kinopoisk.ru/::
2) Make a
packet no: 562) is being
sent as unicast even though the broadcast tag is enabled in the
config file. Please see BOOTP flags.
Please let me know your thoughts.
Best Regards,
Gokularajan G T
On Thu, Apr 7, 2022 at 2:10 PM Simon Kelley mailto:si...@thekelleys.org.uk>&
This seems like a sensible idea, but it does need a clear warning in the
documentation that it will only work if the dnsmasq instance being
configured is not the one providing DNS to the local system.
Two comments about the patch.
1) Geert's point is a good one: This patch uses only libc: it d
There's no regression that I'm aware of. It's worth setting the log-dhcp
option to see what's going on with tags. Also look at packet dumps. Is
the "broadcast" flag set in the OFFER packets?
Simon.
On 07/04/2022 08:35, Gokularajan G T wrote:
Dear Simon,
I believe dnsmasq currently supports t
On 31/03/2022 20:04, Petr Menšík wrote:
Possible vulnerability were found in latest dnsmasq. It were found with
help of oss-fuzz Google project by me and short after that independently
also by Richard Johnson of Trellix Threat Labs.
It is affected only by DHCPv6 requests, which could be crafte
On 30/03/2022 12:13, Ercolino de Spiacico wrote:
It looks like your script which downloads the blocked domains file and
compresses it takes 15s, then dnsmasq takes 15s to uncompress the list
and load it into memory and sort.
The first delay can be solved by doing the download before stoppin
On 31/03/2022 01:00, dnsm...@riseup.net wrote:
The reason it's like this is that if dnsmasq changed to unprivileged
action would fail if the port number was less than 1024
Look at the bug report again - its port is above 1024.
Without 'query-port=' your software always open way too many por
On 28/03/2022 11:49, Ercolino de Spiacico wrote:
This Internet list above (https://hosts.oisd.nl) is 40MB
uncompressed, the regex extracts domains-only so shrinking it to 60%
of its original size and the gzip compression shrinks much further.
Decompressing and scripting it up of course take
I think I might quibble that this is a bug: there are no promises about
the effective userid when a port is opened.
The reason it's like this is that if dnsmasq changed to unprivileged
user dnsmasq before creating the UDP port, then that action would fail
if the port number was less than 1024,
On 27/03/2022 08:52, Ercolino de Spiacico wrote:
>> [ -f list.of.domain ] && { create the formatted configuration }
>>
>> would always fail at dnsmasq level if the list.of.domains doesn't exist
>> despite the file existence condition defined. I'm not sure this is
meant
>> to be and/or i
On 24/03/2022 09:28, Ercolino de Spiacico wrote:
I've just added it to 2.87test8
Please test and report back.
Ok after a first implementation on my test environment this is my feedback:
A- Great feature! the scripting + gzip + zcat is a godsend. Yes it
pushed the CPU up a bit, yes the t
On 24/03/2022 09:03, Ercolino de Spiacico wrote:
The relevant code looks like:
if (testmode)
{
fprintf(stderr, "dnsmasq: %s.\n", _("syntax check OK"));
exit(0);
}
So it's not an accident, but the reason it's like that is rather lost
in the mists of time.
Can you t
On 23/03/2022 21:02, Ercolino de Spiacico wrote:
It seems like "dnsmasq --test" redirects the output "syntax check OK"
message to stderr (2) by default:
root@sparrow:/tmp# dnsmasq --test
dnsmasq: syntax check OK.
root@sparrow:/tmp# dnsmasq --test 1>/dev/null
dnsmasq: syntax check OK.
root@s
On 22/03/2022 07:51, renmingshuai via Dnsmasq-discuss wrote:
For the firest question, if more than one one entry, not in
strict-order, dnsmasq will forward the query to all nameservers
according to matching rules which are set by these entries.
Sort-of. It may send it to only one, if that is
On 22/03/2022 01:42, Preston Crow wrote:
I just ran into an interesting issue:
In my config, I set: resolv-file=/etc/resolv.conf.upstream
If I edit that file, I instantly see dnsmasq reload things as expected
with various log messages. That's good.
However, in my case, /etc/resolv.conf.up
This is another take on a recurring problem. There is a facility to work
around it by allowing multiple addresses to be specified in dhcp-host.
That works for the specific case of chain-netbooting, where the host's
DUID changes at each stage of the boot. I appreciate that may not be the
problem
pretty old, I'd like you to test a more recent
version before putting effort into chasing this.
Cheers,
Simon.
On 11/03/2022 10:20, shashikumar Shashi wrote:
Hi Simon Kelley,
dnsmasq is running continuously for around five months, we had
around 150 clients. After 5 months dnsmasq got k
On 07/03/2022 22:06, Geoff Back wrote:
On 07/03/2022 18:20, Simon Kelley wrote:
A quick test of the current development code fails to reproduce this,
which is puzzling.
One thing to check: having a dhcp-host line which associates an address
with a name is not enough to make this work
On 07/03/2022 20:51, Frank Liu wrote:
On Mon, Mar 7, 2022 at 10:46 AM Simon Kelley wrote:
A quick test of the current development code fails to reproduce this,
which is puzzling.
One thing to check: having a dhcp-host line which associates an address
with a name is not enough to make
A quick test of the current development code fails to reproduce this,
which is puzzling.
One thing to check: having a dhcp-host line which associates an address
with a name is not enough to make this work: there needs to be an active
DHCP lease in place to be able to resolve client1.test.exa
You can set the source address of upstream queries in the --server
option, which can work in some circumstances (and can ensure that the
replies also come back via the VPN, which isn't a given.
In general, this is a routing question: you need to route traffic to
1.1.1.1 via the VPN and do sui
>
> Dnsmasq logs:
>
>
> Is it a known failure/bug?
> Could you please help?
We, being projectlead Simon Kelley and us,
released newer versions of Dnsmasq.
Please try to reproduce the crash with a recent version.
Section "
101 - 200 of 1001 matches
Mail list logo
