So you had messed with your outbound nat like I brought up way earlier in the thread.. If your outbound nat is automatic when you run through the openvpn wizard it will add your tunnel network to the nat.. Did you switch to automatic, or did you create some nat - mind posting your outbound nat screen..

@onyxfire reason I set it to hybrid is because the few youtube videos posted for xbox and Double Nat Type for pfsense said you need to set it for this and then set a bunch of ports but it never helped in the end.. ill worry about that later... as for the alias ah cant be bothered I just have xbox one and 360 and a ps3 but only xbox one hooked up as for the wizards I see it now I didn't see it before.. also with dyslexia I miss read words.. like "mother" I sometimes read as "hello" reason why I need to re read things 3 4 times or so sometimes bad case I have.. and reason I was using cell phone was easier for me to take to tim hortons or home depot and test the OpenVPN then taking the laptop in the store and then I installed Ping program so I could see if I could ping my local network least then I could test with a laptop.. as I originally wanted to do Remote desktop server1.example.com remote desktop server2.example.com but was told I idiot no point In setting it up you need vpn as I been doing like 3389 port for server 1 3391 port for server 2.. and I didn't wanna do port forwarding anymore I wanted to connect like I do at home or least have reverse name look up I think its called like remote desktop server1.example.com @johnpoz and sorry I didn't see the wizard you mention ill try again.. I miss read the screen..

You could enable a feature on the server side that requires OpenVPN 2.4 and then older clients would fail to connect. Harsh, but that's about the only way you could require a minimum version from the client end.

It was a bad source configuration at my VLAN over WAN, I had WAN instead. Thanks anyway!

Firewall > Rules, WAN tab, edit that rule, pick UDP for the protocol, save, apply Update to the latest version, that bug has already been fixed in 2.4.3-p1, released a month ago.

@mightyschwartz Hi, did you ever find a solution for this? I know this is an old topic but I'm having the same issue... Thanks, B.

Figured it out. You have to have a separate "user" cert and a separate "server" cert. Doh!

Ok, I think I get it now, It confused me when the VPN is added it appeared to 'cutoff' the normal traffic from LAN to WAN Dave.

Would need more info to offer more targeted troubleshooting help, but a few gotchas that I've seen and learned: Once you assign the tunnel to an interface, make sure you bounce the tunnel afterward If you're running a remote access server, edit the rules on your OpenVPN tab so the source address is explicit to your tunnel network. Otherwise, incoming traffic will match on the wrong interface. In other words, if there's an any/any rule on your OpenVPN tab, either remove it or modify it so the source address is explicit to the other services you are trying to run (e.g. a remote access server or another tunnel) Verify your Outbound NAT mode is in either Hybrid or Manual and that you have NAT mappings NAT'ing egress traffic to the PIA address on the PIA interface. Verify your port forwards are configured on the PIA interface and have a Destination Address of your PIA address Verify the policy routing rule on your LAN tab is configured with the correct source address, has the PIA gateway and is above your LANnet/any (or any/any) rule that would otherwise send the traffic out the default gateway.

Fixed. Thanks for pointing it out.

Yes, you are correct.

While i was testing out the exporting from pfsense 2.2.4 to 2.3.5 i got the certs working just when i connect i keep getting that auth failure, i even copy and pasted the password thinking i was going mad crazy. Pictures: pfSense 2.2.4 [image: 1528744936318-cfff7347-95d8-4806-84cc-308d34a310c8-image-resized.png] [image: 1528745213313-clipboarder.2018.06.11-resized.png] pfSense 2.3.5 [image: 1528745034722-clipboarder.2018.06.11-005-resized.png] [image: 1528745034637-clipboarder.2018.06.11-004-resized.png] [image: 1528745034553-clipboarder.2018.06.11-003-resized.png] Error: [image: 1528745151952-clipboarder.2018.06.11-006.png] Thank you

I guess your right, tried on my test enviroment 2 pfSense boxes both running 2.3.5 and the Site 2 was using its own WAN rather then using Site 1 WAN

No. I do not have Rogers. If you packet capture on WAN for port 443, attempt a connection, and it arrives, the ISP isn't filtering it. If it doesn't arrive they are or someone else is.

@grimm-spector Exactly, it will work just fine :)

Yeah not a big issue, when you need to install into something that wants to see a password you can just add it via openssl.. Was just curious - thanks. When your wanting your ios phone to connect to a eap-tls wifi network it wants a password. It will not take blank, and space doesn't work, etc. Not a big deal if doing a handful.