4 ms·
In my experience, many NATs just drop UDP packets altogether, but still allow TCP through. Similarly, I find the Internet at my local Starbucks to be some of t
by cbhl 12y ago
In my experience, many NATs just drop UDP packets altogether, but still allow TCP through.
Similarly, I find the Internet at my local Starbucks to be some of the fastest, most-reliable networks around; even faster than some local ISPs hooking up to my home.
- chetanahuja 12y agoNote that any NAT that drops UDP packets altogether will basically disable DNS and VOIP type applications or at least degrade the experience in serious ways. I haven't come across many such NATs recently.
- agwa 12y agoMe neither. I have come across networks that filter everything but a few TCP ports (like 80 and 443), but that's a matter of draconian firewall policy rather than a NAT limitation.
- minimax 12y agoI have come across networks that filter everything but a few TCP ports (like 80 and 443) Another point scored for TCP in TCP with an SSL VPN. :-)
- agwa 12y agoOnly if your TCP VPN is listening on one of the allowed ports ;-) (I do keep a TCP VPN running on port 443 ready to go for these situations, but UDP is always my first choice.)
- selectodude 12y agoGoogle is apparently paying for fiber connections to Starbucks, since AT&T DSL wasn't getting it done.