Bug#408543: marked as done (dhcp3-relay: Does not catch any DHCP packets in my setup)

Debian Bug Tracking System Sun, 08 Jan 2017 22:04:07 -0800

Your message dated Mon, 9 Jan 2017 00:59:32 -0500
with message-id 
<CANTw=mnhdnuhe7++adfckj1rz7t+z2gyu3_jcwanmzayyt8...@mail.gmail.com>
and subject line 
has caused the Debian Bug report #408543,
regarding dhcp3-relay: Does not catch any DHCP packets in my setup
to be marked as done.


This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
408543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Package: dhcp3-relay
Version: 3.0.4-12
Severity: important

DHCP broadcast packets received from network interfaces are not seen by
dhcrelay3, the just traverse all PREROUTING and INPUT hooks (I can trace them
with netfilter rules) and are simply discarded by udp_rcv(), I guess.
Sarge version (3.0.1-2) works as expected: packets do not enter the IP layer
but are forwarded correctly to the DHCP server by dhcrelay3.

My network interfaces:
e49:~# ip link
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,10000> mtu 1500 qdisc htb master bond0 q$
    link/ether 00:0f:3d:f3:e4:c3 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:0d:88:fc:f7:30 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:0d:88:fc:f7:31 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0d:88:fc:f7:32 brd ff:ff:ff:ff:ff:ff
6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,10000> mtu 1500 qdisc htb master bond0 q$
    link/ether 00:0f:3d:f3:e4:c3 brd ff:ff:ff:ff:ff:ff
7: dummy0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether 92:a3:22:2f:85:a6 brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,10000> mtu 1500 qdisc htb qlen$
    link/ether 00:0f:3d:f3:e4:c3 brd ff:ff:ff:ff:ff:ff
9: vlan0001@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb qle$
    link/ether 00:0f:3d:f3:e4:c3 brd ff:ff:ff:ff:ff:ff
10: vlan0002@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
11: vlan0003@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
12: vlan0004@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
13: vlan0005@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
14: vlan0006@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
15: vlan0013@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
16: vlan0014@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
17: vlan0015@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
18: vlan0193@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
19: vlan0212@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
20: vlan0224@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
21: vlan0225@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
22: vlan0226@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
23: vlan0227@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff
24: vlan0228@bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc htb ql$
    link/ether 02:0f:3d:f2:92:ae brd ff:ff:ff:ff:ff:ff

Thanks,
Janusz

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-e49
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Versions of packages dhcp3-relay depends on:
ii  debconf [debconf-2.0]        1.5.11      Debian configuration management sy
ii  debianutils                  2.17        Miscellaneous utilities specific t
ii  dhcp3-common                 3.0.4-12    Common files used by all the dhcp3
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries

dhcp3-relay recommends no packages.

-- debconf information:
* dhcp3-relay/servers: 192.168.160.6
* dhcp3-relay/interfaces: vlan0005 vlan0013 vlan0193 vlan0212 vlan0224 vlan0225 
vlan0226 vlan0227 vlan0228
* dhcp3-relay/options: -a -A 1400 -D

--- End Message ---

--- Begin Message ---

version: 4.3.1-1

This version fixed most issues related to vlans.  Please reopen if not.

Best wishes,
Mike

--- End Message ---

Bug#408543: marked as done (dhcp3-relay: Does not catch any DHCP packets in my setup)

Reply via email to