[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] lwip reply delayed after long communication idle time
From: |
Jochen Strohbeck |
Subject: |
Re: [lwip-users] lwip reply delayed after long communication idle time |
Date: |
Mon, 20 Apr 2020 10:02:48 -0700 (MST) |
Not giving up on this...
Although pinging 10 lwip's in a loop seems to work, from time to time I see
kind of these records in the Wireshark log:
Internet Control Message Protocol
Type: 3 (*Destination unreachable*)
Code: 2 (*Protocol unreachable*)
Checksum: 0xfcfd [correct]
[Checksum Status: Good]
Unused: 00000000
Internet Protocol Version 4, Src: 10.72.43.68, Dst: 10.72.43.1
Internet Control Message Protocol
What does this mean and what can cause such an event?
The 10 lwip's are connected to a PC (10.72.43.1) via a switch.
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html
- [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/01
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/02
- Re: [lwip-users] lwip reply delayed after long communication idle time, address@hidden, 2020/04/02
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/03
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/04
- Re: [lwip-users] lwip reply delayed after long communication idle time, goldsimon, 2020/04/04
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/04
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/08
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/16
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/16
- Re: [lwip-users] lwip reply delayed after long communication idle time,
Jochen Strohbeck <=
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/28