Timeline for Best method for rate limiting ingress & egress traffic hosts in colocation
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 15, 2017 at 1:23 | comment | added | Ron Maupin♦ | Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. | |
Nov 4, 2016 at 13:48 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Oct 5, 2016 at 13:21 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Sep 5, 2016 at 13:07 | answer | added | Ecnerwal | timeline score: 2 | |
Sep 4, 2016 at 21:44 | comment | added | Ron Maupin♦ | You can add RED to keep the queues from filling and TCP from synchronizing. Leave it to the other ends to do the shaping to what you grant. | |
Sep 4, 2016 at 21:40 | comment | added | ausip | Thanks Ron. We don't have the equipment yet. We are trying to use these decisions to assist with selection of hardware. If it's just straight policing, we will probably go with a Cisco or Brocade layer 3 switch. I just wasn't sure about straight policing / rate limiting as once the hard limit is reached it drops packets. I wasn't sure how this would affect user experience as opposed to shaping with queues, although with shaping, once the queues are exhausted packets will be once again dropped. | |
Sep 4, 2016 at 16:47 | comment | added | Ron Maupin♦ | Usually, simple policing to a specified rate is how this is done. If you can tell us the equipment, we can give you examples of how to do this. | |
Sep 4, 2016 at 13:01 | review | First posts | |||
Sep 4, 2016 at 16:38 | |||||
Sep 4, 2016 at 12:59 | history | asked | ausip | CC BY-SA 3.0 |