Report information
The Basics
Id:
37415
Status:
resolved
Worked:
16 hours (960 minutes)
Users:
tmark: 16 hours (960 minutes)
Priority:
Medium/Medium
Queue:

BugTracker
Version Fixed:
4.3.2 4.2.8 4.1-ESV-R11
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.3.2
Priority:
(no value)
Severity:
(no value)
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
(no value)

Dates
Created:Wed, 08 Oct 2014 13:23:35 -0400
Updated:Fri, 07 Jul 2017 20:05:03 -0400
Closed:Mon, 09 Feb 2015 10:16:04 -0500



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: dhcpd generates spurious responses when seeing requests from vlans on plain interface
Date: Wed, 08 Oct 2014 19:23:28 +0200
To: dhcp-bugs@isc.org
From: Jiri Popelka <jpopelka@redhat.com>
Description of problem: If dhcpd is listening on a plain interface "eth0" it also sees the traffic from VLANs "eth0.7" but generates responses without VLAN tags. Steps to Reproduce: 1. dhcp server with ethX and ethX.Y 2. dhcpd -d ethX 3. from a client generate dhcp request on vlan Y Actual results: dhcpd generates DHCPOFFER on non-vlan Expected results: dhcpd ignores the request. Additional info: dhcpd needs to ignore the tagged requests on plain interfaces. If it is listening on all interfaces (including ethX.Y) it will see the tagged version on eth0 and also as an untagged version on ethX.Y, thus generating duplicates (even if the response was correctly tagged). All credits go to Martin Poole from Red Hat, inc. -- Jiri

Message body is not shown because sender requested not to inline it.

Hello Jiri:

You'll be pleased to learn that we used your patch to resolve the VLAN packet issue for Linux OSs.  Thank you for your continued contributions.

Sincerely,

Thomas Markwalder

Subject: Re: [ISC-Bugs #37415] dhcpd generates spurious responses when seeing requests from vlans on plain interface
Date: Fri, 30 Jan 2015 11:57:46 +0100
To: dhcp-bugs@isc.org
From: "Jiri Popelka" <jpopelka@redhat.com>
Hi, Yesterday, I got a bug report [1] that the patch [2] might be breaking dhcrelay (when used with vlan). I haven't had time to look at it so far, just wanted to let you know ASAP, as I see you've been preparing beta releases. The only thing that changed between 4.1.1-43.P1.el6.centos.1 and 4.1.1-43.P1.el6.centos is this added patch. -- Jiri [1] https://bugzilla.redhat.com/show_bug.cgi?id=1187107 [2] https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commitdiff;h=29170f9da9826bd7191f4ad644e61b76c49f6cc6
On Fri Jan 30 10:57:53 2015, jpopelka@redhat.com wrote: > Hi, > > Yesterday, I got a bug report [1] that the patch [2] might be breaking > dhcrelay (when used with vlan). > I haven't had time to look at it so far, just wanted to let > you know ASAP, as I see you've been preparing beta releases. > > The only thing that changed between 4.1.1-43.P1.el6.centos.1 and > 4.1.1-43.P1.el6.centos is this added patch. > > -- > Jiri > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1187107 > > [2] > https://source.isc.org/cgi- > bin/gitweb.cgi?p=dhcp.git;a=commitdiff;h=29170f9da9826bd7191f4ad644e61b76c49f6cc6 Hello Jiri: Actually it isn't that the patch broke dhcrelay, rather it makes dhcrelay behave exactly as its man page states: " The -i flag can be used to specify the network interfaces on which the relay agent should listen. In general, it must listen not only on those network interfaces to which clients are attached, but also on those network interfaces to which the server (or the router that reaches the server) is attached. However, in some cases it may be necessary to exclude some networks; in this case, you must list all those network interfaces that should not be excluded using the -i flag." The user should have alwayws had to specify both interfaces on command line: " -i em2 -i em2.60". They have simply gotten lucky with it until now because the vlan for their server is hosted on the interface that is also used for their clients. Had they used two different interfaces, such as em1 for their server and em2 for their clients, they would have to either specified both: " -i em1 -i em2" or none. The latter of which would cause dhcrelay to listen on all networks.
Subject: Re: [ISC-Bugs #37415] dhcpd generates spurious responses when seeing requests from vlans on plain interface
Date: Fri, 30 Jan 2015 15:20:20 +0100
To: dhcp-bugs@isc.org
From: "Jiri Popelka" <jpopelka@redhat.com>
On 01/30/2015 03:10 PM, Thomas Markwalder via RT wrote: > Actually it isn't that the patch broke dhcrelay, rather it makes dhcrelay behave exactly as its man page states: Thank you very much for such a quick response, it's really appreciated. With regards, -- Jiri