Project

General

Profile

Actions
Copy link

Bug #7356

closed

pfsense 2.3.4: TCP State Timeout cannot be higher than 3600s within a rule - global configuration allows higher values

Added by Alexander Wilke over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Rules / NAT
Target version:
2.3.3-p1
Start date:
03/06/2017
Due date:
% Done:

100%

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

Description

Hi,

whe I am within a firewall rule and change the "TCP State Timeout" under "Advaced options" within that specific rule I cannot set the value higher than 3600s.
Under System --> Advanced --> Firewall & NAT I can configure higher values and the default values are higher than 3600s.

So I would assume it should be possible to set any timeout possible individually on each firewall rule.

Files

Download all files
TCP_state_timeout.png (9.58 KB) TCP_state_timeout.png Alexander Wilke, 03/06/2017 11:14 AM
pfsense_version.png (7.02 KB) pfsense_version.png Alexander Wilke, 03/06/2017 11:15 AM
Actions
Copy link
 #1

Updated by Jim Pingle over 7 years ago

  • Category set to Rules / NAT
  • Status changed from New to Confirmed
  • Assignee set to Jim Pingle
  • Target version set to 2.3.3-p1
  • Affected Version changed from 2.3.3 to All
  • Affected Architecture All added
  • Affected Architecture deleted ()

You're right, that should not be limited in that way.

It affects 2.4 as well.

Easy fix, I'll push it momentarily.

Actions
Copy link
 #2

Updated by Jim Pingle over 7 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Renato Botelho over 7 years ago

  • Status changed from Feedback to Resolved

Works

Actions
Copy link

Also available in: Atom PDF