Default Gateway of VPN don't work
I have configured 4 servers with the same VPC 10.10.50.0/24 the default gateway is 10.10.50.1 and when doing an ip route show
I see that this is the default via 10.10.50.1 dev eth0 proto static
10.10.50.0/24 dev eth0 proto kernel scope link src 10.10.50.5, however I see that when doing a traceroute either to another server in the same VPC or to Google's DNS, for example 8.8.8.8, I see that all the packets go out through an ip that is not configured on any of my servers
root@encrypted-node:~# traceroute 10.10.50.6
traceroute to 10.10.50.6 (10.10.50.6), 30 hops max, 60 byte packets
1 192.0.0.8 (192.0.0.8) 0.099 ms 0.053 ms 0.061 ms
How do I get everything to go through the default route and have access to the internet?
1 Reply
After reaching out to our networking team, it's my understanding that the traffic is going through the default route. The IP you mentioned is a "dummy IP" according to IANA. I found a few possible uses for this address and I can't say exactly how it fits into the infrastructure of our VPC, but it doesn't seem like it's the real IP here.
As long as you enable NAT 1-1 on the VPC interface and make that the default interface, you should be able to reach the internet using the default route.
If you want to explain more about why you need a particular route or what your concerns are, it's possible someone from our Community could have additional networking experience to help you figure it out.