| To: | netdev@xxxxxxxxxxx |
|---|---|
| Subject: | [slightly OT] tcp resets in response to ICMP messages --- required behavior? |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Mon, 17 Sep 2001 17:30:13 +1200 |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.20i |
Somewhat off topic.. but can anyone tell me definitively what a TCP implementation should do when it receives and ICMP unreachable (net or host) during a TCP session (i.e. in response to an ACK or PSH)? rfc1122 seems to indicate all such message are to be treated as transient errors and hence should be ignored --- but it seems some stacks, (e.g. Windows98) reset the connection as if a TCP packet with RST was received. Needless to say, this sucks rocks terribly. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19, Aaron Sethman |
|---|---|
| Next by Date: | skbuff variables set already in ethernet drivers, Guilhem Tardy |
| Previous by Thread: | 2.4.9 SIOCGIF* BSD4.4 compatibility patch, take #2 (restricted impact), Matthias Andree |
| Next by Thread: | skbuff variables set already in ethernet drivers, Guilhem Tardy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |