Note: On some systems that are accessed remotely over the Internet, port forwarding is not needed. They make an outbound connection to “The Cloud” – to servers of their manufacturer, and by doing so, allow the incoming connection. Usually, incoming connections cannot pass the NAT boundary between Public IP and Private IP. Routers do not know which computer or device should receive traffic. Thus, Port Forwarding.
Our Router products already have Port Forwarding in: Settings > Port Forwarding.
Note: Description is whatever you want to call it. Ports: Public is the port(s) accessed from the Internet (outside the boat). Ports: Private is the port or ports range (inside the boat) (usually the same as Public) of your device or system needing remote access. The protocol is the TCP/IP protocol (TCP, UDP, or BOTH). IP: is the inside IP Address of your device or system needing remote access. Usually, the IP is 192.168.101.X or 192.168.105.X depending on whether this device is on Router Ethernet Port #1 (blue port, aka Main LAN) or Port #5 (far left yellow port, aka Guest LAN). The AP – WiFi Access Point of the Router is configured (in Local APs) linked to Router Ethernet Port #1. So, a device on WiFi would be forwarded to as if it were on Ethernet Port #1. It is possible to Port Forward from a WiFi Receiver to the router and then forward to your device or system. We have an instruction document on how to do this.