Localization and geo-specific testing by simulating traffic from different global locations

Testing localization and geo-specific behavior typically requires deploying infrastructure in multiple regions or relying on third-party proxy services. Both approaches add cost and complexity, and proxy-based testing often produces unreliable results because commercial proxies share IP ranges that many services flag or block.

Tailscale exit nodes let you route traffic from your test machine through a device in any geographic location on your tailnet. By deploying exit nodes in the regions you need to test, you can simulate real user traffic from those locations. Combined with Siege, a command-line load testing tool, you can generate realistic traffic patterns to validate localization, geo-routing, and region-specific content delivery.

Set up exit nodes in target regions

Configure Linux servers in at least two geographic regions (for example, US East and EU West) as exit nodes so your test machine can route traffic through them. Each server needs Tailscale installed and running. Follow the Install Tailscale on Linux instructions if needed.

1. On each regional server, enable IP forwarding:

   echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
   echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
   sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
   

2. Advertise each server as an exit node:

   sudo tailscale set --advertise-exit-node
   

3. Approve each exit node in the admin console. This requires Admin privileges.

   1. Open the Machines page.
   2. Find the regional server, open the ... menu, and select Edit route settings.
   3. Enable Use as exit node and select Save.

4. Verify the exit nodes are available from your test machine:

   tailscale exit-node list
   

   You'll find your regional servers in the output.

Grant access to exit nodes

1. Add a grant to your tailnet policy file that lets your test machines use the exit nodes. Tag your exit node servers with tag:exit-node and grant your test group access:

   "tagOwners": {
   "tag:exit-node": ["group:qa"]
   },
   "grants": [
   {
       "src": ["group:qa"],
       "dst": ["tag:exit-node"],
       "app": {
       "tailscale.com/cap/node-exit": [{}]
       }
   }
   ]
   

1. Assign the tag to each exit node server:

   sudo tailscale set --advertise-tags=tag:exit-node
   

Install Siege on your test machine

Install Siege on the machine you will use to generate test traffic.

brew install siege

Verify the installation:

siege --version

Run geo-specific load tests with Siege

With your traffic routed through a regional exit node and Siege installed, generate load against your application to validate its localization behavior.

1. On your test machine, select the exit node for the region you want to test. For example, to route traffic through your US East server:

   sudo tailscale set --exit-node=exit-us-east
   

2. Confirm that your traffic is routing through the exit node by checking your public IP address:

   curl -s https://ifconfig.me
   

   The output displays the public IP address of the exit node server, not your local machine.

3. Run a basic load test through the US East exit node:

   sudo tailscale set --exit-node=exit-us-east
   siege -c 10 -r 50 -H "Accept-Language: en-US" https://your-app.example.com
   

   This sends 50 rounds of requests with 10 concurrent users, each including the en-US language header. Your application will serve US-localized content based on the geographic origin of the traffic.

4. To verify that your application returns region-specific content, use Siege in verbose mode and inspect the responses:

   sudo tailscale set --exit-node=exit-eu-west
   siege -c 1 -r 1 -v -H "Accept-Language: de-DE" https://your-app.example.com
   

   Check the response headers and content to confirm the application returns the expected localized version.

5. Once you've finished testing, turn off the exit node on your test machine so traffic routes normally:

   sudo tailscale set --exit-node=
   

6. Verify your traffic is no longer routed through the exit node:

   curl -s https://ifconfig.me
   

   The output displays your local machine's public IP address.

Test multiple regions sequentially

Create a script that switches exit nodes and runs Siege against each region:

#!/bin/bash

REGIONS=("exit-us-east" "exit-eu-west")
LANGUAGES=("en-US" "de-DE")
TARGET="https://your-app.example.com"

for i in "${!REGIONS[@]}"; do
  echo "Testing region: ${REGIONS[$i]} with language: ${LANGUAGES[$i]}"
  sudo tailscale set --exit-node="${REGIONS[$i]}"
  sleep 5

  siege -c 10 -r 50 \
    -H "Accept-Language: ${LANGUAGES[$i]}" \
    --log="/tmp/siege-${REGIONS[$i]}.log" \
    "$TARGET"

  echo "Completed: ${REGIONS[$i]}"
done

sudo tailscale set --exit-node=
echo "All region tests complete."

The script cycles through regions, sets the exit node, runs Siege using the language for that region, and then turns off the exit node at the end.