extend iservice to turn off DHCPv4 (or handle address service)

[Gert Döring]

as per the thread on openvpn-devel, if the tun/tap interface on windows is set to "manual IP address", open will fail - openvpn.exe runs non-privileged but still tries to run "netsh" to re-enable DHCP, which has to fail.

Two possible approaches to fix this:

• teach the iservice to turn on DHCP
• or just use the iservice to configure the IPv4 address (as we do for IPv6) if "no DHCP" is detected

Tagging this as "Windows GUI" even if it isn't (it's not tap*windows either, and we have no other "windows" category)

Thread:
​https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg17147.html

[tincantech]

CC

[Gert Döring]

I think all relevant functionality is there now? For wintun, we use the iservice to call ipapi already, since:

commit 1c4a47f796639da45ec7c9bf5f38a9f0bb6aa9b2
Author: Lev Stipakov <lev@…>
Date: Wed Dec 18 07:18:18 2019 +0100

wintun: set adapter properties via interactive service

Since Wintun doesn't do DHCP, use interactive service
calls to set up adapter properties.

and the DHCP part came in with

commit b4fc8bbd6b1d0211dd6982c4accedfbe4ae7e3ed
Author: Selva Nair <selva.nair@…>
Date: Tue Oct 2 16:01:13 2018 -0400

Enable dhcp on tap adapter using interactive service

Currently, if dhcp on the TAP interface is disabled, OpenVPN
on Windows tries to enable it using netsh but that succeeds only when
run with admin privileges.

When interactive service is available, delegate this task to the
service.

@selva, @lev, can we close this?

[Selva Nair]

Yes this may be closed.

[Gert Döring]

One down, 400+ to go... :-)