Frederic MASSOT wrote:
Package: dnsmasq
Version: 2.32-2
Followup-For: Bug #364800


Hi,

I have the same problem after an upgrade from 2.22-2 to 2.32.2.

Below the logs, I recorded the input/output with iptables:

kernel: IN=br0 OUT= PHYSIN=eth1 PHYSOUT=tap0
        MAC=ff:ff:ff:ff:ff:ff:00:03:93:83:72:78:08:00
        SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00
        TTL=255 ID=19201 PROTO=UDP SPT=68 DPT=67 LEN=308
dnsmasq[2336]: DHCPDISCOVER(br0) 00:03:93:83:72:78
dnsmasq[2336]: DHCPOFFER(br0) 192.168.2.3 00:03:93:83:72:78
kernel: IN= OUT=br0 PHYSOUT=eth1
        SRC=192.168.2.254 DST=192.168.2.3 LEN=338 TOS=0x00 PREC=0x00
        TTL=64 ID=0 DF PROTO=UDP SPT=67 DPT=68 LEN=318
[etc]

There is neither DHCPREQUEST nor DHCPPACK.


The output of "lsof -c dnsmasq" :

# lsof -c dnsmasq
COMMAND  PID    USER   FD   TYPE     DEVICE    SIZE    NODE NAME
dnsmasq 2336 dnsmasq  cwd    DIR        3,1    4096       2 /
dnsmasq 2336 dnsmasq  rtd    DIR        3,1    4096       2 /
dnsmasq 2336 dnsmasq  txt    REG        3,1  106428 2592770 /usr/sbin/dnsmasq
dnsmasq 2336 dnsmasq  mem    REG        0,0               0 [heap] (stat: No 
such file or directory)
dnsmasq 2336 dnsmasq  mem    REG        3,1   42472 3686528 
/lib/tls/i686/cmov/libnss_files-2.3.6.so
dnsmasq 2336 dnsmasq  mem    REG        3,1   38420 3686627 
/lib/tls/i686/cmov/libnss_nis-2.3.6.so
dnsmasq 2336 dnsmasq  mem    REG        3,1   30428 3686464 
/lib/tls/i686/cmov/libnss_compat-2.3.6.so
dnsmasq 2336 dnsmasq  mem    REG        3,1    9436 2596238 
/usr/lib/gconv/ISO8859-1.so
dnsmasq 2336 dnsmasq  mem    REG        3,1    9436 2600723 
/usr/lib/gconv/ISO8859-15.so
dnsmasq 2336 dnsmasq  mem    REG        3,1 1678848 2605096 
/usr/lib/locale/locale-archive
dnsmasq 2336 dnsmasq  mem    REG        3,1   80888 3686460 
/lib/tls/i686/cmov/libnsl-2.3.6.so
dnsmasq 2336 dnsmasq  mem    REG        3,1 1266832 3686448 
/lib/tls/i686/cmov/libc-2.3.6.so
dnsmasq 2336 dnsmasq  mem    REG        3,1  191324 2592691 
/usr/lib/libdbus-1.so.2.0.0
dnsmasq 2336 dnsmasq  mem    REG        3,1   17888 2592763 
/usr/share/locale/fr/LC_MESSAGES/dnsmasq.mo
dnsmasq 2336 dnsmasq  mem    REG        3,1   92260 3686807 /lib/ld-2.3.6.so
dnsmasq 2336 dnsmasq    0u   CHR        1,3             584 /dev/null
dnsmasq 2336 dnsmasq    1u   CHR        1,3             584 /dev/null
dnsmasq 2336 dnsmasq    2u   CHR        1,3             584 /dev/null
dnsmasq 2336 dnsmasq    3u  sock        0,4            5106 can't identify 
protocol
dnsmasq 2336 dnsmasq    4u  IPv4       5111             UDP *:domain
dnsmasq 2336 dnsmasq    5u  IPv4       5112             TCP *:domain (LISTEN)
dnsmasq 2336 dnsmasq    6u  IPv4       5113             UDP *:bootps
dnsmasq 2336 dnsmasq    7u   REG        3,1       0  770329 
/var/lib/misc/dnsmasq.leases
dnsmasq 2336 dnsmasq    8r  FIFO        0,5            5114 pipe
dnsmasq 2336 dnsmasq    9w  FIFO        0,5            5114 pipe
dnsmasq 2336 dnsmasq   10u  unix 0xc7d72960            5120 socket
dnsmasq 2336 dnsmasq   11u  IPv4       5121             UDP *:2051


