PfBlockerNG
-
Your instructions are great, they're for dummies like me.
It's greatly appreciated! I'm going to try and hit the datacenter this weekend. I'm doing a fresh install and moving from 2.1.5 (32bit) to 2.2 (64bit). I'll try installing pfBlockerNG then.
Thank you!
-
-
The package? Sure. The pkg-utils.inc patch? No idea, never tried.
-
i try install pfblockerng on 32bit pfsense with this patch and it failed.
-
Edit: They aren't built for 2.1.5. Only for 2.2
http://files.pfsense.org/packages/10/All/
pfblockerng-1.6.3_1-amd64.pbi 27-Nov-2014 13:15 2743546 pfblockerng-1.6.3_1-amd64.pbi.sha256 27-Nov-2014 13:15 65 pfblockerng-1.6.3_1-i386.pbi 27-Nov-2014 13:23 2909780 pfblockerng-1.6.3_1-i386.pbi.sha256 27-Nov-2014 13:23 65
i dont see anything in http://files.pfsense.org/packages/8/All/ for 2.1.5
-
ok, thx. this make sense to me.
-
I dont believe the pbi's are built for 32bit yet
They certainly are, see https://files.pfsense.org/packages/10/All/
Looking at the pkg-utils.inc file, you'd rather need $force_install = true; at proper place instead.
-
I dont believe the pbi's are built for 32bit yet
They certainly are, see https://files.pfsense.org/packages/10/All/
Looking at the pkg-utils.inc file, you'd rather need $force_install = true; at proper place instead.
I corrected my post… They are not created for 2.1.5
-
About time to upgrade. :P
-
than if is 32bit ready and i install on pfsense 2.2. release 32 bit i dont know why i cant install with posted patch.
-
Already posted a hint above. As said, never tested the patch, edit the version temporarily and move on.
-
i try install pfblockerng on 32bit pfsense with this patch and it failed.
Did you tested and applied the patch under systempatches? the screen I've sent show how to create the patch but you need to apply after saving.
Or edit file manually if you know how to handle with it.
-
aaa ,stupig me. i forgot apply patch…...... sorry. Now installed....
-
Uhm… censored
-
ye, ******* :)
-
I've updated the install steps to make it easier :)
-
Output of full patch apply test:
/usr/bin/patch –directory=/ -t -p1 -i /var/patches/54c7f4a39c5e8.patch --check --forward --ignore-whitespaceHmm... Looks like a unified diff to me...
The text leading up to this was:-- pkg-utils.orig.inc 2015-01-27 14:27:38.000000000 +0000
+++ pkg-utils.inc 2015-01-27 14:27:50.000000000 +0000 No file to patch. Skipping... Hunk #1 ignored at 624. 1 out of 1 hunks ignored while patching pkg-utils.inc done Close Is the patch info I got when I tried to use your patch. I am running 64 bit release 2.2
-
-p1 is obviously wrong with –directory=/
Kindly use the System Patches package and see the screenshot above. If you cannot handle that, you probably should avoid doing similar changes in the first place.
-
I did use SYSTEM patches and pasted that in the code window and hit Test patch and this is the result I got
-
Go back to the screenshot. Really.