You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So i have rathole in place, and everything is working fine.
One VPS has HAPROXY + RATHOLE as a server
I have a NAS at home, with some services (runnint as docker containers) tunneled to the RATHOLE server
(this is very standard, so when using the public IP of the VPS (through HAPROXY, i can reach my "home" services running inside my NAS).
But now i need to do for one specific use-case the opposite : i want to tunnel a service running on server side (inside the VPS) to only be able to access it from my home network.
As i already have the server <> client of rathole in place (the two processes being connected), is it possible to expose one tunnel in the other direction ?
Basically i would like to have :
on the server (VPS) a "local_addr" configuration
on the client (NAS) a "bind_addr" configuration
(whereas of course for now i have only the opposite - "bind_addr" at server (VPS) level and "local_addr" at client (NAS) level)
But after first test, it seems i can't do that (server only accepts "bind_addr")
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
So i have rathole in place, and everything is working fine.
(this is very standard, so when using the public IP of the VPS (through HAPROXY, i can reach my "home" services running inside my NAS).
But now i need to do for one specific use-case the opposite : i want to tunnel a service running on server side (inside the VPS) to only be able to access it from my home network.
As i already have the server <> client of rathole in place (the two processes being connected), is it possible to expose one tunnel in the other direction ?
Basically i would like to have :
(whereas of course for now i have only the opposite - "bind_addr" at server (VPS) level and "local_addr" at client (NAS) level)
But after first test, it seems i can't do that (server only accepts "bind_addr")
Beta Was this translation helpful? Give feedback.
All reactions