From: Thomas Molina <tmolina@home.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: dropping untracked packets patch for 2.4 (fwd)
Date: Mon, 30 Oct 2000 07:24:53 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010300714300.1445-100000@wr5z.localdomain> (raw)
Linus,
Rusty Russell suggested I send the following patch to you. It redirects
to the log file those annoying dropping untracked packet messages. This
patch works agains any recent 2.4.0-test kernels.
diff -urN linux.new1/net/ipv4/netfilter/ip_nat_standalone.c linux.new/net/ipv4/netfilter/ip_nat_standalone.c
--- linux.new1/net/ipv4/netfilter/ip_nat_standalone.c Sun Oct 22 15:19:07 2000
+++ linux/net/ipv4/netfilter/ip_nat_standalone.c Sun Oct 22 13:37:44 2000
@@ -72,7 +72,7 @@
unreliable. */
if (!ct) {
if (net_ratelimit())
- printk("NAT: %u dropping untracked packet %p %u %u.%u.%u.%u -> %u.%u.%u.%u\n",
+ printk(KERN_DEBUG "NAT: %u dropping untracked packet %p %u %u.%u.%u.%u -> %u.%u.%u.%u\n",
hooknum,
*pskb,
(*pskb)->nh.iph->protocol,
---------- Forwarded message ----------
Date: Mon, 30 Oct 2000 15:50:18 +1100
From: Rusty Russell <rusty@linuxcare.com.au>
To: Thomas Molina <tmolina@home.com>
Subject: Re: Three kernel messages
In message <Pine.LNX.4.21.0010230959520.2837-100000@wr5z.localdomain> you write
:
> I finally got tired of seeing these messages. Win98 boxes on my lan
> spew these each time they are booted and corrupt whatever virtual
> console I'm on. The following workaround sends these messages to
> /var/log/messages. Patch is against 2.4.0-test10-pre4, but should apply
> to recent kernels.
Thanks: please change to KERN_DEBUG and send to Linus...
Cheers,
Rusty.
--
Hacking time.
-
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:[~2000-10-30 13:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.21.0010300714300.1445-100000@wr5z.localdomain \
--to=tmolina@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).