Cox Scraps App-Specific Throttling Trials > Thanks for your desicion, but...

reply to funchords

Re: Thanks for your desicion, but...

I agree. You have the right to break (as in cripple the functionality of) your network stack and leave a bunch of half-open TCP connections in your state table.

And I do indeed know what I'm talking about, and so does Espaeth.

I told you then, and I'm telling you know, screening out TCP RSTs does not avoid any problem and only harms you. YOU HAVE THE RIGHT. It doesn't harm me, so go right ahead. It's yours. Break it if you want to.
--
Robb Topolski -= funchords.com =- District of Columbia -- KJ7RL
Test your Broadband connection today! -- »measurementlab.net/

Again, I were telling that I'd blocked the TCP RST abuser packets INBOUND DIRECTION, NOT OUTBOUND DIRECTION of iptables firewall packet filter that way the iptable firewall operate that I designed that way to filtering TCP RST out of inbound direction but TCP RST is not filtered at outbound in firewall processing before going out of outbound direction that is nothing harms me at all. So screening TCP RST out can help, that bittorrent application won't be interrupted that where TCP RST is filtered out of inbound direction that is I don't have problem with that where TCP RST abuser is filtered out of inbound direction. TCP RST in RFC that were designed to disrupt the connection immediately or cut connection out immediately and unfortunate, abuser can take advantage of TCP RST to abuse the TCP RST flag bit set packet to forge it but I set it to filter TCP RST out for inbound only with iptable firewall that's it I have peace now and my internet performance were great of speeds.
--
Professional Linux environmental blows microsoft windows out of the water.