Difference between revisions of "Port"
(just added the link to the german translation and removed a typo) |
Vollstrecker (Talk | contribs) m (Adjusted Links, Added Version-Tag) |
||
| Line 2: | Line 2: | ||
== Description == | == Description == | ||
| − | |||
A port is a number between ''0'' and ''65535'' which allows a [[server]] or [[client]] to know which application the remote connection is trying to connect. | A port is a number between ''0'' and ''65535'' which allows a [[server]] or [[client]] to know which application the remote connection is trying to connect. | ||
| − | Together with an [[IP]] (which specifies the exact computer, either [[server]] or [[client]], with which some computer is trying to connect to) it specifies the exact destination the connection must get to. It is written in the form ''IP:PORT'' most commonly. | + | Together with an [[IP address|IP]] (which specifies the exact computer, either [[server]] or [[client]], with which some computer is trying to connect to) it specifies the exact destination the connection must get to. It is written in the form ''IP:PORT'' most commonly. |
== Examples == | == Examples == | ||
| − | + | For example, [[aMule]] usually uses port ''4662''. So let's suppose your [[IP address|IP]] is ''80.0.0.1''. Now let's say some computer somewhere sends a [[packet]] to ''80.0.0.1:4662''. This [[packet]] is going to be sent to ''80.0.0.1'', which is your computer, and once there, it will be delivered to port ''4662'', which most probably will be a port where [[aMule]] will be listening, so it will get to [[aMule]]. [[aMule]] will read the [[packet]] and act depending on what its content is. | |
| − | For example, [[aMule]] usually uses port ''4662''. So let's suppose your [[IP]] is ''80.0.0.1''. Now let's say some computer somewhere sends a [[packet]] to ''80.0.0.1:4662''. This [[packet]] is going to be sent to ''80.0.0.1'', which is your computer, and once there, it will be delivered to port ''4662'', which most probably will be a port where [[aMule]] will be listening, so it will get to [[aMule]]. [[aMule]] will read the [[packet]] and act depending on what its content is. | + | |
If the packet was sent to ''80.0.0.1:21'' it will also get to you, but (probably) not to [[aMule]] since [[aMule]] will no be listening on that port. If some other application is listening to it (possible some [http://www.faqs.org/rfcs/rfc959.html FTP] [[server]]), it will read its contents and act depending on what they are. If no application is listening to that port, then the [[packet]] will just fail to be delivered. Though it got to your computer, no application was waiting for it, so it will be refused. | If the packet was sent to ''80.0.0.1:21'' it will also get to you, but (probably) not to [[aMule]] since [[aMule]] will no be listening on that port. If some other application is listening to it (possible some [http://www.faqs.org/rfcs/rfc959.html FTP] [[server]]), it will read its contents and act depending on what they are. If no application is listening to that port, then the [[packet]] will just fail to be delivered. Though it got to your computer, no application was waiting for it, so it will be refused. | ||
== Notes == | == Notes == | ||
| − | |||
Other articles you might want to check: | Other articles you might want to check: | ||
*[[Test port]]s | *[[Test port]]s | ||
*[[IP address]]es | *[[IP address]]es | ||
| + | |||
| + | == Version == | ||
| + | Created by "Unknown User" on 07.06.05 at 18:59<br> | ||
| + | Updated by Vollstrecker on 23.01.08 at 14:48 | ||
Revision as of 14:47, 23 January 2008
Contents
Description
A port is a number between 0 and 65535 which allows a server or client to know which application the remote connection is trying to connect.
Together with an IP (which specifies the exact computer, either server or client, with which some computer is trying to connect to) it specifies the exact destination the connection must get to. It is written in the form IP:PORT most commonly.
Examples
For example, aMule usually uses port 4662. So let's suppose your IP is 80.0.0.1. Now let's say some computer somewhere sends a packet to 80.0.0.1:4662. This packet is going to be sent to 80.0.0.1, which is your computer, and once there, it will be delivered to port 4662, which most probably will be a port where aMule will be listening, so it will get to aMule. aMule will read the packet and act depending on what its content is.
If the packet was sent to 80.0.0.1:21 it will also get to you, but (probably) not to aMule since aMule will no be listening on that port. If some other application is listening to it (possible some FTP server), it will read its contents and act depending on what they are. If no application is listening to that port, then the packet will just fail to be delivered. Though it got to your computer, no application was waiting for it, so it will be refused.
Notes
Other articles you might want to check:
Version
Created by "Unknown User" on 07.06.05 at 18:59
Updated by Vollstrecker on 23.01.08 at 14:48
