Hello, I posted v2 which includes this change. Done Done I didn't included any changes to rate limit the debug messages. It can be done with additional patch, for all such messages. Not sure, may be
Hello, For AH/ESP we use UDP connection, so we rely on UDP. In practice, it would be very difficult to drop template: - it start in NONE state but ... is referred by connection(s) - there must be no
A new template is in NONE state (unassured). I see you modified also UDP and SCTP protocols. The AH/ESP protocols (which I'm not familiar with) don't specify any transition function. Potential new pr
Understood. If space is limited, and can't be easily expanded then I have no objection to "A". But perhaps a comment explaining this space limitation would be useful. Great, thanks! -- To unsubscribe
Hello, Because I was not sure how many flags we can add in the future. ipvsadm.c has state[16] in print_conn. May be we can use ASSURED for now. Good idea Sure I'll add it as separate patch early in
"A" seems a bit cryptic, why not "ASSURED" ? I'd slightly prefer if refactoring ip_vs_state_name to not take a state parameter was a separate patch. Its a nice cleanup. But it doesn't seem related to
and for the first "assured" bit which indicates that some connection controlled by this template was established or assured by the real server. In a followup patch we will use it to drop templates u