Ping went crazy after upgrade. HELP!!!!!!!!!!!!!!

RouterOS General
1

Hi is ping normal! After a few pings it start to re-ping the same replay. See here!

I did a test to ping from other device to upgraded device. It is the same!

Why? Was ok before! There is two R52HN on it in ap-bridge.
Thx
ping.png

2

From one of my linux servers in the network. It is the same to the device. The strange thing is only to device but it does not happen to it client by wifi.

root@gladiador:~$ ping 10.0.0.30
PING 10.0.0.30 (10.0.0.30) 56(84) bytes of data.
64 bytes from 10.0.0.30: icmp_req=1 ttl=30 time=29.2 ms
64 bytes from 10.0.0.30: icmp_req=1 ttl=30 time=37.9 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=2 ttl=30 time=9.60 ms
64 bytes from 10.0.0.30: icmp_req=3 ttl=30 time=19.0 ms
64 bytes from 10.0.0.30: icmp_req=3 ttl=30 time=22.9 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=4 ttl=30 time=7.38 ms
64 bytes from 10.0.0.30: icmp_req=5 ttl=30 time=7.70 ms
64 bytes from 10.0.0.30: icmp_req=6 ttl=30 time=12.1 ms
64 bytes from 10.0.0.30: icmp_req=6 ttl=30 time=22.7 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=7 ttl=30 time=6.70 ms
64 bytes from 10.0.0.30: icmp_req=7 ttl=30 time=11.2 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=8 ttl=30 time=7.70 ms
64 bytes from 10.0.0.30: icmp_req=9 ttl=30 time=4.88 ms
64 bytes from 10.0.0.30: icmp_req=10 ttl=30 time=6.39 ms
64 bytes from 10.0.0.30: icmp_req=11 ttl=30 time=26.0 ms
64 bytes from 10.0.0.30: icmp_req=12 ttl=30 time=2.86 ms
64 bytes from 10.0.0.30: icmp_req=12 ttl=30 time=5.90 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=13 ttl=30 time=8.45 ms
64 bytes from 10.0.0.30: icmp_req=13 ttl=30 time=23.9 ms (DUP!)
64 bytes from 10.0.0.30: icmp_req=14 ttl=30 time=5.77 ms
64 bytes from 10.0.0.30: icmp_req=15 ttl=30 time=5.89 ms
64 bytes from 10.0.0.30: icmp_req=16 ttl=30 time=5.88 ms
64 bytes from 10.0.0.30: icmp_req=17 ttl=30 time=38.6 ms
64 bytes from 10.0.0.30: icmp_req=18 ttl=30 time=7.28 ms
64 bytes from 10.0.0.30: icmp_req=19 ttl=30 time=6.74 ms
^C
— 10.0.0.30 ping statistics —
19 packets transmitted, 19 received, +6 duplicates, 0% packet loss, time 17999ms
rtt min/avg/max/mdev = 2.861/13.726/38.611/10.394 ms

3

this pings are reaching ether1 not wireless pings.

4

I need the mipsbe 5.11 npk for downgrade to last version. Where can I download it?

5

It is a bug for RB433uah! I did a downgrade to 5.11 and now it is ok again.

6

I still have this problem in many device with 5.24.

Please! How can I solve it?

7

He has the same problem. http://forum.mikrotik.com/t/how-to-see-ping-seq-in-terminal/63495/1

8

Duplicate ping responses can be caused by:


  • More than one host has the same IP address, so all these hosts will respond to the ICMP echo request.
  • The IP address pinged may be a broadcast address.
  • The host has multiple TCP stacks bound to an Ethernet adapter.
  • A router believes it has two routes by which it can reach the end host and (presumably mistakenly) forwards the ICMP echo requests by both routes, thus the end host sees two echo requests and responds twice.
  • There maybe two or more (non-routed) paths to the end host and each request is forwarded by more than one path.
  • It may be caused by NIC bonding.
  • A misbehaving NAT box.
9

Thanks! I have check already. It only happens after upgrade to 5.24. Before at 5.11 It did not appear.