| ||
Fri 2024-04-26
Thu 2024-04-25
Wed 2024-04-24
Tue 2024-04-23
Fri 2024-04-19
Thu 2024-04-18
Mon 2024-04-15
Butterick’s Practical Typography Sat 2024-04-13
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
Network address translation is the bane of P2P.
There's a black art for establishing UDP communication
between two peers behind NATs by having a third party introduce the peers
and fooling the NAT routers into routing the packets. Games have been
doing this for a few years. I see now it's
well documented
by Bryan Ford.
Bryan also has a draft RFC for NAT P2P. It's a great document and includes a technique I'd love to see developed further: opening TCP connections through NATs with a "simultaneous open":
If, however, the SYN packet arrives with
source and destination addresses and port numbers that correspond
to
a TCP session that the NAT believes is already active, then the NAT
will allow the packet to pass through.
It requires predicting TCP sequence numbers, though, so I fear it's
impractical.The only alternate I know of is UPnP Nat. There's hardware router support and a free Linux implementation.
As seen on decentralization
|
|
