This is the most weird effect I've ever had:
Server 2008 R2 (virtual in Hyper-V, if that matters), openvpn version is 64 bit.
Config type is TAP, the network bridge is set up.
The VPN Device name is: VPN21
This config should be working:
local 192.168.115.249
port 20021
proto udp
dev tap
dev-node VPN21
ifconfig 192.168.115.221 255.255.255.0
secret abcdefghijlkm-nopqrst-21.key
cipher AES-256-CBC
comp-lzo
; Hold tunnel with more strength
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
And this is the result:
Options error: Unrecognized option or missing parameter(s) in server-21.ovpn:2: y (2.3.4)
Use --help for more information.
This is a variant of the config: The difference is that the secret key file name is ONE character shorter:
local 192.168.115.249
port 20021
proto udp
dev tap
dev-node VPN21
ifconfig 192.168.115.221 255.255.255.0
secret bcdefghijlkm-nopqrst-21.key
cipher AES-256-CBC
comp-lzo
; Hold tunnel with more strength
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
This gives following error:
Options error: You must define TUN/TAP device (--dev)
Use --help for more information.
This is a second variant of the config: The difference is that the secret key file name is ONE character LONGER:
local 192.168.115.249
port 20021
proto udp
dev tap
dev-node VPN21
ifconfig 192.168.115.221 255.255.255.0
secret aabcdefghijlkm-nopqrst-21.key
cipher AES-256-CBC
comp-lzo
; Hold tunnel with more strength
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
This gives following error:
Options error: Unrecognized option or missing parameter(s) in server-21.ovpn:2: ey (2.3.4)
Use --help for more information.
For the fun of it I tried:
local 192.168.115.249
port 20021
proto udp
dev VPN21
dev-mode tap
dev-node VPN21
ifconfig 192.168.115.221 255.255.255.0
secret abcdefghijlkm-nopqrst-21.key
cipher AES-256-CBC
comp-lzo
; Hold tunnel with more strength
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
Result
Options error: Unrecognized option or missing parameter(s) in server-21.ovpn:2: -tun (2.3.4)
Use --help for more information.
That machine does normally have 20 other TUN VPN's running, I tested removing those 20 configs and vpn devices, leaving only that single config there, and it still gives me that errors.
I tried 2.3.2 and 2.3.0, and they give me the identical result.
Version 2.2.2 (32 bit OpenVPN on a virtual 64 bit machine) works though, but it's not really good running that old-old-old version.
When I copy the config over to another working openvpn machine (on a different hyper-v cluster, version 2.3.0, using tun for the other VPN's) I get exactly the same results.
I tested whether the config is ANSI/ASCII or UTF: it is ANSI. I tested for weird characters (i.e. OpenVPN doesn't like tabs in config files), and still no difference.
Now: Is this a bug on my side and I missed something or is this a bug on OpenVPN side ? Or is tap not possible at all on 2008-R2 with Version 2.3.x?
