Build 2.3.b.20160323.1303 makes router un-useable.

  • I am running the pfSense SG-2440 firewall and was running the Build from 03/18 of 2.3 and everything was working great. I attempted to upgrade to the latest snapshot and it broke completely. I had to even drive down to the data center to attempt to reboot it, i was eventually from the command line able to get the firewall to get out to Internet but it was not pasing any traffic via NAT, etc. I now rebooted it and it failed to come back, looks like i'll be driving down to the DC again to try to see about restoring the OS.

    Is there an easy way to get from command line a restore or to boot to other slice? the WEB UI hasn't been accessable and at most times i only can get to console. I guess I learned my lesson about the snapshots not being very stable at all.

    I did see another build and it upgraded but after reboot it failed to come back.

    Installed packages to be UPGRADED:
    pfSense-Status_Monitoring: 0.9.5 -> 0.9.7 [pfSense]
    pfSense: 2.3.b.20160322.1716 -> 2.3.b.20160323.1303 [pfSense]

    The process will require 163 B more space.
    13 KiB to be downloaded.
    Fetching pfSense-Status_Monitoring-0.9.7.txz: .. done
    Fetching pfSense-2.3.b.20160323.1303.txz: . done
    Checking integrity… done (0 conflicting)

    Upgrading necessary packages...
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up-to-date.
    Updating pfSense repository catalogue...
    pfSense repository is up-to-date.
    All repositories are up-to-date.
    Checking for upgrades (3 candidates): ... done
    Processing candidates (3 candidates): ... done
    Checking integrity... done (0 conflicting)
    The following 2 package(s) will be affected (of 0 checked):

    Installed packages to be UPGRADED:
    pfSense-Status_Monitoring: 0.9.5 -> 0.9.7 [pfSense]
    pfSense: 2.3.b.20160322.1716 -> 2.3.b.20160323.1303 [pfSense]

  • It appears that the Traffic Shaping feature is horribly broken. I noticed on bootup it complains about:

    Fatal error: Call to a member function GetInferface() on null in /etc/inc/ on line 254.

    I disable the Traffic Shaping in the config and everything works!

  • That should be fixed by - there was a bad variable name.
    Gitsync or upgrade to the latest and it should be good.

    Actually the snapshots have been reliable, but they are always subject to the introduction of "just a dumb error" in any change. If that "just a dumb error" borks the bootup process then it could render the firewall either useless (no effective firewalling) or locked out (can't get in to the webGUI to make changes) or… I guess that is life and depends on the quality control implemented before each change is committed to master.

  • I think the build in question must have been pulled… when I got home last night and checked for updates, I was offered an update that was built at 0633 yesterday morning... nonetheless, there's a new build from 0516 this morning available now.

Log in to reply