public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nils Rennebarth <nils@ipe.uni-stuttgart.de>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: What does "NAT: dropping untracked packet" mean?
Date: Thu, 1 Feb 2001 13:38:12 +0100	[thread overview]
Message-ID: <20010201133811.D14768@ipe.uni-stuttgart.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

Since enabling (but not yet using) firewalling in the 2.4.1 kernel, my log
gets clobbered with messages like:

Feb  1 12:58:56 obelix kernel: NAT: 0 dropping untracked packet ce767600 1 129.69.22.21 -> 224.0.0.2
Feb  1 12:59:01 obelix kernel: NAT: 0 dropping untracked packet ce767480 1 129.69.22.21 -> 224.0.0.2
Feb  1 12:59:04 obelix kernel: NAT: 0 dropping untracked packet ce767d80 1 129.69.22.21 -> 224.0.0.2
Feb  1 13:00:44 obelix kernel: NAT: 0 dropping untracked packet ce767600 1 129.69.22.51 -> 224.0.0.2
Feb  1 13:00:47 obelix kernel: NAT: 0 dropping untracked packet ce767600 1 129.69.22.51 -> 224.0.0.2
Feb  1 13:00:50 obelix kernel: NAT: 0 dropping untracked packet ce767b40 1 129.69.22.51 -> 224.0.0.2

The IP Adresses belong to Windows 98 computers. What does the message mean,
and what could I do to stop them?


Nils

--
*New* *New* *New*    - on shellac records
   Windows HE        - see top 10 reasons to downgrade on
Historical Edition     http://www.microsoft.com/windowshe

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-02-01 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01 12:38 Nils Rennebarth [this message]
2001-02-01 14:17 ` What does "NAT: dropping untracked packet" mean? Matthias Andree
2001-02-01 23:19   ` dmeyer
2001-02-01 23:45     ` Daniel Pittman
2001-02-01 23:46     ` Magnus Erixzon
2001-02-01 15:09 ` James Stevenson

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=20010201133811.D14768@ipe.uni-stuttgart.de \
    --to=nils@ipe.uni-stuttgart.de \
    --cc=linux-kernel@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