lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 21 Jul 2014 08:44:01 +0000
From:	"Yue Zhang (OSTC DEV)" <>
To:	Richard Weinberger <>
CC:	"" <>,
	LKML <>,
	Greg KH <>,
	"" <>,
	"" <>,
	"David S. Miller" <>,
	Haiyang Zhang <>,
	KY Srinivasan <>,
	Thomas Shao <>,
	Dexuan Cui <>
Subject: RE: [PATCH] Hyperv: Trigger DHCP renew after host hibernation

> From: Richard Weinberger []
> Sent: Monday, July 21, 2014 4:18 PM
> Yue,
> Am 21.07.2014 10:05, schrieb Yue Zhang (OSTC DEV):
> > The problem of systemd implementation is that in different distros, the ways 
> > to restart service are different. Propagating the event to userspace also doesn't 
> > help for this issue.
> This way each distro can provide their own restart script.
> Same as every distro has custom start scripts, etc...
> > The advantage of current solution is that it simulates a cable plugging 
> > in/out event. IMHO, in all the distros, this simulated event has already been well 
> > handled. It is a dup effect to implement new hooks.
> Iff the current solution works for _all_ networking implementations.
> Thanks,
> //richard

Hi, Richard

IMHO, all networking implementations should handle the cable offline event. Consider
this situation. I unplugged the network cable and connect it to a new network switch
after 10 seconds. If the DHCP renew is not triggered, the network will break. I think in 
normal cases, it should already been handled properly. Unless there is a strong 
justification for not doing this. In that case, we shouldn't renew DHCP anyway.


Powered by blists - more mailing lists