Project

General

Profile

Actions

Bug #7062

closed

OpenVPN 2.4 treats "udp" and "tcp" as dual stack now, move old preference to udp4/tcp4

Added by Jim Pingle over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
OpenVPN
Target version:
Start date:
01/01/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4
Affected Architecture:
All

Description

OpenVPN 2.4 changed the meaning of "udp" and "tcp" to be dual stack, listening on IPv6 on all interfaces at once. "local" can still nudge the behavior but to preserve the user's choice, it's safest to move the user preference to udp4/tcp4 which reflect the previous behavior.

Also it's a good time to introduce "multihome" for those who want to run dual stack which will make OpenVPN reply from the address it received the packet on.

To me, I have a patch

Actions #1

Updated by Jim Pingle over 4 years ago

  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Jim Pingle over 4 years ago

  • Status changed from Feedback to Assigned

This apparently still needs one more change. The IPv6 only modes need:

bind ipv6only

Actions #3

Updated by Jim Pingle over 4 years ago

  • Status changed from Assigned to Resolved

OpenVPN's man page and docs say it should work but it tosses an error on the bind directive.

It appears to do the correct thing anyhow without it, only binding to what was chosen since it's declared explicitly.

Actions

Also available in: Atom PDF