To 2.5.1 or not ? that is the question :)

chudak

@waqar-uk

I do the same, but kinda counter-playing now to do a fresh pfBlockerNG install, still don't have guts to wipe out all old settings

SteveITS

The PHP core dump on SG-3100 with some packages is not listed as a known issue but presumably still exists...

MoonKnight

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

Was encouraged buy quick feedback and went for it too :)

My updated was fast and smooth.

But I still see a minor unbound oddness, when after reboot DNS did not seem to be resolving well, even tho no apparent error and service shows as green. Unbound restart fixed this.

I notice the same on version 2.5.0. I haven't upgrade to 2.5.1 yet. But I use Watchdog now, so it helps after a reboot most of the time :)

gkovachev

My setup is 2x WANs, 1x LAN. After upgrade from 2.5 to 2.5.1 port forwarding stoped working on non default WAN2.
The strange thing is that in 2.5 in my setup, port forwardings on both WANs were working just fine.

In 21.02.2/2.5.1 New Features and Changes there is a fix:
Fixed: State matching problem with reponses to packets arriving on non-default WANs #11436
which in my case did the opposite :) Broke working setup.

bmeeks

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

The PHP core dump on SG-3100 with some packages is not listed as a known issue but presumably still exists...

If you use one of the three packages known to be impacted by that bug (Suricata, Snort or pfBlockerNG-devel), and having one or more of those packages running is critical for you, I would suggest not updating yet. To the best of my knowledge no work has been done on the PHP crashing issue on ARM 32-bit hardware.

Bismarck

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

2.5.1 wippend out my root partition, recovering right now...

/edit

Back to normal operation again, now 2.5.1 runs here fast and smooth as well.

swampkracker

Flawless upgrade from 2.5.0 to 2.5.1. Everything is working as it should.

vjizzle

Upgrade went smooth on my pfsense CE. I am running several VPN clients tunnels with routing groups and so far all is working well.

Qinn

Smooth update to pfSense 2.5.1 CE

pietsnot56

Smooth update on J3160 system.
Only I can not start up iperf.
why?

provels

@pietsnot56
Same here, but a quick reinstall fixed it.

EDIT - Whoops, stopped.

EDIT, EDIT... Rolled back to 2.5.0, iperf still doesn't start. So there's that...

MoonKnight

I just updated to 2.5.1.
Some issues here. I have a Plex Server running on another computer. I have VPN running on that one with port-forward and policy routing. The port-forward doesn't work anymore. But the computer can still access Internet with the VPN.
But the only thing that doesn't work is the port-forward :(

Another issue is the DNS Resolver. After reboot of the firewall, i don't have access to internet. Only the computers that have static IP on the interface. I cant access any device using the dns. I have to restart unbound. After that i can access computers with the dns.

The DNS problems was on version 2.5.0 also but not the port-forward problem.
The DNS problems seems to appear when i have multiple VPN Client running. It could be some bad configuration from my side, but it has always worked on version 2.4.5. It starts on version 2.5.0.

So, i'm planing to move back to 2.5.0 or even 2.4.5p1 (not sure when)
To bad i can't run my Plex Server anymore with VPN and port-forward(so my plex server is online and accessible outside my network)

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.