cross-posted from: https://feddit.de/post/10554932

I am looking something to connect to my server from outside my local network.

I am on a shared IP and my ISP doesn’t have port forwarding.

  • Shimitar@feddit.it
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    Why rathole and not ssh tunneling? The latter exposes only one port (that you are already exposing anyway) while the former requires an additional port.

    What is the actual benefit of rathole? I an asking genuinely.

    • towerful@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Hmm, fair.
      I liked it cause i could dockerise it next to nginx and do SNI forwarding.
      It had obvious and declarative config, which helped me get a redundant tunnel set up. Its great at auto-reconnecting.
      I have never used ssh tunnels. Maybe its just as easy as using rathole. Learning ssh tunnels might have been a better path for me.
      But rathole clicked, has been rock solid with 0 tinkering or tweaking, the config files make sense, its easy to in a docker container…

      So, i cant really answer your question.

      • Shimitar@feddit.it
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 months ago

        Fair, setting up ssh tunnels with autoreconnect and such is indeed more complex.

    • towerful@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      I think 1 big advantage is that rathole can work over a websocket connection.
      So, if obfiscating, having to go via HTTP proxies, or whatever… rathole will still work.