@viragomann That's exactly what I needed.... I made the change and tested...my public ip address matches my home address Thank you soo much!!!

@ikonomn most ISP routers will have a way to forward ports to an internal device (your pfSense) or set one as DMZ to forward all ports.

@mcury Oh, interesting (and sad).

I was able to enable CBC ciphers in the OpenVPN server and choose hw crypto for that as well. Can't tell if it works though. We will test and monitor CPU load etc for a check.

@nicp91-0
(I'm no pro, but...) I'm curious - did you ever try setting the gateway's monitor IP to the IP of the server you're connecting to?

Also, could be that since 9.9.9.9 is a DNS server, and some of these privacy VPNs might try to get you to use their DNSes (for privacy... maybe they block access to public DNSes like 9.9.9.9).

Fo my setup, I pinged the server name that's in the .OVPN file from the privacy VPN server and used that IP address in the gateway's monitor IP.

@gandalf33 said in OpenVPN TLS routing issue, shared key working fine:

iroute 192.168.0.0 255.255.255.0;

iroute does not work with DCO according to the docs.
So instead of this line try

route 192.168.0.0 255.255.255.0 10.8.11.2;

Ok. I've managed to fix it.
I used OpenVPN import functionality and it has imported the tunnel and it works as expected. Quite strange for me, but I compared the backups and it seems that the OpenVPN interface refuse to start when you put remote networks. Left the field empty allow the OpenVPN client to pull this settings from the server and it correctly set the needed IP address of the tunnel.

All good. End of story.

I still can't answer to myself why the OpenVPN daemon returned exit status 1 and quit without any warnings/errors when I tested it in the console.

This is a KI: https://redmine.pfsense.org/issues/13963

The "kldxref /boot/kernel" and a reboot resolved it.

@deviace
If I understand your request correctly, watch this video a few times. It's kind of tailored to "Privacy VPNs", but I think it might apply to your OpenVPN interface.

Youtube Video

It discusses setting up a "tagging" rule on all of your LAN interfaces/networks and then use a floating rule to act as a "kill switch" to prevent the tagged packets from going out the WAN.

In this approach, the default gateway is still set to WAN, but you set all your LAN/OPT/VLAN interfaces to use the OpenVPN interface.

Hope I'm not sending you on a wild goosechase.

i think i got it. i disabled DCO and that seems to have fixed it. i can now hit the remote local resources and dns entries over there work now as well..:)

@viragomann got that figured out. thanks. I am now having as different issue that i will start another thread for..thanks again.

The same behavior was on the second unit connected via VPN.
23.01 with enabled DCO on VPN tunnel breaks Traffic Graph.
Is any fix/bug available?

Dear all,
I've discovered with plenty of pleasure that is possible to split DNS traffic.
You just need to associate a zone to DNS :)
https://openvpn.net/vpn-server-resources/troubleshooting-dns-resolution-problems/
(-> "Split-DNS when using DNS Resolution Zones")

if you configure on your firewall (Pfsense or what else) that for a specific "intranet" zone you have to query a specific DNS, that's work!
I've verified directly on the firewall (.91 is my IP address from the OpenVpn assigned subnet)
tcpdump -i ovpns1 src 10.x.y.91 and port 53
DNS queries for xyz.lan appear in the dump otherwise not (ISP DNS are used)

683d84ef-76ed-4027-8246-33f818df2e0c-image.png

Although you'll have to use OpenVpn client... (with tunnelblick, e.g., it will not split DNS)

That's all I needed.

Thanks to all

@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,
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
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)
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...)