I have a nice BBB Node Red application that runs on my LAN quite nicely. Now, I’d like to be able to transport it and access it remotely. I see two problems with this.
To use it on a new system, I have to get through its router. This usually entails forwarding port 1880 to the BBB, but it would have an unknown DHCP-provided IP address, and
To find the new system, I would need to know its external IP address.
I’ve been trying to find answers to these problems, and what I’ve come across is
MQTT, WebRTC, STUN, TURN, and ICE.
This alphabet soup is causing me to tear out what little hair I have left. Do I set up an MQTT broker; do I access a publicly available one? Same questions with WebRTC. And if I do one of these, how do I integrate it with my existing application? Do I do something with its existing websocket nodes? Do I use MQTT nodes?
Please point me at something that can help. I’ve seen basic tutorials (type “Hello World” into one instance and lo-and-behold, it shows up on the other side), but I’ve not found anything useful beyond that. What do I have to do to provide a web page displaying locally acquired data using Node Red dashboard elements?
On Wed, 6 Sep 2017 11:35:21 -0700 (PDT), Richard
<rltenney@gmail.com> declaimed the following:
I have a nice BBB Node Red application that runs on my LAN quite nicely.
Now, I'd like to be able to transport it and access it remotely. I see two
problems with this.
1) To use it on a new system, I have to get through its router. This
usually entails forwarding port 1880 to the BBB, but it would have an
unknown DHCP-provided IP address, and
2) To find the new system, I would need to know its external IP address.
I've been trying to find answers to these problems, and what I've come
across is
MQTT, WebRTC, STUN, TURN, and ICE.
This alphabet soup is causing me to tear out what little hair I have left.
Let me add another bit of alphabet soup: DynDNS (though that is a
particular provider -- look for "dynamic DNS" providers)
You'll still need to set up port forwarding on any routers that are in
the way, but this could be how you'd get a fixed domain name linked to the
assigned IP address of the router. The BBB would be set up to connect to
the dynamic DNS server on boot, identifying itself by name -- which gets
associated with the IP of the packet containing the identity. The server
then handles name translation for initiating requests to the device.
(Open)VPN - that’s Virtual Private Network - lets you access the BBB like you are on the same network.It’s especially easy to set up if you use the BBB as a client.