Problem to shape Microsoft Remote Desktop traffic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

It seems I can't apply QoS over Remote Desktop connections (RDP/3389 TCP). I suspect that tc is not seeing the correct dst port of the 
connections. I believe it is seeing the source port.

I have some tc net rules, and for each of the /24 networks I handle, all 
the other protocols' rules are working. Only 3389 isn't. As I always 
have rules to catch non-specified protocols/ports, 3389 connections are 
always falling in that category.

My doubts were reinforced when I noticed that nettop tool was registering the source port (of the client) of the connection.
Could it be a RDP client behaviour?


By the way, this is an example group rule:

tc class  add dev eth1 parent 1:1 classid 1:33 htb rate 3000kbit ceil 3000kbit 
tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip dst 192.168.31.0/24 flowid 1:33 
tc class  add dev eth1 parent 1:33 classid 1:330 htb rate 750kbit ceil 2000kbit 
tc qdisc  add dev eth1 parent 1:330 handle 330: sfq perturb 10
tc class  add dev eth1 parent
 1:33 classid 1:331 htb rate 1000kbit ceil 3000kbit 
tc qdisc  add dev eth1 parent 1:331 handle 331: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 3389 0xffff flowid 1:331 
tc class  add dev eth1 parent 1:33 classid 1:332 htb rate 200kbit ceil 500kbit 
tc qdisc  add dev eth1 parent 1:332 handle 332: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 80 0xffff flowid 1:332 
tc class  add dev eth1 parent 1:33 classid 1:333 htb rate 50kbit ceil 80kbit 
tc qdisc  add dev eth1 parent 1:333 handle 333: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 53 0xffff flowid 1:333 
tc class  add dev eth1 parent 1:33 classid 1:334 htb rate 150kbit ceil 500kbit 
tc qdisc  add dev eth1 parent 1:334 handle
 334: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 110 0xffff flowid 1:334 
tc class  add dev eth1 parent 1:33 classid 1:335 htb rate 200kbit ceil 500kbit 
tc qdisc  add dev eth1 parent 1:335 handle 335: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 443 0xffff flowid 1:335 
tc class  add dev eth1 parent 1:33 classid 1:336 htb rate 20kbit ceil 180kbit 
tc qdisc  add dev eth1 parent 1:336 handle 336: sfq perturb 10
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 match ip sport 23 0xffff flowid 1:336 
tc filter add dev eth1 protocol ip parent 1:33 prio 1 u32 match ip dst 192.168.31.0/24 flowid 1:330



That's the order on the script which loads these rules.

I would appreciate some tips.

Thanks in advance.



--
Paz e Bem
Bruno Linhares
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux