• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: Peer-to-Peer Ports
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Peer-to-Peer Ports


  • Subject: RE: Peer-to-Peer Ports
  • From: "Tim Dorcey" <email@hidden>
  • Date: Sun, 28 Jun 2009 11:45:27 -0700
  • Importance: Normal

> p2p is a misnomer.  Everything over the internet is client-server.
>
> So-called p2p clients simply implement BOTH a client and a server.

I think there is a worthwhile distinction to make.  On many NAT routers it
is common to allocate a different public port for each outbound "client"
connection, even if a static port mapping has established this client port
as an inbound "server."  I think your characterization contributes to this
kind of mistaken design, by not drawing proper attention to the case where
the outbound "client" traffic serves to establish/authorize the inbound
"server" traffic.

Really, I can't see why any NAT has any business simultaneously mapping a
single private port to multiple public ports.  If an application wants to
appear on multiple ports, it can open them.

Tim

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Peer-to-Peer Ports (From: Eli Bach <email@hidden>)

  • Prev by Date: Re: Peer-to-Peer Ports
  • Next by Date: Re: Gluing from NSNetService to FSMountServerVolumeSync()
  • Previous by thread: Re: Peer-to-Peer Ports
  • Next by thread: Re: Peer-to-Peer Ports
  • Index(es):
    • Date
    • Thread