Static Routing

Hi

We are having issues with Static trace. We have RB1200 Firmware 3.07, Package Version 5.26.
196.6.242.1 (RB1200)
196.6.242.30(Linux Server)
41.162.57.148(Provider SBC)
172.24.29.17(Provider Gateway)
__Static:
8 A S ;;; Crossconnect
dst-address=41.162.57.148/32 gateway=172.24.29.17 gateway-status=172.24.29.17 reachable via ether5 distance=1 scope=30 target-scope=10

From the Router to 41.162.57.148:
/tool traceroute 41.162.57.148

ADDRESS RT1 RT2 RT3

1 172.24.29.17 1ms 1ms ms
2 0.0.0.0 0ms 0ms 0ms_**
From Server to 41.162.57.148 ;
[root@kensington ~]# tracepath 41.162.57.148
1: 196.6.242.30 (196.6.242.30) 0.136ms pmtu 1500
1: 196.6.242.1 (196.6.242.1) 0.282ms
2: no reply
3: no reply


From the Server the second hop should be 172.24.29.17 as it is on the router. That is the provider Gateway. :confused:

Please assist a bigginer.
_**

Fromm all I get
you want to do:

196.6.242.30(Linux Server) ↔ locally connected to ↔ 196.6.242.1 (RB1200) ↔ taking internet from ↔ 172.24.29.17(Provider Gateway) <—> would like to see 41.162.57.148(Provider SBC)

And you need the Mikrotik configuration for that
Have I understand well

Fromm all I get
you want to do:

196.6.242.30(Linux Server) <--> locally connected to <--> 196.6.242.1 (RB1200) <--> taking internet from <--> 172.24.29.17(Provider Gateway) <---> would like to see 41.162.57.148(Provider SBC)

And you need the Mikrotik configuration for that
Have I understand well

@stenlyto, All the routing is configured. The issue is that when doing a traceroute from the Mikrotik to 41.162.57.148(Gateway 172.24.29.17.
From Router:
/tool traceroute 41.162.57.148

ADDRESS RT1 RT2 RT3

1 172.24.29.17 1ms 1ms ms
2 0.0.0.0 0ms 0ms 0ms

From Server:
tracepath 41.162.57.148
1: 196.6.242.30 (196.6.242.30) 0.136ms pmtu 1500
1: 196.6.242.1 (196.6.242.1) 0.282ms
2: no reply
3: no reply

The Traceroute from the Server does not show the Gateway to 41.162.57.148 witch is 172.24.29.17

first thing i notice is that 172.24.29.17 is a private ip address.

i guess your router also have a IP adresses in that private network, therefore it uses this IP when you trace from the router.

when you trace from your server it uses 196.6.242.30.

my guess is the provider gateway didn’t know the route back to you 196.6.242.x network.

Thanks, I have discussed it with the provider and everything has been opened on there gateway.

:smiley: