From: Robert Felber <robtone@gmx.de>
To: lartc@vger.kernel.org
Subject: [LARTC] ingress works with this iproute version (src)
Date: Tue, 29 Oct 2002 02:14:10 +0000 [thread overview]
Message-ID: <marc-lartc-103585774330565@msgid-missing> (raw)
Okay,
for those who have problems with ingress:
ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.4.7-now-ss020116-try.tar.gz
is your version of iproute+tc that you want.
Versions below that didn't work for me either.
I used kernel 2.4.19 and if you are looking for CONFIG_NETLINK
or CONFIG_RTNETLINK - forget it. You are okay with CONFIG_NETLINK_DEV.
--
Robert Felber
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-10-29 2:14 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-103585774330565@msgid-missing \
--to=robtone@gmx.de \
--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.