Age | Commit message (Collapse) | Author |
|
|
|
on an inpect rule - increment number of rules with inspect + logging
|
|
|
|
|
|
|
|
added new configuration parameters:
firewall conntrack-options sip enable-indirect-media
firewall conntrack-options sip enable-indirect-signalling
|
|
|
|
'recent' have different match conditions by moving code for recent to last
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* add comp_help for 'limit rate'
* make sure 'limit rate' is not less than 1/time unit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
source and destination ports are specified.
|
|
|
|
|
|
|
|
* remove reject as an allowed value for action field
in modify & ipv6-modify firewall rulesets
|
|
|
|
under name and ipv6-name rulesets
|
|
|
|
* undo chain setup and refcnt work if chain rule failed during chain creation
|
|
The parameter in question loosens the "acceptability" check on TCP
sequence and ACK numbers in the TCP conntrack module. This allows connection
tracking to survive certain cases where packet loss would cause it to
loose sync with the TCP endpoints.
|
|
|
|
either vyatta/user defined chains or system chains such as INPUT, OUTPUT etc.
* don't allow user to create chains with name starting from 'VZONE'. This is
reserved for zone chains created by us.
|
|
|