Pfsense 2.6 Captive Portal does not allow vpn connection established
I updated pfsense 2.5.2 to 2.6 with Captive portal enabled , after update I can not establish any vpn connection behind the captive portal but when I disable captive portal
my problem solves. whats the problem?
ótimo dia, eu aconselho você voltar a versão anterior, porque eu fiz também a atualização do pfsense em laboratório, deu tudo certo mas tem bugs do captive portal no pfsense 2.6, na verdade o pfsense 2.6 com captive portal ativado e cheio de bugs, ate então não atualizei de nenhum cliente, vou esperar eles corrigir esse bug, na verdade o bug e a seguinte forma, ele não libera as portas, não deixa pingar se você não liberar o ip no captive portal, sites não abre, claro isso depende de cada projeto que no meu caso uso proxy transparente junto com captive portal, não deu certo na versão do pfsense 2.6.
@bagherif Install the latest System Patches package and install:
Fix Captive Portal handling of non-TCP traffic after login (Redmine #12834)
My problem resolved with the patch .
Thanks for the reply
How do I apply this patch?
Where can I find instructions about?
Navigate to System > Packages, Available Packages tab.
Find System Patches in the list.
Click "+Install" at the end of its row, then confirm, to install.
The documentation for this package is still in the Development section and does not yet describe the new version, but the 2.x package will have a list of recommended patches. Just click Apply:
@steveits Great! I love pfSense.
hi everybody. I installed an new pfsense aplliance and did an import from the old applicance (2.5.1) I ran into the same issue but I still cannot establish vpn connection to a Microsoft VPN (l2tp) ist there a reboot required aft installing and acticating the patch or Is something else to do? I put a firewall Rule on the LAN Interface which allows all traffic from internal to external but still no luck.
Network it self is running using a browser. But ping for example to 188.8.131.52 is blocked
We would like to allow our customers everything from internal to external.
Thanks in advance for your answer.
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).
ping for example to 184.108.40.206 is blocked
Not an issue.
220.127.116.11 replies to DNS requests. No need to ping it.
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.