AzureusWiki:Sandbox
From AzureusWiki
Αυτοί οι χα�?ακτή�?ες είναι bold Αυτοί οι χα�?ακτή�?ες είναι Italic
Αυτο είναι ένα Headline text
Image:Example.jpg blah Template:Rand: 5
OK, a lot of people seem to be getting confused over what an open port is, so:
Example of how a HTTP (Normal web browsing) process works:
Computer A == Your PC Server A == The HTTP server you're connecting to (google.com, yahoo.com, etc...)
Your web browser (Computer A), sends a request via a random port which it has determined not to be in use (This does not have to be open, as, it is going OUT of your PC), to the server (Server A) on port 80. The server has had port 80 forwarded in whatever firewalls and routers they have, which allows you to connect to them. The whole purpose of forwarding a port is to allow connections TO your PC, a router will normally block all of these connection attempts...
A port is only 'Open' if it is in use and an application is Listening for connections on it (In this case, a Web Server), therefore, port scanning your own PC or router for open ports is no help, because, even if you find an open port, it is in use. Furthermore, if you are scanning your network internally, you are not counting your router, which is often the main cause of the problem
So, Computer A has sent a connection attempt to Server A and they have connected, so, Server A sends Computer A the requested page, and the connection is closed by Server A. Now, lets throw Server B into this, Server B is the same as Server A, however, it has not had it's port forwarded, so, connection attempts to it are blocked. When Computer A tries to connect to Server B, the router stops it before the HTTP web server (The application that is listening on the port) can even see the request, hence, no data is sent back to Computer A, and, it appears a dead page...
Now, lets relate this to Azureus and Bit Torrent in general:
You have Client A, B and C
Client A has configured port forwarding, everything is peachy... Clients B and C have not...
--> means a connection is possible --! means a connection is not possible
A --! B
A --! C
B --> A
B --! C
C --> A
C --! B
Total them up, A can have connections 2 ways (Both not initiated by himself, which often means the connection is for A's benefit (B/C want to send data)), B only once (with A) and C, only once (again, with A). AND, the one connection that B or C could make must be sent from their PC, so, it's still not guaranteed, and B will never connect to C.
Lets extend this a bit more, 6 Clients, with... lets say, 2 people whom have forwarded and 4 whom have not:
A and B have forwarded C, D, E, F have not...
A --> B
A --! C
A --! D
A --! E
A --! F
B --> A
B --! C
B --! D
B --! E
B --! F
C --> A
C --> B
C --! D
C --! E
C --! F
D --> A
D --> B
D --! C
D --! E
D --! F
E --> A
E --> B
E --! C
E --! D
E --! F
F --> A
F --> B
F --! C
F --! D
F --! E
Right, lets total them up
A = 6 possible connections B = 6 possible connections C = 2 possible connections D = 2 possible connections E = 2 possible connections F = 2 possible connections
And this was only with 6 peers/seeds... 3 times the connections for those whom have forwarded, and, the difference gets exponentially bigger...
Another myth is that "My ISP is blocking torrents", 99% of people believe this because they have miss-interpreted the help, very few actually have ISP enforced NAT errors... If you're unsure, Plugins>IRC and the helpers there will try their upmost to fix your Azureus problems (Not just NAT related)
This is new and getting german:
Wie man Die CVS mithilfe des AZCVS-updaters installiert:
| Bevor es losgeht, starte Azureus, wenn nicht schon geschehen. Prüfe, ob du auch wirklich die aktuellste java-Version hast! | |
| 
|
