Two "peers" behind a NAT router are unable to communicate (it's impossible by design) unless you have the router configured with a static forwarded port (configured in the P2P application and your router), or if the router (and your P2P application) supports dynamic port forwarding (UPnP).
If the remote peer is on a public IP, it's not an issue. This is mostly handled behind the scenes however by UPnP as it's supported by most routers and applications requiring it these days. Tyler Booth // President ph. 503.548.2000 | fx. 503.548.2002 921 SW Washington St, Suite 224 Portland OR 97205 On Dec 2, 2009, at 12:50 PM, Gary wrote: > BitTorrent or apps that use P2P technologies (e.g. Skype) do not need > an inbound open port in order to work as they were designed with NAT > in mind. That kind of traffic not easily blockable on SOHO networking > gear unless something like DD-WRT has been installed on them which has > an option to block P2P traffic. > > -Gary > > -- > The Personal Telco Project - http://www.personaltelco.net/ > Donate to PTP: http://www.personaltelco.net/donate > Archives: http://news.gmane.org/gmane.network.wireless.portland.general/ > > Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette > List information: http://lists.personaltelco.net > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > -- The Personal Telco Project - http://www.personaltelco.net/ Donate to PTP: http://www.personaltelco.net/donate Archives: http://news.gmane.org/gmane.network.wireless.portland.general/ Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette List information: http://lists.personaltelco.net To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
