Hi there,
it seems that the TCP fixes for 2.2.19pre16 do not fix all the TCP problems.
I still see lots of Connection reset by peer errors even after upgrading to
to pre16.
I however see two possibly interesting patterns here:
- the problem happens more often when the PPP link is saturated (eg. a
download is going on)
- Such connection resets only happen during the initial phase of a TCP
session, that is, once established and working, the connection stays
alive
A tcpdump is attached. It was created by an attempt to get to port 80 of
oss.sgi.com:
# telnet oss.sgi.com 80
Trying 216.32.174.190...
Connected to oss.sgi.com.
Escape character is '^]'.
Connection closed by foreign host.
#
tcpdump: listening on ppp0
21:13:16.086888 217.3.36.147.1697 > 216.32.174.190.80: S
3856418047:3856418047(0) win 32648 <mss 1484,sackOK,timestamp 2146105
0,nop,wscale 0> (DF) [tos 0x10]
21:13:19.085505 217.3.36.147.1697 > 216.32.174.190.80: S
3856418047:3856418047(0) win 32648 <mss 1484,sackOK,timestamp 2146405
0,nop,wscale 0> (DF) [tos 0x10]
21:13:21.515544 216.32.174.190.80 > 217.3.36.147.1697: S
3948337129:3948337129(0) ack 3856418048 win 32120 <mss 1460,sackOK,timestamp
618853138 2146105,nop,wscale 0> (DF)
21:13:21.515753 217.3.36.147.1697 > 216.32.174.190.80: . ack 1 win 32648
<nop,nop,timestamp 2146648
618853138> (DF) [tos 0x10]
21:13:24.695452 216.32.174.190.80 > 217.3.36.147.1697: S
3948337129:3948337129(0) ack 3856418048 win 32120 <mss 1460,sackOK,timestamp
618853435 2146105,nop,wscale 0> (DF)
21:13:24.695640 217.3.36.147.1697 > 216.32.174.190.80: R
3856418048:3856418048(0) win 0
21:13:25.265624 216.32.174.190.80 > 217.3.36.147.1697: S
3948337129:3948337129(0) ack 3856418048 win 32120 <mss 1460,sackOK,timestamp
618853477 2146105,nop,wscale 0> (DF)
21:13:25.265702 217.3.36.147.1697 > 216.32.174.190.80: R
3856418048:3856418048(0) win 0
If you need any more information, please email me. Please also CC: me as I
am not subscribed to netdev.
Regards,
Mario
|