Skip to content
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

Open
Robby-Swartenbroekx opened this issue Jul 17, 2023 · 1 comment
Open

pull command seems to generate UNSUPPORTED OPTIONS #277

Robby-Swartenbroekx opened this issue Jul 17, 2023 · 1 comment
Assignees

Comments

@Robby-Swartenbroekx
Copy link

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]


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_
            
@schwabe
Copy link
Contributor

schwabe commented Jul 17, 2023

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.

@flichtenheld flichtenheld self-assigned this Mar 8, 2024
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants