@viragomann Thanks for the advise. It worked finally. I just have a bit of doubt. After I created /30 and not added any remote networks, the server could not get an IP. It was fixed by adding remote IP on both ends which is strange cause if I only want to allow outbound IP without any inter-private routing, i don't need to specify it. This worked for shared-key setup but not on SSL/TLS.

I followed this Youtube tutorial https://www.youtube.com/watch?v=8f13lfnEKY8 and I believe it is the same as your setup. #1 Pfsense running 2 openvpn server instances (has corresponding network as remote network) #2 Pfsense running 1 openvpn client to Pfsense #1 (has both other networks as remote network) #3 Pfsense running 1 openvpn client to Pfsense #1 (has both other networks as remote network) I wasn't able to ping from the Pfsense #2 to #3 nor vice versa. Both #2 and #3 were able to ping to #1 But then I noticed it was only the Pfsense itself. Clients on Pfsense #3 could reach clients on Pfsense #2. Clients could also ping all pfsenses.... Client pfsenses can't ping clients on other network. In fact this is the main purpose of the site-to-site-to-site VPN, so I have it working now. I now have a few questions: Is this behaviour to be expected? What do I need to do so #2 and #3 themselves can ping each other? Should I consider this a bug? Is this a recommended setup? I have a feeling it isn't as #2 and #3 can't reach each other anymore if #1 is failing. Do I solve that single point of failure by creating a server instance on either #2 or #3, and let the other client connect to it??

@khris2fer No, that relies on being within the same subnet, as multicasts are used, which do not pass through routers.

@jimp I have tried at least a dozen different ways to get DCO to work and I can never get any traffic to flow once I switch the tunnel to DCO. I have tried taking existing tunnels and switch them to DCO, build a new one from scratch and tried DCO on both the client, server and both at the same time. I'm not sure if I am running into the iroute issue or what the problem is, the documentation is all for the non-DCO implementations and doesn't really apply here. One scenario I am trying to make work is a remote site connects to central hub, central hub has many sites connecting to it and uses DCO with QAT offload. Once the tunnel establishes, no traffic will flow thru the tunnel. I have tried policy based routing and static routes but neither seems to be working. I even tried setting up a very basic road-warrior VPN setup with no fancy routing at all, and the clients can't even ping across the tunnel to the VPN interface IP. Scouring the internet for working setups has not net any results so I was wondering if there is any documentation from netgate about how to actually do it "properly". Thanks!

Hi @viragomann, Where can I see VPN IP? Because only PfSense client (Branch Office) connected to PfSence Server (Head Office). No I can not ping LAN IP from Head office. I can ping only Pfsense which is in the BranchOffice. Yes I set it to /30 Yes both sides are green. Regards, Mucip:)

@kallabaz I am not sure, but I think that OpenVPN has a licencing scheme for both multiple servers and multiple users (?). Again, I am for no way sure, but I always had problems with openVPN. Maybe just use IPsec or wireguard if you are the only one remoting?

