-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In this context, ra and dhcpv6 are equivalent, ra if provided as a
part of the dhcp service, and the access controls (no-dhcp-interface)
operate on both. Hence RA is configured with a dhcp-range.
This is a possible documentation problem, but it's
Hi,
I using a Fritzbox and a dualstack internet connection (Deutsche Telekom).
Fritzbox is providing router advertisments with rfc5006 dns.
Fritzbopx is running stateless dhcpv6 with IA_P but no IA_NA.
I have running dnsmasq 2.72 on Fedora 21.
My Mac and Linux boxes are happy, but my Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dnsmasq and avahi are reacting to the prefix2003:57:e342:3800:: which
is being alternately added to enp1s0 and then 10 seconds later
deprecated, then added again deprecated again.
Find out what's causing that, and you'll have found the problem.
Hi Simon,
Thanks for the clarification.
BTW, it can never be stated too often how important dnsmasq is to the open
source world.
Lonnie
On Jan 14, 2015, at 1:51 PM, Simon Kelley si...@thekelleys.org.uk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In this context, ra and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dnsmasq checks for incoming network packets and signals in the same
event loop, so the maximum delay to DHCP packets will be the time to
read a configuration file once, even if you send 1 SIGUSER1
signals, because the code will interleave
Hello Simon,
thanks for your reply.
Obviously the problems have gone two days later without having done
something. Maybe the lease times where too long and I was too
impatient.
I reduced the lease times to only a few minutes but later I will set them
to some more practical values again.
But
Hi Simon,
you got a PM from me ('cause i don't wanna post my trust-anchor).
Thank you very much for getting into the Problem.
Am 14.01.2015 um 15:11 schrieb Simon Kelley:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that. Sadly, neither of those domains provoke the crash for
me,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that. Sadly, neither of those domains provoke the crash for
me, so it's not that simple.
What's the configuration? It's noticable that all the DNSSEC queries
are being sent twice to 85.214.20.141, and there's a retry to
213.73.91.35. I
Hi Simon,
i'm the one of the users Michael Tremer told of (Segmetation faults on
IPFire).
I followed your hint and activated --log-queries, so we will (may be)
see what the problem is.
Lucky me, the last few days dnsmasq runs for a couple of hours, the last
crash were
last night at 04:03AM.
Hi,
We have a cloud environment which uses DNSMASQ as DHCP/DNS server; in the
cloud, it usually starts lots of VMs concurrently, for example, 1 VM;
for each VM, we will configure a static DHCP entry in DNSMASQ configuration
and send SIGUSER1 to reload. we observe DNSMASQ becomes very busy of
Hi Simon,
it doesn't took a long time to get a hit. Here are the relevant last
lines before the crash.
I hope it will help.
==
Jan 14 11:59:07 knox dnsmasq[26518]: forwarded bugzilla.ipfire.org to
11 matches
Mail list logo
