[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #50837] LWIP TCP/IP race condition
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #50837] LWIP TCP/IP race condition |
Date: |
Wed, 3 May 2017 16:00:57 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 |
Follow-up Comment #23, bug #50837 (project lwip):
> All that aside, I think we have a problem with a connection stuck in zero
window probing.
Right. I haven't found the time to look at the source be fore but it seems
like my memory tricked me. There's really no upper limit on the zero window
phase.
My suggestion would be to use pcb->nrtx here, too. We could increase it for
every zero window probe and reset it for *every* matching rx segment if the
persist timer is running (as opposed to resetting it when new data is
acknowledged otherwise).
With default settings, that would still take ~11 minutes to time out such a
connection (if my calculations with 'tcp_persist_backoff' and 'TCP_MAXRTX' are
correct).
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?50837>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, preet, 2017/05/01
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Joel Cunningham, 2017/05/01
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Simon Goldschmidt, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Joel Cunningham, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, preet, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Simon Goldschmidt, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, preet, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Joel Cunningham, 2017/05/02
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition,
Simon Goldschmidt <=
- [lwip-devel] [bug #50837] LWIP TCP/IP race condition, Simon Goldschmidt, 2017/05/03
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Joel Cunningham, 2017/05/03
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Joel Cunningham, 2017/05/04
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Simon Goldschmidt, 2017/05/08
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Joel Cunningham, 2017/05/09
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Simon Goldschmidt, 2017/05/12
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, preet, 2017/05/12
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, preet, 2017/05/16
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Joel Cunningham, 2017/05/16
- [lwip-devel] [bug #50837] TCP: zero window probe doesn't timeout, Fayek, 2017/05/17