I have a problem with , I believe , routing on DO Servers.
I manage to connect to servers. One from DO and second from UpCloud with RouterOS on those servers. (I have customized OS on those server to use CHR Mikrotik).
Connected two servers (CHR) with L2TP/IPsec and I have a problem.
Server from UpCloud can ping Mikrotik CHR on DigitalOcean but… Server from DigitalOcean can’t ping Mikrotik CHR on UpCloud
Routing table on Droplet looks strange after adding entry to UpCloud Network where UpCloud Mikrotik is located with all other servers (I have masked public addresses with
Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 xx.xx.xx.xx 0.0.0.0 UG 0 0 0 eth0 10.5.0.0 10.129.9.234 255.255.252.0 UG 0 0 0 eth1 10.14.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 10.129.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 xx.xx.xx.xx 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.129.9.234 - this is the IP of the DigitalOcean Mikrotik CHR Droplet and 10.5.0.0/22 is network on the other side - the UpCloud Network. ping obviously gave me 100% lost packets but traceroute looks strange
traceroute to 10.5.0.120 (10.5.0.120), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * ... 30 * * *
10.5.0.120 is the IP of the UpCloud Mikrotik CHR Router There should be on the first hop
I believe there is problem with Routing Table on that Droplet
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!