Bug #13848
closed
OpenVPN Client Breaking Outbound NAT
Added by AJ Harran over 2 years ago.
Updated over 2 years ago.
Affected Plus Version:
22.05
Affected Architecture:
SG-2100
Description
Issue occurs on vanilla out of the box appliance.
Configuration:
- VLAN 35 added to mvneta0
- PPPoE Dialer added to mvneta0.35
- SFP Module (for GPON) inserted into SFP port
- Tested connectivity
- Imported CA for OpenVPN
- Added OpenVPN Client
Issue:
Outbound NAT stops and loss of internet connectivity. Issue is circumvented by either stopping OpenVPN daemon, incorrectly spelling host or deleting Client configuration.
I have this exact same setup on an old Sophos XG86 running CE 2.6 and also virtualized the time before that without issue. Same WAN configuration. I purchased the 2100 last night for my home network and have been troubleshooting this issue for a few hours today.
Next steps:
- Downgrade to 22.01 to CE 2.6.0
- Use media converter to see if issue persists with RJ45 port instead of SFP port.
Files
Downgraded to 22.01 and OpenVPN Client works as expected.
AJ Harran wrote in #note-1:
Downgraded to 22.01 and OpenVPN Client works as expected.
Hello AJ,
Can you please provide a sanitized version of your OpenVPN Client config and/or screenshots of your OpenVPN Client config in pfSense with the sensitive portions blacked out?
Also, I'm assuming VLAN35 in your config is a WAN interface on VLAN35 for your provider with a PPPoE uplink? Am I understanding that correctly?
Here you go Kris. All the same settings while using 22.05
- Status changed from New to Rejected
- Priority changed from High to Normal
As stated, the issue cannot be reproduced, and is likely something in your specific configuration or environment. This site is not for support or diagnostic discussion, so it's not the place to dig into the details of what is failing in your specific case.
For assistance in solving problems, please post on the Netgate Forum .
If a bug can be identified after that and it can still be reproduced on 23.01, then a new issue can be opened with more specific details on how to reproduce.
See Reporting Issues with pfSense Software for more information.
Hello Jim, this issue was raised as per TAC (Kris P). I am not looking for configuration support, however, I am able to replicate this issue only on 22.05. Issue does not occur on 22.01 nor does it occur on 2.6.0.
Let me know if that clarifies the issue and if this is an actual bug as it only occurs on 22.05.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
