This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.7
---
isc-dhcp (4.3.3-5ubuntu12.7) xenial; urgency=medium
* debian/control : Add "Replaces:" option for package isc-dhcp-client
to allow the packaging system to remove "isc-dhcp-client-noddns" on
systems on which
This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.10
---
isc-dhcp (4.2.4-7ubuntu12.10) trusty; urgency=medium
* Introduction of a new binary package "isc-dhcp-client-noddns" (LP: #1176046)
- isc-dhcp-client : no behavioural change from previous version.
-
** No longer affects: isc-dhcp (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in
[Verification Xenial]
{Before upgrade}
===
ii isc-dhcp-client 4.2.4-7ubuntu12.10
amd64ISC DHCP client
ii isc-dhcp-client-noddns 4.2.4-7ubuntu12.10
amd64Dynamic DNS (DDNS) disabled DHCP client
ii
[Verification Trusty]
ii isc-dhcp-client-noddns 4.2.4-7ubuntu12.10
amd64Dynamic DNS (DDNS) disabled DHCP client
# netstat -anputa | grep dhclient
udp0 0 0.0.0.0:68 0.0.0.0:*
1676/dhclient
# ls -altr /sbin/dhclient*
Verified works on trusty as desired. No more extra ports.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Can confirm for xenial installing the isc-dhcp-client-ddns also works as
expected. This package enables ddns ports.
When not using this package no random ddns ports as desired.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I installed isc-dhcp-client-noddns from trusty-proposed and I don't get
the two random extra high ports anymore:
Before:
# dpkg -l | grep isc-dhcp-
ii isc-dhcp-client 4.2.4-7ubuntu12.9 amd64
ISC DHCP client
ii isc-dhcp-common
Dear Rodney, and anyone else affected,
Please install "isc-dhcp-client-noddns" found in trusty-proposed and
provide feedbacks by commenting the bug. Your feedbacks are paramount
for the success of this SRU.
Additionally, I will also do some precision testing on Trusty and re-run
the release
Hello Rodney, or anyone else affected,
Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Changed in: isc-dhcp (Ubuntu Xenial)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient
> Can I confirm that by "with expected result" you mean that on
Trusty->Xenial upgrade, in both cases (isc-client-dhcp installed and
isc-client-dhcp-noddns installed) you end up with isc-client-dhcp
installed in Xenial?
yes.
--
You received this bug notification because you are a member of
Hi Robie,
Thanks for your review/feedbacks.
At the moment, there is currently an SRU for isc-dhcp via LP: #1689854
for Trusty.
As soon as this SRU is successfully completed. (move to -updates). I'll
start the SRU for this particular bug.
- Eric
--
You received this bug notification because
Hi Eric,
Sorry for the delay in getting back to this. As it has been a while I
have reviewed everything again from the beginning.
Can I confirm that by "with expected result" you mean that on
Trusty->Xenial upgrade, in both cases (isc-client-dhcp installed and
isc-client-dhcp-noddns installed)
@Norman Henderson (norm-audrey)
I would suggest you to report a separate bug/wishlist for this topic.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Eric, please see 1670303 - pending a substantive solution there, would
you be willing to fix dhcpd in the corresponding way that you have fixed
dhclient here, i.e. by making separate packages available with or
without ddns support?
--
You received this bug notification because you are a member
** Changed in: isc-dhcp (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random
** Patch removed: "lp1176046_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff
** Patch added: "lp1176046_xenial.debdiff"
** Patch added: "lp1176046_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864919/+files/lp1176046_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Patch added: "lp1176046_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@rbasak,
* Un-version the "Replaces:" as discussed : DONE
- Upgrade Trusty->Xenial with isc-client-dhcp pkg successfully completed with
expected result
- Upgrade Trusty->Xenial with isc-client-dhcp-noddns pkg successfully completed
with expected result
* Fix typo here and there : DONE
* Add
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random
** Patch added: "verif-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864794/+files/verif-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Patch added: "verif-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864795/+files/verif-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Hi Robie,
To answer your questions...
* Are you proposing your debdiff in commit 40 as ready for upload to Trusty?
No, here's the final one (that I sent you by email), but I will attach them to
the LP bug now.
verif-trusty.debdiff
verif-xenial.debdiff
* Or is it still in progress?
No, I did
14:45 slashd: I'm sure I asked you this before, and you
answered, but I can't find your answer anywhere, sorry. Are you
proposing your debdiff in commit 40 as ready for upload to Trusty? Or is
it still in progress? And do you have a debdiff for the transitional
package in Xenial please? That
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I
Quick note saying that the work is still in progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Installing isc-dhcp-client-noddns on Trusty and then upgrade to Xenial
with a local archive of a modified Xenial's isc-dhcp-client to replace
isc-dhcp-client-noddns package to isc-dhcp-client during release upgrade
from Trusty to Xenial work as expected with a completed successful
release upgrade.
** Changed in: isc-dhcp (Ubuntu Trusty)
Importance: Medium => Wishlist
** Changed in: isc-dhcp (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Third option: Tell users who are bothered by this misfeature to upgrade
to Xenial. "I don't like these ports being in use" isn't a bug, per
se, and our goal should not be to backport exact feature parity from
Xenial to Trusty. We release new releases for a variety of reasons, and
this is one of
Here a new version of the actual in progress... debdiff for Trusty.
** Patch added: "V2_debdiff_noddns_proposal_still_in_progress"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4793975/+files/V2_no_ddns_binary_pkg.debdiff
** Attachment removed:
@rbasak,
Yes, right this is exactly what I had in mind.
Noted for "(no behavioural change from previous version)".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Let me try and restate this in detail to make sure I understand it.
Trusty: add a new binary package called isc-dhcp-client-noddns. This
will work the same as isc-dhcp-client-ddns in Xenial, but in reverse. It
will use the same dpkg-divert mechanism to provide a replacement
/sbin/dhclient that
@caribou
@rbasak
Let me share the work (since rbasak seems to like the approach) I've
done so far on my above recent proposal :
isc-dhcp-client: dhclient with DDNS functionality enabled
isc-dhcp-client-noddns : dhclient with DDNS functionality disabled
This is a working debdiff, I think
Maybe we are not looking the situation the right way ... What if we look
at this the opposite way ?
"isc-dhcp-client" remains the same including the extra random bindings
ports.
and we introduce a new package "isc-dhcp-client-noddns" that change the
dhclient behavior by overriding dhclient and
> Actual results in proposal A: apt resolves this by updating isc-dhcp-
client-ddns first to 4.3.3-5ubuntu12.7 and then isc-dhcp-client to
4.3.3-5ubuntu12.7.
To be clear, that means I think the behaviour in proposal A would be
wrong. I'm open to further suggestions on what we could do, or why my
Notes from online discussion :
==
src:isc-dhcp
Trusty:
4.2.4-7ubuntu12.8 -> (isc-dhcp-client)
Proposal A: 4.2.4-7ubuntu12.9 -> (isc-dhcp-client,
isc-dhcp-client-ddns), isc-dhcp-client Recommends: isc-dhcp-client-ddns
Proposal B:
** Also affects: isc-dhcp (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: isc-dhcp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Fix Released
** Changed in: isc-dhcp (Ubuntu Xenial)
I don't follow. isc-dhcp-ddns in Xenial ships /sbin/dhclient and a dpkg-
divert in its prerm. I don't see how Breaks/Replaces is relevant. Are
you planning something different in Trusty?
Louis said: "...if isc-dhcp-ddns Breaks/Replaces isc-dhcp and Recommends
isc-dhcp-ddns...". isc-dhcp-ddns
@caribou, yes you are reading this correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in
Here is how I understand it :
In Trusty, the isc-dhcp client provides the Dynamic DNS (ddns)
functionality and this one can be disabled. From Xenial onward, two
separate packages provide each of the possibilities.
AFAIU, the Trusty isc-dhcp package should become isc-dhcp which doesn't
provide
I will evaluate/test the "debian/control" fields possible scenarios this
week, and will update the LP with the outcome.
rbasak, if you have any ideas/suggestion/piece of advise/... I'm all
ears.
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
7.6.1 Overwriting files in other packages
It is usually an error for a package to contain files which are on the
system in another package. However, if the overwriting package declares
that it Replaces the one containing the file being overwritten, then
dpkg will replace the file from the old
Hmm need to look more in depth but maybe this would work ? By
mentionning the "earlier than" ootion.
* 7.3 Packages which break other packages -
Breaks normally a Breaks entry will have an "earlier than" version
clause; such a Breaks is introduced in the version of an (implicit or
explicit)
Rectification :
I think we will need a mix of both world Recommends: and Break: .
Need to check more in deep for implementation though (if applicable)
Recommends: for next pkg upgrade and then rely on Breaks: or something
similar to that for following pkg upgrade and release upgrade.
--
You
> This part sounds like it'll work well then, but I'm not sure about the
change in release upgrade behaviour above.
Good point !
What about "Breaks:" instead of "Recommends:" ?
Package A breaks Package B when both packages cannot be simultaneously
configured in a system. The package management
On Sat, Dec 10, 2016 at 08:20:59PM -, Eric Desrochers wrote:
> > What will happen to existing Trusty users who are relying on the
> current ddns functionality?
>
> Existing Trusty user at next isc-dhcp-client pkg upgrade will
> automatically receive (Recommends: isc-dhcp-client-ddns).
I picked "Recommends:" based on following explanation :
Package A recommends Package B, if the package maintainer judges that
most users would not want A without also having the functionality
provided by B.
Ref:
https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html
Eric
--
You
> What will happen to existing Trusty users who are relying on the
current ddns functionality?
Existing Trusty user at next isc-dhcp-client pkg upgrade will
automatically receive (Recommends: isc-dhcp-client-ddns).
And for users bother by the extra random port they will simply have to
apt-get
> isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no
random extra ports)
What will happen to existing Trusty users who are relying on the current
ddns functionality?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
+ [Impact]
+
+ In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
+ The DDNS functionnality, generate 2 random extra ports between 1024-65535.
+
+ Impact reported by users :
+
+ "One impact of these random
I worked on a patch that so far seems to work well.
I still need to arrange a few things, but I should be able to submit a
patch soon.
The patch will create a additional binary package.
isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random
extra ports)
** Changed in: isc-dhcp (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra
** Also affects: isc-dhcp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in isc-dhcp package in
** Changed in: isc-dhcp (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random
** Tags removed: raring
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in isc-dhcp package in
> But perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?
At runtime, it doesn't seem to have a way, for instance, I already tried
the following without success: do-forward-updates false;
# man
> Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.
I think that it's important that existing Trusty users can continue to
use this DDNS functionality after the SRU without any necessary
intervention.
So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".
On Trusty, "isc-dhcp-client" combine both.
Will ask the
So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".
On Trusty, "isc-dhcp-client" combine both, and AFAIK, I
I was able to identify from where the port range list is initialize, and the
decision is taken by binary package "libdns162" (source package "bind9")[1]
which dhclient relies on.
Basically, it randomly takes any port available between 1024 and 65535[2]
So there is a port randomization mechanism
After more investigation, it seems like the 2 extra port-bindings port
assignation decision is made by "libdns" itself.
https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921
--
You received this bug notification because you are a member of
Rectification, after more investigation here what is happening :
Trusty got the random port right away because NSUPDATE is enable at
compile time in package "isc-dhcp-client"
In Xenial and late (including debian) with commit
[b1d5bab630a29f2ca94c458f9402aa43cc5975c4], a new pkg binary package is
The following debian[1] forum indicate that failover and tracing need to
be disabled in order to disable NSUPDATE as well and I confirmed the
steps, otherwise the build fails.
I'm not too sure if this is the right way to fix this problem as I don't
want to introduce new issues that will impact
Applying the Xenial "disable-nsupdate.patch" result in a failling build
in Trusty.
/<>/server/dhcpd.c:498: undefined reference to `trace_ddns_init'
dhcpd-failover.o: In function `dhcp_failover_process_bind_update':
/<>/server/failover.c:5225: undefined reference to `ddns_removals'
Seems like
NSUPDATE is disabled in Xenial, will keep the same approach for Trusty
and then test.
More details can be found here :
xenial/isc-dhcp-4.3.3/debian/patches/disable-nsupdate.patch
description: undefine NSUPDATE
author: cchip
origin: http://forums.debian.net/viewtopic.php?f=10=95273
bug-debian:
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged => In Progress
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in
Then NSUPDATE has been re-enable with debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798237
# changelog
isc-dhcp (4.3.3-4) unstable; urgency=medium
* Reenable NSUPDATE (closes: #798237)
I will look at both changes, but most likely the one in #798237 seems
more suitable for a
Sound similar to debian bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=712503
The situation doesn't occur on Xenial (16.04 LTS), but present in Trusty
(14.04) as a fix has been first introduce in Ubuntu with version : isc-
dhcp (4.3.3-2)
Trusty :
#netstat -tulp | grep -i dhclient
udp
I confirm I have the same behavior in Ubuntu 14.04.5 LTS with isc-dhcp-
client version 4.2.4-7ubuntu12.7
I recompiled the isc-dhcp-client with the fix from
http://forums.debian.net/viewtopic.php?f=10=95273 and I no longer have
the issue:
BEFORE:
root@trustydhclient:~# lsof -i udp
COMMAND PID
I can't reproduce this on Ubuntu 16.04 "xenial" (dhclient only listens
on port 68) but it remains an issue on Ubuntu 15.10 "wily".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
I am still facing same issue in centos 15.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in
Apparently this is still happening in Ubuntu 15.04 "vivid".
Any updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on
I am experiencing a similar or same issue on Ubuntu 14.04 Server 64-bit.
The Dhclient is listening on both ports 68 and 42370. I have no
experience with dhclient so I cannot decide if this is normal behaviour.
Why the extra port?
--
You received this bug notification because you are a member of
80 matches
Mail list logo
