Ping TNSR WAN Interface from local network¶
The instance should now be reachable via ICMP echo request (ping) using the Elastic IP Address associated to the TNSR WAN Interface.
To find the Elastic IP address associated to the TNSR WAN Interface, use the EC2 Web Console:
Navigate to https://console.aws.amazon.com/ec2/
Click the button next to the TNSR interface to select it
Look at the bottom of the page, under the Description tab to see Network Interfaces
Click on eth1
Find the Elastic IP Address field in the popup
Now, try to ping the Elastic IP Address of the TNSR WAN Interface:
bash-3.2$ ping -c 5 22.214.171.124 PING 126.96.36.199 (188.8.131.52): 56 data bytes 64 bytes from 184.108.40.206: icmp_seq=0 ttl=45 time=48.781 ms 64 bytes from 220.127.116.11: icmp_seq=1 ttl=45 time=49.232 ms 64 bytes from 18.104.22.168: icmp_seq=2 ttl=45 time=49.238 ms 64 bytes from 22.214.171.124: icmp_seq=3 ttl=45 time=48.632 ms 64 bytes from 126.96.36.199: icmp_seq=4 ttl=45 time=48.433 ms --- 188.8.131.52 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 48.433/48.863/49.238/0.323 ms
Once the Host OS is capable of reaching the Internet, check for updates (Updating TNSR) before proceeding. This ensures the security and integrity of the router before TNSR interfaces are exposed to the Internet.