I noticed the same issue. I tried upgrading from an earlier version with an .ovpn file (with all settings and inline certs etc that was working previously). The .ovpn is configured as client to receive dhcp address from the server.
But when we ran the upgrade .msi, which created both a TAP and wintun interfaces, the TAP was fine but the wintun had static IPs selected with no IPs entered. Unless someone has some programming smoke and mirrors, that’s asking for a failure. So it didn’t read the .ovpn (to select dhcp) and it didn’t have anything to populate the IP/subnet/dns etc. This can’t be right. At the least it should be set to dhcp by default with static IPs added later if necessary. Or am I doing something wrong? Marvin > On Aug 18, 2020, at 11:03 PM, Gert Doering <g...@greenie.muc.de> wrote: > > Hi, > >> On Tue, Aug 18, 2020 at 07:30:12PM -0300, Rafael Gava wrote: >> Inspecting the wintun interface through the properties I saw that on the >> TCP/IPv4 Properties the default option selected is "Use the following IP >> address" but the IP address and the Subnet mask were empty. Should that be >> a problem? > > No. OpenVPN will set what is needed. > > gert > > -- > "If was one thing all people took for granted, was conviction that if you > feed honest figures into a computer, honest figures come out. Never doubted > it myself till I met a computer with a sense of humor." > Robert A. Heinlein, The Moon is a Harsh Mistress > > Gert Doering - Munich, Germany g...@greenie.muc.de > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
