On Fri, May 30, 2008 at 11:05 AM, Markus Goetz <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alessio Pace wrote: > | I have a question about how to keep a hole open on a router after having > | performed the hole punching procedure. > | > | Assuming peer A (natted) and peer B (natted) are both correctly sending > | and receiving messages to each other. > | > | To keep holes open on both sides, is it necessary that there is incoming > | data in both direction or just from one to another, to make both routers > | believe there is still a "session" among them? I mean, if it is only > | peer A who sends keepalive messages to B, does peer B's router close the > | hole because there is no outgoing data from B itself ? > > I suppose this is an implementation issue of the router of B. Different > routers may behave differently :) that's what I feared :-( > > Why not go the safe way and also make B send keep alive messages? Because if B is already sending data to other peers and it has a simple cone nat, it should theorically be possible to send keep alive messages to just one of B's active sessions end points to make it possible for anyone else to contact B directly on the translated IP and port. Or at least this is what I understood.. :-) Thanks, Alessio Pace. > > > Markus > > > - -- > Markus 'guruz' Goetz > Web: http://guruz.de Jabber: [EMAIL PROTECTED] > P2P on your LAN? Use http://p300.eu/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIP8NSgtPep2m10zsRApvyAKCuIvgqZTKUjQuXRQj8+gEiqGqAAgCbBsM2 > aaApRh8wtyOLsFbteYfxjAk= > =Q+yC > -----END PGP SIGNATURE----- > _______________________________________________ > p2p-hackers mailing list > [email protected] > http://lists.zooko.com/mailman/listinfo/p2p-hackers >
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
