When you actually need port forwarding
If you're running something at home β a personal server, a security camera, a NAS β that you want to reach directly from outside, your router needs to be told which internal device incoming requests for a given port should go to. Without a forwarding rule, unsolicited incoming connections are blocked by default, which is normally exactly what you want for security, but it also means services you're intentionally hosting won't be reachable until you open a path to them.
Weigh security before and after you set it up
Every forwarded port is a small increase in your home network's exposure to the internet, so it's worth pairing the setup with basic hardening: strong, unique passwords on the receiving device, keeping its software updated, and reviewing your router's port forwarding list periodically to remove rules you no longer use.
Frequently Asked Questions
I set up port forwarding but still can't connect from outside β why?
This often happens when the internal device's IP address has changed since you created the rule, or when your ISP assigns you a shared or dynamic address instead of a fixed public IP (including carrier-grade NAT). Confirm with your ISP whether you actually have a public IP address.
Is port forwarding dangerous?
Not inherently β if you open only the ports you need and remove the rule once you're done, the risk is manageable. Leaving unnecessary ports open for a long time is what actually increases exposure to attackers.