Actions
Bug #131
closedsetting flow-timeouts.default.closed to 0 actually sets flow-timeouts.tcp.closed to 0
Affected Versions:
Effort:
Difficulty:
Label:
Description
More issues exist in FlowInitFlowProto. ICMP and UDP timeouts are not set properly. It seems however, that there is a config api issue as well.
Files
Updated by Jason Ish almost 14 years ago
- File 0001-Fix-issue-131.patch 0001-Fix-issue-131.patch added
Sequence is probably not the best here, we can just use mappings as this patch does, as well as updates to the code to read from the mappings. Looks like the configurable timeouts were not being stored in their right section either (ie: ICMP timeouts being put into the TCP timeout values), so fixed that as well.
Updated by Victor Julien almost 14 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied, thanks Jason!
Actions