All of lore.kernel.org
 help / color / mirror / Atom feed
From: johan@pinguind.co.id
To: lartc@vger.kernel.org
Subject: [LARTC] Not proved, fw classifier ?
Date: Thu, 26 Apr 2001 23:50:27 +0000	[thread overview]
Message-ID: <marc-lartc-98832902614971@msgid-missing> (raw)

I had tried this
#iptables -t mangle -A PREROUTING -p tcp --sport 20 -j MARK --set-mark 1

#tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 10Mbit avpkt 1000 cell
8

#tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 10Mbit rate
10Mbit weight 1Mbit prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000

#tc class add dev eth0 parent 1:1 classid 1:1234 cbq bandwidth 10Mbit rate
128Kbit weight 12Kbit prio 5 allot 1514 cell 8 maxburst 20 avpkt 1000
bounded isolated

#tc qdisc add dev eth0 parent 1:1234 tbf rate 128Kbit buffer 10Kb/8 limit
15Kb mtu 1500

#tc filter add dev eth0 parent 1:0 proto ip handle 1 fw classid 1:1234

And, we tested with ftp, we didn't get result that I would expected.

any suggest ?
let me know your example for fw classifier ....

Best Regards

Johan

-- 
             -\x1e'-      
             (o o)     
---------ooO--(_)--Ooo-------------------------------------------------
  (  )/  \( )( ) (  ) ( \( )      Visit us at http://www.pinguind.co.id
 __)(( () ))__(  /__\  )  (   Feel free to contact me at ICQ  #47240718       
(___/ \__/(_)(_)(_)(_)(_)\_)                 email:johan@pinguind.co.id          
-----------------------------------------------------------------------

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-04-26 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 23:50 johan [this message]
2001-04-27  6:28 ` [LARTC] Not proved, fw classifier ? Stef Coene

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-98832902614971@msgid-missing \
    --to=johan@pinguind.co.id \
    --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.