To 2.5.1 or not ? that is the question :)

vjizzle

@ciscox
Hi! Your post triggered me to check if my port forwards my VPN clients were working and they are not :(. Reconnecting the VPN's and even rebooting pfSense does not fix this. Looks like port forwarding on OpenVPN interfaces is broken.

I will try and do more testing later on. WFH so I can't break the internet for now.

MoonKnight

@vjizzle said in To 2.5.1 or not ? that is the question :):

@ciscox
Hi! Your post triggered me to check if my port forwards my VPN clients were working and they are not :(. Reconnecting the VPN's and even rebooting pfSense does not fix this. Looks like port forwarding on OpenVPN interfaces is broken.

I will try and do more testing later on. WFH so I can't break the internet for now.

Hi, thanks for checking this up. :)

Dredex

After upgrading to 2.5.1 non default WAN is not working...
Worked fine in 2.5.0

fireodo

@bismarck said in To 2.5.1 or not ? that is the question :):

Excellent!

Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM

I got these in dmesg too on boot since update to 2.5.0 and present in 2.5.1 too - should I worry?

Regards,
fireodo

Bismarck

@fireodo Only when it's stuck with this message, like in my case where I couldn't boot anymore.

After a fresh install and config.xml recovery, the system booted again but the messages "Root mount waiting for: CAM" still apears aprox 4 - 5 times.

dmesg | grep CAM
Root mount waiting for: CAM usbus0 usbus1 usbus2
Root mount waiting for: CAM usbus0 usbus1 usbus2
Root mount waiting for: CAM usbus0 usbus2
Root mount waiting for: CAM usbus2
Root mount waiting for: CAM usbus2
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM

fireodo

@bismarck said in To 2.5.1 or not ? that is the question :):

@fireodo Only when it's stuck with this message, like in my case where I couldn't boot anymore.

Thanks, it don't stuck here. I got that 5 times in dmesg with my SSD and after changing to HDD it comes also 5 times ... but boot is not affected.

Yanik

After 2.5.1 my port forwards are not working.
They were fine at 2.4.5 and 2.5.0.

vjizzle

@bismarck Same here. I can see the same CAM messages but system boots fine.

vjizzle

@yanik Do you mean port forward on OpenVPN interfaces? That is what I am experiencing.

Port forwards on WAN seems to work fine here.

Yanik

@vjizzle

Yep, vpn port forwards.
I can reach my server through Lan IP but cant from outside (domain).

vjizzle

I can see in my firewall logs that the ports I forwarded from the OpenVPN interfaces are being blocked. I can allow them using the + sign there (Easy rule option) and they do appear on the firewall rules on that specific OpenVPN interface but it still does not work.

On that specific OpenVPN firewall tab I can see my original port forward rule is also there, beside the Easy rule I just added. But none of them are working it seems.

Dredex

I have dual WAN configuration and port forward only works on the default gateway.
For me upgrading from 2.5.0 to 2.5.1 broke port forwarding on non default gateway.

Yanik

@vjizzle

my port forwards pass the firewall rule, no blocks but when i check states its "CLOSED:SYN_SENT".

MoonKnight

@vjizzle said in To 2.5.1 or not ? that is the question :):

I can see in my firewall logs that the ports I forwarded from the OpenVPN interfaces are being blocked. I can allow them using the + sign there (Easy rule option) and they do appear on the firewall rules on that specific OpenVPN interface but it still does not work.

On that specific OpenVPN firewall tab I can see my original port forward rule is also there, beside the Easy rule I just added. But none of them are working it seems.

Yeah same her. Maybe it's time to report it. Make an bug-rapport. Can someone please add it on the bugtracker.

vjizzle

@yanik I can confirm the same CLOSED:SYN_SENT when I check the states. So far the 2.5 line of release is showing interesting behaviour. Every upgrade is a new adventure in squashing bugs....yay!

Yanik

@vjizzle

while tried to decide pfsense vs opsense. I choose pfsense because of stability :D

vjizzle

@yanik Me too! Well let's give the dev's time to fix this. In the meantime I am planning to do a clean install of 2.5.1 and the restore my config. If that does not work I will revert back to a clean install of 2.5 and then restore my 2.5 config. I will make some time tonight to do this and I will post my updates here.

MoonKnight

@vjizzle

We can continue here: https://forum.netgate.com/topic/162952/port-forwarding-on-openvpn-interfaces-is-broken-on-2-5-1

Yanik

@vjizzle

Good luck :)..

Sure devs will fix this but i hope it wont take much time. at least a patch would be nice.

cellobita

@yanik Add me to the "Port forward works only on interface with default gateway, does not work for alternative wans" victims list...

I know, I know, "pfSense CE is free", blah, blah, blah, but it is also undeniable that pfSense CE (formerly just plain pfSense) is, today, quite far from the rock solid firewall distro of a few years back, when I used to upgrade without any trepidation.

Also, the fact that this very serious bug has been fixed in the commercial version, but not the free one (did no one at Netgate notice that the fix was relevant for CE also?!?!), makes me wonder...