On Fri, 6 Mar 2015 10:22:26 -0800,
j...@hpl.hp.com wrote
in E-mail "Re: Hybrid VLAN capability":
> Ken Ajiro wrote :
> >
> > To isolate the L2 domain equivalent to VLAN,
> > I think that following flow entries will be needed.
> >
> > in_port=1,v
Hello Ben, Jean,
Thank you for your reply.
As for my example of configuration:
port 1: trunks 100, 110, 120(connected to tenant networks)
port 2: trunks 100, 110, 120(connected to tenant networks)
port 3: trunks 200, 210, 220(connected to tenant networks)
port 4: trunks 200, 21
Hello,
I am hoping that OVS supports a functionality it allows to use port VLAN
with OpenFlow OFPAT_OUTPUT action. I wrote a patch for such feature,
is it possible to merge it to OVS?
I understand that OVS is supporting port VLAN capability for only
"normal switching". When we impl
When two ovs-vsctl update map type column at same time, one ovs-vsctl's
update will be discarded although all ovs-vsctl succeeded. This patch
fixes this issue.
Signed-off-by: Ken Ajiro
---
utilities/ovs-vsctl.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/util
Kawaguchi
Signed-off-by: Ken Ajiro
---
lib/flow.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/lib/flow.c b/lib/flow.c
index 678b8f0..e4154a7 100644
--- a/lib/flow.c
+++ b/lib/flow.c
@@ -229,9 +229,8 @@ parse_ipv6(struct ofpbuf *packet, struct flow *flow
