Actions
Bug #1216
closed
OpenVPN client interfaces should not be NATed out of when assigned
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.
Updated by Chris Buechler almost 14 years ago
to clarify, that is the tun interfaces are included as "nat on ...", though possibly only where the tun interfaces are assigned.
Updated by Chris Buechler almost 14 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
Updated by Ermal Luçi almost 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset a1d52f81879fc1f2253eeef5189adfa2e6396c11.
Updated by Ermal Luçi almost 14 years ago
- Status changed from Feedback to Resolved
This is fixed since we have people on forum complaining for the now missing nat.
Actions