From: James Stevenson <mistral@stev.org>
To: nils@ipe.uni-stuttgart.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: What does "NAT: dropping untracked packet" mean?
Date: Thu, 1 Feb 2001 15:09:37 GMT [thread overview]
Message-ID: <200102011509.f11F9bV13547@cyrix.home> (raw)
In-Reply-To: <20010201133811.D14768@ipe.uni-stuttgart.de>
In-Reply-To: <20010201133811.D14768@ipe.uni-stuttgart.de>
Hi
do the messages apear when the windows machines a booting ?
i would tend to think that the kernel cannot handle the NET on
IGMP packets so its printting a message about it
the packets do look like they are goign to a multicast address
>
>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
>
--
---------------------------------------------
Check Out: http://stev.org
E-Mail: mistral@stev.org
3:00pm up 16 days, 22:21, 4 users, load average: 1.37, 1.38, 1.25
-
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/
prev parent reply other threads:[~2001-02-01 22:59 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
2001-02-01 23:45 ` Daniel Pittman
2001-02-01 23:46 ` Magnus Erixzon
2001-02-01 15:09 ` James Stevenson [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=200102011509.f11F9bV13547@cyrix.home \
--to=mistral@stev.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nils@ipe.uni-stuttgart.de \
/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