Bug #131
closed
setting flow-timeouts.default.closed to 0 actually sets flow-timeouts.tcp.closed to 0
Added by Victor Julien over 14 years ago.
Updated over 14 years ago.
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
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.
- Status changed from New to Assigned
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF