[LARTC] 'sport' is good but 'dport'?

* [LARTC] 'sport' is good but 'dport'?
@ 2002-10-11  1:04 박정은
  2002-10-11  1:13 ` 박정은
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: 박정은 @ 2002-10-11  1:04 UTC (permalink / raw)
  To: lartc

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

hi all

I just tried to test whether the HTB works well or not .. (policy is very simple ^^;;)

I tried HTB simulator 'Ethloop' with lo (loopback ) and I found HTB works well....(very well)

So I changed lo to eth0  and tested ..

./tc qdisc add dev eth0 root handle 1: htb default 10
./tc class add dev eth0 parent 1: classid 1:1 htb rate 500kbps ceil 500kbps
./tc class add dev eth0 parent 1:1 classid 1:2 htb rate 180kbps ceil 500kbps
./tc class add dev eth0 parent 1:2 classid 1:10 htb rate 150kbps ceil 500kbps prio 2
./tc class add dev eth0 parent 1:2 classid 1:11 htb rate 5kbps ceil 10kbps prio 2
./tc class add dev eth0 parent 1:1 classid 1:12 htb rate 10kbps ceil 20kbps prio 1
./tc qdisc add dev eth0 parent 1:10 handle 20: pfifo limit 5
./tc qdisc add dev eth0 parent 1:11 handle 30: pfifo limit 5
./tc qdisc add dev eth0 parent 1:12 handle 40: sfq perturb 10

./tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip sport 23 0xffff flowid 1:11
./tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip sport 80 0xffff flowid 1:12

 It works well with outgoing packets ..  

 BUT!!   

  I changed last two lines to control Incoming packets .. like below..
./tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip dport 23 0xfffe flowid 1:11
./tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip dport 80 0xfffe flowid 1:12

It never works .. !!   If I send to 23 port 50kbps  It receive 50kbps.. I have no idea ..  

Did I thought wrong?    

thanks in advance...

[-- Attachment #2: Type: text/html, Size: 2744 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread