On Oct 13, 2011, at 10:27 AM, Ben Pfaff wrote: > On Thu, Oct 13, 2011 at 03:42:01PM +0100, Mike Bursell wrote: >> I've also done some further looking around, and it turns out that >> official site (http://lartc.org/) suggests that IPv6 is not >> supported for rate limiting, the site is very out of date, and it >> should, in fact, be possible (see >> http://tcn.hypert.net/tcmanual.pdf, for example). I'm guessing that >> adding a second command, along the lines of >> >> #define POLICE_CONFIG_CMD_IP6 "/sbin/tc filter add dev %s parent ffff: >> protocol ip6 prio 51 u32 match ip6 src 00::00/0 police rate %dkbit burst %dk >> mtu 65535 drop flowid :1" >> >> ...might work, as long as both were applied (note that I've changed >> the priority). Has anyone tried this, or are there other missing >> pieces, such as how the packets are marked, that are likely to cause >> problems? I'm willing to accept that there's much deeper work to be >> done - I've only just started scratching the surface this afternoon, >> and am very far from being a tc guru. > > I don't know, but if you test it and it turns out to be effective, > please let us know and we'll toss it in for the next version.
Yes, just to add to what Ben said, we added policing support way before we had IPv6 support. IPv6 not being supported is simply an oversight. (Oh, and I don't think anyone can be a tc guru. :) ) Thanks for tracking this down and proposing a solution! --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
