One network interface has just one IP address, but it can have a bunch of different programs listening and talking.
A server might have both a webserver and a mail server running on the same machine - and they don’t want each other’s network traffic.
So you mark each packet with a destination port number, to let the server work out which program you’re talking to.
Your web browser will mark all its packets with port 80 or port 443, and when the server gets those, it knows it’s web traffic, and passes it to the webserver software.
Your email client will mark all its packets with port 25 or 993, and when the server gets those, it knows it’s email traffic, and passes it to the mailserver software.
Typically each separate kind of network service will have its own well-known port number assigned to it.
There’s also a source port field on packets, so that your computer can get return traffic back to the right program running on your machine.
No reason, they’re conventions. Check out this list and you’ll get a better idea. It’s simply a number that the developer assigns without a particular meaning. It’s kinda like telephone help lines, one thing that a developer might want to try is to find a pretty memorable number while trying to avoid conflicts with other programs running at the same time.
One network interface has just one IP address, but it can have a bunch of different programs listening and talking.
A server might have both a webserver and a mail server running on the same machine - and they don’t want each other’s network traffic.
So you mark each packet with a destination port number, to let the server work out which program you’re talking to.
Your web browser will mark all its packets with port 80 or port 443, and when the server gets those, it knows it’s web traffic, and passes it to the webserver software.
Your email client will mark all its packets with port 25 or 993, and when the server gets those, it knows it’s email traffic, and passes it to the mailserver software.
Typically each separate kind of network service will have its own well-known port number assigned to it.
There’s also a source port field on packets, so that your computer can get return traffic back to the right program running on your machine.
For convulsion’s sake, one network interface can have more than one ip.
Ok I have a follow up question if you’ll indulge me - why those numbers in particular?
No reason, they’re conventions. Check out this list and you’ll get a better idea. It’s simply a number that the developer assigns without a particular meaning. It’s kinda like telephone help lines, one thing that a developer might want to try is to find a pretty memorable number while trying to avoid conflicts with other programs running at the same time.