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
I should probably split this issue into two separate ones, but it will be less bothersome for you to just have it all in once spot:
I will test this on 23.7 when I have a chance, but haven't done it yet. What is the status for 23.7 support? (They are changing a significant amount of things in the UI and MVC).
Could some documentation be added about the actual tunneling approach? I'm mostly interested in seeing it documented, although I have reviewed the source code.
My notes on the hopping setup: The route setup is a clever way to go about it but it can be tricky if the routing table is polluted and left in an inconsistent state. I have not verified this but you probably want to store the expected addresses somewhere for the current or last call to addroute, and then have some failsafe mechanism to remove those entries (func_delroute). Should the configuration fall out of sync for whatever reason, the route deletion might fail due to a SRVIP mismatch.
I understand this "cannot" happen in normal circumstances, but it's always better to be safe than sorry as they say.
Another idea: v2ray is an excellent way to allow cascading of tunnels. Some providers offer shadowsocks and similar mechanisms to add hops to the VPN chain.
Last but not least, thank you and well done on this plugin :-)
The text was updated successfully, but these errors were encountered:
Hi,
I should probably split this issue into two separate ones, but it will be less bothersome for you to just have it all in once spot:
My notes on the hopping setup: The route setup is a clever way to go about it but it can be tricky if the routing table is polluted and left in an inconsistent state. I have not verified this but you probably want to store the expected addresses somewhere for the current or last call to addroute, and then have some failsafe mechanism to remove those entries (func_delroute). Should the configuration fall out of sync for whatever reason, the route deletion might fail due to a SRVIP mismatch.
I understand this "cannot" happen in normal circumstances, but it's always better to be safe than sorry as they say.
Another idea: v2ray is an excellent way to allow cascading of tunnels. Some providers offer shadowsocks and similar mechanisms to add hops to the VPN chain.
Last but not least, thank you and well done on this plugin :-)
The text was updated successfully, but these errors were encountered: