Could you give more details on exactly how you're testing this?
Whereever that error is coming from, it's not from dnsmasq, which
doesn't use the resolver library at all.
On 20/03/2019 14:59, Philippe Lamhaut wrote:
> I am using dnsmasq version 2.80 as dns client in an
is a first pass on this.
I have a nasty feeling that there are configurations which need some of
the capabilities and have had a free pass because they are always there,
which I've missed (I only
Sorry for lack of reply to this, I hope you're still there, Wojtek.
I think this may have something to do with your other post about
authoritative mode - one of the answers has the "aa" flag set, and the
other one doesn't.
It would be useful, for both of the situations you describe, to set
On 15/03/2019 12:44, Peter Lieven wrote:
> Hi Simon,
> Am 14.03.19 um 18:41 schrieb Simon Kelley:
>> Is this a use for something like the ISC dhcpd shared-network configuration.
>> In the dnsmasq case, we could have something like
Is this a use for something like the ISC dhcpd shared-network configuration.
In the dnsmasq case, we could have something like
In the first case dnsmasq would behave _as_if_ the specified interface
carried the address and netmask specified.
In the second
> [mailto:dnsmasq-discuss-boun...@lists.thekelleys.org.uk] On Behalf Of Simon
> Sent: Tuesday, March 5, 2019 4:04 AM
> To: firstname.lastname@example.org
> Subject: Re: [Dnsmasq-discuss] Configuring DHCPv6 Vendor specific information
> using Option 17
> You ne
On 10/03/2019 02:02, Craig Andrews wrote:
> TCP Fast Open eliminates a round trip for TCP connections. Since dnsmasq
> is performance sensitive and uses many TCP connections, using TCP Fast
> Open would be a nice improvement. See https://lwn.net/Articles/508865/
> for background.
> On the
What a strange configuration!
I can sort-of explain what's happening here.
DHCP is a two-phase process: The server first suggests an address, then
the client accepts it and tells the server that it will be using the
In dnsmasq, the first phase does not reserve an address. It's
On 08/02/2019 09:49, John Robson wrote:
> Hi all,
> I'm trying to understand the mechanism by which dnsmasq uses the
> resolvers specified (in this case they are all specified in
> Specifically I am trying to work out why dnsmasq is (erratically)
> sending the same query to
On 15/02/2019 12:09, Petr Mensik wrote:
> I was playing a bit with auth-vm and auth-server together with virtual
> machine manager. I think it might be useful to omit interface in
> auth-server at all, just change name reported by auth-vm zones on normal
> dns port.
> Libvirt uses
There's not really enough information here to be sure, but I think this
may be fixed by
On 05/02/2019 08:18, Debananda Pal wrote:
> I have updated dnsmasq from 2.79
On 15/02/2019 12:54, Petr Mensik wrote:
> Hi everyone.
> I think it is handy to be able to delegate some suffix from internal
> domain, lets say example.com provided by BIND or any bigger server. But
> recursive servers do not set recursive queries on normal delegation.
> Delegation is when I
On 20/02/2019 06:38, 西谷優希 wrote:
> As mentioned in this post, a PXE request contains a GUID / UUID value.
> Is there a way to refer this GUID / UUID in dhcp script?
> I'd like to implement like below:
You need something like
Check the vendor-specific option number. I got the value of 100 from the
data you provided, but I may have decoded it wrong.
On 04/03/2019 10:01, P,
On 01/03/2019 20:33, Simon Kelley wrote:
> What's worrying is that Cloudflare and Google are both quite happy that
> the answer is _not_ bogus, but dnsmasq thinks it is. I shall poke around
> some more to try and understand that.
Answering myself, this appears t
On 01/03/2019 18:56, Dominik DL6ER wrote:
> Dear list members,
> to my understanding, dnsmasq should not return any valid records for BOGUS
> However, using Cloudflare (184.108.40.206 / 220.127.116.11) as upstream, I see a domains
> validated as BOGUS in the log, however, the A query
Thanks for your work with that one.
On 11/02/2019 16:04, Florent Fourcot wrote:
> We detected a performance issue on a dnsmasq running many dhcp sessions
> (more than 10 000). At the end of the day, the server was only releasing
> old DHCP leases
On 27/02/2019 15:06, Bogdan Harjoc wrote:
> There are 50 calls to close() in dnsmasq-2.80, and 10 of them are
> wrapped in retry_send().
> "man close" has this paragraph in the section "Dealing with error
> returns from close":
> "Retrying the close() after a failure return is the wrong
On 21/01/2019 07:33, Yossi Boaron wrote:
> Is this dnsmasq limitation is just due to lack of support in code/bug?
> or it requires massive architectural changes of dnsmasq?
> If it's the first one, I can try to fix this issue.
It's the second, unfortunately. a DNS query can be answered
On 21/01/2019 08:59, Harald Dunkel wrote:
> On 1/18/19 10:36 AM, Harald Dunkel wrote:
>> Do you think dnsmasq could watch/ping its IP address range while it is
>> idle, caching the result? It might examine the local arp table as well:
>> If there is an entry with matching MAC and IP address,
On 21/01/2019 11:49, Roy Marples wrote:
>> Will dnsmasq offer another IP address in case it receives a decline?
> It does with my testing, unless I hardcode the hardware address to a
> fixed IP. This results in an infinite loop, but there's no real way
> around that.
It's supposed to
It's a known limitation. The actual limitation is that a CNAME and it's
target must both either originate from an upstream server, or both
originate from the dnsmasq local configuration. Mixing sources (ie CNAME
from upstream and target from dnsmasq, or vice-versa) is not allowed.
Patch applied. Thanks.
On 17/01/2019 20:50, Brian Haley wrote:
> There's no reason to stop reading the existing lease file
> when dnsmasq is started and an invalid entry is found, it
> can just be ignored. This was fallout from an Openstack
> bug where the file was being written
On 17/01/2019 10:30, Harald Dunkel wrote:
> Hi folks,
> I see a 3 to 4 secs delay for dnsmasq's dhcp protocol. Example:
> Strongswan's dhcp plugin obtains an IP address on behalf of the peer (a
> road warrior laptop). The strongswan logfile on the host says
> Jan 14 10:48:07 18[IKE]
Patch applied, sorry for missing that in my review.
On 15/01/2019 22:45, Steven Siloti wrote:
> On Tue, Jan 15, 2019 at 12:44 PM Kaas Baichtal > wrote:
> I tried to install this patch manually to my 2.80 and got a segfault
Setting log-queries in the dnsmasq config will get you some useful
On 16/01/2019 21:26, elie...@ngtech.co.il wrote:
> I have couple CentOS 7 hypervisors and VM's.
> On the hypervisors I do not have any issue with dnsmasq as DHCP server but I
> have not tried using
On 14/01/2019 15:56, libor.buk...@oracle.com wrote:
> patches resolve the build failures, functionality, and performance
> issues on Solaris. A brief description is included in each patch.
> Please let me know whether these patches could be merged and which
> changes are
Dnsmasq returns an empty answer, which may not be correct, but is at
least an answer, so I'm not sure where the timeout is coming from.
>From RFC 1995
If incremental zone transfer is not available, the entire zone is
returned. The first and the last RR of the response is the SOA
On 12/01/2019 21:55, Steven Siloti wrote:
> It is possible for a config entry to have one address family specified by a
> dhcp-host directive and the other added from /etc/hosts. This is especially
> common on OpenWrt because it uses odhcpd for DHCPv6 and IPv6
The error is originating in the libidn2 library. Interestingly,
compiling against libidn1, that library doesn't flag the error.
Dnsmasq passes the input domain name to libidn so that it can be
translated to punycode if it contains non-ascii characters.
I guess the authors of libidn2 would
Are you compiling dnsmasq with support for IDN?
dnsmasq -v will tell you.
On 12/01/2019 00:22, Tasnad Kernetzky wrote:
> Hi all,
> I wanted to report a bug (at least we belieave it is one). We had a
> short discussion over at the archlinux bugtracker
> Jan 11 07:17:48 dnsmasq-dhcp: DHCPRENEW(m1s1p1)
> Jan 11 07:17:48 dnsmasq-dhcp: DHCPREPLY(m1s1p1) 2020::12
> Everything is working fine even the renew. Thanks again.
> I will be happy to be your tester :)
> Its fairly a simple setup with two hosts and a switch. I can create this
> any time you want.
> Please provide me the instructions. I am using dnsmasq version 2.78.
> On Wed, Jan
i. Then I could
> uncomment the dhcp-ignore line and devices would need to be explicitly
> added to the conf to get access to anything on my LAN other than the
> internet. I feel like if I understood tags better I might be able to
> figure out how to do this. Otherwise I might n
RFC1531 is twice obsoleted. The current definition of DHCP is RFC2131,
which says, in para 3.2.
The client times out and retransmits the DHCPREQUEST message if
the client receives neither a DHCPACK nor a DHCPNAK message. The
client retransmits the DHCPREQUEST according to the
On 04/01/2019 06:25, Sandeep K M wrote:
> Hi Simon,
> Thanks a lot for your prompt reply.
> Attached are the packet captures:
> 1. Packets exchanged between client and relay (client-relay.pcap)
> 2. Packets exchanged between relay and server (relay-server.pcap)
> 3. strace of dnsmasq
to running the ulimit
> command in the shell script I start dnsmasq from.
> The launch script now does this to set the core dump location:
> echo '/tmp/core.%h.%e.%t' > /proc/sys/kernel/core_pattern
>> On Jan 8, 2019, at 3:14 AM, Simon Kelley w
On 08/01/2019 03:46, Mufasa wrote:
> On 01/07/2019 08:32 AM, Simon Kelley wrote:
>>/I've worked through the patch, and been inspired to clean up a few
>>/>/long-standing nasty bits. This has the consequence that the mechanisms
>>/>/which were added to enable stora
the new dog food here.
Please test away.
On 20/12/2018 23:20, Jeremy Allison wrote:
> On 12/20/2018 03:11 PM, Simon Kelley wrote:
>> This is worth having for the removal of the archaic 16-bit limit on the
>> flags field in a cache record alone. I've been me
It would be useful to get full packet dumps rather than just tcpdump
It would also be useful to run dnsmasq under strace and see what
syscalls it's making: that would tell use where the reply might be going.
On 03/01/2019 07:41, Sandeep K M wrote:
> Hi All,
Prodding me is fine, and has done the trick here.
In general, I'm way behind my inbox, and struggling to catch up. Moving
house is not helping :(
I will try and get to everything in the end, but I won't be offended is
people remind me.
On 03/01/2019 05:49, Christian Weiske
The leftmost 0 means that the leases are infinite, they never expire,
which might explain why you're running out of leases.
There can be duplicate leases per MAC address, but there should never be
duplicate leases for an IP address. So I'm interested in finding out how
you've contrived this
every 3 seconds, overwhelming
> pi-hole and slowing all responses (including DNS). Some client devices
> (iPhone 7) can be observed to temporarily acquire an address, and then
> drop it moments later.
> ## Debug Token:
> ## Versions:
> Dnsmasq version 2.76
On 31/12/2018 21:39, Jon Anderson wrote:
> Hello all,
> I wanted to setup a PiHole for blocking ads and for the ability to
> modify DNS settings network-wide. I have just switched my ISP to AT
> fiber where we are required to use a supplied modem/router (ARRIS
> BGW210-700) which does not allow
I just pushed a fix which should solve this:
On 21/12/2018 14:48, Jangala Anvesh wrote:
> Problem Statement :
> DNSMASQ is offering the declined address repeatedly to
This code is relevant, in src/dnsmasq.c
prctl(PR_SET_DUMPABLE, 1, 0, 0, 0);
On 28/12/2018 03:40, Arvind Nagarajan wrote:
> Hi All,
> When dnsmasq crashes due to segfault (SIGSEGV) I am not getting a core
> file generated.
> Is this
The best solution to this is to stop blocking ICMP.
The simplest solution is not to use dhcp-sequential-ip. The normal
address-allocation process in DHCP perturbs the hash function when a
DECLINE reply is received, so the next allocation will be to a different
Using ARP probing from the
Patch below is untested because I'm away from my test rig, but it would
seem to do the right thing, ie set template->if_index _before_ calling
ra_start_unsolicited() so that if we re-enter here via an async event it
doesn't get called again.
If you could test it in your harness, that would be
This is worth having for the removal of the archaic 16-bit limit on the
flags field in a cache record alone. I've been meaning to tackle that
for some time.
This time of year either frees up lots of time for coding, or yields
none at all, and for me it's the later, but I will go through this and
This is obviously a large amount of work, so thanks very much for that.
To make use of it, I need to be able to see as clearly as possible what
is being changed, and why. To that end, I'd much rather have diff files
ten replacement files, but it's fairly easy to generate those for
I can't answer your question about if this has been fixed, as there's
not enough information to identify the problem or trigger the bug.
Can you provide proof-concept code, or even just packet captures of the
malformed packets that cause problems?
I've confused by the "dhcp to be unresponsive
On 13/12/2018 14:10, Craig Younkins wrote:
> First, thank you for dnsmasq!
> I'm among a number of people having trouble using dnsmasq
> for DHCP when it is running in a docker container. Everyone seems to get
> "no address range available for DHCP request via eth0" in their log
Thanks both for this. Petr's more comprehensive patch is now in my tree.
On 15/12/2018 09:43, Kevin Darbyshire-Bryant wrote:
>> On 14 Dec 2018, at 16:10, Petr Mensik wrote:
>> Hi Kevin et al,
>> sure, your fix is correct one. I just found one more place where
Patch applied. Thanks.
What we really need is a script that calls make repeatedly whilst
cycling through all the possible combinations of build options.
On 10/12/2018 10:34, Kevin Darbyshire-Bryant wrote:
> Hi Simon,
> master has a build error when building without
Ooops. My hand's up for that one. Patch applied. Thanks.
On 12/12/2018 12:00, Kevin Darbyshire-Bryant wrote:
> Hi Simon,
> Another one fallen out of the openwrt tree shake :-)
> ipv6 ipset addresses weren’t being set correctly. patch attached
On 19/11/2018 21:07, M. Buecher wrote:
> Hello Simon and dnsmasq fellows,
> I blacklist several domains via host files and wanted to skip the
> blacklist for my testing client.
> Unfortunately I couldn't find a solution for this in the man page, or
> maybe I just didn't see the correct config
This does seem odd. Would it be possible to capture the DHCP packets,
using wireshark or tcpdump? Send the dump directly to me if you don't
want to post it in public.
I'm not sure what the status of the WIDE client is - it's not common.
Maybe worth trying the ISC client instead, for quick fix. I
> On 8/21/18 11:24 PM, Simon Kelley wrote:
>> On 10/08/18 13:37, Petr Menšík wrote:
>>> we discovered our dnsmasq were using also privileged source ports when
>>> sending queries. Interest
On 05/11/2018 03:30, Kevin Darbyshire-Bryant wrote:
> Hi Simon, Hi List,
> I’m hearing rumblings from the openwrt community that something isn’t right
> with static leases. The behaviour manifests itself as the statically
> assigned host being unable to renew its lease. e.g.
> -this is
On 25/10/2018 09:36, Petr Mensik wrote:
> Hi again.
> This time I have a little bit more controversal patches. But I think
> still useful. They fixes memory leaks that might occur in some cases.
> Most dnsmasq errors is fatal, so it does not matter. But some are not.
> Some parts are reloaded
Kevin's analysis is spot-on, as is his patch, which I've just applied.
On 26/10/2018 00:24, Kevin Darbyshire-Bryant wrote:
>> On 25 Oct 2018, at 21:38, Kevin Darbyshire-Bryant
>> I think Openwrt is safe. There will be a loud scream from me if it isn’t
I'm confused by the references to openssl in your description. Dnsmasq
with DNSSEC does NOT depend on openSSL. You just need libnettle and
libhogweed installed in the standard way, and accessible via pkg-config.
version 3.4 should be fine.
On 31/10/2018 03:21, Peter Nehem
Can you also add a dhcp-range for the ULA range, which deprecates it?
On 27/10/2018 18:17, Christopher Martin wrote:
> Is it possible to prevent Dnsmasq from advertising a specific prefix via
> router advertisements?
> Here's my situation. My ISP provides a
There's a CNAME at the root of the domain, which is not permissible, and
the root cause of the validation failure.
gives some reasons why this is not a good idea.
What actually happens is that dnsmasq makes a
The solution may be use of --hostsdir, which avoids the need for sending
On 28/10/2018 10:55, Микола Василенко wrote:
> Hi all,
> Is there any method to avoid DNS cache clearing on SIGHUP? I want only
> to update host info by sending SIGHUP to dnsmasq daemon. As
On 24/10/2018 16:25, Petr Mensik wrote:
> I have not managed it until dnsmasq 2.80 were out, but anyway. I have
> some proposal to simplify handling of options bits. Static analysis
> complains on compiler dead-code optimization. I propose having array
> instead. It adds few defines. But
The dnsmasq code has a range of binary compile-time options, implemented
conventionally using the C pre-processor. These options are mutually
independent, so the numnber of different versions scales as 2^n. To keep
this managable, I'm trying to limit the number of options.
I've already removed
On 22/10/2018 17:56, Craig Andrews wrote:
> I'm unable to look up *.disa.mil when using dnsmasq - I'm hoping that we
> can figure out why that is.
> I have dnsmasq configured to use Cloudflare's 18.104.22.168 as its upstream
> DNS server; dnsmasq is running on 192.168.0.1.
> Here are some a couple
oudflare's 22.214.171.124 with
> dnssec works, but not with dnsmasq.
> # dnsmasq --version
> Dnsmasq version 2.80test3 Copyright (c) 2000-2018 Simon Kelley
> Compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6
> no-Lua TFTP conntrack ipset auth DNSSEC no-ID
Von: Andrey Vakhitov
> Gesendet: Samstag, 6. Oktober 2018 20:31
> An: 'Simon Kelley' ;
> Betreff: AW: AW: AW: [Dnsmasq-discuss] clients of DHCPv6 with constructed
> IPv6 address range are not notified on address range change
I just published dnsmasq-2.80, available at
Changelog attached below.
Add support for RFC 4039 DHCP rapid commit. Thanks to Ashram
Method for the initial patch and motivation.
address is already in use; the
> client may respond to ICMP Echo Request messages at this point."
> => Invalidates the fix you did in 2017:
> commit 5ce3e76fbf89e942e8c54ef3e3389facf0d9067a
> Author: Simon Kelley
> Date: Fri Apr 28 22:14:20 201
As far as I'm aware, the development tree is in a good state at the
moment, and I'd like to begin the process to release 2.80. Accordingly
I've tagged the first release candidate.
A tarball is available here:
I have to confess I never considered this as a valid possibility, but to
does make sense, maybe.
The sane, backward-compatible way to do it might be to extend the syntax
of auth-soa, to allow a zone name to be included, so your second
auth-soa line would become
On 11/10/18 00:28, Rene 'Renne' Bartsch, B.Sc. Informatics wrote:
> the old root-KSK will be deleted today at 16:00 UTC and the TTLs will
> run out not later than 48 hours.
> Does Dnsmasq support IETF RFC 5011 or are there any plans to implement
> IETF RFC 5011?
No, and probably
On 10/10/18 03:35, Donald Muller wrote:
> Hi Simon,
> I believe that a while ago you mentioned that you were going to be
> releasing 2.80 soon. Do you have a target date yet?
The trite answer to this is always "when it's ready".
There have been two or thee issues over the last week or
On 10/10/18 11:02, Connor Bell wrote:
> Hi everyone,
> I’ve had a strange issue I’ve been trying to resolve over the past few
> days where dnsmasq seems to only be allowing part of a zone transfer
> through, causing dig to hang.
> I opened a Stackoverflow post to track it
On 05/10/18 06:06, Josh Soref wrote:
> Simon Kelley wrote:
>> You say "When I perform DNSSEC validation over IPv6" which implies, but
>> doesn't state, that the same test works when talking to usptream DNS
>> servers over IPv4? Is that the case? Certainly, a qui
On 28/09/18 23:46, Simon Kelley wrote:
> On 28/09/18 23:07, Marc Heckmann wrote:
>> Very nice, I will test this.
>> I am curious though: what will be used for the NS record if the
>> auth-server configuration is omitted?
> It appears to return an NS
le. This may need some more thought
> On Fri, Sep 28, 2018 at 4:42 PM Simon Kelley <mailto:si...@thekelleys.org.uk>> wrote:
> On 28/09/18 02:33, Marc Heckmann wrote:
> > Hello,
> > I'm currently running d
On 28/09/18 02:33, Marc Heckmann wrote:
> I'm currently running dnsmasq in a Docker container and have setup a
> domain for which dnsmasq is to be authoritative for. This is to do
> subdomain delegation to the dnsmasq server. I am using the auth-server &
> auth-zone configuration
dest.sin_port = htons(daemon->dhcp_client_port);
/* unicast to unconfigured client. Inject mac address direct
into ARP cache.
> *Sent:* Thursday, September 27, 2018 at 7:43 PM
> *From:* "Simon Kelley&q
> After that I promise I wont bother anymore ;)
> *Sent:* Wednesday, September 26, 2018 at 4:36 PM
> *From:* "Simon Kelley"
> *To:* email@example.com
> *Subject:* Re: [Dnsmasq-discuss] No Broadcast Dhcp Offe
On 27/09/18 14:42, Kristian Evensen wrote:
> Hi Simon,
> On Wed, Sep 26, 2018 at 7:30 PM Simon Kelley wrote:
>> Simplest test is to make whichdevice always return NULL, and see if that
> Making whichdevice() always return NULL makes the issue go away.
On 26/09/18 17:33, Simon Kelley wrote:
> On 24/09/18 11:45, gravit...@gmx.com wrote:
>> Amof, the first and only frames my dongle sends on eth at start, are
>> some Dhcp DISCOVER, no arps at all.
>> Please note that such Dhcp DISCOVER frames come with the broadca
On 24/09/18 19:12, Kristian Evensen wrote:
> I have some routers running OpenWRT (latest nightly) and that I have
> to access remotely (using reverse SSH). When I restart networking
> (/etc/init.d/network restart), clients on the LAN can no longer obtain
> an IP address using DHCP. If
On 24/09/18 11:45, gravit...@gmx.com wrote:
> Amof, the first and only frames my dongle sends on eth at start, are
> some Dhcp DISCOVER, no arps at all.
> Please note that such Dhcp DISCOVER frames come with the broadcast bit
> NOT set.
> Afaik, that meas my dongle is indeed asking the Dhcp
On 25/09/18 22:15, Chris Staite wrote:
> I've recently upgraded my router to an alpha firmware that uses DNSmasq
> v2.79. I'm having issues with it performing DNSSEC validation that I didn't
> have with the old version of DNSmasq (which I'm not entirely sure which
> version it was).
On 19/09/18 13:04, Dominik DL6ER wrote:
> Hey Simon,
> On 19.09.2018 13:27, Simon Kelley wrote:
>> when rd is not set, never answer
>> from the cache, but always forward the query. That would allow dig
>> +trace to work.
>> Does hat seem sensible?
On 19/09/18 08:59, Kristian Evensen wrote:
> Hi Simon,
> Thanks for a quick reply.
> On Wed, Sep 19, 2018 at 12:23 AM Simon Kelley wrote:
>> Thanks for the report. The obvious explanation is that whine_malloc() is
>> returning NULL, and the code should han
On 19/09/18 11:09, Bernard CLABOTS wrote:
> Thanks a lot for this answer.
> Indeed, it is a special case as we have a simple two way Request/ACK,
> this is also what is seen with some implementations when quickly
> unplugging/re-plugging the cable, it is legal AFAIK.
> I also agree on the
The change in question causes dnsmasq to always return SERVFAIL for
queries without the "use recursion" bit set.
The relevant quote in the reference
Recommendation 2: secondly, and most importantly, non-authoritative
On 18/09/18 23:03, line wrap clean up wrote:
> On Tue, Sep 18, 2018 at 11:13:27PM +0200, Andrey Vakhitov wrote:
> Hi Simon,
>>> I've set it up as you suggested, initially name resolution seems
>>> to work fine. But after some days of operation (and some nightly
>>> reconnects) dnsmasq seems to
On 18/09/18 23:03, line wrap clean up wrote:
> Strange thing: sometimes after reconnect I can observe expected behaviour
> (like you described it, see log 1), sometimes not (SLAAC-CONFIRM is missing,
> see log 2)
> -- log1
> Sep 17 20:22:45 rtr dnsmasq-dhcp: DHCPv6
On 18/09/18 16:59, Bernard CLABOTS wrote:
> Hi all,
> I have been trying to replicate an issue of IP conflict on Open-WRT,
> the issue is randomly seen, and I expect in real life, it is related to
> a de-sync of the lease data base with the actual situation (in case a
> switch is between the
On 18/09/18 11:28, Kristian Evensen wrote:
> I recently updated one of my x86-based OpenWRT-routers to the latest
> nightly, which bumped dnsmasq to 2.80test6. After the update, I see
> that dnsmasq sometimes enters a crash loop. The crash occurs right
> startup (SIGSEV), and the
On 10/09/18 00:19, klondike wrote:
> Hi Simon,
> El 08/09/18 a las 19:17, Simon Kelley escribió:
>> The question is, should the above configuration be "baked in" to the code?
> Yes. In general it is considered against good practice to provide insane
On 10/09/18 19:51, Andrey Vakhitov wrote:
> Hello Simon & Uwe,
>> unfortunately that problem is seen often with providers in Germany, although
>> the large ones no longer
>> do it (or allow to disable the disconnect). The problem is that German
>> providers automatically
>> disconnect the
On 15/09/18 10:05, Andrey Vakhitov wrote:
> Hello Uwe,
>>> My recommendation to the reporter:
>>> - Don't use stateful DHCPv6 in Germany, that does not work well. You
>>> clients should get the addresses using router advertisements. For static
> hosts assign static names in your own domain.
On 13/09/18 10:08, Wojtek Swiatek wrote:
> Le sam. 8 sept. 2018 à 15:45, Simon Kelley <mailto:si...@thekelleys.org.uk>> a écrit :
> No, that's a different problem. your target name "vpnin.swtk.info
> <http://vpnin.swtk.info>" is
1 - 100 of 2866 matches
Mail list logo