Skip to content
Split tunneling based on Ports / Protocols
Suggestions/comments/criticisms are welcome here
Hello,
I've been using Viscosity for about a year now and I really like the way the App was built. It does everything perfectly well without any issues, however I would like to see a feature implemented.
Someone spoke about Split tunneling based on Application here http://www.sparklabs.com/forum/viewtopic.php?f=4&t=1191 and that feature has priority over this one.
However I would like to see a way to split the traffic by ports or protocols. Basically sometimes I end up using networks that are very fast and stable but block everything else than port 80 and 443. It would be great if I could tell Viscosity to allow traffic on port 80 and 443 to flow over the local network gateway but tunnel everything else over a VPN connection.
It would be also good to be able to tell the opposite: Send everything over the VPN except for traffic on ports 1020 or 1040 (for example).
Thank you.
I've been using Viscosity for about a year now and I really like the way the App was built. It does everything perfectly well without any issues, however I would like to see a feature implemented.
Someone spoke about Split tunneling based on Application here http://www.sparklabs.com/forum/viewtopic.php?f=4&t=1191 and that feature has priority over this one.
However I would like to see a way to split the traffic by ports or protocols. Basically sometimes I end up using networks that are very fast and stable but block everything else than port 80 and 443. It would be great if I could tell Viscosity to allow traffic on port 80 and 443 to flow over the local network gateway but tunnel everything else over a VPN connection.
It would be also good to be able to tell the opposite: Send everything over the VPN except for traffic on ports 1020 or 1040 (for example).
Thank you.
Hi TCB13,
Thanks for the feedback - it's much appreciated. Routing based on port or protocol is very difficult as the IP specification was never designed for such a thing, but we'll keep it in mind.
Cheers,
James
Thanks for the feedback - it's much appreciated. Routing based on port or protocol is very difficult as the IP specification was never designed for such a thing, but we'll keep it in mind.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts
Page 1 of 1