icmp sequnce number not matching in lwip stack what are the reason will be there for miss match of seq number

asked 2023-04-07 11:05:02 +0000

sandeep C gravatar image

updated 2023-04-11 10:36:08 +0000

grahamb gravatar image

hi iam developing the driver for ksz8851snli which converts spi to ethenet vice versa while iam pinging the ping id is matching ping sequence number is not but when i got reply from pc it going to ping_rec function in lwip stack with replied data as observed in the wireshark when iam trying to ping from pc to mc to iam getting all packets without some times iam getting 3 or 2 or 1 and even all packets will be iam not getting what might be the problem is it like clock frequency issue between ksz8851 to pc or viceversa or ksz8851 to mc iam getting

i need to know what are the possible chances of missing packets

cmd window shows as below

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1746ms TTL=255
Request timed out.

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Approximate round trip times in milli-seconds:
Minimum = 1746ms, Maximum = 1746ms, Average = 1746ms

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2574ms TTL=255

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Approximate round trip times in milli-seconds:
Minimum = 2574ms, Maximum = 2574ms, Average = 2574ms

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2773ms TTL=255
Request timed out.
Request timed out.

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Approximate round trip times in milli-seconds:
Minimum = 2773ms, Maximum = 2773ms, Average = 2773ms

C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users ...
(more)
edit retag flag offensive close merge delete