You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did found this closed case where that the issue with the pull command was mentioned as maybe being a bug. But I didn't found any extra info about this if this really is a bug that will get resolved in a future update or if this is an intentional change.
OpenVPN Connect 3.4 now uses version 3.8 of this packet and that's why I'm only bitten by this issue right now.
```
Sat May 6 13:42:33 2023 UNKNOWN/UNSUPPORTED OPTIONS
Sat May 6 13:42:33 2023 13 [pull]
Sat May 6 13:42:33 2023 14 [route-delay] [2]
Are the optiosn the opnevpn3 core does not like. ``pull`` seems a bug. replace that with ``client`` for now.
_Originally posted by @schwabe in https://github.com/OpenVPN/openvpn3/issues/271#issuecomment-1537218405_
The text was updated successfully, but these errors were encountered:
That --pull in the client configuration triggers an unknown option is a bug. Please also reports issues with the Connect client via support.openvpn.net as that tis the only way to raise issues with the Connect client.
Config
client
pull
was not correctly handled like client + tls-client
since the code short-circuited if tls-client wasn't set
and so didn't touch pull option.
Github: #277
Signed-off-by: Frank Lichtenheld <[email protected]>
Hello,
I did found this closed case where that the issue with the pull command was mentioned as maybe being a bug. But I didn't found any extra info about this if this really is a bug that will get resolved in a future update or if this is an intentional change.
OpenVPN Connect 3.4 now uses version 3.8 of this packet and that's why I'm only bitten by this issue right now.
Sat May 6 13:42:33 2023 UNKNOWN/UNSUPPORTED OPTIONS
Sat May 6 13:42:33 2023 13 [pull]
Sat May 6 13:42:33 2023 14 [route-delay] [2]
The text was updated successfully, but these errors were encountered: