Hi Ian,

On Wed, May 06, 2015 at 08:48:53AM +0100, Ian Campbell wrote:
> Package: dnsmasq
> Followup-For: Bug #783459
>
> Dear Maintainer,
>
> After upgrading to 2.62-3+deb7u2 on Wheezy/armel dnsmasq now fails to start 
> with:
>
>     root@yog-sothoth:~# dpkg -i dnsmasq*2.62-3+deb7u2*.deb
>     (Reading database ... 25941 files and directories currently installed.)
>     Preparing to replace dnsmasq 2.62-3+deb7u1 (using 
> dnsmasq_2.62-3+deb7u2_all.deb) ...
>     Unpacking replacement dnsmasq ...
>     Preparing to replace dnsmasq-base 2.62-3+deb7u1 (using 
> dnsmasq-base_2.62-3+deb7u2_armel.deb) ...
>     Unpacking replacement dnsmasq-base ...
>     Setting up dnsmasq-base (2.62-3+deb7u2) ...
>     Processing triggers for man-db ...
>     Setting up dnsmasq (2.62-3+deb7u2) ...
>     insserv: warning: current stop runlevel(s) (1) of script `dnsmasq' 
> overrides LSB defaults (0 1 6).
>     [....] Restarting DNS forwarder and DHCP server: dnsmasq
>     dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not 
> available
>      failed!
>     invoke-rc.d: initscript dnsmasq, action "restart" failed.
>     root@yog-sothoth:~#
>
> Downgrading back to 2.62-3+deb7u1 makes things work again.
>
> Searching around there are various (mostly a few year old) reports of this
> which are related to the use of the bind-interfaces option which I had enabled
> in /etc/dnsmasq.conf since dnsmasq runs on a router with multiple interfaces.
>
> For now I've disabled bind-interfaces, although I'm not entirely happy with
> that since it exposes dnsmasq to traffic from the outside Internet, even if it
> is to be discarded.

I just tried to replicate that configuration and set up a wheezy VM up with two
interfaces eth0, eth1, and set the following modifications:

interface=eth1
bind-interfaces
domain=example.com
dhcp-range=192.168.1.128,192.168.1.255,12h

But so far I was not able to reproduce the problem, but only from a quit
re-check (and in particular not the same arch as well).

----cut---------cut---------cut---------cut---------cut---------cut-----
root@dnsmasq-test:~# dpkg-query -f '${Package} ${Version}\n' -W dnsmasq 
dnsmasq-base
dnsmasq 2.62-3+deb7u1
dnsmasq-base 2.62-3+deb7u1
root@dnsmasq-test:~# cat /etc/dnsmasq.d/regression.conf
interface=eth1
bind-interfaces
domain=example.com
dhcp-range=192.168.1.128,192.168.1.255,12h
root@dnsmasq-test:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT qlen 1000
    link/ether 52:54:00:95:ed:78 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT qlen 1000
    link/ether 52:54:00:50:46:5a brd ff:ff:ff:ff:ff:ff
root@dnsmasq-test:~# apt-get install dnsmasq dnsmasq-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  resolvconf
The following packages will be upgraded:
  dnsmasq dnsmasq-base
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 387 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://security.debian.org/ wheezy/updates/main dnsmasq-base amd64 
2.62-3+deb7u2 [370 kB]
Get:2 http://security.debian.org/ wheezy/updates/main dnsmasq all 2.62-3+deb7u2 
[16.3 kB]
Fetched 387 kB in 0s (1,789 kB/s)
(Reading database ... 18634 files and directories currently installed.)
Preparing to replace dnsmasq-base 2.62-3+deb7u1 (using 
.../dnsmasq-base_2.62-3+deb7u2_amd64.deb) ...
Unpacking replacement dnsmasq-base ...
Preparing to replace dnsmasq 2.62-3+deb7u1 (using 
.../dnsmasq_2.62-3+deb7u2_all.deb) ...
Unpacking replacement dnsmasq ...
Processing triggers for man-db ...
Setting up dnsmasq-base (2.62-3+deb7u2) ...
Setting up dnsmasq (2.62-3+deb7u2) ...
Restarting DNS forwarder and DHCP server: dnsmasq.
root@dnsmasq-test:~#
----cut---------cut---------cut---------cut---------cut---------cut-----

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to