|
|
Subscribe / Log in / New account

Multipath TCP: an overview

Multipath TCP: an overview

Posted Apr 1, 2013 21:57 UTC (Mon) by marcH (subscriber, #57642)
In reply to: Multipath TCP: an overview by martinfick
Parent article: Multipath TCP: an overview

To be honest most "middle boxes" I've seen rejecting UDP were just... web proxies and thus not letting *anything* go through.

Of course any intermediate kind of network crippling is possible in theory.


to post comments

Multipath TCP: an overview

Posted Apr 1, 2013 23:31 UTC (Mon) by martinfick (subscriber, #4455) [Link] (1 responses)

Are you sure? I suspect most firewalls, load-balancers, and other middle boxes which do port forwarding or filtering are filtering by protocol, so they will filter out UDP if only the TCP port is open/forwarded.

Multipath TCP: an overview

Posted Apr 20, 2013 0:32 UTC (Sat) by vr000m (guest, #90483) [Link]

YMMV, from what I have encountered during our work on WebRTC this amounts to about 10-20% of the cases. Only very special NATs (typically those deployed in enterprises) are very restrictive and for them one would have to tunnel everything over TCP. For the rest of the cases ICE's NAT traversal works fine (i.e., STUN and TURN).


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds