public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dmeyer@dmeyer.net
To: linux-kernel@vger.kernel.org
Subject: Re: What does "NAT: dropping untracked packet" mean?
Date: Thu, 1 Feb 2001 18:19:52 -0500	[thread overview]
Message-ID: <20010201181952.A5803@jhereg.dmeyer.net> (raw)
In-Reply-To: <20010201133811.D14768@ipe.uni-stuttgart.de>
In-Reply-To: <20010201151717.D5706@emma1.emma.line.org>

In article <20010201151717.D5706@emma1.emma.line.org> you write:
> On Thu, 01 Feb 2001, Nils Rennebarth wrote:
> > Feb  1 12:58:56 obelix kernel: NAT: 0 dropping untracked packet
> ce767600 1 129.69.22.21 -> 224.0.0.2
> 
> It means that your box drops multicast administrative packets on the
> floor.

I'm getting the occasional

Feb  1 13:17:08 yendi kernel: NAT: 0 dropping untracked packet
c3ea4da0 1 146.188.249.73 -> 209.220.232.240

syslog message.  What exactly does it mean?  146.188.249.73 isn't my
machine at all, and 209.220.232.240 is my firewall.  I assume I'm
dropping someone's packets on the floor, but what can cause a packet
to get dropped like that?

-- 
Dave Meyer
dmeyer@dmeyer.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01 12:38 What does "NAT: dropping untracked packet" mean? Nils Rennebarth
2001-02-01 14:17 ` Matthias Andree
2001-02-01 23:19   ` dmeyer [this message]
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=20010201181952.A5803@jhereg.dmeyer.net \
    --to=dmeyer@dmeyer.net \
    --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