mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michel Wilson" <mwilson@dds.nl>
To: <linux-kernel@vger.kernel.org>
Subject: Multicast and IP-conntrack problem
Date: Thu, 22 Mar 2001 23:36:02 +0100	[thread overview]
Message-ID: <NEBBLEJBILPLHPBNEEHIEEMCCAAA.mwilson@dds.nl> (raw)

Hi!

I'm having some problems with ip-connection tracking and multicast packets:
the conntrack stuff doesn't seem to be able to handle multicast packets,
flooding my logs with messages like these:

Feb 28 15:53:00 procyon kernel: NAT: 0 dropping untracked packet c7105b00 1
195.38.203.147 -> 224.0.0.2
Feb 28 15:53:23 procyon kernel: NAT: 0 dropping untracked packet c7a13740 1
195.38.207.229 -> 224.0.0.2
Feb 28 15:53:26 procyon kernel: NAT: 0 dropping untracked packet c7a13740 1
195.38.207.229 -> 224.0.0.2
Feb 28 15:53:31 procyon kernel: NAT: 0 dropping untracked packet c6535a80 1
195.38.207.229 -> 224.0.0.2
Feb 28 15:54:18 procyon kernel: NAT: 0 dropping untracked packet c7a132c0 1
195.38.202.44 -> 224.0.0.2
Feb 28 15:54:21 procyon kernel: NAT: 0 dropping untracked packet c7a132c0 1
195.38.202.44 -> 224.0.0.2
(this is an old logfile, i disabled logging for these messages, because it
generated several megs each day)

I'm currently using kernel 2.4.0-test9, but a friend of mine is using 2.4.0
and is experiencing the same problem.

Is this a known problem which can't be fixed, or is it fixable? And am i
asking this question in the right place here?

Thanks for any help,

Michel Wilson
<michel@procyon14.yi.org>
<mwilson@dds.nl>


             reply	other threads:[~2001-03-22 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 22:36 Michel Wilson [this message]
2001-03-24  9:58 ` Rusty Russell

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=NEBBLEJBILPLHPBNEEHIEEMCCAAA.mwilson@dds.nl \
    --to=mwilson@dds.nl \
    --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
all inboxes | Powered by JetHome®