This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Port forwarding maps an outside port to an inside host. The generator drafts a rule from values you type. The source should be a prefix you can say. The world is a decision you write only when the service is built to be public.
SSH, RDP, and the firewall's own admin port are not the lab service. A forward of those to the world is the mistake. Use a VPN for administration.
0.0.0.0/0 in the draft is a line you delete unless the written decision is a public service and the source line is honestly the public service.
One host, one port. The inside address is a device you administer.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name the inside host and the port.
- Name the source prefix.
- Draft the rule.
- Delete a world source if this is not a public service.
- Confirm it is not a management port.
- Do not enable it on this page.
Mistakes that outlive the command
Port Forwarding Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Admin ports forwarded to the world.
- 0.0.0.0/0 left in by habit.
- A host you do not administer.
- Several ports because the menu allowed it.
- NAT treated as a security policy.
Decisions to write down
One decision for Port Forwarding Explained: One inside host. One port. The source is named. Management ports are excluded. And nothing was enabled.
Checks before you call it done
Confirm this before you call the change done: Host, port, and source are in the ticket. A world source is absent or explicitly a public service. The rule is not applied yet. A second person can say the source. And the VPN remains the admin path. If one of those fails, stop.
One port. A named source.
Do not forward management to the world.Before you leave the device
Port Forwarding Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.