pfBlockerNG-devel 3.2.16_1?

rpotter28

@fireodo I too noticed that, and I too have not been able to find any info on it.

pfsjap

@stephenw10 Can you provide information about this update?

Gertjan

@pfsjap said in pfBlockerNG-devel 3.2.16_1?:

Can you provide information about this update?

For those who can't wait :
Copy the folders (directories) used by pfblockerng, for example this one :

to /usr/local/pkg/pfblockerng-copy

Now run the upgrade.
Then, run the diff command on these two folders, and you'll have the result

A dot or underscore release, imho, a very minor modification, it wouldn't be a new functionality or something like that.

pfsjap

@Gertjan Sure, why not. After all, the procedure you described using diff is the standard and common practice in the industry to find out what and why was something released.

Gertjan

@pfsjap said in pfBlockerNG-devel 3.2.16_1?:

why not

I should have added that pfSense doesn't have a button that proposes 'get the previous version of that package back' if, for some reason, the newest version wasn't the greatest.
pfSense Plus user have ZFS which is next best.

johnpoz

@pfsjap bit of sarcasm detected - heheh ;)

@BBcan177 is the guy who would know - I looked at few resource sites he lists, and seems he is a bit behind in updates to these sites.. Its quite possible the only change is the one listed commit in the github from a few months ago, and it just now has been released as package??

Gertjan

@pfsjap said in pfBlockerNG-devel 3.2.16_1?:

why not

I should have added that pfSense doesn't have a button that proposes 'get the previous version of that package back' if, for some reason, the newest version wasn't the greatest.
That said, pfSense Plus user have ZFS which is next best as it has snapshots.

tagit446

I'm not try to hijack this post but how is it that some people are being offered a devel update of 3.2.16_1 when just a few days ago I was offered update 3.2.14_2 ?

After completing the update to 3.2.14_2, I'm not being offered anything newer. This makes me wonder if maybe there is something wrong with my install.

If it matters, I am using pfSense CE 2.8.1-RELEASE (amd64).

SteveITS

@tagit446 Plus is later than CE so has later version packages.

tagit446

@SteveITS Okay thanks, I was wondering if being on CE had something to do with it.

tman222

Looked around a bit more and came across this issue on Redmine:

https://redmine.pfsense.org/issues/16932

Could this be the fix that led to the 3.2.16_1 release? Thanks again.

Mission-Ghost

This post is deleted!