10 ms·

Hey, tell us more, please :) I'v hoped to find in your profile maybe more info/blog, but instead: > Group supervisor at NASA Jet Propulsion Laboratory working

by jve 5y ago

Hey, tell us more, please :) I'v hoped to find in your profile maybe more info/blog, but instead: > Group supervisor at NASA Jet Propulsion Laboratory working in autonomous vehicles and sensing for space exploration. Oh well, a little out of scope and I see you blog about other things. Anyway - you mean I don't need static IP to form a network of distant IoT devices? This would be some really useful property.

jvanderbot 5y ago
> Group supervisor at NASA Jet Propulsion Laboratory working in autonomous vehicles and sensing for space exploration. Yes, at JPL they let engineers cycle in and out of management. (Serving institution / projects in phases) > Anyway - you mean I don't need static IP to form a network of distant IoT devices? This would be some really useful property. Yes, wireguard will "keep alive" a connection to peers by sending udp packets. This fools stateful sufficiently to allow traffic to migrate across networks easily. Kind of how push notifications magically follow you. On top of those connections, wireguard establishes its own IP addresses for each peer. If you set up wireguard, senging a packet over IP that is one of your wireguard peers will get tunnelled through UDP to the peer at its location and real IP. Thus, you know the node by the WG IP, but it gets delivered seamlessly via whatever means necessary. VPNs have done this forever. Wireguard makes it trivial and portable and fast.