From: Daniel Bergqvist daniel@netatonce.se
To: lartc@vger.kernel.org
Subject: SV: [LARTC] Bandwidth limiting problem
Date: Tue, 17 Oct 2000 14:02:38 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216793@msgid-missing> (raw)
<PRE>Hi!
Please post the other tc commands too, so I may test it.
Regards,
Daniel
><i> -----Ursprungligt meddelande-----
</I>><i> Från: <A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A>
</I>><i> [mailto:<A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A>]För Fredrik Rambris
</I>><i> Skickat: Tuesday, October 17, 2000 2:04 PM
</I>><i> Till: <A HREF="mailto:lartc@mailman.ds9a.nl">lartc@mailman.ds9a.nl</A>
</I>><i> Ämne: [LARTC] Bandwidth limiting problem
</I>><i>
</I>><i>
</I>><i> Hi!
</I>><i>
</I>><i> I'm trying to limit the access to and from a 2MBit leased line to a
</I>><i> total of 128kbit (up+down must not exceed 128kbit).
</I>><i>
</I>><i> eth0 is connected to our lan with 100MBit
</I>><i> eth1 is connected to Internet via a router
</I>><i>
</I>><i> I've tried modifying the examples in the howto and it succeeds up to the
</I>><i> filter definition where I get an error.
</I>><i>
</I>><i> tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip \
</I>><i> dst 192.168.3.0/24 flowid 10:100
</I>><i>
</I>><i> gives
</I>><i>
</I>><i> RTNETLINK answers: Ogiltigt argument
</I>><i>
</I>><i> (Ogiltigt argument = Invalid argument)
</I>><i>
</I>><i> This should be a real easy one. Only one class (the whole local network)
</I>><i> should only get access to 128kbit of the 2Mbit.
</I>><i>
</I>><i> Anyone have some idea of what I could be doing wrong?
</I>><i>
</I>><i> / Fredrik Rambris
</I>><i> --
</I>><i> Admera Solution Provider AB
</I>><i> Tel: 0733-850 814
</I>><i> Position: 55°36´13N 13°03´36E
</I>
</PRE>
reply other threads:[~2000-10-17 14:02 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-98373938216793@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 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.