This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I think there is a very good chance that the support staff is incorrect. Nearly every Internet of Things (IoT) gizmo works the same way:
The device opens a TCP connection to the company "cloud". (This is possible because the router does not block any outgoing connections.)
Once that connection is open, the cloud can communicate with the device on the connection that the device opened.
This allows the user to use a smartphone app to control the device from anywhere by connecting to the company cloud, which then relays commands (and feedback) along that existing connection.
Think about it. When a web page asks to "get" web pages from somewhere, does the router have to "open a port" so that the web site can communicate? No. The web browser opened a connection and the web site sends information through it.
Is it port forwarding or custom port forwarding? I was looking for something worded about opening a port outbound and inbound. I will have to make the device use a static IP also.
@SuperPCM781 wrote: Is it port forwarding or custom port forwarding? I was looking for something worded about opening a port outbound and inbound. I will have to make the device use a static IP also.
Can you tell us more about what you're trying to do (e.g., setup a public Minecraft server)? I ask because we may be able to point to instructions that better describe the overall process vs. helping you with individual steps, without overall context.
Working on getting my MyQ Garage Controller not to go offline. Their support said the following “Verify inbound and outbound TCP port 8883 is open. Verify the port is not being blocked by your router or a firewall product. Not having this port open will cause the myQ Wi-Fi product to not connect to the server.”
I think there is a very good chance that the support staff is incorrect. Nearly every Internet of Things (IoT) gizmo works the same way:
The device opens a TCP connection to the company "cloud". (This is possible because the router does not block any outgoing connections.)
Once that connection is open, the cloud can communicate with the device on the connection that the device opened.
This allows the user to use a smartphone app to control the device from anywhere by connecting to the company cloud, which then relays commands (and feedback) along that existing connection.
Think about it. When a web page asks to "get" web pages from somewhere, does the router have to "open a port" so that the web site can communicate? No. The web browser opened a connection and the web site sends information through it.
