Skip Menu |
Report information
The Basics
Id: 33377
Status: resolved
Estimated: 12 hours (720 minutes)
Worked: 45 minutes
Users:
tmark: 20 minutes
Priority: 40/40
Queue: dhcp-public

Bug Information
Version Fixed: 4.4.0 4.3.6
Version Found: (no value)
Versions Affected: (no value)
Versions Planned: 4.3.6
Priority: P2 Normal
Severity: S2 Normal
CVSS Score: (no value)
CVE ID: (no value)
Component: (no value)
Area: bug

Dates
Created:Thu, 02 May 2013 17:29:06 -0400
Updated:Wed, 21 Jun 2017 13:35:31 -0400
Closed:Wed, 21 Jun 2017 13:35:31 -0400



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: dhclient listening on two additional random UDP ports
Date: Thu, 2 May 2013 16:28:37 -0500
To: dhcp-bugs@isc.org
From: Rodney D Beede <rodney.d.beede@seagate.com>
When I run dhclient it listens on the expected port 68.  However, in addition to that port it also listens on a high number random IPv4 port and IPv6 port (even if I specify -4 as an option).

Reading through the source code would make me think this is related to OMAPI somehow?

I tried this on Ubuntu Server 13.04 64-bit which came with dhclient version 4.2.4.  I also downloaded, compiled, and tried the latest version isc-dhclient-4.2.5-P1.  I get the same result.

I believe this is a bug.  Either it shouldn't be listening on these ports or it should be documented what they are used for.

Screenshots attached.Inline image 1

Inline image 2
Download image.png
image/png 12.7KiB

Image displayed inline above

Download image.png
image/png 17KiB

Image displayed inline above

Subject: Re: [ISC-Bugs #33377] AutoReply: dhclient listening on two additional random UDP ports
Date: Thu, 2 May 2013 16:56:50 -0500
To: dhcp-bugs@isc.org
From: Rodney D Beede <rodney.d.beede@seagate.com>
Also seen on Debian.




-------------------------------------------------------------------------
When I run dhclient it listens on the expected port 68.  However, in
addition to that port it also listens on a high number random IPv4 port and
IPv6 port (even if I specify -4 as an option).

Reading through the source code would make me think this is related to
OMAPI somehow?

I tried this on Ubuntu Server 13.04 64-bit which came with dhclient version
4.2.4.  I also downloaded, compiled, and tried the latest version
isc-dhclient-4.2.5-P1.  I get the same result.

I believe this is a bug.  Either it shouldn't be listening on these ports
or it should be documented what they are used for.

Screenshots attached.[image: Inline image 1]

[image: Inline image 2]


Subject: Re: [ISC-Bugs #33377] AutoReply: dhclient listening on two additional random UDP ports
Date: Mon, 6 May 2013 10:46:04 -0500
To: dhcp-bugs@isc.org
From: Rodney D Beede <rodney.d.beede@seagate.com>
Download (untitled) / with headers
text/plain 1.6KiB
It turns out the two random open ports are related to the dynamic DNS feature (NSUPDATE).

I modified the source code as per instructions at (http://forums.debian.net/viewtopic.php?f=10&t=95273) (forums.debian.net, dhclient UDP ports, 2013-02-01), recompiled, and reran with the random ports disappearing.


Bug Report:  Add into the documentation for dhclient that it has the NSUPDATE functionality which causes it to listen on the IPv4 and IPv6 ANY_ADDR interface on random UDP ports.

Additionally their should be a run-time configuration option that enables that behavior with it disabled by default.  A recompile should not be required to disable the ports.


On Thu, May 2, 2013 at 4:57 PM, Rodney D Beede via RT <dhcp-bugs@isc.org> wrote:
Also seen on Debian.

http://forums.debian.net/viewtopic.php?f=10&t=95273



-------------------------------------------------------------------------
> When I run dhclient it listens on the expected port 68.  However, in
> addition to that port it also listens on a high number random IPv4 port and
> IPv6 port (even if I specify -4 as an option).
>
> Reading through the source code would make me think this is related to
> OMAPI somehow?
>
> I tried this on Ubuntu Server 13.04 64-bit which came with dhclient version
> 4.2.4.  I also downloaded, compiled, and tried the latest version
> isc-dhclient-4.2.5-P1.  I get the same result.
>
> I believe this is a bug.  Either it shouldn't be listening on these ports
> or it should be documented what they are used for.
>
> Screenshots attached.[image: Inline image 1]
>
> [image: Inline image 2]
>
>


We have now updated the dhclient and dhcpd man pages (section 8) to mention the two DDNS ports. We shall keep this ticket alive in order to track adding an option to enable or disable DDNS during run time. The changes to the docs will be released in the next release of the code - barring any problems this will be 4.3.3 and 4.1-ESV-R12. thank you for your report, shawn
Hello Rodney: You'll be pleased to learn that we've addressed this issue in our upcoming maintenance release, 4.3.6 due out July 31st, and in 4.4.0 release date is TBD. We have modified the DDNS support initialization such that the DNS related ports will only be opened: 1. By the server (dhcpd) at startup if ddns-update-style is not "none" 2. By dhclient only when and if it first attempts to do an update 3. Never by dhcrelay. Prior to this all three always did the initialization at startup when DDNS support was compiled in. Thank you for reporting this issue to us. Typically we like to recognize our contributors by citing them in the release notes. If you would like to be so noted please respond with how you'd like to be identified. Sincerely, Thomas Markwalder ISC Software Engineering
To: dhcp-bugs@isc.org
Date: Wed, 21 Jun 2017 11:56:00 -0500
Subject: Re: [ISC-Bugs #33377] dhclient listening on two additional random UDP ports
From: "Rodney D Beede" <rodney.d.beede@seagate.com>
Hello Thomas,

Thank you for the update on the change!

You may identify me as  "Rodney Beede"

Thanks again!

Rodney

On Mon, Jun 19, 2017 at 2:27 PM, Thomas Markwalder via RT <dhcp-bugs@isc.org> wrote:
Hello Rodney:

You'll be pleased to learn that we've addressed this issue in our upcoming maintenance release, 4.3.6 due out July 31st, and in 4.4.0 release date is TBD.

We have modified the DDNS support initialization such that the DNS related ports will only be opened:

1. By the server (dhcpd) at startup if ddns-update-style is not "none"
2. By dhclient only when and if it first attempts to do an update
3. Never by dhcrelay.

Prior to this all three always did the initialization at startup when DDNS support was compiled in.

Thank you for reporting this issue to us.  Typically we like to recognize our contributors by citing them in the release notes.  If you would like to be so noted please respond with how you'd like to be identified.

Sincerely,

Thomas Markwalder
ISC Software Engineering