From: "Michael McTernan" <Michael.McTernan.2001@cs.bris.ac.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] RE: LARTC digest, Vol 1 #336 - 1 msg
Date: Thu, 29 Nov 2001 11:31:33 +0000 [thread overview]
Message-ID: <marc-lartc-100703340524230@msgid-missing> (raw)
Hi,
It uses netlink sockets. Try man netlink and man rtnetlink.
Mike
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
Behalf Of lartc-request@mailman.ds9a.nl
Sent: 29 November 2001 11:01
To: lartc@mailman.ds9a.nl
Subject: LARTC digest, Vol 1 #336 - 1 msg
Send LARTC mailing list submissions to
lartc@mailman.ds9a.nl
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.ds9a.nl/mailman/listinfo/lartc
or, via email, send a message with subject or body 'help' to
lartc-request@mailman.ds9a.nl
You can reach the person managing the list at
lartc-admin@mailman.ds9a.nl
When replying, please edit your Subject line so it is more specific
than "Re: Contents of LARTC digest..."
Today's Topics:
1. How does tc communicate with the kernel? (Joseph Chiu)
--__--__--
Message: 1
From: "Joseph Chiu" <josephc@idealab.com>
To: <LARTC@mailman.ds9a.nl>
Date: Wed, 28 Nov 2001 10:33:26 -0800
Subject: [LARTC] How does tc communicate with the kernel?
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
End of LARTC Digest
_______________________________________________
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-29 11:31 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=marc-lartc-100703340524230@msgid-missing \
--to=michael.mcternan.2001@cs.bris.ac.uk \
--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.