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