From: Simon <tanstaafl@libertytrek.org>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Log flooded with these...
Date: Sun, 19 Oct 2008 12:48:13 -0400 [thread overview]
Message-ID: <48FB64CD.6070205@libertytrek.org> (raw)
In-Reply-To: <48FB4FD8.7090307@libertytrek.org>
On 10/19/2008, Simon (tanstaafl@libertytrek.org) wrote:
> Oct 19 11:10:33 myhost IPTABLES-IN Default Drop: IN=eth0 OUT=
> MAC=ff:ff:ff:ff:ff:ff:00:1c:c0:69:16:89:08:00 SRC=0.0.0.0
> DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=128 ID=46967
> PROTO=UDP SPT=68 DPT=67 LEN=308
> Oct 19 11:10:33 myhost IPTABLES-IN Default Drop: IN=eth0 OUT=
> MAC=ff:ff:ff:ff:ff:ff:00:04:5a:8f:d6:11:08:00 SRC=192.168.1.250
> DST=255.255.255.255 LEN=347 TOS=0x00 PREC=0x00 TTL=128 ID=55784
> PROTO=UDP SPT=67 DPT=68 LEN=327
> Oct 19 11:10:33 myhost IPTABLES-IN Default Drop: IN=eth0 OUT=
> MAC=ff:ff:ff:ff:ff:ff:00:1c:c0:69:16:89:08:00 SRC=0.0.0.0
> DST=255.255.255.255 LEN=360 TOS=0x00 PREC=0x00 TTL=128 ID=46968
> PROTO=UDP SPT=68 DPT=67 LEN=340
Help! I'm not an iptables guy... at a minimum, is there a way to just
tell iptables to stop logging these (silently drop)? I'll continue to
troubleshoot, if there is a problem, but this is making my logs
virtually (not totally, but almost) useless...
Also, I guess it would be good to have the reverse command handy - how
to turn this off and on, so I can test if the problem persists...
Thanks
next prev parent reply other threads:[~2008-10-19 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 15:18 Log flooded with these Simon
2008-10-19 15:53 ` Simon
[not found] ` <78e398b30810190903i610b64e3l56fa51402e607cc6@mail.gmail.com>
2008-10-19 16:42 ` Simon
2008-10-19 16:48 ` Simon [this message]
2008-10-19 18:27 ` Simon
2008-10-20 6:22 ` Robert Nichols
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=48FB64CD.6070205@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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 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.