New Changes To VPN Network Naming Policy is Live

LiquidDave At LiquidVPN

We have published a Liquid Viscosity software and VPN configuration update for both Windows and Mac on 5/3/2015. You can download the latest full install of Liquid Viscosity from your control panel  or wait for you client to notify you of the update. There are some changes to the way our VPN network names are displayed. We have fully switched from a location based naming convention “California 1 Dynamic UDP 1194” “California 2 Dynamic UDP 1194” to a more traditional enterprise naming convention “Brand Dynamic UDP 1194” “Echo Dynamic UDP 1194.” There are a couple reasons behind the change.

Standardized VPN Network Naming Convention

The most important reason was to have a uniform naming convention across the 750+ VPN network configuration files we publish. With the previous setup L2TP/PPTP/SSTP and OpenVPN had different naming conventions and users that generated their own OpenVPN configuration files with our configuration generator would see different names then our Liquid Viscosity users. This is because not all locations with 3 or more server clusters on site can run all of the various protocols and/or ports we offer. This could be very confusing for new users so we finally changed all 750+ configurations to support the newest VPN network names (we hope).

Eliminating The One’s and Two’s From Our VPN Network

When we find good data centers we like to stick multiple servers there. With the previous VPN network naming convention users would choose “California 1 Dynamic UDP 1194” over “California 2 Dynamic UDP 1194” by default simply because it was labeled #1 and we are taught that winners are #1. This lead to an inflated number of users on VPN servers named “California 1 Dynamic UDP 1194” compared to the number of users on “California 2 Dynamic UDP 1194.” Users that bucked the trend and choose “California 2 Dynamic UDP 1194” would benefit from servers with 30% to 50% less users on their chosen server just because they picked #2. We hope that calling our servers by their actual name will spur users to be more adventurous and choose servers via their load statistics. Even if it stops users from automatically selecting #1 there will be a big improvement on overall VPN network usage.

Simplified Technical Support

When a legitimate VPN server problem is reported by a user it is much easier to track down when the actual server name is given instead of “California 1” Because in the past we had 2 servers referred to as California 1. One for PPTP/L2TP/SSTP and another one for OpenVPN. Now these will be referred to by their actual name and will make troubleshooting faster.

Whats Next for LiquidVPN?

We have two new locations coming online this month that we are very excited about. They are Iceland and Singapore. Both of these locations will offer the traditional type of shared IP VPN network only. This is due to IP constraints placed on us at the datacenters. However we still think users will be happy we are finally in Asia and with Iceland privacy laws being some of the strongest on earth it is the perfect offshore location for the next server cluster.