matthieu castet wrote:
Package: dnsmasq
Version: 2.19-1
Severity: normal
Hi,
dnsmasq failed to give the ip address associated with a MAC address if
the host don't release the ip address (for example power failure on a
machine).
The only way to fix it is to clear /var/lib/misc/dnsmasq.leases .
Dnsma
matthieu castet wrote:
Package: dnsmasq
Version: 2.19-1
Severity: minor
Hi,
the gentoo dhcp client take about 1 minute for having a reply from the
dhcp server.
They seem to send lot's of options. Could it be possible that dnsmasq
ignore the request ?
I don't have the version of the dhcp client, nor
matthieu castet wrote:
In /var/lib/misc/dnsmasq.leases , there were 2 entries for
00:d0:b7:4d:d4:3a one for 10.0.0.14 and one for 10.0.0.7
If the two entries have different client-ids (The last field on each
line) then this is a manifestation of the problem that different OS's
generate differen
Dave Holland wrote:
Package: dhcpcd
Version: 1:1.3.22pl4-21
Severity: minor
/etc/dhcpc/config by default only acts on eth0. This can produce
unexpected behaviour, e.g. when switching from a wired connection on
eth0 to a wireless connection on eth1 the nameservers are not updated.
Suggested fix
Chris Boyle wrote:
Package: dnsmasq
Version: 2.20-1
Severity: important
polaris:~# ping tov.uwcs.co.uk
PING tov.uwcs.co.uk (1.0.0.0): 56 data bytes
[...]
polaris:~# /etc/init.d/dnsmasq force-reload
Restarting DNS forwarder and DHCP server: dnsmasq.
polaris:~# ping tov.uwcs.co.uk
PING molotov.uwcs.c
Leonardo Canducci wrote:
Package: dnsmasq
Version: 2.22-1
Severity: important
I'm using dnsmasq with resolvconf and pppoe with 'usepeerdns' option set
for pppd.
At boot time since dnsmasq is started before pppd gets DNS from ISP
('usepeerdns' option) when it reads /var/run/dnsmasq/resolv.conf the
Leonardo Canducci wrote:
I do run ntpdate. It fails at boot since pool.ntp.org is unreacheable
until pppd gets its dns servers. A script called /etc/ppp/ip-up.d/ntpdate
is run just after pppd gets IP and dns servers and time is adjusted.
Usually step time is under 3 seconds so it shouldn't affect d
Thomas Hood wrote:
Package: dnsmasq
Version: 2.20-1
Severity: normal
I just started using dnsmasq again after a couple of months and I find
that the current version of dnsmasq does not re-read resolv.conf when
it is updated. Sending SIGHUP to the process causes it to re-read
/etc/hosts but not res
Thomas Hood wrote:
On Mon, 2005-03-21 at 08:47 +, Simon Kelley wrote:
Just to get things straight: by default dnsmasq checks the mtime of
resolv.conf and re-reads it when the mtime changes. In this mode it
does _not_ re-read resolv.conf on a SIGHUP.
I am running in default mode, but
.
After suspend-and-resume I have problems with other applications such as
squid and pan which access the network. In their case they use 100% CPU
until they are restarted. dnsmasq, in contrast, does not use 100% CPU
and it responds to signals; but it doesn't notice that resolv.conf has
changed.
Wookey wrote:
Package: dnsmasq
Version: 2.22-2
Severity: normal
I accidentally put a line like this in my dnsmasq.conf:
dhcp-option=pxe,next-server,194.70.44.161
instead of like this:
dhcp-option=pxe,66,194.70.44.161
If you so this dnsmasq segfaults.
That's fixable.
It should complain
Malte Schmidt-Tychsen wrote:
Package: dnsmasq
Version: 2.22-1
Hi there,
ever since the last upgrade dnsmasq stops forwarding dns addresses after
a while. I have to restart ( /etc/init.d/dnsmasq restart ) and everything
works again. I have no idea and there is absolutely nothing in
Malte Schmidt-Tychsen wrote:
Hi,
I restarted dnsmasq on saturday and it seems to be working fine still. I
just did a "dig www.heise.de" and it says that the server running dnsmasq
responded fine (I now have a backup, since my firewall is also running dns
all the machines have the firewall as second
Matus UHLAR - fantomas wrote:
Package: dnsmasq
Version: 2.22-1
there are too many trailing spaces and newlines in default dnsmasq.conf
provided. This is just a cosmeticv issue but due to how I work with my
editor, it generates many differencies each time a new version of dnsmasq
is installed and I
Richard Thrippleton wrote:
Package: dnsmasq
Version: 2.22-2
Severity: wishlist
When you specify only one interface (or several) in dnsmasq.conf, it still
binds to all interfaces to listen for requests. It would be preferable if it
only listened on the specified interfaces, leaving other interfa
Package: wnpp
Severity: wishlist
* Package name: dhcp-helper
Version : 0.2
Upstream Author : Simon Kelley <[EMAIL PROTECTED]>
* URL : http://www.thekelleys.org.uk/dhcp-helper
* License : GPL
Description : A DHCP relay agent.
Dhcp-helper is a DH
A brief summary of the differences between dhcp3-relay and dhcp-helper.
1) Size
/usr/sbin/dhcrelay3 size is 157240 octets
/usr/sbin/dhcp-helper is 9924 octets
2) Kernel requirements
dhcrelay3 needs the Linux Packet Filter Facility available in the
kernel, dhcp-helper doesn't. This allows a s
Peter Samuelson wrote:
[Simon Kelley]
A brief summary of the differences between dhcp3-relay and dhcp-helper.
1) Size
2) Kernel requirements
3) Configuration
Yeah - this is the sort of thing to include in the long description.
Except somewhat shorter than your email was. Otherwise none of
Fabien COUTANT wrote:
> Gonna check this.
> Ok, here's the log:
> Nov 22 20:40:08 harris pppd[10147]: PPP session is 2016
> Nov 22 20:40:08 harris pppd[10147]: Using interface ppp0
> Nov 22 20:40:08 harris pppd[10147]: Connect: ppp0 <--> eth0
> Nov 22 20:40:08 harris pppd[10147]: CHAP auth
Fabien COUTANT wrote:
On Monday, 27 November 2006, you (Simon Kelley) wrote:
If that is the case, then adding
sleep 1
or possibly
sleep 2
to /etc/resolvconf/update.d/dnsmasq should fix the problem. Could you
try that? If it works it's a good fix which is easy to apply.
That'
> On a system of mine (which performs NAT for a LAN behind it), I use
> dnsmasq to provide a caching name server and a DHCP server for the
> LAN.
> On this system:
> # netstat -anp | grep raw
> raw0 0 0.0.0.0:1 0.0.0.0:* 7
> 1106/dnsmasq
> Should
Fabien COUTANT wrote:
> Package: dnsmasq
> Version: 2.35-1
> Severity: important
>
> Look at my pppd syslog:
> Nov 16 18:03:31 harris pppd[4693]: CHAP authentication succeeded: Welcome to
> use Quidway ROUTER, Huawei Tech.^M^J
> Nov 16 18:03:31 harris pppd[4693]: CHAP authentication succeeded
>
Rolf Leggewie wrote:
Package: dnsmasq
Version: 1.23
Severity: important
Hi,
the version of dnsmasq I use on my router is 1.23. I think positive
results for anything *.dyndns.org, *.no-ip.com and other such dynDNS
service providers are kept for too long. IMHO they should not be cached
at all or ma
Johannes Stezenbach wrote:
Package: dnsmasq
Version: 2.37-1
Severity: normal
If dnsmasq gets a DNS standard query response with a
reply code of server failure, it repeats the request
infinitely instead of giving up.
Quick configuration question: how many upstream nameservers do you have,
and
Johannes Stezenbach wrote:
Package: dnsmasq
Version: 2.37-1
Severity: normal
If dnsmasq gets a DNS standard query response with a
reply code of server failure, it repeats the request
infinitely instead of giving up.
OK, I've reproduced this now: it appears to depend on having the
--strict-or
Johannes Stezenbach wrote:
> Yes, that's correct, I have strict-order set.
Ok. In that case I think a fully understand the problem.
>
> I use the resolvconf package to manage /etc/resolv.conf
> (no server= in dnsmasq.conf). I also sometimes have to
> use a VPN (using vpnc), thus I need strict-or
Reuben Thomas wrote:
Package: dnsmasq
Version: 2.35-1
Severity: normal
I had dnsmasq installed, but not resolvconf. When I started up
dnsmasq, it said it was reading entries from /etc/hosts (or
equivalently, /etc/banner_add_hosts, which I also tried with the same
contents). Other machines on the
Johannes Stezenbach wrote:
Package: dnsmasq
Version: 2.33-1+b1
Severity: normal
Tags: patch
I have to use a VPN connection (using vpnc) for some of my work.
The same hostname might then resolve to a different IP address
when the VPN connection is up or down.
resolvconf correctly updates /var/run
Ivan A. Beveridge wrote:
Any suggestions? I searched for a copy of 6.3.0-3 but was unable to find
it anywhere, so I can't confirm that rolling-back would work :(
I doubt the 6.3.0-3 -> 6.3.0-4 changes are the culprit, but I can send
you a copy of 6.3.0-3 to test. It'll be about 2M as mail, i
Ivan A. Beveridge wrote:
On 15/10/2006 12:49, Ivan A. Beveridge wrote:
On 15/10/2006 10:28, Simon Kelley wrote:
I doubt the 6.3.0-3 -> 6.3.0-4 changes are the culprit, but I can send
you a copy of 6.3.0-3 to test. It'll be about 2M as mail, is that OK?
(Otherwise, I'll put
Daniel Jacobowitz wrote:
> Package: dnsmasq
> Version: 2.55-2
> Severity: normal
>
> I am using resolvconf and dnsmasq to handle internal DNS servers for
> our VPN. When openconnect creates the tun0 interface, it adds the
> internal nameservers using resolvconf. resolvconf modifies dnsmasq's
> c
On 19/12/13 10:51, Michael Prokop wrote:
Package: dnsmasq
Version: 2.68-1
Severity: normal
I've been involved in two situations already where a default dnsmasq
installation was misused for DDoS nameserver attacks, because
dnsmasq is listening on all network devices without any real
limitations
On 26/11/13 14:16, Alex Corcoles wrote:
Package: dnsmasq
Version: 2.67-1
Severity: normal
Hi,
After setting up libvirt, my dnsmasq occasionally stops resolving cnames
specified in its configuration file. My dnsmasq is configured with:
interface=br0 # for kvm
bind-interfaces # for kvm
, to pre
e are problems or in a week if there's no incident.
Brilliant. Many thanks.
Simon.
Cheers,
Álex
ps.: love dnsmasq! good work
On Tue, Nov 26, 2013 at 3:45 PM, Simon Kelley
wrote:
On 26/11/13 14:16, Alex Corcoles wrote:
Package: dnsmasq
Version: 2.67-1
Severity: normal
Hi,
A
Package: ftp.debian.org
Severity: normal
This package contains the very old dhcpcd version 3. It's long ago
unmaintained upstream and replaced with dhcpcd version 5. Dhcpcd version
5 is not directly comptatible with dhcpcd version 3, so it was good to
have one stable release with both versions ava
On 20/05/14 21:20, l3iggs wrote:
> Package: dnsmasq Version: 2.71-1 Severity: normal Tags: upstream
>
> Dear Maintainer,
>
> I've been trying to use the built in tftp server.
>
> It works fine when I use it to serve up smaller (25byte) files.
> However, when serving up larger (~320k) binary file
On 11/05/14 15:11, Andreas Metzler wrote:
> On 2014-05-11 Michael Biebl wrote:
>> Am 11.05.2014 10:13, schrieb Andreas Metzler:
>>> On 2013-09-25 Julian Andres Klode wrote:
> [...]
dnsmasq currently does not enable its systemd unit in postinst. It should
probably use dh-systemd.
> [...]
On 17/05/14 20:09, Harald Dunkel wrote:
> Package: dnsmasq
> Version: 2.70-3
>
> Since 2.70-3 dnsmasq doesn't recognize the hosts in the local network
> anymore. The log file shows
>
> May 17 20:23:23 sylvester systemd[1]: Starting A lightweight DHCP and caching
> DNS server...
> May 17 20:23:23
On 12/01/13 22:04, Chris Carr wrote:
Happy new year Simon. I have finally discovered bug#681961, which looks
as if someone else is having the same problem that I am. If the offered
patch is applied and solves the problem I will happily close this bug!
CC
Hmm, it would be nice if that was the
On 13/11/11 17:06, Andreas Stempfhuber wrote:
> Hi Simon,
> Regarding bug #506734, I have concerns because it creates an unexpected
> shutdown behavior. It assumes that the shutdown order doesn't matter. But why
> is there a Required-Stop option defined by LSB and why does dnsmasq use it to
> d
On 10/11/12 15:10, intrigeri wrote:
tags 690075 + moreinfo
thanks
Hi Moritz,
Moritz Muehlenhoff wrote (09 Oct 2012 17:51:26 GMT) :
Please unblock package dnsmasq
It fixes CVE-2012-3411
unblock dnsmasq/2.63-4
The new upstream version includes quite a few changes that are
unrelated to the secu
On 15/08/12 09:17, Ritesh Raj Sarraf wrote:
> Package: dnsmasq
> Version: 2.62-3
> Severity: important
>
> Simon,
>
> Looks like, since your last fix of dnsmasq's integration with systemd,
> something has broken. I am not sure where is the problem (could be
> resolvconf too), but as far as I can
On 16/08/12 08:59, Ritesh Raj Sarraf wrote:
> On Wednesday 15 August 2012 02:16 PM, Simon Kelley wrote:
>> If your 192.168.2.1 is local nameserver only handling certain domains,
>> you can configure dnsmasq to use it as such with the
>>
>> server=/example.com/192.168.2.
On Sat, 18 Aug 2012 09:54:26 +0100, Neil Williams
wrote:
> Package: dnsmasq
> Version: 2.63-1
> Severity: serious
> Justification: Fails to install
>
> Upgrading dnsmasq to 2.63-1 fails:
>
> E: /var/cache/apt/archives/dnsmasq-base_2.63-1_amd64.deb: trying to
> overwrite '/etc/dbus-1/system.d/dns
On 15/02/12 14:30, Marc Deslauriers wrote:
Package: dhcpcd
Version: 1:3.2.3-9
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu precise ubuntu-patch
*** /tmp/tmpYPCJL7/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
* S
On 16/02/12 19:09, Florian Weimer wrote:
* Simon Kelley:
I plan to keep this very old dhcpcd version around for wheezy, to give
a one-release overlap with the current, but incompatible, dhcpcd5.
Uhm, what's the source package name? I assumed that ISC DHCP 3.x had
already been dropp
On 02/09/12 08:44, Michael Tokarev wrote:
Package: dnsmasq
Version: 2.55-2
Severity: serious
Tags: security
The initscript (and postinst script) of dnsmasq creates /var/run/dnsmasq
directory and chowns it to dnsmasq:nogroup. However, dnsmasq daemon writes
the pidfile (which apparently is the on
On 02/09/12 08:44, Michael Tokarev wrote:
Package: dnsmasq
Version: 2.55-2
Severity: serious
Tags: security
Ignore my previous question: currently educating myself about O_EXCL
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
On 05/09/12 16:57, Moritz Muehlenhoff wrote:
> On Wed, Aug 01, 2012 at 05:30:47PM +0100, Simon Kelley wrote:
>> On 31/07/12 09:35, Moritz Muehlenhoff wrote:
>>> Package: dnsmasq
>>> Severity: important
>>> Tags: security
>>>
>>> Hi,
>
On 31/07/12 09:35, Moritz Muehlenhoff wrote:
Package: dnsmasq
Severity: important
Tags: security
Hi,
I know you're aware of this bug since you commented it already, but I'm
filing a Debian bug to keep track of this for Wheezy:
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-3411
Cheers,
On 21/05/13 12:43, Thomas Hood wrote:
Package: dnsmasq
Version: 2.66-2
Severity: wishlist
OpenDNS's DNSCrypt client for Linux (called 'dnscrypt-proxy')[0] is not yet
packaged for Debian but some people are already installing it from source
and it is of course possible that it will eventually be
Thomas Hood wrote:
> I now remember that we aren't supposed to assume that invoke-rc.d
> is present. Here's a new version of the script. // Thomas
>
> #!/bin/sh
> # Resolvconf packaging event hook script for the dnsmasq package
>
> restart_dnsmasq() {
> if which invoke-rc.d >/dev/null 2>&1
Monty Taylor wrote:
> Package: dnsmasq
> Version: 2.57-1
>
> Hi! We'd love to get dhcp_release and dhcp_lease_time added to the
> dnsmasq package so that we can use them in some supporting scripts
> around OpenStack.
Seems reasonable.
> I've attached a debdiff that does this. Is there
> anything
On 05/10/11 01:47, Brielle Bruns wrote:
> dnsmasq works properly in 2.57-1 on the same system,
> so this is probably either an upstream bug, or one introduced in a debian
> specific patch.
>
Can I ask you to recheck this? I suspect that the change which
precipitated the problem is actually a kern
On 05/10/11 20:44, Brielle Bruns wrote:
> Hi Simon!
>
> Thanks for contacting me.
>
> I'm using 2.57-1 on linux-image-3.1.0-rc4-amd64 at the moment.
>
> Do you want me to try this on linux-image-3.1.0-rc7-amd64?
>
> I have confirmed it does suffer from the same issues on
> linux-image-3.0.0-1-
This is fixed in 2.58-2, just uploaded, but the changelog closes a
different bug by mistake, I'm not having a good day.
Closing this bug manually.
Cheers,
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
Paul Millar wrote:
>
> If possible, could you reassign this ticket?
>
>
Reassigned to virtualbox, after a small false start where it got
accidentally closed.
Cheers,
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
Michael Stapelberg wrote:
> Hi Sjoerd,
>
>> When using systemd starting dnsmasq just hangs and times out.. Also the sysv
>> init script seems to have a reasonable amount of functionality that the
>> systemd
>> one does not have, so i'm not sure if switching now is the right thing.
> Which version
On 03/09/11 10:16, Jörg Sommer wrote:
> Hello Simon,
>
> I can't see in which way #635383 is related to changes in the resolvconf
> script. Is this bug report number correct? Or should it have been
> #627789?
>
> dnsmasq (2.58-2) unstable; urgency=low
>
>* Fix resolvconf script. (closes: #63
Michael Stapelberg wrote:
> So, I reflected about this, and we cannot use User=dnsmasq in the service file
> because dnsmasq needs to bind to port 53 as root.
Dnsmasq needs to be started as root, but it needs the command-line
argument --user=dnsmasq, to tell it to change to user dnsmasq _after
bi
Michael Stapelberg wrote:
> Hi Simon,
>
> Thanks for your explanations :). My answers follow, a new service file is
> attached.
>
> Excerpts from Simon Kelley's message of 2011-09-05 14:39:42 +0200:
>> Dnsmasq needs to be started as root, but it needs the command-line
>> argument --user=dnsmasq,
> Yep, I did that already (did you see the updated service file?).
Not when I wrote my last message, but I have now. It's much better,
thank you.
>
>>> 1) Make dnsmasq capable of getting the DNS domain name on its own. It’s not
>>> too
>>>much code, I’ve ripped out the appropriate parts of
Paul Millar wrote:
> As a shot-in-the-dark, I've checked for dnsmasq reply packets on the other
> interfaces (lo, eth0, br1). There's no sign of the reply packets.
>
> This used to work, so it looks like a bug introduced with a recent upgrade of
> the dnsmasq package.
>
There have been no rece
I'm not aware of this bug having been manifest anywhere except here and
I can't progress it without further information from the submitter.
Since the package is working fine for almost everyone, I'm downgrading
this to "normal". It's certainly not release critical.
Cheers,
Simon.
--
To UNSUB
On 17/09/13 11:32, YunQiang Su wrote:
Package: dnsmasq
Version: 2.66-4
X-Debbugs-CC: wzss...@gmail.com
This package has one or more -L/usr/lib in its build system,
which will make it ftbfs if there is libraries under /usr/lib,
while is not the default architecture, mips* for example.
On mips* s
On 05/11/11 17:21, Andreas Stempfhuber wrote:
Package: dnsmasq
Version: 2.55-2
Severity: normal
Hi,
I assume dnsmasq should be stopped at runlevel 0, 1 and 6 and not just
at runlevel 1 as currently.
Dnsmasq is currently listed as a process which fails to stop at
/etc/init.d/sendsigs each time
On 07/11/11 20:22, Andreas Stempfhuber wrote:
>> I wonder why sendsigs is failing to stop dnsmasq in a timely manner?
>
> Because dnsmasq requires syslog which is not available during sendsigs.
>
> The LSB header of the dnsmasq initscript contains "Required-Stop: $network
> $remote_fs $syslog"
On 07/11/11 20:22, Andreas Stempfhuber wrote:
>
> I was able to replicate the issue by manually stopping the syslog daemon and
> then manually stopping dnsmasq. In this sequence dnsmasq takes a long time
> (longer than 10 seconds) to stop.
>
I can't replicate this behaviour: I tried datagram an
On 07/11/11 22:30, Andreas Stempfhuber wrote:
Maybe it's related to a change between dnsmasq 2.55 in Squeeze and 2.59 in
SID?
Indeed: from the 2.56 changelog:
Ensure that dnsmasq terminates cleanly when using
--syslog-async even if it cannot make a connection to the
On 22/03/12 10:32, Stéphane Glondu wrote:
Package: dnsmasq
Version: 2.60-1
Severity: grave
Hello,
I cannot start a (squeeze) netboot install (on an eee pc 701) using
dnsmasq on the server. In the past, I have already installed
(successfuly) computers this way. Today, dnsmasq keeps segfaulting
On 18/05/12 10:09, Jörg Herzinger wrote:
> Package: dnsmasq Version: 2.55-2 Severity: important
>
> Hi,
>
> The default location for lease files (/var/lib/misc), which is also
> the home folder of the user dnsmasq, is not writeable for the user
> itself which is why the daemon won't function wit
On 07/06/12 15:41, Ritesh Raj Sarraf wrote:
> reopen 675854
> retitle 675854 "systemd breaks dnsmasq"
> reassign 675854 systemd
> thanks
>
>
> Just verified it back with sysvinit. If the expectation is that every
> package maintainer has to adapt systemd, then this bug can be
> closed/reassigned.
On 08/06/12 14:47, Ritesh Raj Sarraf wrote:
> On Friday 08 June 2012 01:05 PM, Tollef Fog Heen wrote:
>> ]] Ritesh Raj Sarraf
>>
>>> Do you want this bug re-assigned to dnsmasq? I think it fits in on
>>> systemd. systemd should be a drop-in replacement. But then, systemd
>>> doesn't claim to be a
them.
* Hostname: phys-dns51
* Version: dnsmasq-2.55
* Authors: Simon Kelley
* Copyright: Copyright (c) 2000-2010 Simon Kelley
Most likely, either your gateway is blocking connections to TCP port 53,
or your ISP/upstream nameservers won't accept TCP connections.
Try some
On 31/03/12 12:55, FLD wrote:
> Package: dnsmasq
> Version: 2.55-2
> Severity: normal
>
> Did the berkeley's ICSI Netalyzr test on a Win XP (Java 7) machine
> behind my Debian gateway running Squeeze, got following results:
>
> Direct probing of DNS resolvers (?) â
> Your system is configured
On 11/09/15 15:54, Guido Günther wrote:
> On Fri, Sep 11, 2015 at 03:57:19PM +0200, Guido Günther wrote:
>> Package: dnsmasq
>> Version: 2.75-1
>> Severity: normal
>>
>> Hi,
>> I just tried your suggestion with --hostdir=/tmp/test. While I see these
>> log messages nicely:
>>
>> Sep 11 15:53:49 foo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> What does not seem to work is that addresses removed from the file
> are removed from the cache immediately. So if I remove the entry
> for sid it will still be served.
>
That's documented behaviour. New or changed files are read, so extra
inf
On 14/08/14 14:11, Michael Biebl wrote:
> Am 14.08.2014 14:57, schrieb Michael Biebl:
>> Am 14.08.2014 14:30, schrieb Paul Wise:
>>> On Thu, 2014-08-14 at 14:15 +0200, Michael Biebl wrote:
>>>
fwiw, we are using "User:
pkg-systemd-maintain...@lists.alioth.debian.org" since a while now.
>>
The Debian package provides a directory, /etc/dnsmasq.d for config file
fragments. This is automagically enabled with a command-line argument
provided by the init-system start script, without the need to include is
in /etc/dnsmasq.conf
This is documented in para 2 of /usr/shar/doc/dnsmasq/README.D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following code in /etc/init.d/dnsmasq is responsible for this
behaviour.
# /etc/dnsmasq.d/README is a non-conffile installed by the dnsmasq
package.
# Should the dnsmasq package be removed, the following test ensures that
# the daemon is no lon
On 04/04/16 17:13, Thilo Six wrote:
> Simon Kelley schrieb/wrote:
>>
>> The following code in /etc/init.d/dnsmasq is responsible for this
>> behaviour.
>>
>> # /etc/dnsmasq.d/README is a non-conffile installed by the dnsmasq
>> package.
>> # Should
On 09/07/14 18:03, Vladimir Kudrya wrote:
> Package: dnsmasq
> Version: 2.71-1
> Severity: important
>
> Dear Maintainer, when reloading dnsmasq with changed configuration, daemon
> stops.
> Config is valid, daemon can be started normally after that.
>
> Log of the daemon after systemctl reload
On 17/07/14 06:40, Vladimir K wrote:
> Hm... usually changing additional hosts file was enough to trigger this bug.
> But now I can not reproduce it either.
> I've rechecked it on both my home servers and now the bug is gone. Tried
> adding upstream server in config file and host in addn-hosts fi
On 10/07/14 18:11, Benjamin Cama wrote:
> Package: dnsmasq
> Version: 2.62-3+deb7u1
> Severity: wishlist
>
> Hi,
>
> While configuring dnsmasq today, I stumbled upon a very annoying
> behavior: dnsmasq doesn't ignore files not ending in ".conf" in its
> /etc/dnsmasq.d/ configuration directory. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/05/15 11:26, Santiago Ruano Rincón wrote:
> Hi Simon,
>
> On Fri, May 15, 2015 at 04:24:30PM +0200, Santiago Ruano Rincón
> wrote: ...
>> I'm attaching the clean patch to fix CVE-2015-3294.
>
> These other CVEs are related each other and st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Simon.
Many thanks for the offer of help, not having to wade into the
intricacies of systemd is a big win for me.
The current arrangements are "something which was made to work without
big code changes" so I'm not wedded to using the dbus method at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/02/15 09:17, Simon McVittie wrote:
> On Mon, 09 Feb 2015 at 16:33:31 +, Simon McVittie wrote:
>> If I was the maintainer, I'd go for option 2, Type=forking, which
>> makes the systemd unit work even more like the init script does
>> now -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/02/15 21:56, Simon McVittie wrote:
> On 11/02/15 21:26, Simon Kelley wrote:
>> Thanks, that looks good, but I think that probably the default
>> --enable-dbus should go as well. It's only there for the previous
>&g
Salvatore.
The problem occurs if the dnsmasq binary is compiled against libc
headers which #define SO_REUSEPORT and then run on a kernel which
doesn't support that option. I guess the security builds have picked up
SO_REUSEPORT from a libc backport.
The fix applied at the time was:
http://thekel
On 05/05/15 15:15, Salvatore Bonaccorso wrote:
> Control: tags 783459 + pending
>
> Hi Simon,
>
> I've prepared an NMU for dnsmasq (versioned as 2.72-3.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
> Salvatore
>
That looks fine, than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It's a fairly tall order to reproduce this, but I have one idea. What
is the MAC address associated with lxcbr0? Is it possible that that is
changing as a result of the suspend/resume cycle?
Cheers,
Simon.
On 14/09/15 18:17, Ritesh Raj Sarraf w
s
from your dnsmasq configuration.
Cheers,
Simon.
On 27/09/15 10:58, Ritesh Raj Sarraf wrote:
> On Sat, 2015-09-26 at 22:08 +0100, Simon Kelley wrote:
>> It's a fairly tall order to reproduce this, but I have one idea.
>> What is the MAC address associated with lxcbr0? Is it possible
On 05/09/15 15:42, Guido Günther wrote:
> Package: dnsmasq
> Version: 2.72-3+deb8u1
> Severity: wishlist
>
> Hi,
> it would be awesome if dnsmasq could use inotify in case of
>
> --addn-hosts=/a/directory/
>
> this would allow one to dump new files in there (and modify existing
> ones) without r
On 05/09/15 15:42, Guido Günther wrote:
> Package: dnsmasq
> Version: 2.72-3+deb8u1
> Severity: wishlist
>
> Hi,
> it would be awesome if dnsmasq could use inotify in case of
>
> --addn-hosts=/a/directory/
>
> this would allow one to dump new files in there (and modify existing
> ones) without r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/09/15 20:35, Alexander Kurtz wrote:
> Package: dnsmasq Version: 2.75-1
Thanks, I just pushed the fix upstream, it will be in the next release.
Cheers,
Simon.
>
> Hi,
>
> dnsmasq(8) says ...
>
> -R, --no-resolv Don't read /etc/resolv.co
I suspect that the proximate cause of this is lack of support for the
ECDSA ciphersuite in 2.72. As you pointed out, this works OK in 2.75.
2.72 was a very early release for DNSSEC in dnsmasq, and there have been
many changes and fixes between 2.72 and 2.75. Backporting so many
changes is not real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is indeed a dnsmasq bug, introduced in 2.73. My fault, sorry.
Insufficient scrutiny of a "clean-up" patch. I just committed a fix to
the git repo.
Cheers,
Simon.
On 28/06/15 17:27, Michael Biebl wrote:
> Hi Paul,
>
> thanks for your bug rep
Thanks for this. I just checked, and the bug is fixed in later versions
of dnsmasq. (I didn't determine exactly which one, but I expect it was
around 2.67, when DNSSEC validation was added, and the whole code
handling DNSSEC flag bits was re-written.)
Therefore in the next release of Debian, this
On 05/08/14 17:55, Benjamin Cama wrote:
> Hi Simon,
>
> Le samedi 19 juillet 2014 à 22:01 +0100, Simon Kelley a écrit :
>> It would be fairly simple to support this upstream, and with hindsight
>> it's a better way to do things. My main concern is that to make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/12/14 22:25, chris21.r...@free.fr wrote:
>
> Package: dnsmasq Version: 2.72-2 Severity: important
>
> Dear Maintainer,
>
> I configured dnsmasq on debian jessie. When starting dnsmasq, I
> receive: Erreur DBus : Connection ":1.57" is not a
1 - 100 of 257 matches
Mail list logo
