I have setup a ESP32 board to receive and send data from/to Ubidot brokers. I have tested the boad and the program with the board connected to a local network behind a router allowing port forwarding and with a public IP address (dynamic but accessible through services like NOIP). Everything was ok, even without any port forwarding rule related with Ubidots connection.
Then I have moved the board to the local network in my vacation home, with a 4G router and a local network behind, so, CGNAT, with no port forward capability and with no public address accessible. Communication with Ubidots is no longer working.
When moving the board I had the hope that Ubidots software would implement some sort of reverse tunnel allowing the communication with Ubidots even if the client was on a local network behind CGNAT. But clearly this is not the case. I have implemented from my side a ssh reverse tunnel through which I can access through ssh the board in my vacation home network, but I have not set up (yet) any reverse tunnel to communicate with Ubidots broker.
Has anybody faced a similar situation and solved the communication problem of a client behind CGNAT and Ubidots broker ? This is something that many IOT applications will have to overcome to run on remote sites without “normal” internet access.
Thanks very much for your help
Best regards
Joan