2.4.5 Snapshots are Live

jimp

@Gertjan said in 2.4.5 Snapshots are Live:

which is / should be fine because I'm loading, as you, the same bogons and bogonsv6 files ( 70 lines / 1136 Bytes and 108611 Lines / 1767 KB ).

His error is not the usual error for that condition. I can't load bogonsv6 on amd64 or arm with the same error. Read the redmine issue I linked above (#9356) and https://redmine.pfsense.org/issues/10254 which is what's happening on 2.4.5.

behemyth

Are the multiple times a day updates going to stay normal, or are you guys really pushing that many fixes to the RC still? I know I saw that you guys had an internal bug fix board somewhere, I'm just assuming all the updates are because of fixes from there.

jimp

@behemyth said in 2.4.5 Snapshots are Live:

Are the multiple times a day updates going to stay normal, or are you guys really pushing that many fixes to the RC still? I know I saw that you guys had an internal bug fix board somewhere, I'm just assuming all the updates are because of fixes from there.

The snapshot builds are now on a timer, and not triggered by changes. So even though a new one shows up every ~3 hrs that doesn't necessarily mean it contains anything new.

cybrnook

@jimp said in 2.4.5 Snapshots are Live:

@behemyth said in 2.4.5 Snapshots are Live:

Are the multiple times a day updates going to stay normal, or are you guys really pushing that many fixes to the RC still? I know I saw that you guys had an internal bug fix board somewhere, I'm just assuming all the updates are because of fixes from there.

The snapshot builds are now on a timer, and not triggered by changes. So even though a new one shows up every ~3 hrs that doesn't necessarily mean it contains anything new.

Is it best then to just keep an eye on the commit history: https://github.com/pfsense/pfsense/commits/RELENG_2_4_5

Then, when we see something that has been commited, it's safe to assume any timestamped generated update AFTER the commit contains the changes?

jimp

Essentially, yes, though it would also include changes in the freebsd-ports and freebsd-src repositories.

cybrnook

@jimp Yep Yep, naturally. Thank you Jim.

cybrnook

Just following up, been running 2.4.5 for the past few days. Nothing to report........

Intel E3-1275v5, Supermicro C236 based MB, Dual WAN, OpenVPN client to Mullvad, some port forwards, 3 VLAN's, few bits here and there... all working as expected.

johnsonmagnus

I upgraded a relatively new (~2 weeks since clean install from iso) 2.4.4 p3 installation to 2.4.5.r.20200317.1200 today via System --> Upgrade within WebGUI, mainly to benefit from the many security patches in 2.4.5.

I have just the Avahi & iperf packages installed, nothing fancy. Hardware is PCEngines APU2E4.

The upgrade went smoothly and rebooted with no problems. It has been only 30 minutes or so but everything appears to be working normally. Will update this comment if any problems appear.

louis2

Jimp,

I did the upgrade via shell command 13

I noticed, quick reading during startup scroll,

package pecl-radius reinstall i think
package net-socket same i think

routing invallid argument

After reboot and back in the gui pfSense is reporting 245 now just as it should be (was reporting 244 before, some halfway status)

There is no error message on the dashboard.

Louis

brcisna

@Gertjan

Does this fix this issue on recent updates from 2.4.4 to 2.4.5?
Updated (2) XG-7100 appliances two weeks ago,and have this problem with Captive Portal. Have never tried the Package patch addon but may give this a try?

Thank You

Gertjan

I can confirm that the patch :
@free4 said in 2.4.5 Snapshots are Live:

https://github.com/pfsense/pfsense/compare/RELENG_2_4_4...Augustin-FL:fix-reconfig-for-2-4-4.diff

is now retired, as of 2.4.5 based on FreeBSD 11.3 - the Tue Jun 02 17:51:17 build.

The patch cant' be used any more as the files to be patched don't match with patch.
Now, I can be 'stupid' and edit portal settings while portal user are connected.

free4

@Gertjan said in 2.4.5 Snapshots are Live:

I can confirm that the patch :
@free4 said in 2.4.5 Snapshots are Live:

https://github.com/pfsense/pfsense/compare/RELENG_2_4_4...Augustin-FL:fix-reconfig-for-2-4-4.diff

is now retired, as of 2.4.5 based on FreeBSD 11.3 - the Tue Jun 02 17:51:17 build.

The patch cant' be used any more as the files to be patched don't match with patch.
Now, I can be 'stupid' and edit portal settings while portal user are connected.

oooops
sorry, it's my fault. I thought I could delete my github repo safely

would you like me to restore the patch?

Gertjan

The initial issue is gone now.