Please see my forum posting on this same topic located at http://forum.goldenfrog.com/t/connect-to-fastest-server-within-a-specific-region/1057/2

Currently VyprVPN has the capability to connect to the "fastest server", which is an excellent feature.

However, there are times when the "fastest" (closest) server is not the best one for me to use.

Example: I am abroad, (outside the U.S.), and I need to connect to a server within the U.S. - somewhere - though it may not really matter where. (My e-mail clients depends on this to successfully send mail.)

As it is now, I select a particular server, (in my case, NY), and automatically connect to it at Windows startup.

What I would like to do is to connect to whatever server is the fastest server within a particular region - be it the U.S., Europe, Australia, etc. This would have certain particular advantages:

1. If my "usual" server, (NY for example), goes down, has issues, or is swamped with connections, my VyprVPN would automagically select another - better - server to connect to.
2. If a new server is added to the region I selected, it would automagically become part of the server pool I can use to connect.
3. If the server rotation feature becomes available - and is integrated with this feature - I would have the potential for a different server location each login - which could be a significant advantage if you want to avoid being geo-location tracked.

Thanks again for a wonderful product!

Jim

Crosspost from:
http://forum.goldenfrog.com/t/vyprvpnservice-exe-constantly-running/1247/8
"vyprVPNservice.exe constantly running"

Crossposted here at request of Golden Frog.

@keegan

Thanks for the update! I had also noticed this behavior and figured that something like the reasons you enumerated were the cause of it.

Suggestion:
This is especially important on potentially memory-starved systems where the user may wish to use VyprVPN, but cannot afford to have it running full-time, or on the Android version where memory and processor cycles are very likely to be at a premium:

• Create separate option items for "Start Application and start Service on startup, where "Start Application on startup" would automatically enable service start too.

• Add the behavior that, if both "Start application" and "Start service" at startup are not selected, when the application quits that all subordinate processes are killed as well.
  ** Alternately, there could be an option " 'Quit' also kills background services" that would be enabled if neither of the previous options are selected. (i.e. This option would be greyed-out if either of the two prior options get selected.)

• Add the behavior that, if the service is not running at application startup, that the service gets started silently. (This would also solve the "Cannot Contact Service" issues everyone is reporting!) An exception (error) would only get thrown if the service could not be started within a reasonable amount of time, or after "X" number of attempts.

The justifications for these actions are thus:

• If the user does not want the app to run at startup, he probably has a good reason for not wanting it to run at all. (i.e. He's on a trusted network, etc.) Forcing the user to specifically hunt-down and kill the service, if not selected at startup, is just pissy and annoying.

• If the user wants the service to run at startup, it can be selected. It can even be selected as the default setting during installation.

• In memory starved environments, or operating systems that are just pigs, (make that read "Windows 8"), leaving the service running can impact system performance.

• Android systems, especially on phones, are often memory and processor cycle starved. Leaving potentially unnecessary services running can have a seriously negative impact on performance, causing the user to ultimately un-install the app to avoid the performance crunch.

Thanks again for an excellent application, and I hope that these suggestions will receive expedited consideration.

Jim (JR)

At the moment, VyprDNS seems to be only available for users of the VyprVPN apps (confirmed by online support team).

In my case my Synology NAS need to connect as a client to VyprVPN (which works fine using the howto), but DNS queries are not resolved over VyprDNS as there seems to be no way to set the VyprDNS server address in /etc/resolv.conf (at least for me it does not get set automatically).

Would be great if we could get the VyprDNS server IP addresses to use for manual setups.

Now I have to use Google DNS servers as using the router IP address will bypass the VPN connection on DNS lookups (Wireshark confirmed). This only gives partial protection (only a degree of anonymity).

Of course, this might be integrated in a Synology NAS application, but that might still clash with my setup as the NAS is also my DHCP and DNS server (dnsmasq) for resolving internal network addresses (depending on how the app would be written of course).