[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: |
Thu, 16 Apr 2020 06:54:38 -0700 (MST) |
Another observation/idea/question:
At the time ping times out or is delayed, I noticed a bulk of dest:FF...
(broadcast?) messages:
Antwort von 192.168.0.100: Bytes=32 Zeit=1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit=1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit=*60ms* TTL=255
*Zeitüberschreitung der Anforderung.*
Antwort von 192.168.0.100: Bytes=32 Zeit=*2513ms* TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit<1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit<1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit<1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit<1ms TTL=255
Antwort von 192.168.0.100: Bytes=32 Zeit<1ms TTL=255
2012-01-01 00:03:37 [W]ethernet_input: dest:de:bd:01:00:00:16,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 *00:03:37* [W]icmp_input: ping
2012-01-01 00:03:38 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:38 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:38 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:38 [W]ethernet_input: dest:de:bd:01:00:00:16,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 *00:03:38* [W]icmp_input: ping
2012-01-01 00:03:38 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:38 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:39 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:39 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:39 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:42 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:43 [W]ethernet_input: dest:de:bd:01:00:00:16,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 *00:03:43* [W]icmp_input: ping
2012-01-01 00:03:43 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:44 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 00:03:46 [W]ethernet_input: dest:de:bd:01:00:00:16,
src:98:e7:43:7a:2c:51, type:800
2012-01-01 *00:03:46* [W]icmp_input: ping
2012-01-01 00:03:46 [W]ethernet_input: dest:ff:ff:ff:ff:ff:ff,
src:98:e7:43:7a:2c:51, type:800
Is it possible that many of these "broadcast" messages block / delay the
ping request processing?
ping_delay.pcap <http://lwip.100.n7.nabble.com/file/t1988/ping_delay.pcap>
pingdelay.txt <http://lwip.100.n7.nabble.com/file/t1988/pingdelay.txt>
--
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 <=
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/20
- Re: [lwip-users] lwip reply delayed after long communication idle time, Jochen Strohbeck, 2020/04/28