Proceedings of the 6th Intl Symposium on Modeling and Optimization 2008
DOI: 10.4108/icst.wiopt2008.3249
|View full text |Cite
|
Sign up to set email alerts
|

Spurious TCP Timeouts in 802.11 Networks

Abstract: Abstract-In this paper, we investigate spurious TCP timeouts in 802.11 wireless networks. Though timeouts can be a problem for uploads from an 802.11 network, these timeouts are not spurious but are caused by a bottleneck at the access point. Once this bottleneck is removed, we find that spurious timeouts are rare, even in the face of large changes in numbers of active stations or PHY rate.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

1
2
0

Year Published

2011
2011
2015
2015

Publication Types

Select...
2
2

Relationship

2
2

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 10 publications
1
2
0
Order By: Relevance
“…As expected, as flows are added to the system, the per-flow throughput is reduced by a factor of n. Interestingly, for 3 and 4 flows, timeouts occur for short bursts: this suggests that a similar TCP ACK starvation phenomenon to that reported by [16] may be an issue for HomePlug AV and IEEE 1901 systems as well. Future testing aims include verifying this result using a larger test set: as described in [16], the downlink node must transmit n/2 TCP ACKs for n uplink flows. While each source/uplink node has a single flow to buffer, the sink/downlink node has to deliver n/2 the number of channel accesses.…”
Section: B Impact Of Additional Flowssupporting
confidence: 61%
See 1 more Smart Citation
“…As expected, as flows are added to the system, the per-flow throughput is reduced by a factor of n. Interestingly, for 3 and 4 flows, timeouts occur for short bursts: this suggests that a similar TCP ACK starvation phenomenon to that reported by [16] may be an issue for HomePlug AV and IEEE 1901 systems as well. Future testing aims include verifying this result using a larger test set: as described in [16], the downlink node must transmit n/2 TCP ACKs for n uplink flows. While each source/uplink node has a single flow to buffer, the sink/downlink node has to deliver n/2 the number of channel accesses.…”
Section: B Impact Of Additional Flowssupporting
confidence: 61%
“…The distinction between the two tests are that for uplink tests, the access point receives multiple flows, while the downlink must source multiple flows. Potential problems can occur in the uplink for TCP flows if the ACKs cannot access the channel due to contention issues [16].…”
Section: B Measurement Methodsmentioning
confidence: 99%
“…A consequence of using DCF is thus that when the number of upload flows increases, the uploads may produce enough TCP ACK packets to keep the AP's queue saturated. In fact, once there are two upload flows, TCP becomes unstable due to repeated timeouts (see [20] for a detailed demonstration), causing the unfairness issue discussed in Section II-C. Therefore, we present results for up to two uploads in Fig.…”
Section: Dcf Operationmentioning
confidence: 99%