-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pull command seems to generate UNSUPPORTED OPTIONS #277
Comments
That |
dsommers
pushed a commit
that referenced
this issue
Apr 24, 2024
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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: