weird ping behavior

Here’s one I haven’t seen before so I am posting here in hopes that someone has. When I try and ping a host on my network with ip 10.100.50.105 from my laptop 10.10.251.8 I get icmp replies from about 10 different hosts on the network, and it is completely random. For example:

ping 10.100.50.105 (this host does not respond to icmp packets, but when pinged he shows up in the arp table)
reply from 10.101.2.12: TTL expired in transit
reply from 10.106.9.13: TTL expired in transit
reply from 10.101.2.12: TTL expired in transit
reply from 10.106.1.12: TTL expired in transit
…and so on for as long as I let it run each time replying from random hosts…

There is nothing funny in the routing table that would cause something like this and I am not running any routing protocols (all routes are set statically). When I ping a host that does respond to icmp packets, there are no random replies.

I torched the connection in mikrotik in hopes of discovering what was going on, and I saw something very interesting. When I ping hosts that don’t reply to icmp packets, I get a huge influx of icmp packets to my local machine from hosts that I am not pinging (view attachment below).

My best guess is that this host 10.100.50.105 is running some sort of routing protocol on the network and is causing these hosts to respond with their addresses to my ping requests, but then again, I have never come across this before. Any help would be greatly appreciated.

thanks.
torch icmp.jpg

Maybe you have a loop?

What is shown in a traceroute to that destination?

Regards
Lutz