Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Google application displays content from a different region when accessed using VMware SD-WAN by VeloCloud. (74777)

Last Updated: 10/3/2019Categories: InformationalTotal Views: 1926Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A Google application, such as YouTube, Google Search, Maps, Gmail etc. uses a region different from the user’s actual location. Example: a user in the northwest United States is streaming YouTube content. The user is behind a VMware SD-WAN by VeloCloud powered network, their traffic traversing a VMware SD-WAN by VeloCloud Gateway located in the Greater Seattle Area and uses a US public IP address.  However, the user notices that the YouTube location is Canada, and not the expected US.

Purpose

This article will outline the reasons an incorrect site geolocation may occur when using Google applications and the different solutions that a network engineer may use to overcome the problem.

Cause

In order to understand why a service such as Google may load content from a region different from the user’s location, we need to understand how these applications deliver data based on the location of the user.

Google maintains a Geo IP database which is updated whenever a client uses a Google application. Many users utilize a smart phone with GPS and connection to a cellular network, and Google can track where those users are located and update their Geo IP database accordingly to show the content for that country. This can be an issue when a VeloCloud Gateway is located near a national border such as Canada.  VeloCloud Gateways are multi-tenant—meaning numerous customers and their client users are connecting out to the web using a single Gateway.

Going back to our example, all these clients may be using the Seattle-based VeloCloud Gateway, but many of those clients are in Vancouver, Canada.  Consider a VeloCloud client user in Vancouver who using a smartphone and is connected to a VMware SD-WAN Edge.  When that user connects to a Google application, Google's geolocation mechanism will detect that the traffic is sourcing from Canada and update its Geo IP database to reflect that the IP for the Seattle Gateway is in fact located in Canada. Google will then adjust the content delivered to the customers connected to this Gateway to reflect this new geolocation.

Resolution

VMware SD-WAN by VeloCloud customers should expect that sending traffic through a VeloCloud Gateway may result in inaccurate geolocation for Google applications—especially when customers are located near a national border. VeloCloud cannot control Google’s method of establishing geolocation for our Gateway IP’s and previous efforts to engage Google on this matter have not been productive.

There are several ways to work around this issue:
•    The most common workaround is to configure a business policy to send a Google application Direct instead of going through the VeloCloud Gateway.  You may need to configure multiple rules to account for all affected Google applications.

Sending traffic Direct means that Google will see the source IP as the Local ISP.  Local ISPs do not suffer from Google geolocation issues the way a multi-tenant/single IP service such as VMware SD-WAN using a Gateway would.
Note: You will need to run Remote Diagnostics->Flush Flows to ensure the rule applies immediately to all traffic.
•    Backhaul traffic to a hub that does not use the affected Gateway; or change the Gateway assignment by modifying the gateway pool. There are two potential drawbacks with this workaround: first the alternate hub or Gateway may increase latency for this customer; second the alternate Gateway may manifest the same behavior seen with the current Gateway.
•    Ask users to select their default region for the specific Google application. The drawback here is that this requires each user to manually configure settings versus a more global solution.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ホット パッチを適用した後、使用量メーターがログ バンドルのエクスポートに失敗し、暗号化されていないレポートを送信する (74693)

KB
•
在 VMware NSX-T Controller 节点上，/var/log 分区呈指数增长，而不进行轮换 (74758)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware SD-WAN by VeloCloud

Take Our Survey

Support Assistant