[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140623131723.GA7026@aepfle.de>
Date: Mon, 23 Jun 2014 15:17:23 +0200
From: Olaf Hering <olaf@...fle.de>
To: Haiyang Zhang <haiyangz@...rosoft.com>
Cc: Greg KH <greg@...ah.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"driverdev-devel@...uxdriverproject.org"
<driverdev-devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [PATCH net-next] hyperv: Add handler for
RNDIS_STATUS_NETWORK_CHANGE event
On Mon, Jun 23, Haiyang Zhang wrote:
> > I think its reasonable to expect guest config changes on this new kind
> > of host. Would a link-down/link-up event work? I'm sure it will, there
> > is enough code floating around in the guests which handles cable unplug.
>
> Do you mean netif_carrier_off() / netif_carrier_on()? They are already
> called in the code before this patch, but DHCP renew is not triggered by
> them.
I do not know how to simulate a cable unplug. The point is that calling
/etc/init.d/network will fail, at least in SLES12.
Maybe some sort of "DHCP refresh required" event is required?
Maybe the DHCP clients need to renew on cable unplug?
No idea what the solution to the issue really is.
Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists