From: Steffen Schober Steffen.Schober@stud.uni-karlsruhe.de
To: lartc@vger.kernel.org
Subject: [LARTC] iptables-table empty, can't get tc to work...
Date: Tue, 30 Jan 2001 12:17:52 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416925@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416922@msgid-missing>
<PRE>Am Montag, 29. Januar 2001 18:56 schrieben Sie:
><i> I have an ISDN connection here at my apartment and wanted to make sure
</I>><i> to have enuf bandwidth to play a game while one of my roommates is
</I>><i> surfing.
</I>><i> I compiled the 2.4 kernel for advanced routing and tos and iptables as
</I>><i> modules.
</I>><i>
</I>><i> I have iptables v1.2 and when adding a rule and then doing iptables -L
</I>><i> the list is empty tho the rules are applied.
</I>><i>
</I>><i> When I type:
</I>><i> tc qdisc add dev ippp0 root handle 1: cbq bandwidth 64kbit avpkt 1000
</I>><i> I get the error:
</I>><i> RTNETLINK answers: Invalid argument
</I>
You have to turn on the option
Prompt for development and/or incoplete code/drives
after that, you can select various options in the
networking -> QoS and/or fair queueing
options menue.
Greetings
Steffen
</PRE>
prev parent reply other threads:[~2001-01-30 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 17:56 [LARTC] iptables-table empty, can't get tc to work
2001-01-29 18:16 ` Stefan
2001-01-29 18:35 `
2001-01-30 12:17 ` Steffen [this message]
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-98373940416925@msgid-missing \
--to=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