(although on ubuntu 18.04 desktop, the underlying network system might
be systemd rather than dhclient; it's hard to tell, there are so many
layers to keep track of, and they keep changing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
This affects me on Ubuntu 18.04 desktop. After changing hostname, I
have to use nmcli c down... nmcli c up... to update the dynamic DNS
entry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Ti
Major categorization aspects:
- this very important core functionality (properly reliable resource management
of DHCP leases, also in suspend-to-RAM etc.) **NEVER EVER WORKS** (exclusively
suspend-to-RAM use case here, ending up with stale IP address):
- this did not work in 12.04LTS
- this s
This is happening only if "Ethernet Lan Option Rom" is checked (active)
in BIOS (ThinkPad X230). So there is the reason. After disabled this
option IP is not lost after first renew.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Some details:
===
dpkg --list|grep -u dhc
ii isc-dhcp-client 4.3.3-5ubuntu12.7
amd64DHCP client for automatically obtaining
an IP address
ii isc-dhcp-common 4.3.3-5ubuntu12.7
I am affected with this bug too. First renew of IP is failing, after reconnect
everything is ok until next reboot. Shutdown is often suspended for some time
(always when shutdown is soon after start or reboot).
Ubuntu 16.04.3 LTS
isc-dhclient-4.3.3
--
You received this bug notification because
I did a fresh install of artful on a shuttle SZ170 with the following
ethernet adapters according to `lshw`:
*-network
description: Ethernet interface
product: I211 Gigabit Network Connection
vendor: Intel Corporation
physic
I believe I am still affected by this bug.
$ dhclient --version
isc-dhclient-4.3.3
My lease is for 24 hours and every day, I get disconnected. If I
disconnect and reconnect the Ethernet cable, connection is restored.
kern.log shows this pattern:
Jan 24 03:17:12 kubuntu NetworkManager[1132]: [
I have compiled dhclient v4.3.5 from the isc site, installed and it does not
work.
I have to create a new directory /var/db and dhclient 4.3.5 put
dhclient6.leases in this directory
No trace in syslog, ifconfig eno1 seems OK but ping6 fails
--
You received this bug notification because you are
Hi,
I've compiled and setup the isc dhclient v4.3.5 downloaded from the isc site
and everything works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
dhclient does not renew leas
It happens to me after recent updates in 16.04 LTS. On boot I get an IP
from the DHCP server, all is well, but the IP is dropped after a while,
without complaint from network manager applet which still shows like the
network is connected. Unplugging and plugging the ethernet cable solves
the proble
I am also still affected by this bug. I build small Ubuntu-based
routers, and the ones running Xenial are very likely to fail to get new
leases after the connection drops from the ISP, or if they're booted
while the connection to the ISP / the ISP's edge device is down.
I'm having to resort to mon
There's no package "isc-dhcp" - shouldn't this be fixed in the package
isc-dhcp-client? I am still affected by this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
dhclient does no
** Changed in: isc-dhcp (Ubuntu)
Milestone: ubuntu-16.04 => None
** Changed in: bind9 (Ubuntu)
Milestone: ubuntu-16.04 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
d
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu10
---
isc-dhcp (4.3.3-5ubuntu10) xenial; urgency=low
[ Stefan Bader ]
* Revert back to bind against bind9 export libraries
(LP: #1556175, LP: #1551351)
[ LaMont Jones ]
* libirs-export requires libisccfg-export no
We have some testing packages that can be obtained by adding Lamont's
PPA (sudo apt-add-ppa ppa:lamont/ppa). From local testing this looks to
be solving at least the lease renewals. At least for me a normal kill
still seems not enough to end the dhclient daemon.
--
You received this bug notificat
This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-3
---
bind9 (1:9.10.3.dfsg.P4-3) experimental; urgency=medium
* Fix vcs links
* build in debian/tmp, use bind9.install
-- LaMont Jones Fri, 18 Mar 2016 14:46:30 -0600
** Changed in: bind9 (Ubuntu Xenial)
Status
The plan here is to restore the -export libraries for the time being,
until upstream finishes the dhcp changes that are needed to have the
common libs work. This is in-progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Since I am running dhclient -d eth0 I have not been disconnected. I do
not intend to run dhclient this way, it is a part of the minimal system
and should work in the background with no intervention. Who is actively
working on this bug from Cannonical?
--
You received this bug notification becaus
Correction 1: Stefan not Stephan, sorry.
Correction 2: Things broke down about another 1/2 day after the lease times
changes to 1 hour. The client didn't seem to release this and resorted to
broadcast type discover stuff. Then it was getting leases for 5 minutes, and
the cycle continued until I
>From Stephan comment 14:
"Hm, of course, if one starts dhclient in debug mode (foreground) by
adding a "-d", everything does work."
Yes, that does seem to work, but only for about another day, at least in
my case. Thereafter, my ISP stopped returning my domain name, host name
and some other stuf
I have tested this bug this way.
1) With the newest setup with all upgrades installed (Ubuntu Gnome)
there is 6-8 sec slow down when shutting down or rebooting. No delay at
start up.
2) I then downgraded the package isc-dhcp-client (4.3.3-5ubuntu9) to
isc-dhcp-client (4.3.3-5ubuunutu5). Also the
** Changed in: bind9 (Ubuntu Xenial)
Milestone: None => ubuntu-16.04
** Changed in: isc-dhcp (Ubuntu Xenial)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15513
I believe I got a vague feeling about what is going wrong. So the isc
library which now is shared for bind9 and dhcp is compiled (because
bind9 is rather wanted that way) with threads enabled. Before that the
export version of the library was not. So an isc_app which dhclient
creates and runs was m
So maybe we should un-duplicate bug 1551415 as not acting on SIGHUP
likely is something that could be different and also affect the network-
manager case. I think I saw some comment there about shutdown/reboot
times being increased. The problem of not keeping leases active is
limited to systems usi
Hm, of course, if one starts dhclient in debug mode (foreground) by adding a
"-d", everything does work. :/ Interestingly when I attach to it with strace, I
see "strace: Process attached with 4 threads". The foreground process
does not act on ctrl-c which at least is consistent with the broken
For more data points on this, someone mentioned today that for him the
leases get renewed (with dhclient started by network-manager). The
command line is slightly different there:
/sbin/dhclient -d -q -sf -pf -lf
-cf
while on an ifupdown system where I see the stall it is:
/sbin/dhclient -
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: bind9 (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Looking at the changelog history of bind9, the change to 9.10 looks to
be older (around December last year) but then only a recent upload to
isc-dhcp mentions "Link with the non-export bind9 libraries". Which I
think we can assume is what causes the problem. That went to the archive
around noon on
@Dough, yes, so basically did not renew but obtained a new lease (which
sensibly is the same IP as before). And while the dhcp server still
wonders why a client ask for some IP _again_, it also silently marks the
lease time as extended for another period. And since the old clients do
not die (but p
Potentially related https://lists.isc.org/pipermail/bind-
users/2015-February/094637.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
dhclient does not renew leases
To manage notif
Stefan, I think the answer is yes. Just a few minutes before my lease was going
to expire, I did: "sudo dhclient enp4s0"
However, I didn't notice any change in the leases file, so I expected internet
it to stop working after the expire time, but it didn't stop working. So I
looked at my tcpdump
Doug, was that granted when running dhclient manually? Which would be the
initial lease case. When I looked at this last one would get a new lease
whenever dhclient got started (once). Same would happen if one killed the
daemon (-11) and then did an ifdown && ifup. If there is a means of having
Well, that one got set as a duplicate of this one. Please see also bug
#1551415.
I did manage to avoid having to re-boot, via the Rob Whyte method "sudo
dhclient eth0", however my leases file is now out of date, but I did
observe a new lease actually being granted via capturing the packets on
tcpd
FYI, I just filed 1551855 for dhcpd not stopping when sent the TERM
signal. If Stephan's observation that dhclient is in a futex wait, I
wonder if the dhcpd server not stopping is suffering from a similar
wait.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Also affects: isc-dhcp (Ubuntu Xenial)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Description changed:
Release: Xenial
I think this only recently started after some bind9 updates triggered a
rebuild. When booting dhclient gets started and acquires an IP address, but it
does seem to lock up somewhere as it does not renew the lease.
In my environment I set the lease
I too have struggled with this on my server, leaving us without internet
until sudo dhclient eth0 or the interace is taken down and brought back
up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155135
This occurs also on my server, and as of two days ago.
My system is not renewing the lease of its IP address from my ISP.
(while I have static IP adresses, my ISP still requires using dhcp). The
expire time is 24 hours, and exactly 24 hours since my last re-boot,
internet stopped working. Confirme
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
d
As far as I can see, the dhclient process seems to be in some futex
wait...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
dhclient does not renew leases
To manage notifications about
41 matches
Mail list logo
