From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth limiting problem
Date: Wed, 18 Oct 2000 09:45:20 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216803@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216792@msgid-missing>
<PRE>On Wed, Oct 18, 2000 at 09:34:30AM +0200, Fredrik Rambris wrote:
><i> Daniel Bergqvist wrote:
</I>><i> >
</I>><i> > It works fine for me. Have you compiled the kernel with all QoS settings on?
</I>><i>
</I>><i> Darn. I forgot the u32 rate esitmator... it works fine now. One thing
</I>><i> that the HOWTO doesn't really tell is if the upstream and downstream is
</I>><i> 128kbit+128kbit or 128kbit/128kbit (they share the same bandwidth).
</I>
It does tell you. Unless you use the ingress policer, you only limit
*outgoing* data on an interface. So if you want to limit both up and
downstream, you need 2 interfaces, and 2 sets of rules.
You can also use the ingress policer but that's a bit after the fact, as the
HOWTO says 'like throwing away half the letters you receive, in the hope
that people will stop sending you them'.
Regards,
bert hubert
><i>
</I>><i>
</I>><i> > > -----Ursprungligt meddelande-----
</I>><i> > > Från: <A HREF="mailto:boost@lxmul01aspm.admera.local">boost@lxmul01aspm.admera.local</A>
</I>><i> > > [mailto:<A HREF="mailto:boost@lxmul01aspm.admera.local">boost@lxmul01aspm.admera.local</A>]För Fredrik Rambris
</I>><i> > >
</I>><i> > > tc qdisc add dev eth0 root handle 10: cbq bandwidth 100Mbit avpkt 1000
</I>><i> > >
</I>><i> > > tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10Mbit \
</I>><i> > > rate 100Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
</I>><i> > >
</I>><i> > > tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 100Mbit \
</I>><i> > > rate 128kbit allot 1514 weight 80Kbit prio 5 maxburst 20 avpkt 1000 \
</I>><i> > > bounded
</I>><i> > >
</I>><i> > > tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 15
</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> > _______________________________________________
</I>><i> > LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> > <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>><i>
</I>><i> --
</I>><i> Admera Solution Provider AB
</I>><i> Tel: 0733-850 814
</I>><i> Position: 55°36´13N 13°03´36E
</I>Content-Description: Card for Fredrik Rambris
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
next parent reply other threads:[~2000-10-18 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <marc-lartc-98373938216792@msgid-missing>
2000-10-18 9:45 ` bert [this message]
2000-10-18 12:57 ` [LARTC] Bandwidth limiting problem bert
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-98373938216803@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.