-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I can't see any immediate reason for this.
If the local-service setting is the cause of this, dnsmasq should log
Ignoring query from non-local network
the first time it throws away a query. Please could you look in the
logs and see if that message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/02/15 07:51, Yongkang You wrote:
> On Tue, Feb 3, 2015 at 6:38 AM, Simon Kelley
> wrote:
>
>> Could you try the latest code again? I just checked in a fix.
>>
>>
> Still doesn't work. I still need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wonder if the code assumes that there won't be two or more
interfaces on the _same_ subnet? Will check and get back to you.
Cheers,
Simon.
On 02/02/15 05:26, T o n g wrote:
> On Sat, 31 Jan 2015 15:32:46 +, T o n g wrote:
>
>> On Sat, 31 J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Could you try the latest code again? I just checked in a fix.
Cheers,
Simon.
On 02/02/15 16:13, Yongkang You wrote:
> On Sun, Feb 1, 2015 at 6:05 AM, Simon Kelley
> wrote:
>
>> I just checked in code which supports
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/15 22:20, Brian Haley wrote:
> The one thing I'm curious about is if dnsmasq is restarted while a
> VM holds a lease, how will it respond? As someone else has
> pointed-out to me - isc-dhcp will respond with a DHCPNAK in that
> case, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/15 15:57, Niels wrote:
>
>> On 31 Jan 2015, at 23:21, Simon Kelley
>> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 31/01/15 13:57, Joachim Zobel wrote:
>>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/15 03:22, Alan wrote:
> I configured dnsmasq to read an additional hosts file using:
>
> addn-hosts=/var/run/openvpn/hosts.muvpn
>
> This file is created and updated by openvpn when users connect and
> disconnect via external script, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/15 19:50, Brian Haley wrote:
> Hi,
>
> There have been a number of people chasing an issue in Openstack
> where dnsmasq was sending DHCPNAK's after it was restarted since
> it's being started with --leasefile-ro
> (https://launchpad.net/bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/01/15 15:32, T o n g wrote:
> On Sat, 31 Jan 2015 03:44:26 +, T o n g wrote:
>
>>> I following the following to config dnsmasq as DHCP and DNS
>>> server
>>> http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation-
>>> configuration-5/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just checked in code which supports
- --dhcp-hostsdir (as before) but also
- --dhcp-optsdir
- --hostsdir
to allow automatic reads of new DHCP options, and host IP addresses
(like /etc/hosts)
That should be what you need, if I understood right.
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/01/15 13:57, Joachim Zobel wrote:
> Hi.
>
> I am currently thinking about implementing a feature in dnsmasq
> that I consider highly useful. When I do a netstat-nat on my router
> (asuswrt), I will mostly get reverse names that are about as usef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/01/15 03:50, Yongkang You wrote:
> On Thu, Jan 22, 2015 at 4:48 AM, Simon Kelley
> wrote:
>
>> OK, the first problem: I didn't anticipate that you're using
>> dhcp-optsfile, do there's no support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No offence taken. I tweaked the patches and pushed the changes into git.
Cheers,
Simon.
On 24/01/15 16:50, Kevin Darbyshire-Bryant wrote:
> On 23/01/2015 14:07, Simon Kelley wrote:
>> Yes, that's fine. It'll be a couple of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/01/15 21:03, John Connett wrote:
> I have a router running OpenWrt (BarrierBreaker 14.07) with
> dnsmasq (2.71-4).
>
> I would like to use Dynamic DNS Updates via TSIG as offered by
> Dyn: http://dyn.com/apps/updater/tsig/
>
> How can I do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Expired entries are evicted first. (since expired entries are dead
anyway, that means, in effect that nothing is evicted whilst there are
expired entries.) If there are no expired entries then the least
recently _used_ entries are victimised next.
New
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/01/15 22:39, Alexander Clouter wrote:
>> On 20/01/15 20:33, Alexander Clouter wrote:
>>
>> One possible solution to this might be to make the filter
>> language in - --auth-zone allow _exclusion_ of subnets as well as
>> inclusion, say somthing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, that's fine. It'll be a couple of days before I have time to do
the work.
Cheers,
Simon.
On 22/01/15 09:09, Kevin Darbyshire-Bryant wrote:
> Hi Simon
>
> I'm wondering if you'd consider putting the new 'inotify' related
> code as a compile ti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My first reaction to this was to apply it, but then I went and looked
at RFC3315, and found this:
If the server will not assign any addresses to any IAs in a
subsequent Request from the client, the server MUST send an Advertise
message to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/01/15 12:48, Sharan Basavaraj wrote:
> Problem: I am doing a DNS query and i see that queries are first
> sent for address and then sent for A on failure of
> option.
This is a feature of the client which is using dnsmasq, not dnsm
;s no logging for this, given we're
trying to support lots of files, I didn't want to clog up the logs.
Cheers,
Simon.
On 21/01/15 16:10, Yongkang You wrote:
> On Wed, Jan 21, 2015 at 4:57 AM, Simon Kelley
> wrote:
>
>> There's some code in the git repo now,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/01/15 20:33, Alexander Clouter wrote:
>> Two observations:
>>
>> 1) The patch as it stands doesn't just affect authoritative DNS
>> answers - it filters those addresses from "ordinary" internal
>> DNS requests too.
>
> Boo!
>
>> 2) Follow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No, the caching is limited to A, and CNAMEs. (plus some others
when DNSSEC is in use.) Everything else is forwarded but not cached.
Cheers,
Simon.
On 20/01/15 11:08, Channabasappa, Ravindra wrote:
> Hi, Is there an option to cache SRV recor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/01/15 22:47, David Erickson wrote:
> Hello- I am using dnsmasq inside dd-wrt, I am a recent build of
> DD-WRT with dnsmasq v2.72. I am having problems getting server
> domain forwarding to work, in particular I can tcpdump and watch my
> req
have identical MACs
>>
>> On Sun, Jan 18, 2015 at 22:22:33, Simon Kelley wrote:
>>> Please could you check that the code in git now behaves as
>>> expected?
>>
>> I planned to do this today but got stuck doing other things: will
>> get back to you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
>
>
>>
>> The simple way to implement this simply adds new configuration
>> from new files, if a file gets changed or deleted, then the
>> dhcp-hosts that were created by its old contents are not deleted,
>> and SIGUSR1 is still needed to re-read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Two observations:
1) The patch as it stands doesn't just affect authoritative DNS
answers - it filters those addresses from "ordinary" internal DNS
requests too.
2) Following from that, there's a good chance that there are dnsmasq
installations tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/01/15 08:35, Cory Benfield wrote:
> On Wed, Jan 14, 2015 at 21:44:54, Simon Kelley wrote:
>> The obvious thing to do is still to add the scope_is check in
>> scokaddr_isequal. I'll find time in the next couple of days
ers,
Simon.
> I reduced the lease times to only a few minutes but later I will
> set them to some more practical values again.
>
> But for now time healed any wounds.
>
> Thanks again, Helmut
>
>
> Am Montag, 12. Januar 2015, 20:32:39 schrieb Simon Kelley:
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/01/15 09:25, Yongkang You wrote:
> On Thu, Jan 15, 2015 at 9:56 PM, Simon Kelley
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 15/01/15 07:47, Yongkang You wrote:
>>> Hi Simon,
&g
her reload
> events, when last reload event is not finished.
>
> On Thu, Jan 15, 2015 at 6:10 AM, Simon Kelley
> wrote:
>
> 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
-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 handling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/01/15 15:18, Cory Benfield wrote:
> On Mon, Jan 12, 2015 at 20:46:36, Simon Kelley wrote:
>> You're well on the trail.
>>
>> In src/network.c in iface_allowed() there's some code
>>
>> /* check whet
-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.
Ch
-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 w
-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 can'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
You're well on the trail.
In src/network.c in iface_allowed() there's some code
/* check whether the interface IP has been added already
we call this routine multiple times. */
for (iface = daemon->interfaces; iface; iface = iface->next)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A couple of things to start with:
First, tell us the version of dnsmasq you're using.
Second, add
log-dhcp
to the configuration file, let you clients attempt to get an address,
and see what was logged. Amongst other things, all the tags that
dnsma
#x27;s all of the feedback I got so far.
>
> -Michael
>
> On Sat, 2015-01-03 at 15:35 +, Simon Kelley wrote:
>> Given the available information,
>>
>> http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=094b5c3d904bae9aeb3206d9f3b8348926b84975
>>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There shouldn't be any need to change the dnsmasq configuration at
all. It should just work.
Cheers,
Simon.
On 11/01/15 18:32, Rene Stoutjesdijk wrote:
> Goodday, unitll now i'm using dnsmasq where the clients are on the
> same interface (and su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OK, that's useful, but not good. The last thing DNSSEC/IPv6 needs is
yet another reason why network access which used to work now doesn't.
edns-packet-max=1280 seems to be working fine here. Please let me know
if you find anything more.
Cheers,
Si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Normally, queries are sent to just one server, but every so often, a
query is sent to both servers, to see which on answers first. The
server which answers first is used until the next time the test is
done. If a query times out, the retry is done to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
An interesting observation: my IPv6 connectivity is via a sixXS tunnel.
Resolving isc.org through dnsmasq w/DNSSEC to google's IPv6 DNS
servers times out, because dnsmasq was never getting a reply to a
query for the DNSKEY RRset for org. This reply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A backtrace is the most important starting point. A query log _if_
it's query dependent, but that seems unlikely since it doesn't break
when forwarding to IPv4. An easy way to reproduce would be great :-)
I can do the same tests here, but it's a bit
I will still try to produce a test dnsmasq version from
> the cerowrt-3.10 tree but I doubt it would be safe to do an opkg
> update for it.)
There shouldn't be any non backwards-compatible changes in dnsmasq to
bite you. Don't know about other stuff.
Cheers,
Simon.
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OK, it's taken some time, but with this insight, I've recoded the
relevant stuff to look for the limits of the signed DNS tree from the
DNS root down. That's clearly the correct way to do it, and should
avoid the original problem here, caused by send
Simon.
> wkr rene
>
>
> On Sat, Jan 3, 2015 at 6:21 PM, Simon Kelley
> wrote: I think you're right about the
> problem.
>
> The simplest solution would be to add code the dhcp_release to
> provide the same circuit-id information that the client would.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Applied. Thanks.
Simon.
On 04/01/15 10:58, Yousong Zhou wrote:
> When doing rebuild with `make -j32' or the like, a race condition
> is likely to occur and the following error be emitted when doing
> parallel build.
>
> make[1]: Entering directo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I think you're right about the problem.
The simplest solution would be to add code the dhcp_release to provide
the same circuit-id information that the client would.
To be honest dhcp_release is a bit of a hack, and making it work in
the general ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That's nice: fixes something that bites me regularly.
Patch tweaked to suit my tastes, and fixed up (Need to delete .conf_*
when making a new one, md5sum dnsmasq.h not config.h)
Please shout of I broke anything.
Applied.
Cheers,
Simon.
On 31
e stay tuned for that. I will also try to encourage some of
> our users in testing this pre-release.
>
> If that would be of any help, I can try setting up a domain that
> signs its records by using that algorithm.
>
> -Michael
>
> On Tue, 2014-12-23 at 16:02 +, Simon Ke
27;re using and excerpts from
logs where that configuration is misbehaving. It's fine if you don't
want to post system-specific stuff to the list, just send it to me direct.
Cheers,
Simon.
On 22/12/14 19:52, Malte Forkel wrote:
> Am 21.12.2014 um 18:25 schrieb Simon Kelley:
>>
r merging?
>
> I have been personally using the patch for over a month without
> problems.
>
>> On Oct 9, 2014, at 10:48 PM, Simon Kelley
>> wrote:
>>
>> On 08/10/14 13:13, Glen Huang wrote:
>>> Is it possible to ask dnsmasq to ignore DNS responses w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try
local=/virt/
the extended domain= syntax is broken in some recent dnsmasq releases.
Cheers,
Simon.
On 23/12/14 19:59, martin f krafft wrote:
> also sprach Simon Kelley [2014-12-23
> 18:14 +0100]:
>> My guess is that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My guess is that the SERVFAIL is coming from a server upstream of
dnsmasq. Unless told to, dnsmasq "overlays" the DNS information is has
locally onto the global DNS a record-at-a-time, not a domain-name at a
time. So if dnsmasq knows the IPv4 address
>
> On October 22, 2014 11:20:35 PM CEST, Simon Kelley
> wrote:
>> On 21/10/14 15:24, SiGe wrote:
>>> I experienced that problem myself, posted about it on the
>>> mailing
>> list
>>> a few days ago. At least it happens on my domain that has b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try the dnsmasq git repo, and specifically this commit, which should
fix things.
Cheers,
Simon.
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=cbc652423403e3cef00e00240f6beef713142246
On 18/12/14 12:15, janos.mattyasovs...@bmw.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/12/14 11:01, Malte Forkel wrote:
> Hello,
>
> I'm trying to convince two instances of dnsmasq to cooperate while
> their LANs are connected by a bridged OpenVPN connection. Both LANs
> use the same domain name and subnet. DHCP traffic throug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The deep reason for this is that the architecture of dnsmasq doesn't
allow it to return DNS answers with information that comes from
upstream _and_ local information.
You have defined the address of itavm0002.muc. locally, but the CNAME
comes from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/11/14 20:27, Eric Johansson wrote:
> my goal is to make all interfaces in a multi-homed host have the
> same name so users are directed to the right (local network)
> interface.
>
> I have the following line in subnet specific lease files.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just pushed changes to the git repo to implement this. Michael,
please could you seen if it now behaves as you'd like?
Cheers,
Simon.
On 01/12/14 18:49, Michael Gorbach wrote:
> On Nov 30, 2014, at 11:17 AM, Simon Kelley
> wrote:
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I confess I can't come up with a sensible rationalisation for this,
but I think it has something to to with the immediately preceding
commit in dnsmasq, which adds, this code.
+ if (header->hb3 & HB3_TC)
+ {
+ /* Trunca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try git now. realpath() is my friend.
Cheers,
Simon.
On 12/12/14 09:11, Toke Høiland-Jørgensen wrote:
> Simon Kelley writes:
>
>> That sounds sensible, I shall continue my tour around the
>> farther reaches of the Un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/12/14 07:17, Toke Høiland-Jørgensen wrote:
> Simon Kelley writes:
>
>> I just pushed code into git which uses inotify to track changes.
>> Dnsmasq should now re-read the file whenever it is closed after
>> being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Vikram,
Dnsmasq imposes a hard limit on the number of DHCP leases, to avoid
DoS attacks. Old releases used to default this to 150, I think.
Current releases have the default at 1000. The limit can be changed
with the dhcp-lease-max config paramet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/12/14 17:30, AJ Weber wrote:
> Is there a way to set multiple dhcp ranges (on the same interface
> and subnet)?
>
> For example, can I set: DHCP Range = 192.168.1.20-100 AND
> 192.168.1.130-254
>
> I realize it's a strange request, but wond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That's difficult to explain, at least at first glance.
Could you look in the log for startup of dnsmasq, it will have logged
all the configured IP ranges for DHCP. Is there anything which
corresponds to the 0.0.0.145 address?
Also, the client seems
Hi Toke,
I just pushed code into git which uses inotify to track changes. Dnsmasq
should now re-read the file whenever it is closed after being open for
write, or when it's moved into the parent directory.
I'm pretty sure (unless I've done it wrong) that this will fix your
problem. Please could
On 09/12/14 10:18, Hans Dedecker wrote:
> Make sure dst_addr is assigned the correct address in receive_query when
> OPTNOWILD is
> enabled so the assigned mark can be correctly retrieved and set in
> forward_query when
> conntrack is enabled.
>
> Signed-off-by: Hans Dedecker
Patch applied. Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/12/14 10:04, Benjamin Picardat wrote:
> Hello,
>
> So I dug around a bit in the code, and I think my line in the
> configuration "dhcp-option=tag:eth2,54,192.168.0.10" is ignored
> because "server-identifier" is tagged OT_INTERNAL in opttab[]
On 01/12/14 18:49, Michael Gorbach wrote:
> On Nov 30, 2014, at 11:17 AM, Simon Kelley
> wrote:
>>
>> On 29/11/14 19:18, Michael Gorbach wrote:
>>> Hi All,
>>>
>>> I've got a question and potential enhancement request. It looks
>>> lik
On 29/11/14 19:18, Michael Gorbach wrote:
> Hi All,
>
> I've got a question and potential enhancement request. It looks like
> right now, the (very useful) interface-name feature pulls all
> (global) addresses from the interface. One of my machines uses IPv6
> privacy extensions (known in Linux as
On 28/11/14 21:44, Michael Rack wrote:
> Hi!
>
> My DNSMASQ Process was open to anyone on the Internet.
> Since few days, i had many service interruptions, so i did a
> network-monitoring and found, that DNSMASQ had many connections open.
>
> It looks like a DDoS - also it felt for me as one.
>
On 23/11/14 01:09, Synchunk wrote:
> Hey,
>
> I'm trying to create a web interface where you can select which
> computers should boot using TFTP.
> Other computers should get a DHCP lease, but then continue to boot
> normally (without PXE).
>
> I went through the mailing list archive and found:
>
On 24/11/14 15:02, Christoph Kaminski wrote:
> Hi
>
> it is normal that dnsmasq tries to resolve the MX record on each request
> to the forwarder?
> how can I turn it off?
> It is possible to cache this to?
>
> the goal is to make a local caching server what is able 'to survive' some
> time wit
On 23/11/14 17:16, Dave Taht wrote:
> I setup a bunch of picostations running openwrt barrier breaker to try
> and get hnetd working, some details here:
>
> https://plus.google.com/u/0/107942175615993706558/posts/jV9WJyEYGGP
>
> Ran into problems also with getting reverse dns to work right.
>
On 22/11/14 23:06, Dave Taht wrote:
> I have been fiddling with improving my internal dns, by creating a
> file that has all my internal dns servers in it that I can easily copy
> everywhere.
>
> Example serversfile.
>
> server=/rossow.r.lupinlodge.org/172.23.143.9
> rev-server=172.23.8.0/23,172.
>
>> On Oct 9, 2014, at 10:48 PM, Simon Kelley wrote:
>>
>> On 08/10/14 13:13, Glen Huang wrote:
>>> Is it possible to ask dnsmasq to ignore DNS responses whose records
>>> match a certain list of ip, and keep waiting for another response?
>>>
Not sure what's happening here, but the use of "logwrapper" is rather
strange. As I understand it that logs whatever the child process send to
stdout. But dnsmasq has a proper logging system which is aware of the
android logging system and calls __android_log_vprint() (look for
ANDROID in src/log.c
On 21/10/14 15:24, SiGe wrote:
> I experienced that problem myself, posted about it on the mailing list
> a few days ago.
> At least it happens on my domain that has both a SHA-1 AND 256 hash.
> I'm experiencing it with the version currently shipped in the current
> stable OpenWRT version.
>
> So
On 14/10/14 19:33, Nilesh Govindrajan wrote:
> On Tue, Oct 14, 2014 at 11:19 PM, Simon Kelley
> wrote:
>> On 14/10/14 04:09, Nilesh Govindrajan wrote:
>>> Hi list,
>>>
>>> I'm playing with IPv6 after getting a tunnel from HE. I have
>>> co
On 14/10/14 04:09, Nilesh Govindrajan wrote:
> Hi list,
>
> I'm playing with IPv6 after getting a tunnel from HE. I have
> configured dnsmasq as:
>
> domain-needed
> resolv-file=/etc/resolv.dnsmasq
> strict-order
> interface=eth0
> interface=lo
> no-dhcp-interface=lo
> bind-interfaces
> expand-ho
On 10/10/14 03:28, microcai wrote:
> 在 2014年10月8日 星期三 20:13:33，Glen Huang 写道：
>> Is it possible to ask dnsmasq to ignore DNS responses whose records match a
>> certain list of ip, and keep waiting for another response?
>>
>> The rational behind this is that in China, when querying a domain like
>>
On 11/10/14 12:16, Mathias Kresin wrote:
> Hello,
>
> querying dnsmasq from a system which uses uClibc can result in a
> partly not working name resolution.
>
> I'm using dnsmasq 2.71 and uClibc 0.9.33.2 on openWRT 14.07
> (mips/x86). The openwrt version of uClibc includes already a lot of
> fixe
On 07/10/14 18:28, Neil Jerram wrote:
>> On 03/10/14 16:54, Neil Jerram wrote:
>
>>> I'd like to propose the attached patches, which extend the aliasing
>>> concept of the --bridge-interface option to DHCPv6 and Router
>>> Advertisement processing. [...]
>>
>> A query: the semantics you've provid
On 13/10/14 03:07, Dave Taht wrote:
> on cerowrt (ALONG with all the fq_codel, and ipv6 chocolately goodness)
>
>
> http://n1.netalyzr.icsi.berkeley.edu/summary/id=43ca253f-2477-6d1fcde4-650e-45fa-8551
>
> dnssec. working. after 12 years.
>
> /me happy
>
> THANK YOU SIMON FOR THIS IMPORTANT WO
On 08/10/14 13:13, Glen Huang wrote:
> Is it possible to ask dnsmasq to ignore DNS responses whose records
> match a certain list of ip, and keep waiting for another response?
>
> The rational behind this is that in China, when querying a domain
> like youtube.com or twitter.com, a fake ip is quic
On 08/10/14 16:42, Kyle Manna wrote:
> Your issue is definitely related to Android's init system. Android
> has an init system (think extremely crippled systemd or launchd) that
> launches processes and restarts them when they die if so configured,
> among many other things.
>
> The init system o
On 06/10/14 16:30, AJ Weber wrote:
>>Try either dhcp-option=vendor:,1,ip.ip.ip.ip
>>or dhcp-option=vendor:,1,http://fqdn:8080/inform
>>Refer --dhcp-option
> http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html for details
>
> OK, so I'm still confused. Is it assumed that if I use
> dhcp-opt
On 06/10/14 10:34, Christian Ruppert wrote:
>
>
> On 10/03/2014 11:02 PM, Simon Kelley wrote:
>> On 30/09/14 10:52, Christian Ruppert wrote:
>>> Hi Simon,
>>>
>>> the related code is indeed really simple. I have no idea how that could
>>>
On 03/10/14 16:54, Neil Jerram wrote:
> Hi all,
>
> I'd like to propose the attached patches, which extend the aliasing
> concept of the --bridge-interface option to DHCPv6 and Router
> Advertisement processing. Prior to these patches, the effect of the
> --bridge-interface option is limited to D
On 05/10/14 14:17, Praveen Sunagar wrote:
> Hi,
>
> I would like to run the DHCPv6 Server on android devices.
> Please provide us the info to run the dnsmasq for such use case.
> Please provide all necessary info like configuration and command line
> arguments etc.
>
There's a "makefile" for And
On 30/09/14 13:50, Karl Vogel wrote:
> SO_MARK has to be done before issuing the connect() call on the
> TCP socket.
> ---
> src/forward.c | 35 ++-
> 1 files changed, 18 insertions(+), 17 deletions(-)
>
Patch applied. Thanks.
Cheers,
Simon.
__
watched it in gdb but no luck. I hope it's really gone now, whatever caused
> it...
> I'll keep an eye on it. Thanks!
Race between starting NTP and starting dnsmasq?
Cheers,
Simon.
>
> On 09/26/2014 09:45 PM, Simon Kelley wrote:
>> On 26/09/14 09:34, Christian Ruppe
On 30/09/14 15:02, Karl Vogel wrote:
> First version of the patch generated a compiler warning due
> to improper initialization of a variable.
>
> Karl Vogel (1):
> Use nanosecond granularity when checking for file changes.
>
> src/dnsmasq.c | 20 +++-
> src/dnsmasq.h |7
On 02/10/14 15:28, Roy Marples wrote:
> On 2014-09-29 20:17, Simon Kelley wrote:
>> On 27/09/14 11:01, Roy Marples wrote:
>>> On Friday 26 Sep 2014 21:14:20 Simon Kelley wrote:
>>>> This is just a heads-up that if you're using the --dhcp-script
>>>>
On 02/10/14 15:03, Tomas Hozza wrote:
> Hello.
>
> while testing dnsmasq 2.72 I discovered it can fail with segfault.
>
> Reproducer:
> ./dnsmasq --conf-dir=.,
>
> I'm attaching a patch.
Thanks, I applied a fix that just ignores empty suffices, the semantics
are defined, and it avoids yet anoth
On 29/09/14 14:07, Moritz Warning wrote:
> Hi,
>
> I have dnsmasq running and configured to hand out different DHCP
> ranges on two different interfaces. Pretty standard. Now I need to
> use a different set of DNS servers for each interface.
>
> Is that possible?
>
> So far I have tried to run t
On 27/09/14 11:01, Roy Marples wrote:
> On Friday 26 Sep 2014 21:14:20 Simon Kelley wrote:
>> This is just a heads-up that if you're using the --dhcp-script option in
>> dnsmasq, and the script you're calling is being interpreted by bash,
>> then you're affec
ed from the dnsmasq process that doesn't drop privilege,
> unless that new --dhcp-scriptuser option is active.
Correct.
>
> On Fri, Sep 26, 2014 at 4:14 PM, Simon Kelley
> wrote:
>
>> This is just a heads-up that if you're using the --dhcp-script option in
>&g
This is just a heads-up that if you're using the --dhcp-script option in
dnsmasq, and the script you're calling is being interpreted by bash,
then you're affected by the shellshock bug.
The bug allows execution of arbitrary code contained in the values of
environment variables, and there are sever
1501 - 1600 of 4126 matches
Mail list logo
