They've given out a bot identification signal. Now botters are going to deliberately cancel 6% of their TCP connections ;)
Bringing insights into TCP resets and timeouts to Cloudflare Radar
11–13 of 13 posts
Re: Bringing insights into TCP resets and timeouts to Cloudflare Radar
#12Earlier quoted context omitted.
Maybe a fun idea - run an application on both sides of a remote TCP connection that records but doesn't respond to TCP RST packets. Then see how many times you get "reset".
You can just drop RST packets. iptables -I INPUT -p tcp --tcp-flags ALL RST,ACK -j DROP iptables -I INPUT -p tcp --tcp-flags ALL RST -j DROP
Why do I find this so funny...
Re: Bringing insights into TCP resets and timeouts to Cloudflare Radar
#13Earlier quoted context omitted.
Maybe a fun idea - run an application on both sides of a remote TCP connection that records but doesn't respond to TCP RST packets. Then see how many times you get "reset".
You can just drop RST packets. iptables -I INPUT -p tcp --tcp-flags ALL RST,ACK -j DROP iptables -I INPUT -p tcp --tcp-flags ALL RST -j DROP
That looks like exactly what I did, but it was a pain trying to get random users to do run code as root.