David Miller writes:
> From: Haiyang Zhang
> Date: Tue, 9 Feb 2016 15:31:34 +
>
>> 1) I share your concern as well. Is there a universal way to immediately
>> trigger
>> DHCP renew of all current and future daemons with a single event from
>> kernel?
>> If not, can we put the delay (RNDI
From: Haiyang Zhang
Date: Tue, 9 Feb 2016 15:31:34 +
> 1) I share your concern as well. Is there a universal way to immediately
> trigger
> DHCP renew of all current and future daemons with a single event from kernel?
> If not, can we put the delay (RNDIS_STATUS_NETWORK_CHANGE only) into a
rg;
> driverdev-de...@linuxdriverproject.org
> Subject: Re: [PATCH net-next] hv_netvsc: Increase delay for
> RNDIS_STATUS_NETWORK_CHANGE
>
> From: Haiyang Zhang
> Date: Tue, 2 Feb 2016 16:15:56 -0800
>
> > We simulates a link down period for RNDIS_STATUS_NETWORK_CHANGE
> > message to
From: Haiyang Zhang
Date: Tue, 2 Feb 2016 16:15:56 -0800
> We simulates a link down period for RNDIS_STATUS_NETWORK_CHANGE message to
> trigger DHCP renew. User daemons may need multiple seconds to trigger the
> link down event. (e.g. ifplugd: 5sec, network-manager: 4sec.) So update
> this link
rg;
> driverdev-de...@linuxdriverproject.org
> Subject: Re: [PATCH net-next] hv_netvsc: Increase delay for
> RNDIS_STATUS_NETWORK_CHANGE
>
> Haiyang Zhang writes:
>
> >> -Original Message-
> >> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> >> Sent: Wedn
fle.de; linux-ker...@vger.kernel.org;
>> driverdev-de...@linuxdriverproject.org
>> Subject: Re: [PATCH net-next] hv_netvsc: Increase delay for
>> RNDIS_STATUS_NETWORK_CHANGE
>>
>> Haiyang Zhang writes:
>>
>> > We simulates a link down period for RNDIS_S
rg;
> driverdev-de...@linuxdriverproject.org
> Subject: Re: [PATCH net-next] hv_netvsc: Increase delay for
> RNDIS_STATUS_NETWORK_CHANGE
>
> Haiyang Zhang writes:
>
> > We simulates a link down period for RNDIS_STATUS_NETWORK_CHANGE
> message to
> > trigger DHCP renew. User daemons
Haiyang Zhang writes:
> We simulates a link down period for RNDIS_STATUS_NETWORK_CHANGE message to
> trigger DHCP renew. User daemons may need multiple seconds to trigger the
> link down event. (e.g. ifplugd: 5sec, network-manager: 4sec.) So update
> this link down period to 10 sec to properly tr
We simulates a link down period for RNDIS_STATUS_NETWORK_CHANGE message to
trigger DHCP renew. User daemons may need multiple seconds to trigger the
link down event. (e.g. ifplugd: 5sec, network-manager: 4sec.) So update
this link down period to 10 sec to properly trigger DHCP renew.
Signed-off-by
