Skip

Drawing 03 · Gateway boundaries

Home / Gateways

Gateway and forwarding plan

Every tunnel needs named ends.

MobaXterm supports SSH gateways for several session types and provides a graphical tunnel manager. We turn the diagram into an owned route with explicit local, gateway, and destination endpoints.

Blueprint model of nested SSH tunnels connecting a workstation to services
LOCAL END → GATEWAY → REMOTE ENDPorts are recorded in the working packet

Forwarding is a direction, not a label.

ROUTE VOCABULARY
PatternQuestion to answerTypical test
Gateway / jump hostWhich boundary must be crossed first?Destination reachable only through approved gateway
Local forwardingWhat local listener reaches which remote service?Local endpoint resolves to intended destination
Remote forwardingWho is allowed to expose the reverse path?Explicitly authorized remote listener
Dynamic forwardingWhich applications may use the proxy route?Scoped client behavior and teardown
Source
Workstation, local interface, client, and initiating user.
Gateway
Host owner, authentication, logging, lifetime, and support contact.
Destination
Resolved host, service port, environment, and data sensitivity context.
Stop condition
How to close the route, confirm teardown, and escalate unexpected reachability.

Review sequence

  1. Draw endpoints

    No unnamed arrows.

  2. Confirm owners

    Each boundary has an accountable team.

  3. Exercise

    Test connect, failure, reconnect, and teardown.

  4. Record

    Publish purpose and expiry assumptions.

Add the base session record.

Pair with SSH session design