@wn7ant Sorry for 3 replies in a row... I tend to write as I see. But, [image: 1676831396971-2dc8ce97-7897-4096-af84-3821fbdc1ac0-image.png] this right here could be your issue, seeing as you might be behind another (CPE, yes, but) firewall. That means NAT with pfsense behind it. That means that you are not using a Public IPv4. Can't do OpenVPN reliably behind NAT, at least not with firewalls like PfSense as clients. Also, because of the way IPv4-NAT and IPv6-GUAs are routed, you might be having additional problems (and latencies) because of double NAT and a single IPv6 (/128) address on the WAN interface. WAN needs at least a /64 IPv6 subnet to perform either DHCPv6 or do Prefix Delegation on the ifaces downstream (eg, LAN). In the case of prefix delegation (which is strongly suggested), you need subnets larger than /64 (/60, /56, /52, /48). It's usually /48, but that is not a given (my ISP hands out /56's). If your environment isn't a VM lab, maybe try to contact your ISP and put the CPE modem/AC/router in PPPoE (or PPPoA) passthrough mode (the CPE will still be a WiFi AC and router for any clients connected on it, like phones, TVs, PCs and such) or bridge mode (the CPE will no longer be a router or a WiFi AC, but just a bridge for PFSense, the ISPs own VoIP and/or TV). That way, you can [image: 1676834205598-715ded1f-d443-402b-8b56-2a0f536ed32f-image.png] and here you usually you need your username and pass tied to your subscription account (you get those from your ISP) [image: 1676834366646-192e4609-eba1-486c-bfce-27f5c37692bc-image.png] In business environments, most ISPs give a static /32 IPv4 for free as an option (not advertising it, though). In that case, you might get them to give you a static /32 IPv4 for pfsense (through PPPoE/A passthrough) AND a dynamic (usually CG-NATed) /32 IPv4 for the CPE. Also, if you are situated in a VM lab, you not only need to give pfsense a physical interface (network card) passed-through by the hypervisor, but you also need this interface to NOT be behind a CPE (router-modem or just router). If that is the case, you will encounter a lot more problems down the road. As long as you do not do that, you are under the thumb of the ISP (they control the CPE's firewall) and must accept the limitations that come with this type of setup (UDP connections are notoriously unfriendly to NAT, some applications depend on a stable internet-facing port, you might be getting a CG-NATed address on the CPE, which makes any client behind pfsense triple NATed...)

@mikey_s I haven’t had the opportunity to try it yet but per https://docs.netgate.com/pfsense/en/latest/vpn/openvpn/dco.html: “Thus, DCO is beneficial even when only one endpoint is capable of DCO. That said, tunnels employing DCO on all peers will see the most benefit. With DCO on only one peer the performance improvement can still be notable but not as significant as the gains with DCO support on both endpoints.” That page also says it’s (still) experimental.

@viragomann Thank you so much. Yes. I did setup the gateway monitoring and indeed that was the fix. Need to set the default gateway to the multiwan gateway group i created.

@thomas_br Really wish there was a real solution for this. Sure I need to upgrade my device, but I also have a problem right now that Netgate is aware of but has made no effort to resolve without further service impact.

A few weeks ago I went through and tested LDAP auth with extended query in a few different LDAP setups with/without RFC2307 groups and updated the docs with better info on that and using multiple server entries limited by groups for these sorts of purposes. If you haven't reviewed the docs recently, look them over again. https://docs.netgate.com/pfsense/en/latest/usermanager/ldap.html https://docs.netgate.com/pfsense/en/latest/troubleshooting/authentication.html Also I highly recommend using an LDAP browser such as Apache Directory Studio to test your queries and settings to dial in getting the results you want.

@jims The traffic doesn't go through the WAN interface in a logical way. It is tunneled and come in on the OpenVPN interface in pfSense. Also the traffic cannot pass through a LAN device by default. This would require special settings on the device. Since I assume, you control this device, you can be sure that they are not done. The whole security depends on the VPN authentication, regardless how you realize the access to the LAN devices. The server is under your control, you say, so use strong password and client certificates and you're safe. On pfSense you can additionally configure, what the clients are allowed to access.

To answer this myself - I do not think OpenVPN user authentication failures from the pfSesne local database causes account lockout. SSH and Web UI failed logins will cause the source of the connection to be temporarily added to the block list. @jimp just answered this (as I type) to say it does not lockout the local database users. I have found, with help from Lawrence Systems videos (Tom L is a legend, n'est pas?) I can install FreeRadius package, and enable mobile one-time-passwords, add Radius users with OTP and get two benefits - disable accounts that fail to authenticate AND MFA/OTP. This satisfies UK Cyber Essentials, and I have a much stronger login process. Today is a good day.

Solved it, and now I can ping LAN IPs and do RDP etc. It was the devices on my LAN were not using the pfsense IP as their gateway, but a different gateway device. I didnt think all the target devices on the inside of the network needed the pfsence box as their gateway. It makes sence now. Also, a gateway IP is still not present for the openVPN connection, but connection to LAN devices and to the internet is working normally despite this.