@jimp I tried but unfortunately it didn't work, because the User Certificate that I use for export the OpenVPN Client have the same CA that the server certificate (I think). The final solution was to reinstall all OpenVPN clients on all devices, hard work but at least all users continue to work! Thanks for the support

@stephenw10 Yes it is. And I disabled vmware virtual network local dhcp ANd it works. Thank you for your patience ! You really helped me out on this, have a nice day/night [image: 1687387415421-c3e53068-4ad2-4014-9e91-1c1ec4ab18d3-image.png]

@gertjan Hey there! Thank you for taking the time to reply! I figured out what happened after taking another stab at it. Manually assigning the ports did the trick. I was able to setup the router after that.

@przemyslaw85 dzięki za odpowiedź. Jedynie zacząłem używać czasami wireguarda na komórce. Do stronki www mam wykupiony hosting. Póki co mam zintegrowaną kartę intela + tplinka ale chcę kupić właśnie jakąś intela. pfBlocker jeszcze nie konfigurowałem (używam snorta) Mój PC (router) to dell optiplex 7010 i5-3570 16GB ram i SSD 256GB Pozdrawiam

Yeah just do that. It is possible to disable the pkg reinstall process but not in any easy way. For example if you interrupt the boot and go into single user mode you can remove the 'needs_package_sync' file from /conf. If you're running ZFS that's a bit involved but possible. https://docs.netgate.com/pfsense/en/latest/troubleshooting/single-user-mode.html#single-user-mode-zfs You could probably also comment out the check in rc.bootup but that's likely more error prone. Steve

@marcelobeckmann O problema foi resolvido quando liberei as portas 1194 na LAN e no OPENVPN, nas regras do firewall dos dois PFsenses. Após isso, as VPN começaram a fechar a conexão e consigo pingar entre os servidores. Muito obrigado pela ajuda.

pfSense will only allow access from the WAN side by default if there is only one interfaces assigned. As soon as you assign two of more interfaces all connections to WAN are blocked by default and you need to add WAN firewall rules to allow them.

@qssysadmin How does your question relate to the captive portal ? ( you posted in the captive portal section of the forum ) A reboot is always mandatory as you changed the kernel version (a kernel can't be reloaded in place). @qssysadmin said in Pfsense 2.6 Captive Portal does not allow vpn connection established: ping for example to 8.8.8.8 is blocked Not an issue. 8.8.8.8 replies to DNS requests. No need to ping it. @qssysadmin said in Pfsense 2.6 Captive Portal does not allow vpn connection established: I put a firewall Rule on the LAN Interface which allows all traffic from internal to external The default LAN firewall rue permits everything. No extra rules needed.

For anyone else finding this thread. I've found the solution. Create a port forwarding rule INTERFACE: WG0 PORT: 44158 DESTINATION: WG0 DEST PORT: 44158 REDIRECT TARGET IP: MINER IP REDIRECT PORT: 44158 Then everything works as expected.

Hmm, yup. Checking....