A node that only makes outbound connections is still fully validating and perfectly useful. But a node that also accepts inbound connections helps more, because new nodes can connect to it while they bootstrap. Making your node reachable means forwarding a port on your router. Here is how, step by step.
Step 1: Understand what you are doing
By default your router blocks unsolicited inbound traffic. Port forwarding tells the router: when a connection arrives on this specific port, send it to my node machine. This makes your node visible to the wider network without exposing anything else.
Step 2: Find your node listening port
Check the node configuration or documentation for the network port it listens on. You will forward exactly this port. Note it down precisely; forwarding the wrong port simply does nothing.
Step 3: Give your node machine a fixed local address
In your router settings, reserve a static local IP for the node machine (often called a DHCP reservation). This stops the machine address from changing, which would break the forward. Use the machine network name or hardware address to pin it.
Step 4: Create the forwarding rule
Log into your router admin page. Find the port forwarding section. Create a rule that forwards the node port to the fixed local address from the previous step, for both the protocol the node uses. Save and apply the rule.
Step 5: Allow the port in any local firewall
If the node machine runs its own firewall, add a rule there to permit inbound connections on the node port. A forward at the router does no good if the machine firewall then blocks the traffic.
Step 6: Test reachability
Use an external port-checking method while the node is running to confirm the port is open from outside. If it shows closed, recheck the local IP, the firewall, and that the node is actually running and listening.
Step 7: Watch inbound peers appear
Once the port is open, your node status will start showing inbound connections over time as other nodes discover and dial in to you. You are now hosting newcomers and pulling more weight on the network.