OpenVPN / OpenVPN/openvpn3

pull command seems to generate UNSUPPORTED OPTIONS

Open
#277 2 comments 0 reactions 1 assignee View on GitHub

@flichtenheld is already working on this.

Since Mar 8, 2024.

Dominant language
C++
Stars
1.2k
Forks
467
PR merge metrics
No merged PRs in 30d

Description

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_
            

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.