-address.
Simon.
Martin-Éric
On Wed, Feb 16, 2022 at 10:11 PM Simon Kelley wrote:
67 is DHCP and always binds the wildcard: that's necessary to make DHCP
work. It checks the arrival address of packets and discards those which
are not valid.
interface= is documented to listen on the addresses
the above config.
Cheers!
Martin-Éric
On Wed, Feb 16, 2022 at 9:36 PM Simon Kelley wrote:
I'm not clear what you think is happening, and what you want to happen.
bind-interfaces works for tftp; there will be a socket for each address
on each valid interface bound to that address and port 69
I'm not clear what you think is happening, and what you want to happen.
bind-interfaces works for tftp; there will be a socket for each address
on each valid interface bound to that address and port 69
no-dhcp-interface does indeed suppress tftp on that interface too, and
is documented so to
That's not good.
I need to reproduce this here, and I can't as yet.
Could you send a copy of your dnsmasq configuration file and maybe a
copy of /use/sbin/dnsmasq
Simon.
On 03/02/2021 09:32, Marek Jambrich wrote:
> Package: dnsmasq
> Version: 2.80-1+deb10u1
> Severity: important
>
> Dear
On 19/04/2020 09:55, Laurent Bigonville wrote:
> On Sat, 18 Apr 2020 18:48:37 + Debian FTP Masters
> wrote:
> [...]
>> dnsmasq (2.81-2) unstable; urgency=low
>> .
>> * Fix FTBFS on kFreeBSD. (closes: #958100)
>
> Thanks for the fast upload, the package is now building fine.
>
> Why didn't
On 17/03/2020 01:21, Lorenzo Puliti wrote:
> Package: src:dnsmasq
> Followup-For: Bug #929884
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.5.9-van
..40ad6c6 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -4,7 +4,7 @@ Priority: optional
> Build-depends: gettext, libnetfilter-conntrack-dev [linux-any],
> libidn11-dev, libdbus-1-dev (>=0.61), libgmp-dev,
> nettle-dev (>=2.4-3), libbsd
Can I query the version number for this? I think that this behaviour was
fixed in the 2.80 upstream release and therefore the Debian 2.80-1 package.
Simon.
On 04/03/2019 23:02, Chris Carr wrote:
> * What outcome did you expect instead?
>
> I expected Windows to receive the correct MTU size of 1280 as set in
> /proc/sys/net/ipv6/conf/he-ipv6/mtu
>
> interface=int0
> dhcp-range=tag:int0,::1,constructor:int0,ra-names,24h
There seem to be two
C validation) then in this particular
case (answer comes from --address in the command line or config file)
the ad bit is set in the answer, even though the answer is NOT DNSSEC
validated.
This bug also exists in 2.79, which made me think that it was not the
source of the problem. As you found, th
On 21/10/2018 00:05, Michael Biebl wrote:
> After rebuilding the LXC chroot, I was able to reproduce the issue after
> all.
>
> Runnig a git bisect shows the following as the first faulty commit
>
>
> commit 1682d15a744880b0398af75eadf68fe66128af78
> Author: Simon Kelley
On 29/01/18 18:28, Drexl Johannes wrote:
> Package: dnsmasq
> Version: 2.76-5+deb9u1
> Severity: normal
>
> Dear Maintainer,
>
> when using tags for different address ranges (e. g. privilege separation) for
> IPv4, option 3 (router) is not forwarded to the client. In its stead the
> interface
On 04/02/18 20:26, Sven Hartge wrote:
> Does dnsmasq need a PIDfile when running under systemd? Can't it just
> not double fork, stay in the foreground using a Type=simple systemd unit?
>
> That way the whole problem could be avoided all together.
>
Sending signals to the dnsmasq process cause
With my dnsmasq maintainer hat on, the current arrangement looks like this.
1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
root, so is root:root
3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
OK, thanks for that useful information. I see the problem. Fixed upstream at
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=a6cee69af4c77c9795f57a459ea88d37227b3271
Cheers,
Simon.
signature.asc
Description: OpenPGP digital signature
On 05/12/17 15:00, Gaudenz Steinlin wrote:
>
> Hi
>
> Sorry for the incomplete bug report. I wanted to resume a reported I did
> not finish with reportbug, but it decided to send the backup copy as is
> instead of letting me edit it before sending.
>
> Looking at the code the wrong error code
On 04/06/17 16:36, Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> On Sun, Jun 04, 2017 at 09:58:44AM +0100, ? wrote:
>> The dnsmasq package in testing has a serious problem when dns-root-data is
>> installed, due to changes in the format of the dns-root-data files.
>> The effect is to
That change is the fix, not the cause. It's not on 2.76, but has made it
to 2.77. I've requested that the release-managers push 2.77-1 into Stretch.
Cheers,
Simon.
On 04/06/17 13:08, Colin Wetherbee wrote:
> This regression is caused by the following change upstream in dnsmasq:
>
>
On 05/08/16 16:59, Clément Hermann wrote:
> Hi,
>
> Just want to add my bit on this one.
>
> The documentation states that when "interface" option is used, the
> daemon binds on * but reject queries that come to interfaces not listed.
>
> This does not work, so eitheir the documentation is
Hi,
Thanks for this. I need to upload 2.76-2, which has a fix for a
different bug, #831372. I've patched this with the 2.76-1.1 and 2.76-1.2
NMUs, so they're included. However by the time 2.76-1.2 gets to the end
of the delay, 2.76-2 will be in place. That's not going to confuse
things, is it?
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
-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
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
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
>> that that is
-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
-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
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
-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
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
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
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
-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 report.
-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 still
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:
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, thanks for
-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
use with systemd's dbus method
-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
There's a potential problem with this: dnsmasq has an option to invoke
child processes when the DHCP lease database changes, using the
- --dhcp-script option. By making this change, those processes are going
to be invoked with read-only /usr. That's
-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 allowed
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 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.
Ah, there are
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
change now introduces a behavior
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 file.
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 had copied
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 action:
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 files the
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 11/05/14 15:11, Andreas Metzler wrote:
On 2014-05-11 Michael Biebl bi...@debian.org wrote:
Am 11.05.2014 10:13, schrieb Andreas Metzler:
On 2013-09-25 Julian Andres Klode j...@debian.org wrote:
[...]
dnsmasq currently does not enable its systemd unit in postinst. It should
probably use
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
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
Great, thanks for getting back to me. I'll close the bug when 2.68 gets
done.
Cheers,
Simon.
On 03/12/13 11:06, Alex Corcoles wrote:
Hi,
I've been running:
http://www.thekelleys.org.uk/dnsmasq/release-candidates/dnsmasq-2.68rc4.tar.gz
for a week and I've had no failures whatsoever, so I
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
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*
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
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
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
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,
I know you're aware of this bug since you commented it already, but I'm
filing
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 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.
On Sat, 18 Aug 2012 09:54:26 +0100, Neil Williams codeh...@debian.org
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
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.1
style configuration on /etc
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 remember
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 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 drop-in
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 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 without
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 to use 1
.
* 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 something like
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 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:
*
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 dropped
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
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 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 to make
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 and
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 kernel
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-amd64 and
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
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
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, to tell
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: #635383)
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 of systemd
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
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? Contact
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
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 else
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 recent
On 17/06/11 07:34, Roy Marples wrote:
On Fri, 2011-06-17 at 00:02 +0200, Juliusz Chroboczek wrote:
The point I'm making is that replacing dhcpd with dhcpcd5 broke
a working system by replacing resolvconf with openresolv. I'd like to
clarify whose bug that is:
...
No, it worked out of the
Robert Edmonds wrote:
Simon Kelley wrote:
Some implementations of gethostbyname, given the name com or
mycomputer will attempt to look it up in the DNS with just such a
query, thus wasting upstream bandwidth and leaking internal network
information.
hm, so? a heuristic based solely
Robert Edmonds wrote:
Robert Edmonds wrote:
so unbound forwarding to 4.2.2.1 works, but unbound forwarding to
dnsmasq which forwards to 4.2.2.1 does not work. so dnsmasq is not
fully transparent when forwarding between a validating forwarder and a
validating recursive nameserver.
ugh, i
Robert Edmonds wrote:
Simon Kelley wrote:
Robert Edmonds wrote:
Robert Edmonds wrote:
so unbound forwarding to 4.2.2.1 works, but unbound forwarding to
dnsmasq which forwards to 4.2.2.1 does not work. so dnsmasq is not
fully transparent when forwarding between a validating forwarder
Robert Edmonds wrote:
ok, now that i look in the dnsmasq debian changelog i see this option
started defaulting to disabled in 2006. still...
Probably best not to look at filterwin2k then. Not the finest hour.
Simon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
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 21 ; then
Thomas Hood wrote:
Sorry to bother you about this again, but it occurs to me now
that this would be even better:
#!/bin/sh
# Resolvconf packaging event hook script for the dnsmasq package
case $1 in
install) invoke-rc.d dnsmasq restart ;;
esac
That is, instead of restarting
Thomas Hood wrote:
should /etc/resolvconf/packaging-event.d/dnsmasq be a conffile?
Good question!
I am a bit embarrassed to have to admit that I didn't really
consider this issue. I just assumed that the hook scripts
should be conffiles (as the update scripts are) and located
in /etc/.
Vincent van Leeuwen wrote:
Package: dnsmasq
Version: 2.57-1
Severity: important
Lines like the following in /etc/dnsmasq.conf cause dnsmasq 2.57 to fail to
restart:
dhcp-host=00:11:d8:a8:58:21,10.32.1.3,tag:lan,tijger
^^^
There's an error in
Thomas Hood wrote:
Package: dnsmasq
Severity: wishlist
Please add the hook script /etc/resolvconf/packaging-event.d/dnsmasq.
The purpose this script is to cause dnsmasq to take notice of
the installation or removal of the resolvconf package. If resolvconf
has been installed, for
Thomas Hood wrote:
P.S.
The patched script updates the mtime by doing:
echo $TMP_FILE
This is less than idea, since it adds a useless CR
to the end of the file. I tried:
: $TMP_FILE
which doesn't add anything to the file, but this failed
to change the mtime.
1 - 100 of 256 matches
Mail list logo
