Bug #954
closed
Switching to manual outbound NAT creates incorrect rule for PPTP server
100%
Description
When switching to manual outbound NAT when the PPTP server is enabled, it does not pick up any kind of IP address from the PPTP server, so the source address ends up blank. It also specifies a /32 subnet.
Somewhat related, I seem to recall the automatic rule specifying an IP address but also only a /32 subnet last time I checked it.
Updated by Erik Fonnesbeck about 14 years ago
It at least picks up an IP address now, but I'm not sure if it is the right one. It is also still using /32 for the subnet.
Updated by Ermal Luçi
Updated by Erik Fonnesbeck about 14 years ago
Any particular reason you set this to feedback? I'm fairly sure the issue is not fully resolved by just that one commit, which is why I did not change the status. (though that is only a guess; I have not tested it to be sure that it does not resolve this)
Updated by Chris Buechler almost 14 years ago
- Status changed from Feedback to New
- Priority changed from Normal to Low
Not fixed. It uses the server address rather than the client addresses.
Updated by Jim Pingle over 13 years ago
The internal automatic rule is wrong as well. Regardless of how many clients you have, the outbound NAT rule it makes when set on automatic doesn't have a subnet mask, so only the first connected client gets NAT applied when trying to reach the Internet from behind the PPTP connection.
Updated by Jim Pingle over 13 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 4e12754d1ae3405a8910686a7fa0bb012c01d8da.
Updated by Chris Buechler over 13 years ago
- Status changed from Feedback to Resolved