netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael D. Berger" <m_d_berger_1900@yahoo.com>
To: netfilter@vger.kernel.org
Subject: repeated local ephemeral to 80
Date: Thu, 31 Mar 2011 18:04:20 +0000 (UTC)	[thread overview]
Message-ID: <in2fn4$ksm$1@dough.gmane.org> (raw)

On my CentOS box that I use mainly as a web server, I have iptables
set to log and reject anything that I don't expect.  So lately,
I have getting things like this:


Mar 29 17:27:20 mbrc20 kernel: IPT-DROP IN= OUT=lo SRC=192.168.9.20 
DST=192.168.9.20 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=46910 DF PROTO=TCP 
SPT=56624 DPT=80 WINDOW=32792 RES=0x00 SYN URGP=0 OPT 
(0204400C0402080A4A26F7A50000000001030307) UID=0

that on at least one occasion repeated for every few seconds for
more than three hours.  The ephemeral source port keeps changing in an 
irregular manner.

Any suggestions?

Thanks,
Mike


                 reply	other threads:[~2011-03-31 18:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='in2fn4$ksm$1@dough.gmane.org' \
    --to=m_d_berger_1900@yahoo.com \
    --cc=netfilter@vger.kernel.org \
    /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).