Opened 8 years ago
Closed 8 years ago
#793 closed Bug / Defect ( fixed )
man page for --proto
| Reported by: | krzee king | Owned by: | Gert Döring |
|---|---|---|---|
| Priority: | trivial | Milestone: | release 2.3.15 |
| Component: | Documentation | Version: | OpenVPN 2.3.9 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
there is no mention of udp6 / tcp6 here!
Change History (3)
comment:1 Changed 8 years ago by
| Owner: | set to Gert Döring |
|---|---|
| Status: | new → assigned |
comment:2 Changed 8 years ago by
comment:3 Changed 8 years ago by
| Milestone: | → release 2.3.15 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
commit 69c4e0640e076facaf8cd945833ea0b1078a836e
Author: Gert Doering
Date: Sun Mar 19 20:34:51 2017 +0100
Document --proto udp6, tcp6, etc.
will be part of 2.3.15, whenever that is going to happen
Patch sent to openvpn-devel list.
New text will read:
--proto p Use protocol p for communicating with remote host. p can be udp, tcp-client, or tcp-server. These will only try IPv4 to connect to the remote host. To use IPv6, add "6" to the protocol, as in udp6, tcp6-client, or tcp6-server. OpenVPN 2.3 can not auto-determine whether to use IPv4 or IPv6 (or automatically try whatever is available) - full dual-stack functionality is available starting with OpenVPN 2.4.0good enough? if yes, please ACK on the list, if not, please provide better text.