Recently I had the following issue with my Turtlebots: They are only connected to a local network without a route to an uplink with internet connection. This is okay as I just want them to communicate with other ROS2 devices inside the local network. But sometimes I want to update or install a new package with apt or pip. Usually the Turtlebot/Pi would need a internet connection for this. But inside this local network only my notebook has internet access through a different network interface. I could use the notebook as a router but I don't want to get into the hassle of doing this, as network stuff with ROS2 is already complex enough.
But there is another way to achieve this communication from the Turtlebot to the WWW via my notebook: the SOCKS5 proxy.
When I ssh onto the Turtlebot (remotehost) I can use the -R option to open a SOCKS5 proxy port on the remotehost whi