Is it possible to throttle a given internal IP address to\nsome maximum bandwidth? I have a 3 Mbit/s link and I want to make\nsure\nthat our database replication system doesn't try to take more than 2\nMbit/s.\nUnfortunately the replication goes over SSH, so I can't easily\nseparate\nit from developer's SSH terminal sessions. I want them to have\nlow latency terminals, but I want bulk traffic also going over SSH to\nhave\na lower priority. I can mark the database replication SSH traffic\nbased on\nthe IP of the database. I toyed around with using trickle, but\nI would rather just have the firewall handle this detail.\n\nSometimes developers will do a bulk copy of data with SCP.\nIf possible I would like to make sure that any one IP address on\nour network cannot slow everyone else down. ... of course, you can't\nlook into an SSH stream and easily categorize the content; although,\nit\nseems to me that SSH streams that have not been using much bandwitdh\nshould be rewarded with a higher-priority. Maybe this type of QOS is\ntoo\nsophisticated for the ASA.\n\nI've been going over the QOS documentation and I understand how\nI can assign priority to certain categories of traffic, but I'm not\nsure\nhow to get from there to solving my problem.\nThe information might be here in the docs, but I'm missing the\nterminology.\nCorrect me if I'm just using the wrong terms to ask what I want or if\nI'm looking at this in the wrong way.\n\nAny pointers or examples?