Hi Ashish Varma,
I think I have misunderstand the experimental message and nxm_match.
The match field is only contained in "flow_mod" or other messages.
But experimental openflow message could not be "flow_mod" message. For
example, it could be "nxm_set_packet_in" message.
Thanks. Regards
kai x
Hi Ashish Varma,
I have read the document as https://patchwork.ozlabs.org/patch/1145870/
When controller wants to send a flow to ovs through openflow, and the flow
both contains nicira match and openflow match. What's the value of "message
type" in "struct ofp_header".
Do the message contain both
It seems reasonable for OVS to always work this way.
There's information on contributing to OVS in
Documentation/internals/contributing/.
On Sat, Aug 31, 2019 at 12:34:59PM +0200, Dejan Pojbič wrote:
> Thanks Ben.
> Sadly it doesn't control Port/status/stp_sec_in_state field. That one still
> get
On 9/2/2019 7:20 AM, Sven Gebauer wrote:
Am 27.08.19 um 19:17 schrieb Gregory Rose:
Maybe someone else can help with that part but I'm curious why you feel
the need to specify the link-local address.
- Greg
Essentially, I'm trying to do GRE-over-Wireguard and need some kind of
addressing wit
Hi,numan,
As previous talk says, packets may be dropped by ACL rules, and
I find if create a port with tyx-net4(the shared network), traffic goes, I
think the new port bring up new ACLS. I do not know if this situation is
normal, if it is , the neutron could not support this f
