I'm only interested in a general solution, as described in the cited
email. I'm not going to take this change.
On Thu, Aug 20, 2015 at 03:04:52PM +0800, ychen wrote:
yes, maybe it is not a perfect resolution, but it did resolved
this problem: when tapB deleted from ovs bridge, tapA's ingress
yes, maybe it is not a perfect resolution, but it did resolved
this problem: when tapB deleted from ovs bridge, tapA's ingress rule disappeared
and of course, there maybe some problem I haven't consider,
so I want more detailed suggestions, thanks!
At 2015-08-20 13:03:53, Ben Pfaff
On Thu, Aug 20, 2015 at 11:29:07AM +0800, ychen wrote:
port's ingress qdisc rule will automatically disappeared after
the following steps:
1)use ip tuntap to create port tapA and tapB
2)set tapA and tapB to ingress qdisc with linux tc command
3)add tapA to ovs bridge
4)add tapB to the same
port's ingress qdisc rule will automatically disappeared after
the following steps:
1)use ip tuntap to create port tapA and tapB
2)set tapA and tapB to ingress qdisc with linux tc command
3)add tapA to ovs bridge
4)add tapB to the same ovs bridge(ingress rule disappear for tapA)
