From: Stephen Hemminger <shemminger@vyatta.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org, Bill Fink <billfink@mindspring.com>,
Eric Dumazet <dada1@cosmosbay.com>
Subject: Re: ports beeing reused too fast
Date: Tue, 12 May 2009 08:11:19 -0700 [thread overview]
Message-ID: <20090512081119.598b22c5@nehalam> (raw)
In-Reply-To: <200905121532.57477.opurdila@ixiacom.com>
On Tue, 12 May 2009 15:32:57 +0300
Octavian Purdila <opurdila@ixiacom.com> wrote:
>
> > > > >> Any strong reason why a firewall would drop a SYN because ports were
> > > > >> used in a previous session ?
> > > > >
> > > > > We don't know why the firewall (Cisco FWSM) is dropping the packets,
> > > > > may be a bug, limitation or miss-configuration. We are trying to
> > > > > track this down with the firewall vendor.
> > > >
>
> Interestingly, we are seeing the same behavior with another high-end firewall
> (Juniper SRX).
>
> As mentioned previously, this can not be caused by the TW state, because the
> connections are getting closed on the server side.
>
> Thanks,
> tavi
I raised the issue to the original author of the proposed RFC and added
the issue to the ongoing review of the draft.
There is a suggested workaround using a bitmap but it seems like it would be
expensive to implement:
http://ietfreport.isoc.org/all-ids/draft-ananth-tsvwg-timewait-00.txt
--
next prev parent reply other threads:[~2009-05-12 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 20:11 ports beeing reused too fast Octavian Purdila
2009-05-09 6:58 ` Eric Dumazet
2009-05-09 13:11 ` Octavian Purdila
2009-05-09 15:17 ` Eric Dumazet
2009-05-09 16:16 ` Eric Dumazet
2009-05-09 19:31 ` Bill Fink
2009-05-09 19:41 ` Octavian Purdila
2009-05-09 22:45 ` Stephen Hemminger
2009-05-12 12:32 ` Octavian Purdila
2009-05-12 15:11 ` Stephen Hemminger [this message]
2009-05-12 15:52 ` Octavian Purdila
2009-05-14 20:29 ` Stephen Hemminger
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=20090512081119.598b22c5@nehalam \
--to=shemminger@vyatta.com \
--cc=billfink@mindspring.com \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.