 Ikyuao join:2007-02-26 Wichita, KS Reviews:
·Cox HSI
2 edits | Iptables How about Iptables? that's part of Linux kernel, Topolski should start to use Iptables to blocking the TCP RST issues and then issues are solved that's there is, Robb have a final option is to use Iptables after that worthless settlement. -- the aggregate link are carrying higher quality of connection to boost productivity. |
|
|
|
 | When properly deployed, the end user would never see the rst injection into their stream. (Which would make the use of IPTABLES rules impossible). The whole suit demonstrated to me how ignorant Comcast was regarding the technology they deployed on their network.
I'm Sandvine certified. |
|
 Ikyuao join:2007-02-26 Wichita, KS Reviews:
·Cox HSI
| I see, When that Sandvine were deployed, Sandvine platform could send a TCP RST packets to the customers' CPE, The computer TCP receives the RST packet then TCP connection should be stopped communicating and permanently unless the user start the application over again to reconnect to establish, and however if Linux IPTABLE was deployed in the middle, RST should be removed out of the packet streams as RST injection in middle of packet streams by using IPTABLE rules settings of DROP. -- the aggregate link are carrying higher quality of connection to boost productivity. |
|
 1 edit | No, proper network management affects the NetFlow upstream from the customer in the form of a discard. IP Tables has no effect within the carrier's network. There is no need to forge, Comcast got in trouble because they did. |
|
 Ikyuao join:2007-02-26 Wichita, KS Reviews:
·Cox HSI
2 edits | I see, that explanation makes so clear, Comcast got just in a seriously trouble that they did started to forge the TCP packet streams by putting RST injection in the middle of TCP packet streams that got Comcast in a trouble that they did that to their customers. but what about court settlement? that not much deal about court settlement that a little deal for customers, to allowing Comcast to get away with it.
But... Comcast's networks is Comcast property owned, if they want to forge the TCP packet streams by injecting the RST bit in middle of TCP streams then it is their rights to manage the Comcast property network equipments, mostly customers will more likely to receives a RST forge packets without an advanced firewall equipped at the customer computers which connected to Comcast networking.
I have no indentation to do anything to sue the Cox communications since I'm running a Linux and IPTABLE part of Linux that I configured to block the any TCP RST packets ingoing and outgoing.
-- the aggregate link are carrying higher quality of connection to boost productivity. |
|