AnycastIP - setup and configuration

Connecting to AnycastIP


Note: connecting to Rage4 AnycastIP requires some system and network administrating skills.

1. AnycastIP requires ZeroTier client installed. Please follow ZeroTier documentation how to install it on your desired platform.  

2. Once the ZeroTier client is installed download our setup script by running following command
wget -O connect2anycast.sh https://gbshouse.com/connect2anycast.sh
3. Before connecting your server to AnycastIP you will need following details available in our control panel
  • Rage4 username (email address)
  • Rage4 API key
  • AnycastIP network AS number
  • AnycastIP region code (see below)
4. To connect please execute the setup script with arguments from step #3
bash ./connect2anycast.sh -u <Rage4 username> -p <Rage4 API key> -a <AnycastIP AS number> -r <AnycastIP region code>
5. Once connected your server should be visible in control panel

Establishing BGP session and routing configuration


Once connected to AnycastIP platform, in order to use your anycast addresses you need to establish BGP session. One node can be connected to single AnycastIP router (single IPv4 and/or IPv6 session). Your can have multiple nodes per region - all our routers support ECMP.

1. Install desired routing software (for example FRRouting, BIRD, Quagga, ExaBGP etc.)

2. Get the IP addresses of our router in given region (see below) and configure BGP sessions using following details
  • Remote AS number: 198412
  • EBGP multihop: 25
  • Local AS number:  available via control panel
  • Password: available via control panel
3. Start the sessions, wait around 5-10 minutes for our configuration to auto adjust

4. Create interface of type "dummy" and assign your anycast IP to it
ip link add dummy0 type dummy
ip link set dummy0 up
ip -4 addr add dev dummy0 <anycast IPv4 address>/32
ip -6 addr add dev dummy0 <anycast IPv6 address>/128
4. Before announcing your anycast subnets please configure the reverse routing
echo '666       anycast' >> /etc/iproute2/rt_tables
ip -4 rule add from <anycast IPv4 address>/32 table anycast
ip -4 route add default via <router IPv4 address> table anycast
ip -6 rule add from <anycast IPv6 address>/128 table anycast
ip -6 route add default via <router IPv6 address> table anycast
5. Add announcement of given anycast addresses to your BGP configuration

BGP traffic engineering


Please note that AnycastIP utilizes extended BGP communities only

Customers wanting to alter local preference on their routes
  • rt 198412:120 - customer default
  • rt 198412:110 - customer backup
  • rt 198412:100 - customer fallback
  • rt 198412:666 - blackhole
Communities marked on routes sent to customer
  • 198412:1000 - North America
  • 198412:1003 - Chicago, IL, US
  • 198412:1004 - Dallas, TX, US
  • 198412:1005 - Los Angeles, CA, US
  • 198412:1006 - Miami, FL, US
  • 198412:1007 - Seattle, WA, US
  • 198412:1008 - San Jose, CA, US
  • 198412:1009 - New York, NY, US
  • 198412:1200 - Europe
  • 198412:1201 - Frankfurt, DE
  • 198412:1203 - London, UK
  • 198412:1205 - Paris, FR
  • 198412:1206 - Amsterdam, NL
  • 198412:1400 - Asia and Pacific
  • 198412:1405 - Singapore, SG
  • 198412:1406 - Sydney, AU
  • 198412:1407 - Khabarovsk, RU
  • 198412:1408 - Tokyo, JP
  • 198412:1600 - South America
  • 198412:1601 - Sao Paulo, BR
  • 198412:1800 - Africa
  • 198412:1801 - Johannesburg, ZA

AnycastIP regions


AnycastIP is available in following regions

Africa  
  • Johannesburg, ZA (code "jhb", IPv4 172.31.255.181, IPv6 fd00:dead:c0de:cafe:172:31:255:181) 
Asia
  • Khabarovsk, RU (code "khv",  IPv4 172.31.255.147, IPv6 fd00:dead:c0de:cafe:172:31:255:147)
  • Singapore, SG  (code "sin", IPv4 172.31.255.145, IPv6 fd00:dead:c0de:cafe:172:31:255:145)
  • Sydney, AU (code "syd", IPv4 172.31.255.146, IPv6 fd00:dead:c0de:cafe:172:31:255:146)
  • Tokyo, JP (code "tok", IPv4 172.31.255.148, IPv6 fd00:dead:c0de:cafe:172:31:255:148)
Europe
  • Amsterdam, NL (code "ams", IPv4  172.31.255.126, IPv6 fd00:dead:c0de:cafe:172:31:255:126)
  • Frankfurt, DE  (code "fra", IPv4 172.31.255.121, IPv6 fd00:dead:c0de:cafe:172:31:255:121)
  • London, UK  (code "lon", IPv4 172.31.255.123, IPv6 fd00:dead:c0de:cafe:172:31:255:123)
  • Paris, FR  (code "par", IPv4 172.31.255.125, IPv6 fd00:dead:c0de:cafe:172:31:255:125)
North America
  • Chicago, IL, US (code "chi", IPv4 172.31.255.103, IPv6 fd00:dead:c0de:cafe:172:31:255:103)
  • Dallas, TX, US (code "dal", IPv4 172.31.255.104, IPv6 fd00:dead:c0de:cafe:172:31:255:104)
  • Los Angeles, CA, US (code "lax", IPv4 172.31.255.105, IPv6 fd00:dead:c0de:cafe:172:31:255:105)
  • Miami, FL, US (code "mia", IPv4 172.31.255.106, IPv6 fd00:dead:c0de:cafe:172:31:255:106)
  • New York, NY, US (code "nyc", IPv4 172.31.255.109, IPv6 fd00:dead:c0de:cafe:172:31:255:109)
  • San Jose, CA, US (code "sjc", IPv4 172.31.255.108, IPv6 fd00:dead:c0de:cafe:172:31:255:108)
  • Seattle, WA, US (code "sea", IPv4 172.31.255.107, IPv6 fd00:dead:c0de:cafe:172:31:255:107)
South America
  • Sao Paulo, BR (code "sao", coming soon)

Feedback and Knowledge Base