Skip to content
Better handling of multiple connection profiles
Suggestions/comments/criticisms are welcome here
OpenVPN provides connection profiles, allowing for a single .ovpn to contain multiple endpoints:
(From the 2.4 man page)
Case in point, the Streisand script generates a suite of OpenVPN profiles, one of which is a `combined` profile that groups together the various OpenVPN access points it provides, making it easy to use a single configuration that would stand a better chance of establishing a connection in a more restrictive network environment (i.e try udp 8757, then try tcp 636, then finally try tcp 443).
While Viscosity does import the profiles correctly and they all do work, it does make it slightly more cumbersome to use in such a situation, and for those people who may be less tech oriented may face some degree of difficulty.
In any case, thank you for your time!
(From the 2.4 man page)
Code: Select all
Based on my observation, importing such a profile into Viscosity duplicates them into separate connections that must be chosen manually. Here is an example of connection profile usage:
client
dev tun
<connection>
remote 198.19.34.56 1194 udp
</connection>
<connection>
remote 198.19.34.56 443 tcp
</connection>
<connection>
remote 198.19.34.56 443 tcp
http-proxy 192.168.0.8 8080
</connection>
<connection>
remote 198.19.36.99 443 tcp
http-proxy 192.168.0.8 8080
</connection>
persist-key
persist-tun
pkcs12 client.p12
remote-cert-tls server
verb 3
Case in point, the Streisand script generates a suite of OpenVPN profiles, one of which is a `combined` profile that groups together the various OpenVPN access points it provides, making it easy to use a single configuration that would stand a better chance of establishing a connection in a more restrictive network environment (i.e try udp 8757, then try tcp 636, then finally try tcp 443).
While Viscosity does import the profiles correctly and they all do work, it does make it slightly more cumbersome to use in such a situation, and for those people who may be less tech oriented may face some degree of difficulty.
In any case, thank you for your time!
Hi cudiaco,
Thanks for the feedback, we'll take it on board.
Viscosity actually already supports trying multiple servers/ports/protocols for a single connection by listing multiple servers in the Remote Server Address field by separating them, for example:
Cheers,
James
Thanks for the feedback, we'll take it on board.
Viscosity actually already supports trying multiple servers/ports/protocols for a single connection by listing multiple servers in the Remote Server Address field by separating them, for example:
Code: Select all
This however does not allow other settings to be mixed in, such as the http-proxy setting in this instance.198.19.34.56:1194:udp, 198.19.34.56, 198.19.34.56:443:tcp, 198.19.36.99:443:tcp
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
3 posts
Page 1 of 1