Hi Graeme,
Actually this issue occurred within Keepalived with `per second` loop
delay_loop and 1 second TCP verification check, but since it uses IPVS
under the hood, I sent the question into this mail list.
What I found so far, is `secure_tcp` sysctl option:
http://www.linuxvirtualserver.org/do
On 13 Apr 2018, at 10:45, kay wrote:
> I have a special use case for the Direct Routing (DR) mode.
> Is there a possibility to reroute SYN packets, when they can not be
> delivered to the backend? It could be easily detected by several SYN
> packets being sent.
Repeating the earlier answer:
You
Hi,
I have a special use case for the Direct Routing (DR) mode.
Is there a possibility to reroute SYN packets, when they can not be
delivered to the backend? It could be easily detected by several SYN
packets being sent.
Here is how you can reproduce this situation:
1) configure ipvs with direct
On 12 Apr 2018, at 15:28, kay wrote:
> I have a special use case for the Direct Routing (DR) mode.
> Is there a possibility to reroute SYN packets, when they can not be
> delivered to the backend? It could be easily detected by several SYN
> packets being sent.
Firstly, please susbcribe to the li
Hi,
I have a special use case for the Direct Routing (DR) mode.
Is there a possibility to reroute SYN packets, when they can not be
delivered to the backend? It could be easily detected by several SYN
packets being sent.
Here is how you can reproduce this situation:
1) configure ipvs with direct