The output of "/proc/<pid>/status" :

# cat  /proc/2336/status
Name:   dnsmasq
State:  S (sleeping)
SleepAVG:       98%
Tgid:   2336
Pid:    2336
PPid:   1
TracerPid:      0
Uid:    100     100     100     100
Gid:    30      30      30      30
FDSize: 32
Groups:
VmPeak:     3912 kB
VmSize:     3908 kB
VmLck:         0 kB
VmHWM:       860 kB
VmRSS:       860 kB
VmData:      304 kB
VmStk:        84 kB
VmExe:       104 kB
VmLib:      1660 kB
VmPTE:        12 kB
Threads:        1
SigQ:   0/4294967295
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 0000000000016201
CapInh: 0000000000000000
CapPrm: 0000000000003000
CapEff: 0000000000003000


The output of tcpdump :

# tcpdump -i br0 'portrange 67-68'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB (Ethernet), capture size 96 bytes
14:43:30.821278 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:03:93:83:72:78 (oui
Unknown), length: 300
14:43:30.825208 IP dagon.juliana-multimedia.com.bootps > 192.168.2.3.bootpc: 
BOOTP/DHCP, Reply, length: 310
14:43:36.074691 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:15:f2:ee:10:57 (oui
Unknown), length: 300
14:43:36.077090 IP dagon.juliana-multimedia.com.bootps > 192.168.2.92.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:43:39.382560 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:03:93:83:72:78 (oui
Unknown), length: 300
14:43:42.074028 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:15:f2:ee:10:57 (oui
Unknown), length: 300
14:43:42.153023 IP dagon.juliana-multimedia.com.bootps > 192.168.2.3.bootpc: 
BOOTP/DHCP, Reply, length: 310
14:43:42.153873 IP dagon.juliana-multimedia.com.bootps > 192.168.2.92.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:43:48.242643 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:03:93:83:72:78 (oui
Unknown), length: 300
14:43:48.244040 IP dagon.juliana-multimedia.com.bootps > 192.168.2.3.bootpc: 
BOOTP/DHCP, Reply, length: 310
14:43:51.072159 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:15:f2:ee:10:57 (oui
Unknown), length: 300
14:43:54.077371 IP dagon.juliana-multimedia.com.bootps > 192.168.2.92.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:43:56.748057 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:03:93:83:72:78 (oui
Unknown), length: 300
14:43:56.749244 IP dagon.juliana-multimedia.com.bootps > 192.168.2.3.bootpc: 
BOOTP/DHCP, Reply, length: 310
14:44:05.303318 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:03:93:83:72:78 (oui
Unknown), length: 300
14:44:05.304823 IP dagon.juliana-multimedia.com.bootps > 192.168.2.3.bootpc: 
BOOTP/DHCP, Reply, length: 310
'14:44:10.069237 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 00:15:f2:ee:10:57 (oui
Unknown), length: 300
14:44:10.070429 IP dagon.juliana-multimedia.com.bootps > 192.168.2.92.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:44:27.066817 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:15:f2:ee:10:57 (oui
Unknown), length: 300
14:44:30.069782 IP dagon.juliana-multimedia.com.bootps > 192.168.2.92.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:44:40.806884 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:50:da:d8:14:77 (oui
Unknown), length: 300
14:44:43.077745 IP dagon.juliana-multimedia.com.bootps > 192.168.2.13.bootpc: 
BOOTP/DHCP, Reply, length: 316
14:44:45.806666 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request 
from 00:50:da:d8:14:77 (oui
Unknown), length: 300
14:44:45.808216 IP dagon.juliana-multimedia.com.bootps > 192.168.2.13.bootpc: 
BOOTP/DHCP, Reply, length: 316



Regards.




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages dnsmasq depends on:
ii  adduser                       3.87       Add and remove users and groups
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  libdbus-1-2                   0.62-4     simple interprocess messaging syst
ii  netbase                       4.25       Basic TCP/IP networking system

dnsmasq recommends no packages.

-- no debconf information

As far as I can see from this information, dnsmasq is behaving fine: it is certainly replying to the DHPCDISCOVER queries.

The problem may be iptables rules: dnsmasq-2.32 DHCPOFFER replies are send through iptables, but 2.22 DHCPOFFER replies bypass iptables.
Could there be something in your iptables which blocks those replies?


Cheers,

Simon.


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

Reply via email to