From: Frank Gruellich <frank@der-frank.org>
To: netfilter@lists.netfilter.org
Subject: Re: What about these packets?
Date: Sat, 29 Jan 2005 08:55:27 +0100 [thread overview]
Message-ID: <20050129075527.GI18279@der-frank.org> (raw)
In-Reply-To: <1106967050.21043.7.camel@croaker>
* Mohammad Khan <mkhan@lextranet.com> 28. Jan 05:
> On Fri, 2005-01-28 at 21:43 -0500, Jason Opperisano wrote:
> > On Fri, 2005-01-28 at 21:29, Mohammad Khan wrote:
> > > two rules in my INPUT chains are:
> > > -A INPUT -s 63.110.21.51 -m state --state NEW -j LOG --log-prefix
> > > "PLAYNC_NEW " --log-level debug
> > > -A INPUT -s 63.110.21.51 -m state --state NEW -j DROP
> > >
> > > My router is keeping the following logs
> > > [snip udp logs]
> > >
> > > What can I say about these packets?
> > judging from the destination UDP ports and the TTL--i would say that
> > they are traceroute packets.
> my log file is full of this shit.
So, why are you logging it? It's just the normal white noise of
ordinary Internet traffic. Nothing to care about.
> Are they doing traceroute for all the day long??
Maybe you should tell them to go away instead of remain silent.
(Replace the -j DROP with a -j REJECT --reject-with
icmp-port-unreachable.)
HTH,
regards, Frank.
--
,------------------------.------------------------.--------------------.
| Chemnitzer Linux-Tage | "Linux loves desktops" ' team@linux-tage.de |
| March, 5th + 6th, 2005 | http://chemnitzer.linux-tage.de/ |
'------------------------'---------------------------------------------'
prev parent reply other threads:[~2005-01-29 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:29 What about these packets? Mohammad Khan
2005-01-29 2:43 ` Jason Opperisano
2005-01-29 2:50 ` Mohammad Khan
2005-01-29 7:55 ` Frank Gruellich [this message]
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=20050129075527.GI18279@der-frank.org \
--to=frank@der-frank.org \
--cc=netfilter@lists.netfilter.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 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.