Trace to ip keeps looping

Hi, just noticed, I could be wrong but if I trace ip 172.26.155.254 it just keeps looping to 172.26.30.14.

See attached screenshots…due to load shedding ?

Could possibly be due to loadshedding in the area that u trying to reach. . . Or in the areas en-route to the destination you trying the reach . . .
I might be wrong also . . . But try it again - perhaps at another time when loadshedding is not roaming about . . . Hopefully it works then . . .

1 Like

Hey @Apex wie se ip is daai ek kry nie eers n dns naam nie lol en traceroute loop nie eers nie

nslookup 172.26.155.254
Server: dns.ctwug.za.net
Address: 172.18.1.1

*** dns.ctwug.za.net can’t find 172.26.155.254: Non-existent domain

tracert 172.26.155.254

Tracing route to 172.26.155.254 over a maximum of 30 hops

1 rb3.razor.ctwug.za.net [172.26.29.14] reports: Destination net unreachable.

Yis razor, soos ek gese het ek kan dalk verkeerd wees…sien soos screenshot op Housekeeping. Die ip maak dat alles stadig loop hier by ons, weti wie se ip dit is nie en daar is ook geen dns naam op daai ip nie…

ah ok ek sien nou hy is daar op by wms het gewonder waarna toe jy getrace het :slight_smile:

Was blackholed so you won’t be able to trace to it. You guys need to install wms properly on that rb and also set it up on wind.

1 Like

thats Diabolix new range
172.26.155.0/ 24 172.26.155.0 to 172.26.155.255 Diabolix01 Active Kuilsriver

1 Like