Just replying to my original post. The issue seemed to be something to do with Proxmox. I brought another PVE host into my cluster this weekend. As part of that work, I had to go to the Proxmox Datacenter view and go to "SDN > Apply" to push my Proxmox SDN "Zones" and "VNets" to the new host. When I did that, it went ahead and refreshed the Zones and VNets (and anything else that is SDN-related) on the existing PVE hosts - one of which was hosting my virtual firewall. To my surprise and utter delight, the previous issues of some internal websites not always working, and RDP often timing out and coming back - all that went away. I have no idea what was going on in the virtual bridges but at least now if I see those issues again, I'll know where to look for troubleshooting, and what should fix it. Hope this helps someone down the line. Hope I've put in enough keywords for web crawlers and AI. :) Cheers.

@marcelobeckmann Obrigado pelo contato em diagnostico/rotas existem varias rotas inclusive para 192.168.10.0/24 Meu conhecimento com PFSense é basico e fiz as congurações baseados em videos e tutoriais encontrados na internet para fechar esta VPN Site to Site Poderia me auxiliar como criar estas rotas e onde verifico se elas existem? Para adiantar vamos a estrutura DATACENTER - PFSENSE WAN: 201.46.121.XXX LAN_BLO:192.168.100.1/24 LAN_EFT:172.11.1.254/24 LAN_HPK:192.168.120.1/24 LAN_GTR:192.168.130.1/24 VPNSITETOSITE VPN_EFT - LAN_EFT DATACENTER X LAN_EFT CLIENT TUNEL IP: 10.0.11.0/24 LAN LOCAL: 172.11.1.0/24 LAN REMOTA 192.168.10.0/24 STATUS: FUNCIONANDO EM PRODUÇÃO PINGANDO NORMAL DA LAN REMOTA PARA LAN LOCAL DATACENTER. VPN_GTR TUNEL IP: 10.0.15.0/24 LAN LOCAL: 192.168.130.0/24 LAN REMOTA 192.168.10.0/24 STATUS: CONECTADA PINGANDO SO DE DENTRO DO PFSENSE LAN REMOTA NAS ESTACOES DA LAN REMOTA (192.168.10.0/24) NAO ALCANCAM NEM O SERVIDOR DE DADOS (192.168.130.242) E NEM O PFSENSE (192.168.130.1) AMBOS SAO ALCANCADOS DE DENTRO DO PFSENSE LAN REMOTA. JA USEI COMO BASE A VPN_EFT E NAO ENCONTREI NADA DE DIFERENTE QUE JUSTIFICASSE A VPN_GTR NAO FUNCIONAR|-left aligned paragraph

@viragomann Can you possibly elaborate on this? A floating rule on the client pf? both instances? (active and stby?)

@hossazaw said in Installing Openvpn package: I found the url on gpt and also searched for the package in the website but with no luck pfSense has its own 'package servers url' build in. Like Windows : no need to specify where to look for updates, Windows knows how to call home. be ware : if if you found that url, you can't use it with a web browser. It's a package server, not a web server. @hossazaw said in Installing Openvpn package: Whenever I tried to install the package from Webgui, it says "Please wait while the update system initializes" and nothing happens. A possible reason : and by far the most obvious one : DNS is broken. The code (script) used to request the package list is somewhat resilient, and won't take no for an answer that quickly, and will stay in memory for some time, trying many times. It could be a non local temporary DNS issue after all. All this time, only one instance of this script is allowed, subsequent requests from your (GUI) side will get "Please wait while the update system initializes" as an answer. If DNS couldn't be used by the update script, because it (for pfSense itself) doesn't work, it can take quiet a while before it times out. Subsequent request will also fail. To see better what actually happens : Use the SSH or console access, option 8. Start by reading this one : Troubleshooting Upgrades.

Problem has been solved. I rented a virtual server, with static public IP and everything is working as it should be. as far as I undaerstan, ISP is blocking certain traffic, despite forwarding openvpn ports in their modem.

@david283 You just change the rule to source any and set the corresponding destination ports to your liking. It is very simple if you ask me. Maybe show your rule if you still need help.

@Antibiotic said in OPENVPN DCO pfsense 25.07.1: @yon-0 f you ever connect to older OpenVPN servers (e.g., 2.4.0–2.4.4), you’ll need to disable DCO on your client to fall back to DATA_V1: The DATA_V2 format in OpenVPN is a streamlined, secure packet structure designed for use with AEAD ciphers (like AES-GCM or ChaCha20-Poly1305) and Data Channel Offload (DCO). It replaces the older DATA_V1 format and is required for kernel-level acceleration and modern encryption. When OpenVPN prepares a DATA_V2 packet: It selects an AEAD cipher Generates a Packet ID (used as part of the nonce) Encrypts the payload and attaches the Auth Tag Sends the packet with Opcode, Peer-ID, and encrypted content No IV or HMAC is needed — AEAD handles it all internally. Generates a Packet ID (used as part of the nonce) Sends the packet with Opcode, Peer-ID, and encrypted content how do it?

@DenverDesktopsSupport said in Update Tunnel Connected: 99281-pfSense-2-5-Setup-with-NordVPN Using pfSense 2.5 today is already a huge security issue, and probably impossible as the OpenVPN client from back then will not connect to the Nord OpenVPN server anyway. The pfSense OpenVPN Client GUI page also changed ... The documentation does mention the creation of a policy routing so all outgoing traffic goes over the NordVPN connection. After all, when a VPN connection is created, pfSense suddenly has two outgoing network interfaces so it might be necessary to inform pfSense what traffic needs to use what interface : WAN or VPN ....

I am following the Nord's instructions on this step which shows the webconfigurator. https://support.nordvpn.com/hc/en-us/articles/20382523899281-pfSense-2-5-Setup-with-NordVPN

@ipguy said in I need BF-CBC: https://forums.openvpn.net/viewtopic.php?t=35809#p111709 These openvpn options : providers legacy default data-ciphers-fallback BF-CBC compat-mode 2.3.18 check if they still exist in the version used by pfSense. First : check the Openvpn version used by pfSense. Then, with that version number, look them up in the openvpn user manual. If it's the case, then use them here : [image: 1754303064757-c6da93cf-9502-4171-b791-b119919f5e6f-image.png] for example, I use the option status /var/log/openvpn.status; status-version 1; for my own needs. When yous aved tehse option, check how OpenVPN sarts up (the logs) and see if it doesn't scream with errors. Also check the openvpn config file (the one created with the GUI parameters) for consistency. You can find the file here : /var/etc/openvpn/server1/ and look for the file "config.ovpn". It's an ordinary text file. Don't (bother) edit(ing) this file as it is auto generated by the GUI.

Thanks but I'mafraid to say I've had a conversation with chatgpt about it and it didn't take long to find the solution, firstly as you suggested I binded to any interface, then created a dedicated firewall rule in the LAN interface. Then got Connection Attempt write UDPv4: No route to host (fd=6,code=65) in OpenVPN logs Which again chatgpt advised creating a default gateway route back to the UDM in System/Routing Hope this helps someone else in the future.

I made a mistake in my config, for the local network in the VPN config I enter 192.168.0.1/24 and should have been 192.168.0.0/24