Setting up selective routing
Let's see an example of setting up selective routing to a site via a backup connection Backup ISP, when the Internet connection is provided by the main Internet connection Main ISP.
In our example, the router uses Backup ISP and Main ISP connections, but you may have other interfaces and connections (e.g., Ethernet, DSL, Modem, Wireless ISP, PPPoE, VPN, etc.).
In this article, we will show you how to configure routing to whatismyipaddress.com
through the backup connection.
1. Check that the Backup ISP connection is active and in Connected state:

2. Using the nslookup
utility, we find out which IP address on the Internet resolves the domain name whatismyipaddress.com
:
C:\Users\User> nslookup whatismyipaddress.com
Non-authoritative answer:
Address: 104.16.155.36
Importante
The domain's IP address may change (in our example, it is 104.16.155.36
). If the settings shown in this article do not work, you need to rerun the nslookup
command and check the domain name address.
3. Using the tracert
utility (in Windows), determine the route of the IP packet from the initial client node to the final server node.
Standard ICMP packet transmission to the whatismyipaddress.com
[104.16.155.36
] node in tracert
:
C:\Users\User> tracert whatismyipaddress.com
Tracing route to whatismyipaddress.com [104.16.155.36]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.201.1
2 2 ms 1 ms 1 ms 192.168.8.1
3 2 ms 2 ms 2 ms EMEA.Germany.5504.IP1.regusnet.com [217.110.233.97]
4 2 ms 2 ms 7 ms hosting-240.43.rev.fr.colt.net [213.41.43.240]
5 2 ms 2 ms 2 ms 193.114.169.141
6 31 ms 30 ms 4 ms de-cix-frankfurt.as13335.net [80.81.193.129]
7 3 ms 7 ms 4 ms 172.70.248.5
8 3 ms 3 ms 3 ms 104.16.155.36
Upon finishing the trace, we can see that the IP packet is routed through the servers of the main Internet service provider Main ISP (from the third hop) to whatismyipaddress.com
[104.16.155.36
].
4. Create a static route to the IP address 104.16.155.36
of the whatismyipaddress.com
domain in the router settings:

In Static Route Parameters, select:
— Route type: Route to host;
— Destination host address: 104.16.155.36 (this is the address of the domain whatismyipaddress.com
);
— Interface: the name of the interface through which routing will be carried out (in our example, this is Backup ISP).
Importante
If Connection Policies are configured, the interfaces of the main Internet provider and the backup connection must be in the same policy.

5. Check the IP packet route from the client's initial IP address to the final IP address of the domain whatismyipaddress.com
:
C:\Users\User> tracert whatismyipaddress.com
Tracing route to whatismyipaddress.com [104.16.155.36]
over a maximum of 30 hops:
1 <1 мс <1 мс <1 мс 192.168.1.1
2 48 ms 49 ms 48 ms 10.15.0.0
3 48 ms 50 ms 49 ms vss-xx-yy.fr.eu [5.39.47.47]
4 49 ms 49 ms 49 ms 10.117.81.26
5 49 ms 49 ms 48 ms 10.173.16.108
6 148 ms 50 ms 49 ms 10.195.64.0
7 53 ms 53 ms 53 ms par-th2-sbb2-nc4.fr.eu [54.36.50.226]
8 52 ms 52 ms 52 ms 10.215.2.85
9 56 ms 53 ms 53 ms cloudflare.as1338.fr.eu [54.36.50.29]
10 54 ms 53 ms 53 ms 172.71.124.2
11 53 ms 53 ms 53 ms 104.16.155.36
Upon finishing the trace, we can see that the IP packet is now routed through the Backup ISP (from the third hop) to the whatismyipaddress.com
node [104.16.155.36
].
In the hop chain, we see a change in the provider's IP addresses, which differ from those in point 3 of this article.