The bug with gen_subnetv4_max() on 32-bit systems effects quite a few disparate places, and sends PHP into a spin whenever it tries to iterate through to the (erroneously calculated) subnet max IP address 255.255.255.255.
It is fixed by commit: https://github.com/pfsense/pfsense/commit/e69a0cf3a216c8647a6def4eee41ab01319ce90f

This causes quite a few times of tracking down symptoms in the forum.
The latest case effected firewall_nat_edit.php when there are VIPs: https://forum.pfsense.org/index.php?topic=88912.msg491627#msg491627

On all 32-bit installs of pfSense 2.2-RELEASE it is "a good thing" ™ to also apply the change to /etc/inc/util.inc in the commit above.

;D Have one more then  ;D

Ah, yes, the style I used focuses on the navigation actions taken by the user. The page titles don't always line up or may have longer titles. The page titles are more free-form and less restricted by space than the menus, but when instructing the user what to click or where to go, it's preferred to list the items they should be clicking on.

So the page titles are more informative, but less useful as a navigation aid.

https://forum.pfsense.org/index.php?topic=86882.msg476757#msg476757

Congratulations(!)

Well maybe since it was posted back in Aug, and your trying to download it in Nov.. Have to assume that position has been filled and they pulled down the job desc, etc..

@kejianshi:

It started a couple updates back for me.  It has had no impact on performance so I ignore it.

I have come to find that this does affect rules and port forwarding. I have a few website setup to use the my local ISP and not the VPN, however, when the VPN shows the arrow down, the website rules get messed up and for some reason is trying to send the traffic through the VPN (when the VPN is up then the rules function normally??) Also I have a script that checks to make sure my VPN's port is being forwarded correctly and if it detects that the VPN port has been closed it restarts the VPN to find a new open port. When the VPN is up then it functions as it should. When the VPN is down it thinks that the port is open when in fact the port is closed.

Has anyone found a solution to fix this issue? It is really starting to be a nuisance.

Upgrading in-place should work. If it does not, start a new thread for that to diagnose the problems encountered.

See https://forum.pfsense.org/index.php?topic=80092.0

We're working on it.

@gonzopancho:

As usual, details are in the blog post:  https://blog.pfsense.org/?p=1377

Error encontred on function killbyname
/etc/inc/util.inc
/* kill a process by name */
function killbyname($procname) {
if(isvalidproc($procname))
missing return here -> mwexec("/usr/bin/killall " . escapeshellarg($procname));
}

Bump, reminder this is coming up in just over 12 hours.

Thanks Chris, looking forward to Mays hangout.

A quick note on Fuze. In April I was once again thwarted by the Linux client. For a brief period in March they had clients available for multiple Ubuntu base versions and reports of them working well in the forum. One helpful forum user had even packaged it correctly to make the install process seamless. However since then they been through a re-branding exercise that seems to have included deleting almost all the content from the Linux section of their forum. The available client on April the 18th was a non-starter.  :(

Back to Android for me.  ::)

Steve