Excellent initiative.

Please keep that up  :)

@divsys:

That's a lot of blocked outgoing IPv6, yes?

Did I miss something?

I don't see any blocked IPv6 traffic in that graph, just a whole whack of outgoing traffic.

I have seen a few notes about an issue with IPv6 traffic being mangled at the moment, but that graph doesn't say much about that IMHO

Don't know if there's as much v6 traffic as you might expect, looks like ~10:1 v4 over v6 but that's really a guess based on 1 graph.

(Kudos on 2.2.5 to all at pfSense, it's very clean and solid so far)

I seem to have mixed the two IPv6 colors. I blame poor LCD monitor color reproduction.

Ok Thank you Jimp. I did not good check in hangout archive. I will check its again.

@router_wang:

Totally stoked about the webGUI update, cant believe nobody else has posted on this….

Second that! Love pfSense and the screenshots in that post look awesome.  8)

@Supermule:

Wondering if its the same meachanism that stops rounting when SYN/ACK flooded?

Brian, are you going to stop, or not?

@cmb:

Start a new thread on that, including the output of:

grep -i aesni /var/log/dmesg.boot

and we can troubleshoot there.

Just wanted to point out… I started a thread about this as it's affecting me as well.

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

It just started!

Ping statistics for 192.168.1.1:
    Packets: Sent = 2054, Received = 2041, Lost = 13 (0% loss),

I started to ping PFSense when I started the install, then it rebooted and was back up quickly enough that only 13 packets dropped. Windows is a 4sec timeout, so just under a minute. Then I forgot to stop the ping.

Seems to be working  8)

No, there is no 2.2.2.1/a/whatever.

@Supermule:

Did the upgrade at home… nothing so far.

EDIT: Stuck on this... nothing installing in the console.

Will try a reboot.

Happened to me to when I upgraded to 2.2

I left it there for about a hour and then when I saw it was stuck, rebooted pfSense from console. It went away and no problems.

@Supermule:

I get this running in a VM using latest tools.

No problems here when I updated in a VM.

Id uninstall and reinstall the tools.

Reminder: This is today! If you're a gold subscriber, login at https://portal.pfsense.org/members/ and the hangout link and other info will appear on the left side of the page.

If you're not a Gold Subscriber, there is still time, sign up at https://portal.pfsense.org/gold-subscription.php for access.

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.