From: Simon <tanstaafl@libertytrek.org>
To: Doc Nielsen <docnielsen@gmail.com>
Cc: Netfilter list <netfilter@vger.kernel.org>
Subject: Re: Log flooded with these...
Date: Sun, 19 Oct 2008 12:42:05 -0400 [thread overview]
Message-ID: <48FB635D.2050603@libertytrek.org> (raw)
In-Reply-To: <78e398b30810190903i610b64e3l56fa51402e607cc6@mail.gmail.com>
On 10/19/2008 12:03 PM, Doc Nielsen wrote:
> SPT=68 DPT=67 = DHCP
>
> did you allow dhcp client/server requests and responses in the
> firewall?
Hey Doc,
Thanks for taking a look...
This is an well-established network, no major/unusual changes prior to
these entries showing up in the log, especially to firewall rules.
> do you have a running dhcp server/client?
The domain controller is the DHCP/DNS server, running Windows Server
2000. The linux server running iptables that has this logging issue has
a static IP, and is not (obviously) running a DHCP server or client.
> what kind of firewall are you using, as frontend for iptables?
I'm not using a 'front-end' - this is a gentoo linux box that serves a
mail and web server, which I also run iptables on for obvious reasons.
It has been running for over 3 years, is kept updated regularly (though
not obsessively so), and survived all of the ensuing major updates to date.
The only things I updated that day - but it was a few hours before this
started - was libpcre and udev...
Any other ideas?
next prev parent reply other threads:[~2008-10-19 16:42 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 [this message]
2008-10-19 16:48 ` Simon
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=48FB635D.2050603@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=docnielsen@gmail.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 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.