Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| en:network_terms:network_address [2022-04-01-23-39] – ↷ Links adapted because of a move operation 7saturn | en:network_terms:network_address [2022-04-01-23-41] – ↷ Links adapted because of a move operation 7saturn |
|---|
| Most of the time data sent via a network is chopped into packages, that are sent over the physical connection. Each package has a source address (sender) and a target address (recipient). In case of TCP/IP, there is also another number required, the [[port]] number. Such a combination //must// be unique on a computer and on the network. So for example you can reach a FritzBox router by 192.178.0.1:80 (TCP) on an IPv4 network, with IP address 192.178.0.1 and port 80 (TCP). So any connection attempted to that IP-port-combination will end up at the exact same spot every time. Same goes for your own end. When attempting to communicate with another device, your own IP is used, along with a (usually randomly pre-defined) port. If you use a connection protocol like [[TCP]], this combination of source IP and port and destination IP and port defines the connection parameters (not the state of that connection). If you use a connection less protocol like [[UDP]], in principle the same applies, only that there is no such formal state like "is communicating". So those two behave a bit differntly, but both use IP-port-combinations for communication. | Most of the time data sent via a network is chopped into packages, that are sent over the physical connection. Each package has a source address (sender) and a target address (recipient). In case of TCP/IP, there is also another number required, the [[port]] number. Such a combination //must// be unique on a computer and on the network. So for example you can reach a FritzBox router by 192.178.0.1:80 (TCP) on an IPv4 network, with IP address 192.178.0.1 and port 80 (TCP). So any connection attempted to that IP-port-combination will end up at the exact same spot every time. Same goes for your own end. When attempting to communicate with another device, your own IP is used, along with a (usually randomly pre-defined) port. If you use a connection protocol like [[TCP]], this combination of source IP and port and destination IP and port defines the connection parameters (not the state of that connection). If you use a connection less protocol like [[UDP]], in principle the same applies, only that there is no such formal state like "is communicating". So those two behave a bit differntly, but both use IP-port-combinations for communication. |
| |
| [ [[..:games:games_database]] ] [ [[..:games:game_related_terms]] ] [ [[..:games:network_terms]] ] | [ [[..:games_database]] ] [ [[..:game_related_terms]] ] [ [[..:network_terms]] ] |
