Re: P2P Filesharing over UDP

--===============1612201344==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-+ZWacUg3F/zNPnjF7Uho"


--=-+ZWacUg3F/zNPnjF7Uho
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2005-06-19 at 16:42 -0700, David Barrett wrote:
> Pyda Srisuresh wrote:
> > --- Saikat Guha <[email protected]> wrote:
> >>Subsequent Rodi clients perform a port scan on a remote address as
> >>before. If the address is a NAT'ed Rodi client (that has already
> >>performed step 1 above), then one of the port-scan packets make it
> >>through to the other end. This is assuming the NAT is Full Cone for UDP=
.
>=20
> Just curious, how "broad" is this port scan?  Does it do a total=20
> portscan (ie, of the complete range of possible UDP ports), or pick a=20
> subset that it somehow knows will work?

Last I looked into it, it asked the user to specify the range. For it to
work with existing NATs, this would be 1024--65536.

--=20
Saikat

--=-+ZWacUg3F/zNPnjF7Uho
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCuFsBnFltqi691/oRAuofAJ9kjI4mZGKuvabyGZHr/KaDXPDrxQCffN6u
dLnvZF9biJzZWMo5jx8UsPs=
=l3oS
-----END PGP SIGNATURE-----

--=-+ZWacUg3F/zNPnjF7Uho--


--===============1612201344==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline