Project

General

Profile

Actions
Copy link

Bug #610

closed

max-mss -39

Added by Brett Burley over 14 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
2.0
Start date:
05/20/2010
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

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.

Thanks!

Files

rulesDebug.txt (3.2 KB) rulesDebug.txt Brett Burley, 05/20/2010 09:04 PM
Actions
Copy link
 #1

Updated by Ermal Luçi over 14 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Chris Buechler over 14 years ago

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

Actions
Copy link
 #3

Updated by Jim Pingle over 14 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.

Actions
Copy link
 #4

Updated by Chris Buechler over 14 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.

Actions
Copy link
 #5

Updated by Brett Burley over 14 years ago

Just a quick "thanks". Nice work guys.

Actions
Copy link
 #6

Updated by Erik Fonnesbeck over 14 years ago

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

Actions
Copy link

Also available in: Atom PDF