Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Joseph Chiu" <josephc@idealab.com>
To: lartc@vger.kernel.org
Subject: [LARTC] How does tc communicate with the kernel?
Date: Wed, 28 Nov 2001 18:33:26 +0000	[thread overview]
Message-ID: <marc-lartc-100697211932591@msgid-missing> (raw)

Hi,
I am developing on an embedded MIPS-based system; I have iproute2's ip
working correctly talking to the kernel, but tc seems to be broken.  I'd
like to fix this, but I need a little bit of help in figuring out how tc
communictes with the kernel -- can someone tell me the places I should be
looking?
Thanks.
Joseph


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-11-28 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 18:33 Joseph Chiu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01  0:55 [LARTC] How does tc communicate with the kernel? bert hubert

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-100697211932591@msgid-missing \
    --to=josephc@idealab.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox