All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Nychis <gnychis@cmu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to debug RTNETLINK invalid argument?
Date: Tue, 23 May 2006 17:12:54 +0000	[thread overview]
Message-ID: <44734296.4050807@cmu.edu> (raw)
In-Reply-To: <44733597.4000208@cmu.edu>



Larry Brigman wrote:
> On 5/23/06, George Nychis <gnychis@cmu.edu> wrote:
>> Hey,
>>
>> I am getting an invalid argument trying to insert a qdisc:
>>
>> [root@emu-5 iproute2]# tc qdisc add dev eth0 root xcp capacity 50Mbit
>> limit 500
>> RTNETLINK answers: Invalid argument
>>
>> I'm not sure whats wrong here, because i can successfully insert this
>> qdisc on other computers of mine.
>>
>> How can i debug this?
>>
> Check to see which kernel versions you have on the boxes that work and
> the one that
> does not.  Also check to see if you have the latest version of
> iproute2 installed on the
> machine that does not work.
> 

They are both running the exact same kernel and version of iproute2,
however they are in different environments, what could the environment
have to do with it?

Thanks!
George
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-05-23 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 16:17 [LARTC] how to debug RTNETLINK invalid argument? George Nychis
2006-05-23 16:23 ` Larry Brigman
2006-05-23 17:12 ` George Nychis [this message]
2006-05-23 17:51 ` Larry Brigman
2006-05-23 23:29 ` George Nychis
2006-05-24  0:21 ` Larry Brigman
2006-05-24  1:04 ` George Nychis
2006-05-24  1:40 ` Stephen Hemminger
2006-05-24  2:12 ` Luciano Ruete
2006-05-24 14:14 ` George Nychis
2006-05-24 15:06 ` George Nychis
2006-05-24 15:24 ` George Nychis

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=44734296.4050807@cmu.edu \
    --to=gnychis@cmu.edu \
    --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.