#16 closed Bug / Defect ( wontfix )
Problems mixing UDP- and TCP-based connection profiles with --auto-proxy
| Reported by: | Samuli Seppänen | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Configuration | Version: | OpenVPN 2.1.0 / 2.1.1 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
It's currently not possible to freely mix UDP- and TCP-based connection profiles. More details in comments.
Change History (4)
comment:1 Changed 15 years ago by
comment:3 Changed 13 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
As all these seems to be related to --auto-proxy. I didn't get access to the sf.net tickets, as they were closed. I'll close this ticket as --auto-proxy is removed from OpenVPN and will be tackled in the GUI instead.
comment:4 Changed 13 years ago by
| Summary: | Problems mixing UDP- and TCP-based connection profiles → Problems mixing UDP- and TCP-based connection profiles with --auto-proxy |
|---|
This issue has been discussed and reported on several occasions. From SF.net bug tracker:
In IRC meetings:
In mailing lists discussions: