What is taking so long for next update

[NollipfSense]

@provels said in What is taking so long for next update:

@NollipfSense FWIW, I've been running 2.5 w/o out major issues for a couple of months. I'd say the base case is quite stable. But there are too many environmental variables for you to see issues with features you do not use. I'd just install it and keep up with the snapshots and forum.

Thanks for the vote of confidence Provels, I'll do just that.

[NollipfSense]

@provels What a sense of relief when one takes the jump in the cold water!

[johnpoz]

And what was it in the 2.5 that you needed, that you could not wait til actually released? Curious...

[jimp]

@NollipfSense said in What is taking so long for next update:

I don't know much but to me, V.2.4.5 seems a waste of energy at this stage.

We have some hardware coming out soon that needs a new release which includes new code to support it, and 2.5.0 is not close enough to be done in time. Plus it's been a while since we made a release and there are plenty of important updates to get out to users.

[jimp]

There are still plenty of blockers left in 2.5. Limiters do not work properly, various interfaces are not behaving properly, and we need to move to 12-STABLE yet and shake out issues there. Plus all the remaining open issues we need to address. Some of those can be moved up, but not all of them.

[JKnott]

@jimp said in What is taking so long for next update:

We have some hardware coming out soon that needs a new release which includes new code to support it,

Any chance nut and APCUPSD will work properly with newer APC UPSs?

[NollipfSense]

@johnpoz Mainly it was Snort inline mode except for just want to help if I can, and anyway I can. So, now I have Suricata inline mode on WAN and Snort inline mode LAN.

[jimp]

@JKnott said in What is taking so long for next update:

Any chance nut and APCUPSD will work properly with newer APC UPSs?

If it's something fixed in the ports tree, maybe? We do not maintain the apcupsd port. If there is something it's missing in the port, it needs fixed there. From another recent thread I got the impression it was an upstream problem with the drivers. That isn't something we can really control.

2.4.5 has the latest quarterly ports branch (from a few days ago, 2020Q1), so if it's fixed there, 2.4.5 would have it. Otherwise, it'd need to be fixed in FreeBSD first and then we can maybe pick it back. That's not really a topic for this thread, though.

[JKnott]

@jimp said in What is taking so long for next update:

From another recent thread I got the impression it was an upstream problem with the drivers.

I knew it was upstream. I was just hoping the FreeBSD team had fixed it.

BTW, that other recent thread was likely mine. I bought a couple of new UPSs a few months ago and found that they worked fine with Linux, but not pfsense. The older UPSs, which they replaced, worked fine with both Linux and pfSense.

[NollipfSense]

@jimp My comment applied only to me...there was no guarantee that Snort 4.0 would work with V.2.4.5.