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 the concrete issue I'm facing is that the SOCKS proxy I'm using is broken after my Mac goes to sleep.
A simple toggle-off/toggle-on restores it back to working, but obviously not having to do that would be better.
I'm not sure if that impacts tunnels besides SOCKS proxies.
Having some sort of auto reconnect that restores the connection when XPipe detects that it is broken would be great (not sure if that is technically feasible).
The text was updated successfully, but these errors were encountered:
Something like that would be technically feasible, but it would require some work. Essentially implementing some form of background thread that continuously checks all open tunnels if they are still alive.
I would have to try that out myself first with the sleep, but in theory something like https://superuser.com/a/146641 could work around this by letting the ssh client do more retries. If you add that to your SSH config and it makes a difference, xpipe could do the same
So the problem that I see, at least on macOS, is that I use a wireless connection and that takes like 15s to initialize after the system starts/resumes. Or just restarting any tunnels on resume will probably fail because the internet connection is not there yet
Hi,
so the concrete issue I'm facing is that the SOCKS proxy I'm using is broken after my Mac goes to sleep.
A simple toggle-off/toggle-on restores it back to working, but obviously not having to do that would be better.
I'm not sure if that impacts tunnels besides SOCKS proxies.
Having some sort of auto reconnect that restores the connection when XPipe detects that it is broken would be great (not sure if that is technically feasible).
The text was updated successfully, but these errors were encountered: