IP and SSH over LoRa - incredible job @geeksville! This feature might be more valuable, in the future, than we might think today…
Thank you @Noki for describing the idea behind meshing over UDP.
UDP could be understood, in this case, similarly to wireless connections: direct connections to all within the reach (within the same LAN, WLAN, VPN…). Therefore, nodes could handle both LoRa and UDP interfaces similar, by building a mesh net from nodes they “hear”/reach to, and by maintaining a list of all nodes (both LoRa and UDP neighbors). Mesh packets could be sent the same way on both LoRa and UDP, as the interfaces are responsible for the lowest levels of networking.
UDP is handy, as you can send packets always to a predefined IP and port, regardless of the IP addresses interfaces are currently using. To do UDP meshing, the IP and port to listen to on UDP, for incoming mesh packets, has to be predefined.
The nicest features of UDP meshing would be the a) speed, and b) the ability to seamlessly link the mesh on both LoRa and IP nets. Think about a Meshtastic repeater on a hill, with a 4G/5G WLAN modem nearby with VPN client capability. You could then connect the node to the modem with WLAN, and the modem to the rest of your VPN network. With this setup, users could send ordinary mesh packets from LoRa trough VPN to anywhere on the mesh (limited by the hop count). This configuration would help the maintenance of repeater nodes, as one could do it trough the VPN with help of predefined mesh commands.
Any comments are always appreciated!
PS. @mc-hamster I’m also a big fan of a automatic air time calculation and restricting system. The app could print a value to inform users about the bandwidth left usable on the mesh (answering to the questions: “When will my packet be sent? and How much air time will my message consume of the allowed air time?”)