On 12-12-11 10:14 PM, Tom Herbert wrote:
This patch adds ipv6 set action functionality. It allows to change
traffic class, flow label, hop-limit, ipv6 source and destination
address fields.
I have to wonder about these patches and the underlying design
direction. Aren't these sort of things and more already implemented
by IPtables but in a modular and extensible fashion? Has there been
any thought into hooking OVS to IP tables to leverage all the existing
functionality?
I gave up this fight, but id be curious to see what the answer is ;->
Actually at the level they are doing things (bridge level)
as i was mentioning to you tc action is the right abstraction. There is
nothing they do that cant be done at that level. I am hoping that i will
get time/resources to illustrate a purely standard kernel level approach.
cheers,
jamal
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev