The simplest way to look at port forwarding is if you have a Mine craft server and you want people on the outside to be able to connect and play games with you.
Let’s say you have a second computer you use as the server; it has an IP address on your local network.
You start Minecraft and connect this to your server.
The default port numbers for Minecraft are 25565 – for Java Edition and 19132-19133 – TCP and UDP ports for Bedrock.
In the Internet Protocol, there are 65,636 possible ports. For instance, you are reading this page because your browser connects to my server on port 443, HTTPS.
By default, all routers turn off all ports for inbound establishing traffic and turn on all ports for outbound establishing traffic.
When you first go to a new webpage on one of my servers using your browser, down in the depths of TCP, you send out a packet of data asking to connect to my server on port 443.
My server’s firewall accepts that package because it is allowed and forwards it to the Apache server running on my Linux box. Apache sees your request, and if everything is good, a response and a connection are established. Next, there are packages sent back on forth that are tagged as ‘established’ therefore, both my server and your router, and finally, your computer allows these packets through, and your browser fills up with the page you requested to see.
On any given network, millions of packets could be sent back and forth every minute as you play a game, someone does homework, and people watch Netflix, Youtube, or Rumble.
