Skip to contentSkip to conversation

Bandwidth limiting problem

LARTC bert hubert [email protected] 1 participant 2 messages Oct 18, 2000 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): marc-lartc-98373938216792@msgid-missing

bert hubert [email protected]

author
#1 lore raw

<PRE>On Wed, Oct 18, 2000 at 09:34:30AM +0200, Fredrik Rambris wrote:
&gt;<i> Daniel Bergqvist wrote:
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; It works fine for me. Have you compiled the kernel with all QoS settings on? </I>&gt;<i>
</I>&gt;<i> Darn. I forgot the u32 rate esitmator... it works fine now. One thing </I>&gt;<i> that the HOWTO doesn't really tell is if the upstream and downstream is </I>&gt;<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

&gt;<i>
</I>&gt;<i>
</I>&gt;<i> &gt; &gt; -----Ursprungligt meddelande-----
</I>&gt;<i> &gt; &gt; Från: <A HREF="mailto:[email protected]">[email protected]</A>
</I>&gt;<i> &gt; &gt; [mailto:<A HREF="mailto:[email protected]">[email protected]</A>]För Fredrik Rambris
</I>&gt;<i> &gt; &gt;
</I>&gt;<i> &gt; &gt; tc qdisc add dev eth0 root handle 10: cbq bandwidth 100Mbit avpkt 1000
</I>&gt;<i> &gt; &gt;
</I>&gt;<i> &gt; &gt; tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 10Mbit \
</I>&gt;<i> &gt; &gt; rate 100Mbit allot 1514 weight 1Mbit prio 8 maxburst 20 avpkt 1000
</I>&gt;<i> &gt; &gt;
</I>&gt;<i> &gt; &gt; tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 100Mbit \
</I>&gt;<i> &gt; &gt; rate 128kbit allot 1514 weight 80Kbit prio 5 maxburst 20 avpkt 1000 \
</I>&gt;<i> &gt; &gt; bounded
</I>&gt;<i> &gt; &gt;
</I>&gt;<i> &gt; &gt; tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 15
</I>&gt;<i> &gt; &gt;
</I>&gt;<i> &gt; &gt; tc filter add dev eth0 parent 10:0 protocol ip prio 100 u32 match ip \
</I>&gt;<i> &gt; &gt; dst 192.168.3.0/24 flowid 10:100
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; _______________________________________________
</I>&gt;<i> &gt; LARTC mailing list / <A HREF="mailto:[email protected]">[email protected]</A>
</I>&gt;<i> &gt; <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>&gt;<i>
</I>&gt;<i> --
</I>&gt;<i> Admera Solution Provider AB
</I>&gt;<i> Tel: 0733-850 814
</I>&gt;<i> Position: 55°36´13N 13°03´36E
</I>Content-Description: Card for Fredrik Rambris

Signature · 6 lines
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>
author
#2 lore raw
In reply to a message not in the archive

<PRE>On Wed, Oct 18, 2000 at 01:39:56PM +0200, Fredrik Rambris wrote:

&gt;<i> &gt; You can also use the ingress policer but that's a bit after the fact, as the </I>&gt;<i> &gt; HOWTO says 'like throwing away half the letters you receive, in the hope </I>&gt;<i> &gt; that people will stop sending you them'.
</I>&gt;<i>
</I>&gt;<i> I could live with that (if it works). In the shaping example in the </I>&gt;<i> howto. How would ingress be implemented? What's the syntax? </I>
See the dDoS example in the HOWTO, it installs an ingress policer on SYN packets. I tried it at home and had some problems, tc gave an error, but perhaps I lack features in the kernel.

Regards,

bert hubert

Signature · 6 lines
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>