2 ms·
In an emergency, one could rig up a server to drop TCP connections without sending RST. The result would be a client that thinks it’s connected without using se
by amluto 6y ago
In an emergency, one could rig up a server to drop TCP connections without sending RST. The result would be a client that thinks it’s connected without using server resources. Bonus points for some code on the server that responds to some fraction of incoming segments with ACKs to keep stringing clients along.
- toast0 6y agoIt's pretty effective to drop a percent of incoming SYNs. But if you're behind a load balancer, and the load balancer doesn't know to do that, you can't do it on the origins, because the load balancer will fail the origins and that's not good.
- salawat 6y agoComputing isn't free. Energy is being produced/generated somewhere to prop up the demand created by the system you put in place, and your network congestion adversely effects everyone else. Don't let the "transparency" of the network lull you into Tragedy of the Commons behavioral patterns. Act with intention. If you find your thing is overwhelming your own capacity to handle traffic, either implement rate modulation capability, or restructure your program to mitigate whatever is creating the problem. Just because there are selfish. a-holes who think the internet is an infinite resource intended solely for their own enjoyment, convenience and exploitation, does not mean it is okay for everyone to act that way. Not that anyone in this case is one of those types of person mind, but it's worth pointing out. This seems more like unexpected growth far outstripping provisioned resources.