AnalogX PortMapper — Configure IP-Based Access Controls Easily

How to Use AnalogX PortMapper to Redirect TCP/UDP Ports

What it does

AnalogX PortMapper listens on one IP:port and forwards incoming TCP or UDP traffic to another IP:port on your network. Use it to expose services behind NAT, redirect ports to different machines, or run multiple services on the same host.

Step-by-step setup (Windows)

1. Download & run

   • Download PortMapper from the AnalogX site or a trusted archive.
   • Run the executable (no install usually required). Allow through Windows Firewall if prompted.

2. Add a mapping

   • Click Add (or New).
   • Listen IP/Port: set the local IP and port PortMapper should listen on (use 0.0.0.0 to listen on all interfaces).
   • Destination IP/Port: set the target machine’s IP and port where traffic should be forwarded.
   • Protocol: choose TCP or UDP depending on the service.

3. Save & enable

   • Save the mapping and ensure it’s enabled (checkbox or Start button).
   • Repeat for additional mappings.

4. Firewall & router

   • On the forwarding host, allow the listen port through Windows Firewall (Inbound rule).
   • If forwarding traffic from the wider internet, create a port-forward on your router to the forwarding host’s LAN IP and listen port.

5. Testing

   • From the client side, connect to the listen IP:port. Confirm the destination service receives the traffic.
   • Use tools: telnet or nc for TCP, ncat / socat or UDP-specific testers for UDP. You can also use online port checkers for remote tests.

Tips & troubleshooting

• Use specific listen IP to avoid exposing the forwarding on unintended interfaces.
• UDP is stateless: some UDP protocols require handling of responses; test thoroughly.
• Check conflicting services: ensure nothing else is bound to the listen port.
• Logs: PortMapper provides basic logging—inspect it for connection attempts and errors.
• Permissions: run as a user with rights to bind low-numbered ports (<1024) if needed.
• Multiple mappings: you can create many mappings but watch resource limits on the host.

Security considerations

• Only expose services you trust. Restrict listen IPs and use firewall rules to limit allowed source IPs where possible.
• Consider using VPN or SSH tunnels for secure remote access instead of exposing sensitive services directly.