-
I am going to ask a question that is on a lot of people's minds but not many if any have asked. When will the 2.5.0 snapshots be rebased to freebsd 12.1? thanks. It is 2020 already c'mon.
-
They'll be moved to 12-STABLE when they do move, and there is no ETA. We need to get 2.4.5 out first. So the usual answer: "Soon."
-
So going by the FreeBSD releases page, FreeBSD 12.0 was released in December 2018, and FreeBSD 12.1 was released in November 2019.
Is it mainly missing security updates, that would be a cause for concern?
Or other things, like driver support etc?
-
There are some fixes for Ipv6 we all hope for.
-
12.0 will be EOL very shortly, plus there are quite a few bugs fixed in (or after) 12.1 at the OS level that we need to pick up. We are moving to 12-STABLE at some point after 12.1, not 12.1 exactly. The details have not yet been finalized.
-
Also guys please keep in mind, that FreeBSD -RELEASE is not the same as -STABLE. Even if 12.1-RELEASE is dated 11/2019 that doesn't mean it's immediatly considered as -STABLE successor for 12.x
-
@jimp Last week, I moved my builds from 12.1 to 12-Stable and that went reasonably smooth. I'm current with the 2.5 changes (up to 1/14) and haven't noticed any issues. I'll continue to track the updates and let you know if something breaks.
-
@rschell Curious how you had upgraded to FreeBSD 12.1, and why you down grade back to FreeBSD 12 stable! Based on the discussion in this thread, it seems that pfSense v2.5 might not get release this year as the wait for FreeBSD 12.1 to get stable might take September or October or possible later.
-
@NollipfSense I was having issues with 2.5 regarding 6RD implementation of ipv6 tunnels. So I decided to test build my own version. Then discovered issues with the radvd port and 12.1, so I have fixed that as well. There are a few build wiki's out there if you choose to go that route, but not for the faint at heart. :-)
In release vernacular, my understanding is that 12.1 a close snapshot of stable/12 at a specific time and is behind the current version of stable/12.
-
There are a few build wiki's out there if you choose to go that route, but not for the faint at heart. :-)
I must say this statement got me nervous indeed, despite my naivety and willingness to learn. I am current running pfSense v2.5-dev and was wondering if I upgrade it to FreeBSD 12.1, what would happen. Do you have any links to the build wiki you mentioned?
-
@NollipfSense I've used two help guides, PiBi-NL's Building a pfSense.iso and Augustin-FL's Building pfSense iso from source. I'm currently using the later as I find it a little more straight forward.
Building the FreeBSD source of 12.1 or stable-12 requires applying around 170 commits from 2.5 to those sources and there are 7 or so commits that require resolution of merge conflicts. As I said, not for the faint at heart.
Unless there is something fundamentally not functioning in the pfSense v2.5-dev, there would not be much to gain. For me I wanted to explore ipv6 when my ISP only provides direct ipv4 but provides a 6RD tunnel for dual stack functionality.
I have a bare metal router as my main interface and use a Windows PC with two NICs to build a version pfSense. That PC runs three VM's to maintain the source, build and test. I found that using the Github Desktop was not viable, as Windows doesn't support the file naming conventions of some of the FreeBSD ports. So each of the VM's is running a current version of FreeBSD to avoid those conflicts.
-
-
@jimp Last week, I moved my builds from 12.1 to 12-Stable and that went reasonably smooth. I'm current with the 2.5 changes (up to 1/14) and haven't noticed any issues. I'll continue to track the updates and let you know if something breaks.
I'm not sure where to report these findings, so if there is a better place, move it there. Hopefully this is adding value, if not I can be silent. Since moving to the Stable/12 base, I have found to issues that will require further investigation, my tack has been to revert those commits:
-
MFC r339557 (5d9e751) on 1/16/2020 conflicts with Loos-br's a cherry-picked commit on the 2.5 branch (8b64875 on 2/15/2019). MFC r339557 pulls in a reference to uid which was placed into an if block in if_pflog.h by Loos-br. Since change just involved improving a logging message in Stable/12, I choose to revert the MFC 339557 commit.
-
The second commit I have had to revert is MFC r 355881 by hselasky on 12/25/2019, this commit makes a minor location change of a subroutine call in in6_mcast that causes radvd to again start to failing its IPV6_JOIN_GROUP call. I have tried debug this further without success so far.
Another observation, my VM installs work just fine, but my baremetal installs crash on the first boot:
--- trap 0xc, rip = 0xffffffff81063b46, rsp = 0xfffffe00248eda30, rbp = 0xfffffe00248eda50 --- pfsync_state_export() at pfsync_state_export+0x26/frame 0xfffffe00248eda50 pfsync_sendout() at pfsync_sendout+0x280/frame 0xfffffe00248edb00 pfsyncintr() at pfsyncintr+0xd1/frame 0xfffffe00248edb50 ithread_loop() at ithread_loop+0x1db/frame 0xfffffe00248edbb0The second boot works just find, the baremetal instance has a Openvpn server running. I don't have a HA configuration setup intentionally, not sure what's triggering the crash yet. Prefer not to rebuild it from scratch if I can avoid it.
-
-
It has been a few months and my original question still stands, When is pfsense 2.5 moving to 12-stable. Thanks?
-
Soon
-
Not helpful using a non-answer for everything time related.
-
It's the most useful reply you'll get for asking the same question repeatedly. When there is news, it will be announced. We're quite busy working on things trying to get 2.4.5 out, we also just released TNSR 20.02.
Be patient. Stop asking the same question so often.
-
I ask the same question because I never get an answer. When I don't get an answer, I loose hope. When I loose hope, I have to check back to try to get some hope. It is a cycle and only you can break it by giving me valid answers.
-
You have received an answer. The most valid answer you'll get.
Nobody is going to give you any kind of timeline because there is none. It will be ready when it's ready. We do not rush things like that.
-
So you are telling me you have no internal time goals to get projects done by. If so, how do you get your employees to do anything before it is obsolete also, you said you are pushing on 2.4.5. If you are pushing on it, then you must have an idea of when you want that released.
-
I'm sure we'd all love for it to be out already, but it's not ready, so "soon".
This conversation has vastly outlived its usefulness. We have better things to be doing (like working on pfSense)
Please refrain from wasting everyone's time with irrelevant and repetitive questions in the future.
