The lport directive in config file being ignored
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 467
- PR merge metrics
- No merged PRs in 30d
Description
I have config which requires the use of the lport directive but openvpn3 as well as openvpn2 completely ignore it. Log for both shows the lport as being an unused option -
2021-10-22 17:55:47 Client DEBUG: UNUSED OPTIONS
4 [resolv-retry] [infinite]
5 [lport] [58137]
I am using OpenVPN 3/Linux v16_beta version on ubuntu bionic.
The same config works fine with openvpn 2.4 but it needs to run with sudo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the configuration on OpenVPN 3/Linux v16_beta using Ubuntu Bionic and compare its handling with OpenVPN 2.4. Start from the lport option reported under UNUSED OPTIONS and trace why it is not applied. Done means lport is recognized and honored without the option appearing as unused, with the behavior verified against the provided configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100