s and causing a lot of confusion.
Appriciated. Yes, much respect to care what people encounter.
Another compliment: Thanks for awareness "time is precious".
You make it possible that people can read in the discussion order.
The gain in time, the time saving factor, is that you make it p
dnsmasq scambles the case of letters in DNS queries...
>
> should be corrected to
>
>By default, dnsmasq scrambles the case of letters in DNS queries...
>
The patch request has been seen. ( at least by me :-)
Proposal:
* Allow Simon more time to respond
* Consider a true pa
cables
> > or different wireless names. Vlans are the same: like two or more
> > physical ethernets that happen to be on the same cable.
> >
>
> Thanks Simon.
>
"Thanks for the advice, I will try it." or "Thanks, I have it working!"?
Groeten
Ge
On Mon, Jan 13, 2025 at 02:37:25PM +0100, Sven Geuer wrote:
> On Fri, 2024-12-27 at 19:30 +0100, Sven Geuer wrote:
> > On Tue, 2024-12-24 at 08:54 +0100, Geert Stappers wrote:
> > > [...]
> > > I suggest to do an upload to Debian for playing on safe to be in th
On Sat, Feb 01, 2025 at 10:48:00PM +, Simon Kelley wrote:
> On 2/1/25 15:00, Donald Muller wrote:
> > *From:* Geert Stappers, *Sent:* Saturday, February 1, 2025 2:41:59 AM
> > > On Sat, Feb 01, 2025 at 01:28:54AM +, Donald Muller wrote:
> > > > Does dnsm
quest, it can be achived.
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
rom Brain Haley (2025-01-23).
> > > Thank you!
Thanks reporting back!
> >
> > Maybe it can get applied :)
> >
> No, I was unable to apply it, don't know why, so I applied it manually.
>
That looks like an invite for resubmitting the patch.
Regards
Geert Stap
st regards
> strict-order
> except-interface=lo
> bind-dynamic
> leasefile-ro
> interface=dnsmasq-test
> dhcp-range=192.168.126.2,192.168.126.254,255.255.255.0
> dhcp-no-override
> dhcp-authoritative
> dhcp-lease-max=253
> dhcp-hostsfile=hosts.conf
> dhcp-optsfile=options.co
24.0.36
Jan 27 21:53:50 alpaca dnsmasq[5809]: forwarded fosdem.ems.host to
127.0.0.1#35353
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/m
h have been at https://lists.sr.ht/~stappers/dnsmasqmlpc/patches
the Dnsmasq mailing list patch collection
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
On Fri, Jan 17, 2025 at 10:47:45PM +0100, Geert Stappers wrote:
> On Sun, Jan 12, 2025 at 02:24:35PM +, Andrew Sayers wrote:
> > Print a specific INFO message instead of a generic WARNING message,
> > so users know what to do.
> >
> > Starting dnsmasq without u
nt-patch=diff' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
stappers@paddy:~/src/mlpc/dns
On Thu, Jan 09, 2025 at 03:22:50PM +0100, Paul Donald wrote:
> Some writing was improved for clarity, especially regarding the use of
> tags which can be confusing and difficult to grasp.
Nice. Thanks.
I'll raise it at dnsmasq mailinglist. (Already done ;-)
Groeten
Geert Sta
DBus"));
> + else
> +#endif
> + my_syslog(LOG_WARNING, _("warning: no upstream servers configured"));
> + }
> }
>
> if (daemon->max_logs != 0)
> --
> 2.47.1
>
Looks good to me.
(That `git am` did complain some what, is considered &
On Mon, Jan 13, 2025 at 01:43:09PM +0100, Petr Menšík wrote:
> On 10. 01. 25 14:15, Geert Stappers wrote:
> > Hi,
> >
> >
> > What about a face to face meeting during FOSDEM2025?
> >
> >https://fosdem.org/2025/
> >
>
> It seems I won&#x
interface lan
> dnsmasq: reading /etc/resolv.conf
> dnsmasq: using nameserver 127.0.0.53#53
> dnsmasq: read /etc/hosts - 8 names
> dnsmasq-dhcp: DHCPDISCOVER(lan) 192.168.2.56 ac:1f:xx:xx:xx:xx
> dnsmasq-dhcp: DHCPOFFER(lan) 192.168.2.101 ac:1
Hi,
What about a face to face meeting during FOSDEM2025?
https://fosdem.org/2025/
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
nks. Also manpage typo fix.
>
Mailinglist Patch Collection
https://lists.sr.ht/~stappers/dnsmasqmlpc/patches?page=1
updated with that information.
> Cheers,
> Simon.
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-d
le \fB--dhcp-relay\fP
> configs with the same local address and different server
> --
> 2.47.1
Nice.
Please bounce it to ~stappers/dnsmasqm...@lists.sr.ht
Or upon retransmit, have ~stappers/dnsmasqm...@lists.sr.ht in the Cc.
So the patch will be add to the mailinglist patch collection, m
an for playing on safe to be in the
next Debian release.
But what about the proposed patches at MailingList Patch Collection
( https://lists.sr.ht/~stappers/dnsmasqmlpc/patches ) ?
> Cheers,
> Simon.
Groeten
Geert Stappers
--
Silence is hard to parse
On Wed, Dec 18, 2024 at 10:23:18AM +0400, Loganaden Velvindron wrote:
> Gentle reminder to dnsmasq developers :-)
>
It became
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d6379cd923676dd21bc05ed8bd8fe4fb24337c98
>
> On Fri, 6 Sept 2024 at 01:35, Geert Stappers wrote
Examples of verdicts:
* Patch has been reviewed and is rejected, no further comment. [0]
* Patch has been seen and was inspiration for another commit.
* Patch applied, thanks.
* Patch needs reworks, foo needs to bar. [1]
* Coding style
* A release that is in Debian testing before the freeze i
ot several "it is an improvement" responses.
Some how is the patch still not merged.
What to do to prevent that the patch falls between the cracks?
Groeten
Geert Stappers
P.S.
At https://lists.sr.ht/~stappers/dnsmasqmlpc/patches are more proposed patches
From: Dominik Derigs
Signed-off-by: Dominik Derigs
---
src/rfc2131.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/rfc2131.c b/src/rfc2131.c
index f494a55..f99b8d5 100644
--- a/src/rfc2131.c
+++ b/src/rfc2131.c
@@ -934,6 +934,7 @@ size_t dhcp_reply(struct dhcp_context *context, char
---
src/option.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/option.c b/src/option.c
index 92f3582..730adf4 100644
--- a/src/option.c
+++ b/src/option.c
@@ -452,7 +452,7 @@ static struct {
{ 'o', OPT_ORDER, NULL, gettext_noop("Use nameservers strictly in the order
g
On Mon, Dec 02, 2024 at 07:36:56AM +0100, Geert Stappers wrote:
> On Sun, Dec 01, 2024 at 11:38:53PM +, Simon Kelley wrote:
> > I just synced the public git to my personal git repo, and there are quite a
> > few commits.
> >
> > Apologies for the dump. Mos
What has to be done, needs to be done.
(a.k.a. it is OK to break eggs to get an omelet.)
I will try the changes. (Hopefully early this week.)
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.th
On Tue, Nov 19, 2024 at 12:23:40PM +0100, Sven Geuer wrote:
> On Sun, Nov 10, 2024 at 10:53:02AM +0100, Geert Stappers wrote:
> > [PATCH] Removed empty trailing lines
> >
>
> In addition there are 6793 lines in 110 files with trailing spaces
> including \r characters
T
There are even OSs that do not support DHCPv6 at all,
> Android being the prime example.
>
> Kind regards,
> Buck
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
On Sun, Nov 10, 2024 at 10:53:02AM +0100, Geert Stappers wrote:
> [PATCH] Removed empty trailing lines
>
> Because there is no information in empty trailing lines.
> ---
> FAQ | 11 ---
> bld/get-version
On Mon, Nov 11, 2024 at 04:19:18PM +0800, Glen Huang wrote:
> On Sun, Oct 27, 2024 at 7:56 PM Geert Stappers wrote:
> > On Sun, Oct 20, 2024 at 3:50 AM Glen Huang wrote:
> > >
> > > I have this flag set
> > >
> > > dhcp-host=example,[::10],192.168.1
Because there is no information in empty trailing lines.
---
FAQ | 11 ---
bld/get-version | 1 -
bld/install-mo | 2 --
contrib/CPE-WAN/README | 2 --
contrib/Solar
ther research in parallel of waiting on
response from the community, report progress.
A true "Thanks" will be sharing the solution or a workaround.
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
; > no-dhcp-interface=wan
> > no-resolv
> > port=1053
> > rebind-localhost-ok
> > server=8.8.8.8
> > stop-dns-rebind
>
> Forgot to mention, I use dnsmasq 2.90 on linux.
>
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
out/flushed because
> the REFUSED reply lasted much longer than 40s(the timeout in source code)
> while no request going in for that period.
>
Please try again to explain "the problem". Start with describe how to
reproduce. Add "Expected to see" and "Actual
On Mon, Oct 07, 2024 at 10:55:44PM +0200, Geert Stappers wrote:
> On Fri, Oct 04, 2024 at 04:58:04PM +0100, Simon Kelley wrote:
>
> >
> > I'll commit that change as soon as I've sent this.
> >
>
> That became commit f006be784210. It is the f
of the
record is given by the hex data, which may
be of the form 01:23:45 or 01 23 45 or
012345 or any mixture of these.
If there are better ways to define NS records, I would love
to learn about it.
Groeten
Geert Stappers
On Mon, Oct 14, 2024 at 05:24:54PM +, Roger Lucas via Dnsmasq-discuss wrote:
> From: Dnsmasq-discuss on behalf of Geert Stappers:
> Sent: 14 October 2024 16:26
> > On Thu, Oct 10, 2024 at 10:13:05AM +, Roger Lucas via Dnsmasq-discuss
> > wrote:
> > >
> > &
On Mon, Oct 14, 2024 at 06:21:40PM +0300, Leonid Evdokimov wrote:
> On Sun, Oct 13, 2024 at 10:18 PM Geert Stappers wrote:
> > To prevent the patches getting lost in the mailing list archive,
> > have I saved them in a local branch. What would be a good name for
> > that git
it to work.
As I see it, is the extension of the chain incomplete. [1]
With "chain" I mean chain of DNServers. With "extension" I mean
the insertion of a DNS in the chain.
> Thanks in advance for any suggestions!
Back to the drawing board, draw the chain on it.
Make a cut in the c
list archive,
have I saved them in a local branch. What would be a good name
for that git branch? My plan is to make the carrying git repository
public available.
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
ee
them. And are willing to express that.
However, my fear is that there will be silence.
We will see happens next.
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
Previous-Subject: Re: [Dnsmasq-discuss] Question on dnsmasq code, which may
occur a bad-free
Welcome back,
On Fri, Oct 04, 2024 at 04:58:04PM +0100, Simon Kelley wrote:
>
> I'll commit that change as soon as I've sent this.
>
That became commit f006be784210. It is the first commit in
s starting earlier, unless caching /etc/hosts is significant speedup.
> And we have nss-lookup.target, I am not sure if socket activated service cat
> make it started also.
> >
> > I really hope that socket-activation is considered, this would improve
> > dnsmasq's integra
Reflect outcome of discussion on mailinglist.
Removed reference to meanwhile removed KB, Knowledge Base, note.
---
src/dhcp.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/dhcp.c b/src/dhcp.c
index b65facd..e34b292 100644
--- a/src/dhcp.c
+++ b/src/dhcp.c
@@ -824,8
On Wed, Oct 02, 2024 at 01:32:07AM +0200, Petr Menšík wrote:
> On 24/09/2024 08:52, Jan Ceuleers wrote:
> > ... context ...
>
> I have hit this comment once too.
Ah, the comment is what hits. That comment be changed
into something that hurts less.
_
.
Please Cc email address '~stappers/dnsmasqmlpc at
lists.sr.ht' on sending the v3 patch to get it at
https://lists.sr.ht/~stappers/dnsmasqmlpc/patches (mlpc:
mailinglistpatchcollector) for preventing that the patch falls through
the cracks.
Groeten
Geert Stappers
--
Silence is ha
emon->doing_ra)
That looks like a retransmit from April 2024.
It made it to the mailinglistpatchcollection, mlpc,
https://lists.sr.ht/~stappers/dnsmasqmlpc/patches/51909
When another retransmit a.k.a. reminder is needed,
please state something like "you might seen this before"
to
e client decide what it wants
> > to do rather than forcefully dropping the answers.
> >
> > Best regards,
> > Rahul Thakur
> >
>
> Hi Simon,
>
> So what do you think of my reasoning for this patch? Do you agree?
Review the feedback
only UDP port 53 open.
> -- or how to fix.
Open TCP port 53 in the "firewall"
> Thanks.
A much better "Thanks" is reporting back.
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-discuss mailing list
D
he feedback. The discussion has convinced me that the
> balance between risk and potential benefit is not favourable.
>
> I also take the point that making this special treatment configurable,
> while enabling the small benefits to be realised for those willing to
> take the
etion is being addressed with IPv6.
> But if the dnsmasq project isn't ready to remove this restriction, would
> a patch be accepted that makes it configurable? If so, what should the
> default be?
>
> Thanks, Jan
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
On Sun, Sep 22, 2024 at 09:16:02AM +0200, Jan Ceuleers wrote:
> On 21/09/2024 09:29, Geert Stappers wrote:
> > On Wed, Sep 18, 2024 at 07:22:35PM +0200, Jan Ceuleers wrote:
> > > Dear dnsmasq community,
> > >
> > > The changelog for
On Sat, Sep 21, 2024 at 01:53:59PM +0200, Geert Stappers wrote:
> On Sat, Sep 21, 2024 at 07:08:45PM +0800, 胡义臻 wrote:
> > Are there any common test cases for dnsmasq?
> >
> > I found this test case on github, but it covered so little that I
> > wanted to find a compr
ems.
>
> https://github.com/InfrastructureServices/dnsmasq-tests
>
Yes, I would be good thing if dnsmasq gets test cases.
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists
uot;first time right"). The "it works for me" reward can get as next
reward the warm feeling of "I was able to give back" [2].
> Many thanks, Jan
You are welcome [3]
Groeten
Geert Stappers
[1] I could not resist to ignore the posting,
hence te long "the post
On Sat, Aug 17, 2024 at 06:38:52PM +, Dan Schaper wrote:
> From Geert Stappers, Date 8/17/2024 11:05:25 AM
> > On Sat, Jul 27, 2024 at 11:25:04AM +0200, Dominik Derigs wrote:
> > > Hey Simon,
> > >
> > > another patch ...
> >
> > IMNSHO shou
On Thu, Jun 06, 2024 at 01:59:23PM +0200, Geert Stappers wrote:
> On Sat, Jun 01, 2024 at 12:36:49AM +0200, Petr Menšík wrote:
> > Hi!
> >
> > As part of our review of dnsmasq code, our code scanning tools revealed few
> > warnings. Some of them are valid, although it
t;
>
> [image: Screenshot 2024-09-05 at 09.42.38.png]
> https://smirnov.la/Screenshot%202024-09-05%20at%2009.42.38.png
>
>
>
> I'm using these params
> https://github.com/dockur/dnsmasq/blob/master/entry.sh#L14
> plus "fast-dns-retry". Also tried adding &
ot-anchors/root-anchors.xml
>^^It
>
That feedback converted in a patch. In the mailinglist archive at
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q3/017720.html
and also at https://lists.sr.ht/~stappers/dnsmasqmlpc/patches/54886
Groeten
Geert Stappers
--
Sil
Some minor changes in comment lines
Reported-by: Gary R. Schmidt
---
trust-anchors.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/trust-anchors.conf b/trust-anchors.conf
index 1a7de74..e8bacf4 100644
--- a/trust-anchors.conf
+++ b/trust-anchors.conf
@@ -1,7 +1,7 @@
From: Loganaden Velvindron
Signed-off-by: Loganaden Velvindron
Signed-off-by: Jaykishan Mutkawoa
---
trust-anchors.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/trust-anchors.conf b/trust-anchors.conf
index 2a1e2a0..1a7de74 100644
--- a/trust-anchors.conf
+++ b/t
dnsmasq community and for a future version of
you in your current situation which has to start an email thread
with "There is some evidence on the Internet that dnsmasq doesn't play
well with docker".
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
::250:56ff:feb5:ee27/64 scope link proto kernel_ll
>valid_lft forever preferred_lft forever
>
> I guess it is most likely be down to the setup on the clients (openSUSE).
The 'UP' and 'LOWER_UP' in ''
says that the interface is up.
> But as I pl
ze all configured backend servers, so the query succeeds
> instead of fails like it does now.
For what it is worth: My gut feeling says the problem description is
incomplete.
> This is our dnsmasq.conf:
>
> all-servers
> clear-on-reload
> bind-interfaces
>
thanks
Idea for a better "Many thanks": Share with the mailinglist archive
feedback on the file contrib/conntrack/README like a "Works for me"
or even an addition as "Here a patch that documents my working use case".
Groeten
Geert Stappers
--
Sile
On Sat, Jul 27, 2024 at 11:25:04AM +0200, Dominik Derigs via Dnsmasq-discuss
wrote:
> Hey Simon,
>
> another patch ...
IMNSHO should we, this mailinglist, help Simon where we can. Insteadof
just pushing work towards Simon.
Groeten
Geert Stappers
P.S.
I understand that Domini
ts as DHCPv4 did.
>
Please try to understand https://cbea.ms/git-commit/
Groeten
Geert Stappers
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q3/017649.html
(increase patch survival chance)
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2023q3/017238.html
izeof(struct in_addr))];
> #endif
> char control6[CMSG_SPACE(sizeof(struct in6_pktinfo))];
> - } control_u;
> + } control_u = { 0 };
>
>iov[0].iov_base = packet;
>iov[0].iov_len = len;
> --
> 2.34.1
>
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
FreeBSD, the file is /usr/local/etc/dnsmasq.conf ) (but see the
--conf-file and --conf-dir options.) The format of this file con-
sists of one option per line, exactly as the long options detailed
in the OPTIONS section but without the leading "--". Lines sta
t; + * happen as pheader should be strictly within header after current
> ansp */
> + if (!CHECK_LEN(header, ansp, plen, hlen))
> +return plen;
>/* must use memmove, may overlap */
>memmove(ansp, pheader, hlen);
>header->arcount = htons(1);
>
e data seamlessly. This is useful for creating
scripting interfaces to C/C++ libraries, or for connecting C/C++ code
with other software components written in different programming languages.
https://www.swig.org/
Groeten
Geert Stappers
--
S
ource
> DE:AD:BE:EF:00:11 -j DROP
s/DROP/REJECT/ to get more as just silence when the limit kicks in.
And triple check the -m, all three.
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
Hello,
For your information: FLOSS weekly had an interview
with Simon Kelley, the creator of dnsmasq:
https://hackaday.com/2024/03/27/floss-weekly-episode-776-dnsmasq-making-the-internet-work-since-1999/
Enjoy
Groeten
Geert Stappers
--
Silence is hard to parse
rver IP to dnsmasq via the command line and does not provide
> any example of how to do so.
> I can't find an example of how to do so anywhere on the net...
>
Advice: Elaborate on the original problem.
Groeten
Geert Stappers
--
Silence is hard to parse
Hello Marek,
Hello Dnsmasq Mailinglist,
On Mon, Jun 17, 2024 at 09:31:44PM +0200, Geert Stappers wrote:
> From: Marek Skrobacki via Dnsmasq-discuss
>
>
> If the DHCP server is running inside a container or behind a load
> balancer, the DHCPREQUEST arriving at dnsmasq for proc
On Fri, May 17, 2024 at 11:00:17PM +0200, Geert Stappers wrote:
> On Wed, Apr 17, 2024 at 09:40:17PM +0200, Geert Stappers wrote:
> > Hi,
> >
> > Another 17th of month, another attempt
> > to prevent that patches fall through the cracks.
:-)
> > At https://
From: Marek Skrobacki via Dnsmasq-discuss
If the DHCP server is running inside a container or behind a load
balancer, the DHCPREQUEST arriving at dnsmasq for processing may have a
Server ID (option 54) configured with an IP address that is not assigned
to the local interface. In this case, dnsma
e Coverity scan. 3
> small changes attached.
Most likely another reminder is needed. Upon "retransmit", please
CC ~stappers/dnsmasqm...@lists.sr.ht
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsmasq-discuss
s no /etc/resolv.conf
> at all which, as I said, upsets some things. I want the local dnsmasq
> just to provide DNS cacheing in the system where it is running and
> nothing more, the 'upstream' DNS is provided by whatever
> /run/NetworkManager/no-stub-resolv.conf points at
On Wed, Apr 17, 2024 at 09:40:17PM +0200, Geert Stappers wrote:
> Hi,
>
> Another 17th of month, another attempt
> to prevent that patches fall through the cracks.
>
>
> At https://lists.sr.ht/~stappers/dnsmasqmlpc/patches
> is 1 pending patch, "Quieten DHCPv6 log w
From: Erik Karlsson
Not doing so can result in a use after free since the name for DHCP
derived DNS records is represented as a pointer into the DHCP lease
table. Update will only happen when necessary since lease_update_dns
tests internally on dns_dirty and the force argument is zero.
Signed-of
borate, make it possible to reproduce those tests.
> Looking forward to get feedback on this proposal.
Here **not** the project lead, just someone acknowledging
the patch has been seen.
Groeten
Geert Stappers
--
Silence is hard to parse
___
Dnsma
-+
| add | old | add | old | del |
+=+=+=+=+=+=+
mac_address | y | y | y | y | y |
client_address | y | y | | | | Either IPv4 addr or ?IPv6?
address
client_id | | | * | * | * | derived from MAC addr. Not
always present
lease_expires | | | y | y | y |
time_remaining | | | y | y | | If present, always '3600.0'
ip_address | | | y | y | y |
hostname| | | y | y | y |
domain | | | y | y | y |
interface | | | y | y | |
data_missing| | | y | y | | if present, always '1.0'
| | | | | |
+-+-+-+-+-+-+
--]]
> Many thanks,
> Phil
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
original packet. This should never
> + * happen as pheader should be strictly within header after current
> ansp */
> + if (!CHECK_LEN(header, ansp, plen, hlen))
> + return plen;
>/* must use memmove, may overlap */
>memmove(ansp, pheader, hlen);
&
mon->doing_ra)
> --
> 2.43.2
>
Looks good to me.
For preventing that the patch falls through the cracks,
send the patch to email address '~stappers/dnsmasqm...@lists.sr.ht'
to get it at https://lists.sr.ht/~stappers/dnsmasqmlpc/p
On Fri, Apr 19, 2024 at 06:20:03AM +0200, Geert Stappers wrote:
> On Thu, Apr 18, 2024 at 10:07:04PM -0400, Christopher Hill wrote:
> > Hi,
> >
> > I have a question regarding if upstream DNS forwarding can be based on the
> > source interface? Reading the manual I d
10.0.2.1 via tun 2.
>
> I have considered running two instances (one bound to eth1 and another
> to eth2) but that duplicates setup and makes local queries across VLANs more
> complicated.
Read the dnsmasq manual and reread the dnsmasq manual.
Groeten
Geert Stappers
--
Silence is har
From: Olaf Hering
The make target 'install-common' expects results from the target 'all'.
A 'make -j install' may fail because both targets are brought
up-to-todate in parallel. As a result the final binary will not exist at
the time 'install-common' runs, because 'all' is not yet done.
Adjust t
some patches haven't yet
reached the "mailinglist patch collector". Such as "Fix dependency
in make install target". See email 2024-03-17.
Most likely more patches were missed / are missing
please resend them with Cc: ~stappers/dnsmasqm...@lists.sr.ht
Groeten
Geert Stapper
at original poster & I think that DDNS is,
are two different Dynamic Domain Name Servers.
> If I'm wrong and dnsmasq can be configured as a DDNS client and my google
> foo has been poo - can anyone give me a pointer to where I might find more
> information.
>
> Thanks folks
gitlab.com/8.8.8.8
combination. The second line is NOT needed.
The
> address=/#/0.0.0.0
is another configuration I don't get.
So I think there are two problems. One how to use # character for server.
The other one original poster having a hard time configuring dnsmasq
for their
records accurately on the lan. I think DNS Update could resolve this
> problem.
And even documented in RFC 1925.
> Any thoughts on reconsidering support for this protocol in dnsmasq?
Try to express were the complexity should be.
> Or other solutions?
>
>
pipermail/dnsmasq-discuss/2024q1/017464.html
and https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017473.html
Patches being ignored happened before and most likely will happen again.
Hence my experiment with dnsmasqmlpc, dnsmasq mailing list patch
col
On Sun, Mar 17, 2024 at 01:09:36PM -0400, Brian Haley wrote:
> Nak.
Acknowledge
--
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-discus
Hello Olaf,
(Mailinglist in the Cc:)
On Tue, Oct 17, 2023 at 10:59:29PM +0200, Geert Stappers wrote:
> On Mon, Oct 16, 2023 at 12:02:53PM +0200, Olaf Hering wrote:
> > The make target 'install-common' expects results from the target 'all'.
> > A 'make -j in
From: Ian Dall
When a DHCP range has a mode of "static" then the pool of dynamically
allocated address is configured to be of zero size. DHCPv6 will still
respond with statically defined addresses. In these cirumstances, not
allocating an address is expected behaviour and not an error, so allow
"
From: Brian Haley
When a new IPv6 address is being added to a dhcp_config
struct, if there is anything invalid regarding the prefix
it looks like there is a potential memory leak.
ret_err_free() should be used to free it.
Signed-off-by: Brian Haley
---
src/option.c | 2 +-
1 file changed, 1 in
On Tue, Mar 05, 2024 at 07:29:55PM +1030, Ian Dall wrote:
> On Mon, 2024-03-04 at 07:13 +0100, Geert Stappers wrote:
> > On Mon, Mar 04, 2024 at 03:53:23PM +1030, Ian Dall wrote:
> > > When a DHCP range has a mode of "static" then the pool of dynamically
> > >
On Sat, Mar 02, 2024 at 05:03:01PM +0100, Geert Stappers wrote:
> On Fri, Mar 01, 2024 at 04:43:20PM -0500, Brian Haley wrote:
> > When a new IPv6 address is being added to a dhcp_config
> > struct, if there is anything invalid regarding the prefix
> > it looks like there
1 - 100 of 850 matches
Mail list logo
