Project

General

Profile

Actions

Bug #1216

closed

OpenVPN client interfaces should not be NATed out of when assigned

Added by Chris Buechler almost 11 years ago. Updated over 10 years ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

outbound NAT is applied on OpenVPN client interfaces when they are assigned, and should not be. Routing is almost always the desired behavior, and assigning the interface shouldn't change that behavior.

Actions #1

Updated by Chris Buechler almost 11 years ago

to clarify, that is the tun interfaces are included as "nat on ...", though possibly only where the tun interfaces are assigned.

Actions #2

Updated by Chris Buechler almost 11 years ago

  • Subject changed from OpenVPN client interfaces should not be NATed by default to OpenVPN client interfaces should not be NATed out of when assigned
Actions #3

Updated by Ermal Luçi over 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Ermal Luçi over 10 years ago

  • Status changed from Feedback to Resolved

This is fixed since we have people on forum complaining for the now missing nat.

Actions

Also available in: Atom PDF