>From 81ed4df0eb1d70fc1ac5f94b5839f8cb45602ed0 Mon Sep 17 00:00:00 2001
From: renmingshuai
Date: Tue, 20 Feb 2024 16:13:11 +0800
Subject: [PATCH] Fix error introduced in
51471cafa5a4fa44d6fe490885d9910bd72a5907
Signed-off-by: renmingshuai
---
src/dnssec.c | 4 ++--
1 file changed, 2
My dhclient process received a Confirm message from dnsmasq-dhcp, when the
dhclient process sent a Confirm message which contains a ip address that is not
appropriate for the link to the dnsmasq-dhcp.
# tcpdump -i veth1 port 547
dropped privs to tcpdump
tcpdump: verbose output suppressed, use
Set pointers to NULL after memory is freed to reduce dangling pointers,
although they are later set to new values.
>From 5567d99099191f0cdb2922555e6ade2634f94f30 Mon Sep 17 00:00:00 2001
From: renmingshuai
Date: Sun, 8 Oct 2023 16:06:46 +0800
Subject: [PATCH] Set pointers to NULL after memory
When I repeatedly reloaded the dnsmasq process, I found a memory leak. To
reproduce the problem, perform the following steps:
(1) Run dnsmasq as follows:
# dnsmasq --no-hosts --no-resolv --dhcp-optsfile=/tmp/opts
Hi,
I run dnsmasq as the follow:
dnsmasq --no-hosts --dhcp-hostsfile=/home/hosts
Every time I changed the dhcp host information in /home/hosts, I found that the
VmRss value of dnsmasq increases accordingly. Has anyone else had a similar
problem?
___
When ra-only, slaac, or ra-stateless is configured in dhcp-range and the prefix
len is set to a value other than 64, like this:
"dhcp-range=2000:1000:1000:1000:1000:1000::, ra-stateless,120,infinite"
the following error message is displayed:
dnsmasq: prefix length must be exactly 64 for RA
---
src/dhcp-common.c | 3 +++
src/rfc3315.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/src/dhcp-common.c b/src/dhcp-common.c
index b004e40..6f829f3 100644
--- a/src/dhcp-common.c
+++ b/src/dhcp-common.c
@@ -394,7 +394,10 @@ static struct dhcp_config *find_config_match(struct
Hi !
When dnsmasq attempts to search for the configured DHCPv6 address based on the
MAC address, it will send NS packets to obtain the client MAC address. If
dnsmasq fails to obtain the MAC address because any net reason, it cannot find
the configured DHCPv6 address. As a result, the client
Hi,
Dnsmasq may not store SSHFP record in the cache. You can read the source code
to know which types of records will be stored in the cache. As I know, only A,
, and CNAME will be stored.
where possible relevant code is located:
#0 cache_insert (name=name@entry=0xaab82ce0 "baidu.com",
Hi,
When you want reject the eth0:0 query when configured with "-interface=eth0",
you could add "---bind-interfaces" in your cmdline, such as "dnsmasq
-interface=eth0 -bind-interfaces".
Hope I didn't misunderstand what you meant.
Best,
Mingshuai Ren
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.
For the second question, when dnsmasq start with
In some cases, such as system reinstallation, the duid of the client has
changed when the client renews the lease. dnamsq will assign a new lease back
to the client if the new lease is available. However, if the old lease of the
client is not released or the client cannot actively release the
12 matches
Mail list logo
