Yeah, the problem is there's no "global" port number with many NATs. The BEHAVE working group at the IETF is the most up on all of this I think, and they've broken it down into the way NATs 1) map addresses and 2) filter addresses. Some are address dependent, some address and port dependent, and them some really hairy combinations.
It all boils down to the port usually being relevant only to the server you're talking to. Sorry for the slight hand waving, but I still haven't taken the time to get up to speed on the newer IETF classifications on all this stuff. Basically, you can use STUN (or any ad-hoc protocol of your choosing, although STUN is nice) to obtain the public port mappings, but the relevance of that information depends on the NAT. -Adam On 7/2/07, Lemon Obrien <[EMAIL PROTECTED]> wrote:
given a dude, somewhere on the internet, starts a server from a computer with a consumer DSL connection (NAT'd you get no break here). Now, for others to connect to the server, they need to know his global-ip address, AND the global port number. getting the global address is easy enough, nut how would you obtain the global port number. please disregard port-forwarding...i'm trying to determine it without, and without port-scanning. thanks ps. any of you guys wanna work on an extrememly cool project? You don't get no juice unless you squeeze Lemon Obrien, the Third. http://www.tamago.us _______________________________________________ p2p-hackers mailing list [email protected]<https://mail.google.com/mail?view=cm&tf=0&[EMAIL PROTECTED]> http://lists.zooko.com/mailman/listinfo/p2p-hackers
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
