Use policy routing https://docs.netgate.com/pfsense/en/latest/routing/directing-traffic-with-policy-routing.html https://docs.netgate.com/pfsense/en/latest/book/multiwan/policy-routing-configuration.html

@CNLiberal said in Solution for Multicast Over Tunnel: haven't found decent OpenVPN software for the Mac yet. On this point, the client linked on this page from the OpenVPN Access server docs, in my experience, works fine with an OpenVPN server on pfSense. Just import the standard config. I have not tried this with a tap connection. I used the 2.7 version, and haven't tested the 3.1 beta. The page also mentions alternate clients. https://openvpn.net/vpn-server-resources/connecting-to-access-server-with-macos/

We are aware, but that is unstable and runs in user space and cannot be anywhere near as fast as if it were in the kernel like it is on Linux. It's not worth including until it's done properly.

Thanks, I will look into setting up OpenVPN instead.

All of those links take me to a page that requires login on aliexpress. Is there any reason the official netgate solution wouldn't work for you? I'm not sure if the SG-3100 would work for the home, office and guest setup using the LAN and OPT1 interfaces. Not sure if the RT-AC87u setup as an access point with a separate guest login would prevent the guest users from accessing the rest of the LAN it's connected to. My feeling is it wouldn't so you might need another interface and AP for the guest if that's the case (SG-5100). If price is an issue, I hear good things about the apu2 platform.

I could not find my previous post, I thought it was not posted properly, now I found it but can not remove this one... please Admin, remove it and pardon my mistake

@Pippin Thank you for the reply. I went into VPN -> OpenVPN -> Clients and edited my client's configuration. Under Advanced Configuration I put into the custom options "ns-cert-type server; persist-tun; persist-key; mssfix 1400" and then saved. I then reloaded the VPN by going to Status -> OpenVPN. I did the usual ping/nmap verification checks to confirm connectivity. However this does not seem to have done anything. Below is a picture of the wireshark output (with the TCP stream from the browser being currently selected) and below that is the capture file. mssfix1400_full_cap.pcapng

We have been working on this in support and currently believe it's a missing setting in AWS somewhere. Steve

@KOM ok thanks will try that

Show your OpenVPN Config and Firewall Rules (Screenshots). -Rico

Thanks Pablo. Good to have in case we ever move to an HA setup with Google VPN. For anyone else that reads this, my posts were for the Classic Google VPN setup (non HA). One note I wanted to add, in the BGP settings in my instructions above, don't change the setting for "Redistribute connected networks" to Yes. When set to Yes this advertised our WAN network to Google and caused issues with hitting public facing servers we had in Google. Since we only have a few networks locally, I just manually defined those along with the BGP network 169.254.10.0/30 in the fields below that setting. The other option may be to change the setting to Yes and somehow mark it to ignore the WAN network, but I haven't looked into that.

ah ok i added a Fall over for P2P so if Nord Goes down it cant leak internet and start using the WAN.. had to adding a Floating Rule... this way IF Nord goes down i can still use internet but it denys it to the P2P and my guest network router

After contact with microsoft helpdesk I found the solution for me. For future reference: I had to turn on mss clamping and set it to 1350. This is also in the advanced IPSec settings Maybe this settings was defaulted after an update? I wasn't the one who configured it in the first place, so I wouldn't know for sure. I made sure to match my settings to this document https://docs.microsoft.com/nl-nl/azure/vpn-gateway/vpn-gateway-about-vpn-devices @stephenw10 Thanks for the reply, I had this disabled already, but the pointer was appreciated

Solution can be found here: IIPsec to Mikrotik

Hi, your machines uses s.o windows ? in that case turn off the firewall each and check pin to the other machine

@treborjm87 I'd be curious about this as well... I think you need to establish how much throughput/bandwidth you need and how many concurrent user connections you anticipate, etc? (Is this box dedicated to routing and VPN only or more exotic use cases like running VMs, etc) I've seen some charts floating around with hardware recommendations based on required throughput here and at the servethehome website.

https://www.netgate.com/docs/pfsense/virtualization/virtio-driver-support.html

Yes, nothing will change unless you change it. For example: https://www.netgate.com/docs/pfsense/book/openvpn/openvpn-and-multi-wan.html Steve

I am disappointed in this forum because not one suggestion was offered. Usually, community support for stuff like this is pretty good. Regardless, I figured it out myself. This thread can be considered closed.

I stand corrected! ~Mat

@patrick0525 If you're completely certain that nothing on your end changed, it stands to reason that maybe something on their end did? I'm not familiar with the provider, but have you checked to see whether they have an updated configuration guide? Have you tried connecting to them from a PC instead of the pfSense machine? If they support TCP as well have you tried that? Just a few thoughts for preliminary troubleshooting steps.

@medikopter said in OpenVPN TLS Fehler: Das klingt ja eigentlich ganz cool und simple, allerdings scheitere ich schon an der Umsetzung eines Failover. Nunja, aber das sind ja auch zwei verschiedene paar Stiefel ;) VPN auf beiden Interfaces zum Laufen zu bringen ist wesentlich leichter, weil du nichts umschalten/routen/sonstwas musst. Daher überhaupt nicht schwer. Also das er das Interface automatisch wechselt wenn eins Down ist. Es genügt doch eine Gateway Gruppe zu machen und die bei den Regeln auf dem LAN einzusetzen?