Bug #610

max-mss -39

Added by Brett Burley about 10 years ago. Updated almost 10 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


I don't know how the following is getting into rules.debug:

"scrub in on $WAN all max-mss -39 fragment reassemble"

But it is causing rules not to load. I'm using last nights build.

Config attached.


rulesDebug.txt (3.2 KB) rulesDebug.txt Brett Burley, 05/20/2010 09:04 PM

Associated revisions

Revision 79f9b9bc (diff)
Added by Ermal Luçi about 10 years ago

Fixes #610. Do not use the value of mtu blindly test it is set or use 1500 as default.


#1 Updated by Ermal Luçi about 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Chris Buechler almost 10 years ago

Not sure how to replicate this. The fix looks fine. Brett - can you confirm the fix?

#3 Updated by Jim Pingle almost 10 years ago

It was a side effect of "1" showing up in some Wizard boxes. It was trying to set the MTU to 1, and the max-mss to MTU-40.

#4 Updated by Chris Buechler almost 10 years ago

  • Status changed from Feedback to Resolved

ahh, so the real issue is improper input validation on the setup wizard. Confirmed if you stick 1 in the config manually it generates this still, and you can put 1 in that field in the setup wizard. That's already in #464, closing this one.

#5 Updated by Brett Burley almost 10 years ago

Just a quick "thanks". Nice work guys.

#6 Updated by Erik Fonnesbeck almost 10 years ago

Also, the issue of 1's showing up in the setup wizard for some of the blank fields was already fixed sometime.

Also available in: Atom PDF