Pfsense 2.4 and pfBlockerNG issue.



  • Pfsense 2.4 and pfBlockerNG.

    I am testing 2.4 and pfBlockerNG is listed as compatible in available packages.

    It crashes 2.4.

    Just an FYI, so no one else runs into the same issue.

    Possibly it needs to be updated to latest xmlrpc to be 2.4 compatible?



  • Correct.. pfB 2.1.1_4 is not yet adapted to the latest xmlrpc changes.. I've left that for BBcan177, he is aware some changes are needed.

    I've tried updating most of the other packages to at least 'work' as they did before regarding xmlrpc sync.. Though there are several differences here and there between packages. I think ill leave that up to each respective package maintainer for the moment.



  • I just found that out for myself last night, so  I uninstalled it again or so it seems.

    Just for clarification, can you confirm that the attempted install of this package in its current form wont leave anything corrupt, like traces of files going to the wrong places or anything?

    If so I will freshly install 2.4 again and start a fresh again.

    @PiBa:

    Correct.. pfB 2.1.1_4 is not yet adapted to the latest xmlrpc changes.. I've left that for BBcan177, he is aware some changes are needed.

    I've tried updating most of the other packages to at least 'work' as they did before regarding xmlrpc sync.. Though there are several differences here and there between packages. I think ill leave that up to each respective package maintainer for the moment.

    @Dazog:

    Pfsense 2.4 and pfBlockerNG.

    I am testing 2.4 and pfBlockerNG is listed as compatible in available packages.

    It crashes 2.4.

    Just an FYI, so no one else runs into the same issue.

    Possibly it needs to be updated to latest xmlrpc to be 2.4 compatible?



  • afaik, if you uninstalled it again there shouldnt be any 'issues' arising from it..

    Keeping it installed might prevent webgui and some services from launching properly at startup.. (if you do reboot and run into this the Webgui can be 'fixed' by running (11 restart) and (16 php-fpm) commands from console menu. after which you can then login and launch other services again..)


  • Moderator

    Yes I have to adjust for the new XMLRPC changes in 2.4…

    If you don't use XMLRPC sync in pfBlockerNG:

    A temporary workaround would be to download this file which will allow the rest of the package to function…  I haven't fully tested it, so keep in mind to fully test this before using in production... This file should be downloaded before installing the package...

    fetch -o /etc/inc/xmlrpc.inc https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_2/src/etc/inc/xmlrpc.inc
    

    Once the package has been updated for 2.4, this file should be deleted…

    rm  /etc/inc/xmlrpc.inc
    

  • Banned

    There are issues with using PFsence. Here is a crash dump. Looks like a logging issue. I will turn off all PFblockerNG logging and see if it helps.

    Crash report begins.  Anonymous machine information:

    amd64
    11.0-RELEASE-p3
    FreeBSD 11.0-RELEASE-p3 #178 8fb831d(RELENG_2_4): Fri Nov 11 19:23:26 CST 2016    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense

    Crash report details:

    PHP Errors:
    [12-Nov-2016 13:57:24 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [12-Nov-2016 13:57:24 America/Phoenix] PHP Stack trace:
    [12-Nov-2016 13:57:24 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [12-Nov-2016 13:57:24 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
    [12-Nov-2016 13:57:24 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [12-Nov-2016 13:57:24 America/Phoenix] PHP Stack trace:
    [12-Nov-2016 13:57:24 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [12-Nov-2016 13:57:24 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184


  • Banned

    Update - Got another Crash Report. Disabling logs does not fix this issue. PFblockerNG does need some work to run on PFsense 2.4
    I sent the logs to the dev team.


  • Moderator

    Which log file were you trying to view?


  • Banned

    I wasn't trying to view logs, most of them don't work, or at least the firewall logs don't work. This was a crash report that hasn't shown up since.


  • Moderator

    @dcol:

    I wasn't trying to view logs, most of them don't work, or at least the firewall logs don't work. This was a crash report that hasn't shown up since.

    The crash report that you posted above is for the pfBlockerNG Log tab… so it looks like it didn't find a particular log file to view?? If this only happened once than ignore...

    I haven't had any time to load 2.4 and test it out... on the list of things too do...

    Also not the following redmine:
    https://redmine.pfsense.org/issues/6919


  • Banned

    Just updated to today's version of 2.4.0 and got another PFblockerNG crash report when I forced an update. Forced update again and did not see a crash report. PFblocker does work.

    Crash report begins.  Anonymous machine information:

    amd64
    11.0-RELEASE-p3
    FreeBSD 11.0-RELEASE-p3 #179 8fb831d(RELENG_2_4): Sat Nov 12 21:27:00 CST 2016    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense

    Crash report details:

    PHP Errors:
    [13-Nov-2016 15:17:17 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [13-Nov-2016 15:17:17 America/Phoenix] PHP Stack trace:
    [13-Nov-2016 15:17:17 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [13-Nov-2016 15:17:17 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
    [13-Nov-2016 15:17:17 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [13-Nov-2016 15:17:17 America/Phoenix] PHP Stack trace:
    [13-Nov-2016 15:17:17 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [13-Nov-2016 15:17:17 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184
    [13-Nov-2016 15:17:37 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [13-Nov-2016 15:17:37 America/Phoenix] PHP Stack trace:
    [13-Nov-2016 15:17:37 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [13-Nov-2016 15:17:37 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
    [13-Nov-2016 15:17:37 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
    [13-Nov-2016 15:17:37 America/Phoenix] PHP Stack trace:
    [13-Nov-2016 15:17:37 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
    [13-Nov-2016 15:17:37 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184


  • Banned

    A note for anyone that applied the forced patch above.
    You must apply it after every update until it is fixed in 2.4



  • Adding the earlyshell-command "touch /etc/inc/xmlrpc.inc" in the shellcmd package seems to keep things happy relatively easy.. Sync wont work though, but i don't expect it will with the fetch either though.


  • Banned

    Thanks for that. Installed the Shellcmd package and added the command. Let you know if any problems after the next update.


  • Banned

    That Shellcmd worked great. Updated to the latest dev version 11/19 and had no issues with PFblocker this time.
    Thanks!