From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Stuart Kendrick <stuart.kendrick.sea@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: unable to send TCP SYNs from ports below 1024
Date: Wed, 15 Jan 2014 12:47:15 +0100 [thread overview]
Message-ID: <20140115114715.GC19945@order.stressinduktion.org> (raw)
In-Reply-To: <CAACXELm1Yfv+=oC-N+nnR7apHc+gtZSVpqSbX2Rtkiq6-Y1QtA@mail.gmail.com>
On Tue, Jan 14, 2014 at 05:37:03PM -0800, Stuart Kendrick wrote:
> VALIDATION
> I verify the problem by using netcat plus two instances of tcpdump,
> one running on the box itself, the other running on a second box
> plugged into a SPAN port on the local Ethernet switch
This sounds strange. Could you try to skip the switch and plug the
boxes together directly. Maybe a switch policy? They can filter such
things nowaday.
Greetings,
Hannes
next prev parent reply other threads:[~2014-01-15 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 1:37 unable to send TCP SYNs from ports below 1024 Stuart Kendrick
2014-01-15 11:47 ` Hannes Frederic Sowa [this message]
2014-01-16 13:37 ` Stuart Kendrick
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=20140115114715.GC19945@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=stuart.kendrick.sea@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox