Philipp Kern wrote:
one-shot mode (-1) and will exit after it acquired a lease successfully.
dhclient isn't doing that, at least on kfreebsd. I'm not sure that's
what -1 means. It will try only once to get a lease, initially. If
successful it stays running - I assumed it continues to refresh
On Wed, Feb 18, 2015 at 10:05:27PM +, Steven Chamberlain wrote:
We did expect that during freeze, some regressions may be introduced
that affect only GNU/kFreeBSD, and we'd have to fix things up in our
unofficial release, perhaps rolling packages back to an older version,
or uploading a
Hello,
Thanks for the notice,
Cyril Brulebois, le Wed 18 Feb 2015 22:29:23 +0100, a écrit :
Philipp Kern pk...@debian.org (2015-02-18):
So now I guess the question is if we revert the change that broke it:
Don't kill_dhcp_client without reason (Closes: #757711, #757988)
On Tue, Feb 10, 2015 at 09:22:25AM +0100, Philipp Kern wrote:
On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote:
On the other hand it also seems wrong for di_exec_shell_log to continue
after the invoked binary exited. I suspect that'd mean ppoll() and
proper signal handling, but
Philipp Kern pk...@debian.org (2015-02-18):
On Tue, Feb 10, 2015 at 09:22:25AM +0100, Philipp Kern wrote:
On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote:
On the other hand it also seems wrong for di_exec_shell_log to continue
after the invoked binary exited. I suspect that'd
Cyril Brulebois wrote:
Philipp Kern pk...@debian.org (2015-02-18):
So now I guess the question is if we revert the change that broke it:
Don't kill_dhcp_client without reason (Closes: #757711, #757988)
Do not kill_dhcp_client after setting the hostname and
domain,
On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote:
On the other hand it also seems wrong for di_exec_shell_log to continue
after the invoked binary exited. I suspect that'd mean ppoll() and
proper signal handling, but I'm at a loss right now how to do that
properly in C. Maybe
On Thu, Dec 18, 2014 at 03:04:38PM +0100, Peter Valdemar Mørch wrote:
netcfg: Do not kill_dhcp_client after setting the hostname and domain,
otherwise Linux udhcpc will stop renewing its lease, and on other
platforms dhclient will de-configure the network interface (#757711,
#757988).
The
On Thu, Dec 18, 2014 at 3:04 PM, Peter Valdemar Mørch pe...@morch.com
wrote:
This occurs in in our work environment in VMware Workstation and
Proxmox when using bridged eth0, but not when using NAT.
I have also tried this on physical hardware without virtualization, and got
the same hang.
On Mon, 22 Dec 2014 12:03:24 +0100 =?UTF-8?Q?Peter_Valdemar_M=C3=B8rch?=
pe...@morch.com wrote:
If it adds value, I can try booting the image on e.g. a laptop to see
if it is VMware specific. But I'm pretty sure it will experience the
same symptoms. That is only possible from January 5th
On Thu, Dec 18, 2014 at 03:04:38PM +0100, Peter Valdemar Mørch wrote:
This occurs in in our work environment in VMware Workstation and
Proxmox when using bridged eth0, but not when using NAT. In my home
network, the exact same procedure goes through without any hangs for
both bridged and NAT.
On Mon, Dec 22, 2014 at 11:52 AM, Philipp Kern pk...@debian.org wrote:
But please tell me: Why is there no Router Advertisement in the packet
dump? I see Router Solicitations and DHCPv6 interactions, but no RA.
I have absolutely no idea. Perhaps that is the reason for the hang?
All I know is
Thanks for the details. Adding Philipp to the loop:
Peter Valdemar Mørch pe...@morch.com (2014-12-18):
I'm also seeing that d-i hangs after DHCP setup.
But only in Jessie Beta 2 - debian-jessie-DI-b2-amd64-netinst.iso. Not
with Beta 1. The OP also used debian-jessie-DI-b2-amd64-netinst.iso.
In my setup, i've got dhcp for IPv4 and IPv6 without dhcp. Same result.
I could reproduce the bug in a vm and on a notebook
There is a process in zombie state: [netcfg]. Its parent process seems to be
udpkg --configure --force-configure netcfg
A workaround is to kill the process
dhcp6c -c
14 matches
Mail list logo
