Am 14.03.18 um 17:17 schrieb Selva Nair: > Hi, > > On Wed, Mar 14, 2018 at 3:32 AM, Jiří Engelthaler <eng...@gmail.com> wrote: >> Hi. >> You right. Disabled dhcp media sense can be set as global for all >> interfaces or in adapter specific setting if it supports it (TAP supports >> it). >> But for must users is the global settings hidden deep in the system and for >> me it took several months to find the cause of my problems. Interface >> specific settings can be cleared by uninstalling and reinstalling OpenVPN. > > Well, Windows ships with media sense enabled, isn't it? So if its > disabled, either the user did that or some third party application did > it for some reason. Without knowing those unknowables, we can't even > decide whether to suggest the user to enable it back or not. > > Whereas, using --dhcp-renew (or making it the default) looks much > simpler and something in our control. Anyone knows why it shouldn't be > the default? I don't see how it could hurt except that openvpn needs > to fork to run --dhcp-renew when the parent process is waiting for the > the interface to get the address. But that's not a big deal on a > Windows client.
This on of the old patches that are still pending. It seems that the original submitter never replied. This is still something we want to merge or should we just "close" due to timeout? I am not too familiar with the DHCP problem to have a good opinion on that. Arne
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
