From: Frank van Maarseveen <frankvm@frankvm.com>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
Kernel Netdev Mailing List <netdev@vger.kernel.org>
Subject: Re: 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE
Date: Thu, 1 Jun 2006 11:11:25 +0200 [thread overview]
Message-ID: <20060601091124.GA31642@janus> (raw)
In-Reply-To: <447DD66C.30605@trash.net>
On Wed, May 31, 2006 at 07:46:20PM +0200, Patrick McHardy wrote:
[...]
> > ip -s link doesn't show any
> > dropped packets so far with any patch and I don't use traffic control
> > that I'm aware of. But I'm not sure what to make of "tc" output, maybe
> > because CONFIG_SHAPER is not set:
> >
> > # tc -s -d qdisc show
> > RTNETLINK answers: Invalid argument
> > Dump terminated
>
> Thats because you're missing CONFIG_NET_SCHED. Please enable it and
> try the tc command again, without it we can't see whether the qdisc
> (which is present even without CONFIG_NET_SCHED) just dropped the
> packets.
ok, now "tc -s -d qdisc show" says (after noticing missing netconsole
packets):
qdisc pfifo_fast 0: dev eth0 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 155031 bytes 2067 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
--
Frank
next prev parent reply other threads:[~2006-06-01 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060531094626.GA23156@janus>
2006-05-31 14:57 ` 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE Patrick McHardy
2006-05-31 16:06 ` Frank van Maarseveen
2006-05-31 16:36 ` Patrick McHardy
2006-05-31 17:29 ` Frank van Maarseveen
2006-05-31 17:46 ` Patrick McHardy
2006-05-31 18:20 ` Frank van Maarseveen
2006-06-01 9:11 ` Frank van Maarseveen [this message]
2006-06-01 17:34 ` Patrick McHardy
2006-06-02 12:35 ` Frank van Maarseveen
2006-06-02 14:02 ` 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE (2) Frank van Maarseveen
2006-06-02 14:16 ` Patrick McHardy
2006-06-02 14:39 ` Frank van Maarseveen
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=20060601091124.GA31642@janus \
--to=frankvm@frankvm.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).