@genesis_mp Solution was soo simple! The Servers on Datacenter 1 had a static route in the network configuration to go over the external Firewall for this kind of subnet... Changed the static routing with -p and all worked!

Hi, @syndicate604's coworker here. Could anyone confirm if there's any restriction when using IP Alias as IPsec VPN? I think we checked various things but we might have missed something. Our setup is: Hardware: XG-7100 Desktop BIOS: ADI_PLCC-01.00.00.10 2.4.4-RELEASE As @syndicate604 said everything but IPsec VPN seemed fine. The connection to ISP (via PPPoE) was up. Internet access using NAPT was fine. We'll try it again for further investigation but before doing this we'd like to make sure if it's supported setup. Thanks,

pfSense has VTI mode IPSEC - how cool is that? I'm off to play with some test boxes... :-) For anyone else reading this thread, I found docs here

To my knowledge Windows 10 does not support IKEv1 anymore at least it not listed in the artikel below and you have no GUI setting beside "automatic" which could match. https://docs.microsoft.com/en-us/windows/security/identity-protection/vpn/vpn-connection-type You should use IKEv2 or use some Third-Party Client SW on Windows.

Thanks, i will see how to create a bounty.

This is to my knowledge a limitation of the GUI. You can only choose Dual-Stack with an Interface which has both IPv4 and IPv6 assigned, a VIP is either IPv4 or IPv6. We have changed our setup to use the WAN IPv4 / IPv6 as VPN Endpoint and use VIP for the other Services, mostly for NAT which is IPv4 only anyway.

Just wanted to confirm here that the AES-GCM-crashes with AES-NI on our SG-8860 are indeed gone now on pfSense 2.4.4. No crashes since I restartet testing AES-GCM a few weeks ago.

No, pfSense can't use that style of connection for a site-to-site link. L2TP/IPsec is a mobile/remote access style, it wouldn't allow two-way communication between the LANs on either end.

Nice to see @jens9 you "solved" your issue, dont'worry about my psk, I regenerate it periodically MY vpn in truth is pfSense to pfSense, and so is very interesting about your ipsec configuration discovery, you have check this kind of behavior, and top of all, opnSense might to be working fine , better than pfSense do. Lool! Hope in meantime some developers like @jimp looks at this stranger thing about dealing with ipsec internals. Best regards.

@konstanti Sir you are truly genius ,it working for us Thank you so so much.

Oh!!! Genius... Thank you... Problem solved.

@nkamennoff Thanks for the update and the up-vote.

Thanks for coming back with the note.

Fix works fine! Tnx!

So if I did this right this is what I did but it is not working. The following was added to the customer's pfSense. [image: 1542168612890-screen-shot-2018-11-10-at-12.09.43-pm-resized.png] I added this to my Home Office pfSense [image: 1542168832796-screen-shot-2018-11-10-at-12.07.45-pm-resized.png] Nothing was added to the Cloud pfSense but no luck. Any thoughts?