netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: john@screen.lv, netdev@vger.kernel.org,
	David Miller <davem@davemloft.net>
Subject: Re: strange tcp behavior
Date: Fri, 3 Aug 2007 16:09:20 +0400	[thread overview]
Message-ID: <20070803120920.GA23166@2ka.mipt.ru> (raw)
In-Reply-To: <60580.simon.1186142626@5ec7c279.invalid>

On Fri, Aug 03, 2007 at 01:03:46PM +0100, Simon Arlott (simon@fire.lp0.eu) wrote:
> On Fri, August 3, 2007 12:56, Evgeniy Polyakov wrote:
> > On Fri, Aug 03, 2007 at 12:21:46PM +0100, Simon Arlott (simon@fire.lp0.eu) wrote:
> >> Since the connection is considered closed, couldn't another socket re-use it?
> >>
> >> Socket A: Recv data (unread)
> >> Socket A: Recv RST
> >> Socket B: Reuses connection (same IPs/ports)
> >> Socket A: Close
> >>
> >> Wouldn't that disrupt socket B's use of the connection?
> >
> > Then it will drop our data, since there were no appropriate handhsake.
> 
> Couldn't the sequence numbers be close enough to make the RST valid?

It does not matter - if connection is not in synchronized state all
unrelated data is dropped, so remote side is only allowed to receive syn
flag only, anything else must be dropped. If remote side does not do
that, it violates RFC.

> -- 
> Simon Arlott

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-08-03 12:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  6:19 strange tcp behavior john
2007-08-02  9:55 ` Evgeniy Polyakov
2007-08-02 10:16   ` Evgeniy Polyakov
2007-08-02 11:38     ` Simon Arlott
2007-08-02 12:04       ` Evgeniy Polyakov
2007-08-02 12:28         ` Evgeniy Polyakov
     [not found]       ` <46860.212.93.96.73.1186055105.squirrel@mail.screen.lv>
2007-08-02 12:15         ` Simon Arlott
2007-08-02 17:15           ` Simon Arlott
2007-08-02 18:08             ` Evgeniy Polyakov
2007-08-02 18:48               ` Evgeniy Polyakov
2007-08-02 22:02                 ` David Miller
2007-08-03  2:21                 ` David Miller
2007-08-03  8:22                   ` Evgeniy Polyakov
2007-08-03 20:04                     ` David Miller
2007-08-04 16:49                       ` Evgeniy Polyakov
2007-08-03 21:17                     ` David Miller
2007-08-04 16:51                       ` Evgeniy Polyakov
2007-08-05  3:21                         ` David Miller
2007-08-02 18:58               ` Simon Arlott
2007-08-03  8:25                 ` Evgeniy Polyakov
2007-08-03 11:21                   ` Simon Arlott
2007-08-03 11:56                     ` Evgeniy Polyakov
2007-08-03 12:03                       ` Simon Arlott
2007-08-03 12:09                         ` Evgeniy Polyakov [this message]
2007-08-03 16:51                           ` Simon Arlott
2007-08-03 17:39                             ` Evgeniy Polyakov
2007-08-03 18:29                               ` Simon Arlott
2007-08-04 16:03                                 ` Evgeniy Polyakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070803120920.GA23166@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=davem@davemloft.net \
    --cc=john@screen.lv \
    --cc=netdev@vger.kernel.org \
    --cc=simon@fire.lp0.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).