[riot-notifications] [RIOT-OS/RIOT] sam0_eth: extremely long time to RX (frames stuck in buffer?) (#16451)

benpicco notifications at github.com
Wed Jul 14 18:47:09 CEST 2021


Not sure if this is related, but this is something odd:

TTL of ICMPv6 ping replies goes up to 255 shortly after reset:

```
> ping fe80::a4ed:29ff:feec:cbf3%eno1 
PING fe80::a4ed:29ff:feec:cbf3%eno1(fe80::a4ed:29ff:feec:cbf3%eno1) 56 data bytes
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=7 ttl=64 time=0.690 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=8 ttl=255 time=0.300 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=9 ttl=255 time=0.332 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=10 ttl=255 time=0.343 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=11 ttl=255 time=0.296 ms
# reset
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=15 ttl=64 time=0.732 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=16 ttl=64 time=0.312 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=17 ttl=255 time=0.303 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=18 ttl=255 time=0.352 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=19 ttl=255 time=0.315 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=20 ttl=255 time=0.317 ms
64 bytes from fe80::a4ed:29ff:feec:cbf3%eno1: icmp_seq=21 ttl=255 time=0.323 ms
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/16451#issuecomment-880048746
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210714/b4103ae1/attachment-0001.htm>


More information about the notifications mailing list