3 ms·
> The reassembler is responsible for ordering TCP packets. It needs to do this at line rate while maintaining state for 100K flows. 100k flows at a line rate o
by londons_explore 6y ago
> The reassembler is responsible for ordering TCP packets. It needs to do this at line rate while maintaining state for 100K flows.
100k flows at a line rate of 100Gbps, suggests the average flow is 1Mbps. I find that hard to believe - A typical home or office computer might have hundreds of TCP connections open at any given point in time, yet barely be downloading anything. Most of those connections are just sitting idle.
Perhaps this hardware only bothers with keeping the 100k most active flows in the reassembler... In which case the obvious attack is simply to send some packets out of order by a few seconds to make sure you're out of the most-active reassembly window?
- stefan_ 6y agoDing ding ding. Not only is the number of flows limited by the BRAM which is going to be impossible/very expensive to scale, it will drop particularly OOO flows: If the OOO Engine detects that BRAM capacity for OOO flows exceeds 90% of its maximum capacity, it drops the flow with the longest linked list
- londons_explore 6y agoI mean you could potentially drop out of order packets that can't be reassembled to force them to be retransmitted in-order? That way, you'd reduce performance of some flows, but perhaps that's a small enough proportion of flows that it doesn't matter? The state you keep per flow also only needs to be the length of the longest pattern, so if your patterns are short (eg. banning rude words, <script> tags, etc.), it isn't much state at all... I would assume in most cases it's just a few bytes.
- ashika 6y ago> the average flow is 1Mbps. I find that hard to believe hard to believe? I can confirm - tcp sessions with average flows of >1Mbps do exist. you are right in identifying a weakness of the system but incorrect as to its significance. A drag racer cannot turn, because it has been optimized for something else.