On Fri, Aug 08, 2014 at 08:11:20AM +0000, Dexuan Cui wrote: > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Friday, August 8, 2014 11:32 AM > > > Hi Richard and all, > > > > > > IMO the most feasible and need-the-least-change solution may be: > > > the hyperv network VSC driver passes the event > > > RNDIS_STATUS_NETWORK_CHANGE to the udev daemon? > > > > > > In this way, every distro only needs to add a udev rule, which should > > > be simple. > > > > No, don't do that, again, act like any other network device, drop the > > link and bring it up when it comes back. > > > > greg k-h > > Hi Greg, > Thanks for the comment! > > Do you mean tearing down the net device and re-creating it (by > register_netdev() and unregister_netdev)?
No, don't you have link-detect for your network device? Toggle that, I thought patches to do this were posted a while ago... But if you really want to tear the whole network device down and then back up again, sure, that would also work. good luck, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
