RDP Client Hogging Bandwidth
-
Hello All,
Ive only just started to use PFsense, looks great, but im not having much luck with the traffic shaper.
My problem is that ive got a site with 10 clients that RDP to a remote server, this is over a 1024/1024 link. Once 1 or 2 people connect and start looking at website or something over RDP, it saturates the link and everyone else becomes slow.
RDP is the ONLY thing that gets used (there mostly thin clients)
RDP can happly run on 150Kbits/s, but if you update the screen offen, IE a full screen flash animation, then it will hog up 1000KBits/s easy, it will grab as much as it can.
How can i limit each of the 10 clients to only use only 150Kbit/s each?
Thanks
-
You need to create queues for each client and then setup shaper rules to send traffic from each client to the individual queue.
-
This is going to make me sound dumb, but how can i even do simple traffic shaping?
Ive ran the wizard, didn't really do what i wanted.
Ide like to just create a test 'shape' that will limit all FTP download traffic to 64Kbit/s
Can someone please correct my if ive got the following steps wrong.
1, create a download queue, name it qFTPdown give it 64Kbits bandwidth and give it an upper limit or 64Kbits, select NO flags. parent queue is qLANroot
2, create a upload queue, same as above, called qFTPup, parent queue is qWANroot
3, create a rule, called LimitFTPDownload, set target is qFTPdown/qFTPup, WAN => LAN, proto=any, source=any, dest=any, TOS=all dont care, flags=all dont all
4, apply it,
5, my downloads are stilling going fast (even after a restart),
6, the queues says the qlandef is running about 512Kb/s and qwanacks is about 11Kb/s
Whats going wrong??
Thanks
what else is there??
-
ftp is useing more ports then just port 20 and 21
it is using random ports for the downloading of the files
and sinse you can's now on wat for port that will be done you will not have a rule for it so then it will fall into the default queue -
Ok, understaood.
So lets forget the fact its FTP, lets say its all data (source=any dest=any protocol=any), and i want to limit it to 64Kbps.
I still cannot do something as simple as that???
Is there a tutorial or something i can follow, the doco is a little lite right now.
Thanks all
-
Have a look at http://forum.pfsense.org/index.php/topic,3135.msg18892.html#msg18892
databeestje added a penalty box option to the wizard that is acting as limits for an alias/IP. -
Hi, I've been scouring the net for this specific problem, specifically that Remote Desktop (RDP) will saturate over a WAN connection when viewing highly graphical content, e.g. ppt files, graphically intense web pages, active content etc.
I was thinking about this, and realized that the only reason packet shaping works with downloads is because packets are dropped until the machine you are downloading from gets the hint to stop sending packets. Correct?
So, considering that in this situation you have one server with many RDP sessions, if you attempt to limit RDP downloads per session on the client side with packet shaping, this may not actually do anything because everything we want to limit is coming from the same IP. As far as the server goes, it will try and transfer X RDP packets, the server side internet connection will throttle packets (including printer stuff etc) down globally to match whatever the client is receiving, but most of what is transferred will still be whatever is hogging the queue.
I suspect that the optimal solution to this problem would be to stick the packet shaping box between the RDP server and that server's internet connection. That way you can truly limit where the bottlenecks are - packets sent from the server to the various WAN terminals. It would also be cheaper, since you'd only need one shaping box. After all, most of the upload at the WAN ends are just keyboard presses, mouse clicks and pointer positions over RDP, which should be fairly minimal and constant info. Will try it and see how we go.