Hi buddy…
Is anybody facing the Ping corrupted when running on the wds mode?
We experience few unit having ping corrupted issue when you in AP ping to CPE or from the CPE ping to the AP via the winbox.
But if you ping from the pc, there is no problem.
The thing is, only the ping is ok, you are not able to browse, doing remote desktop and etc..
i have try RouterOS V4.10 and RouterOS V5.4 Beta, even netinstall also not able to resolved this issue.
No matter indoor or outdoor, R5h, R52Hn or F50-Pro, the problem remain the same.
i pretty sure this is not related to the wireless card issue, as i re-use those card to other routerboard, there is no issue at all…
When sending the ICMP echo request packet, the ping command includes some random data, which it then checks when receiving the reply. If the data doesn’t match, it means the packet is corrupted. You can look with a packet sniffer to see what’s happening.
It’s exceedingly unlikely that any given host has a bad ICMP implementation that leads to payloads getting corrupted (the echo reply payload is not equal to the echo request payload, and I think the same error can be thrown when header checksums don’t match), so the most likely error cause is physical. Bad cabling, a wireless link with really bad interference, that sort of thing. I guess it could be a bad NIC, too.
Hi fewi..
i am not agreed with what you shared with us, in fact, i have tried that unit to difference place and the problem still same even upgrade the firmware.
But when i replace a unit on the same area, same height, same cable, same direction… it’s working fine.
When i take out the mici pci and put on other routerboard, the wireless card is working fine.
I’m having a corrupt ping issue as well with my NATed network running 5.0Beta6. Any ping sent over sent 92bytes in size gets a corrupted status consistently.
This happens from the Mikrotik terminal, pings from a windows system on mikrotik (not-PPPOE) over 92 work, however, from client AP’s terminal all pings over 92 are dropped.
