Hi Farhad,
Got you, thanks your help.
Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
District, Shanghai, China (201203)
From: Farhad Sunavala
To: "discuss@openvswitch.org"
Hi Juno,
Each flow-classifier has a mandatory logical-source port (mandatory for OVS
driver).If it is mandatory for OVN driver also, you should be able to get the
lswitch fromthe logical source port in the flow classifier.
Farhad.
From: "Na Zhu"
To: John McDowall
Cc: Srilatha Tangirala , "Ope
Ryan,
Thanks your really helpful comments.
If the lswitch is determined by flow classifier, I think no need to record
in logical router, ovn creates patch port pair for router interface, one
patch port connects logical switch, the other connects logical router. The
one connects logical switch i
"discuss" wrote on 06/14/2016 10:31:40
PM:
> From: John McDowall
> To: Na Zhu
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)" d...@lists.openstack.org>, discuss
> Date: 06/14/2016 10:48 PM
> Subject: Re: [ovs-discuss] [opens
Hi John,
Another question, I think port-chain is irrelevant with lswitch, one
port-chain includes multiple port-pair-groups and one flow-classifier, how
to get the lswitch by port-chain?
Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com
5F, Building 10
John,
Since you have port-chain as child of lswitch, do you need port-pairs as
child of lswitch any more?
Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
District, Shanghai, China
John,
OK, I will change networking-ovn IDL to align with the new schema.
Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
District, Shanghai, China (201203)
From: John McDowall
On Tue, Jun 14, 2016 at 12:19:14PM +0200, james hopper wrote:
> Hey Everyone,
> While configuring group chaining on OVS-2.4, I am
> getting OFPGMFC_CHAINING_UNSUPPORTED. Am i missing something or OVS-2.4 does
> not support it at the moment?
OVS 2.5 supports group chaining, but OVS 2.4 and earlier
Hi John,
I submit one patch to every private repo, the create port chain can work
now.
Regards,
Juno Zhu
IBM China Development Labs (CDL) Cloud IaaS Lab
Email: na...@cn.ibm.com
5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
District, Shanghai, China (201203)
From:
Hey Everyone,
While configuring group chaining on OVS-2.4, I am getting OFPGMFC_CHAINING_UNSUPPORTED. Am i missing something or OVS-2.4 does not support it at the moment?
OFPT_ERROR (OF1.5) (xid=0x2): OFPGMFC_CHAINING_UNSUPPORTED
OFPT_GROUP_MOD (OF1.5) (xid=0x2):
(***truncated to 64 bytes from
When I use hostapd to create a protected AP (psk2) on wlan0 with ovs acting
as bridge to wlan0 & eth0. The client gets authenticated successfully but
it does not get ip address & client gets stuck on obtaining IP.
The client is connected successfully if i manually create bridge, the
problem only oc
11 matches
Mail list logo
