All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreani Luca <landreani@seltatel.it>
To: lartc@vger.kernel.org
Subject: R: [LARTC] iproute and kernel 2.4.17
Date: Mon, 04 Nov 2002 09:56:53 +0000	[thread overview]
Message-ID: <marc-lartc-103640465315634@msgid-missing> (raw)

I've already done it, but it doesn't work!
Looking at the code, I discovered that the "statistic truncated" message
concerns the 
use of the RTA_PAYLOAD macro from rtnetlink. I discovered that beginning
with 2.4.17 kernel the option CONFIG_RTNETLINK has been removed from the
kernel configuration (now it is by default). Do you think It is possible
that this change could influence the behaviour of iproute? Perhaps It looks
for some #define CONFIG_RTNETLINK and doesn't find it?

Thanks

Luca

-----Messaggio originale-----
Da: Stef Coene [mailto:stef.coene@docum.org]
Inviato: lunedì 4 novembre 2002 10.48
A: Andreani Luca; LARTC mailing list (E-mail)
Oggetto: Re: [LARTC] iproute and kernel 2.4.17


On Monday 04 November 2002 10:20, Andreani Luca wrote:
> I moved from kernel 2.4.7 to 2.4.17 and iproute begin to not work
properly.
> I receive a strange message:
>
> statistic truncated
>
> Any idea?
No.  But I think it's a good idea to recompile a new tc binary from the 
iproute2 source.

Stef


-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-04  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  9:56 Andreani Luca [this message]
2002-11-04 17:57 ` R: [LARTC] iproute and kernel 2.4.17 Stef Coene

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=marc-lartc-103640465315634@msgid-missing \
    --to=landreani@seltatel.it \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.