I'm designing a electronic device running an embedded HTTP server. I'm using lwip TCP/IP stack and the httpd application that comes with lwip.
Because the device is under an ADSL router and the public IP is dynamic, I need to register to a DDNS service, configure it in the router and open one port (NAT). These steps are too tricky for the most of my users. So I'm thinking to a simpler solution.
I know I can create a cloud on the Internet that runs a standard HTTP server to the users, and a custom "IOT" protocol to the remote devices. However this way is too difficult for me and I have to change almost everything that now works well.
I'm thinking of a public HTTP tunnel that limits to forward the users HTTP requests to the HTTP server. Of course, the tunnel is made by two ends: one on the public server (and I could use everything, because I have to start from zero), the other on the embedded device (where I have many restrictions on memory size, computational power, no-OS and so on).
Any experience on implementing a HTTP tunnel on lwip?