2.2.4-RELEASE Coming Soon

cmb

The most recent snapshot builds should be nearly identical to release, assuming all our testing checks out.

Help with testing would be appreciated!

phil.davis

Looks good.
1 Alix2D13 running at home:

2.2.4-DEVELOPMENT (i386)
built on Thu Jul 23 18:30:29 CDT 2015
FreeBSD 10.1-RELEASE-p15

and 1 APU:

2.2.4-DEVELOPMENT (amd64)
built on Thu Jul 23 18:30:13 CDT 2015
FreeBSD 10.1-RELEASE-p15

and I see since then all that has been done since then is the LoginGraceTime reduction to 30 seconds.

cmb

Thanks for the feedback.

Yeah I forgot to push that one last change before the final snapshot run. That looks like it’ll be the only diff from the last snapshot to release, still going through testing though.

Gertjan

Good !
~~Was looking for a reason to canceled this weekend beach trip. Snapshot testing gave me one !~~
2.2.4(64) on Dell Dimension 5120 triple NIC up and humming.
Real time info : => Portal clients are happy.

stephenw10

Ha, that’s dedication.

Steve

KOM

Ha, that’s dedication.

Or a mental defect. I can’t decide which one

dennypage

I guess it depends on the beach

Gertjan

@KOM:

Or a mental defect. I can’t decide which one

~~Your close~~
It was a “Honey, I really need you to pay me that new bikini” situation.
A 10 square inch piece with the +800 $ price tag.

2.2.4 still ok.
pppoe IPv4 switch ok.
he.net IPv6 good.

phil.davis

It was a “Honey, I really need you to pay me that new bikini” situation.
A 10 square inch piece with the +800 $ price tag.

You can buy her an SG series device at less per square inch

cmb

Ok guys… cleaned up what most would consider NSFW. Though we enjoyed it, this thread is linked across a variety of our social media accounts and a lot of people follow those from work. Please keep it clean.

chpalmer

@cmb:

Please keep it clean.

Sorry dad!

On topic- two of my sites have been on 2.2.4 D for just over a week and no issues to report! Both on latest as of last snap. One of them is on an MLPPP connection.

cmb

Everything tested out fine. Release will come after I get up tomorrow (not going to drop a release, then go to bed).

phil.davis

@cmb:

Everything tested out fine. Release will come after I get up tomorrow (not going to drop a release, then go to bed).

And why would you go to bed? No dedication
And anyway it looks like it is early AM in your timezone already.

maverick_slo

Do it!
I migrated exchange server and went on vacation lol

doktornotor

@maverick_slo:

I migrated exchange server and went on vacation lol

In fact that’s an extremely wise decision. (Of course, leave your mobile phone at home or switched off… :P)

Mr. Jingles

If I could politely ask: is the firewall rules log mess, that has existed ever since 2.0, finally fixed?

As in descriptions don’t match the actual rules, and the non descriptions, only (@540645064) kind of descriptions, making the FW log utterly useless?

stephenw10

Hmm, a number of log issues were fixed for 2.2.3:
https://doc.pfsense.org/index.php/2.2.3_New_Features_and_Changes#Rules.2FAliases.2FNAT
I know you’re running an earlier version. That may have already been addressed.

Steve

Harvy66

Do we know if it includes the very recent last fin fix?

https://www.freebsd.org/security/advisories/FreeBSD-SA-15:13.tcp.asc

cmb

@Harvy66:

Do we know if it includes the very recent last fin fix?

https://www.freebsd.org/security/advisories/FreeBSD-SA-15:13.tcp.asc

Yes. It’s generally not applicable for our use cases though. https://doc.pfsense.org/index.php?title=2.2.4_New_Features_and_Changes

@Mr.:

If I could politely ask: is the firewall rules log mess, that has existed ever since 2.0, finally fixed?

As in descriptions don’t match the actual rules, and the non descriptions, only (@540645064) kind of descriptions, making the FW log utterly useless?

That general issue has been fixed with static tracking IDs in all 2.2.x versions. Every pre-2.2x version (not since 2.0, every release ever) used pf’s rule numbers, which may change every time you make a ruleset change.

cmb

Now coming tomorrow. Noticed fixing a mobile IPsec rightid problem made it impossible to configure many EAP situations. That’s fixed.
https://github.com/pfsense/pfsense/commit/9a2bec12621c8feaaddd781a89915267659496d2
https://github.com/pfsense/pfsense/commit/5e11c6a176d70f1caa987e64a01a8f996b18aad7

and documentation updated to reflect the correct config.
https://doc.pfsense.org/index.php/IKEv2_with_EAP-MSCHAPv2

Release rebuilt, going through test matrix again now. This one should come out after I get up on Sunday.

Those who want to test the latest, gitsync RELENG_2_2 off the most recent snapshot and you’ll have the same as we’re testing for final release.

n3by

Limiter - NAT reflection problems are fixed in this release ?

stephenw10

Are referring to this? https://redmine.pfsense.org/issues/4326

Steve

n3by

yes … it’s work in progress.
Thx

Supermule

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

jwt

@Supermule:

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

Brian, are you going to stop, or not?