This is very helpful. Thanks!
On Mon, Mar 25, 2024 at 1:18 AM Eelco Chaudron wrote:
>
>
> On 22 Mar 2024, at 19:58, Ashish Varma via discuss wrote:
>
> > Hi
> > I have been trying to look at the concept of recirculation in OVS.
> >
> > Foun
Hi
I have been trying to look at the concept of recirculation in OVS.
Found an old description by Joe Stringer:
*OVS_ACTION_ATTR_RECIRCULATE:* Open vSwitch datapath interface extension.
Not exposed at the OpenFlowlayer.* Datapath interface inserts this action
when it needs more in
Hello all,
I saw a setup where the ct action was used like:
ct(table=100, commit, zone=6000, exec(
move:NXM_OF_IN_PORT[0..15]->NXM_NX_CT_LABEL[48..63]))
According to the ovs-actions man page:
"
Without *commit*, the *ct *action accepts the following arguments:
*table=**table*
Thanks for the clear explanation!
From: Ilya Maximets
Date: Monday, July 10, 2023 at 5:05 AM
To: Ashish Varma , ovs-discuss@openvswitch.org
Cc: i.maxim...@ovn.org
Subject: Re: [ovs-discuss] NXAST_CONTROLLER vs NXAST_CONTROLLER2
!! External Email
On 7/10/23 02:16, Ashish Varma via discuss
Hello,
>From ovs-actions man pages, the controller action is defined as:
The controller action
Syntax:
controller
controller:max_len
controller(key[=value], ...)
There is no ‘controller2’ action. So, when programming a flow, can we ask OVS
to u
ple, this following rule works:
>
> # If reg0 is 1 and reg1 is 1, then output such packet via reg0
> # reg0 and reg1 would have been set via learn operations earlier
> ovs-ofctl add-flow br0 table=4 reg0=1,reg1=1 actions=output:reg0
>
> *Vasu Dasari*
>
>
> On Tue, Mar 8, 2
I am trying to find the meaning of the following statement in the
ovs-actions man page:
"Output to a register is an OpenFlow extension introduced in Open vSwitch
1.3."
Does this mean that we can specify an action like: "output:"
and the value of the output port would be taken from the given regis
I have attempted to write a document explaining the Nicira extension which
is still a v1 patch for review.
https://patchwork.ozlabs.org/patch/1145870/
Nicira extensions were added in the early days of OVS during early OpenFlow
versions and a lot of those extensions made it to standard OpenFlow
sp
Please see inline as [Ashish]
On 5/23/19, 8:39 PM, "Ben Pfaff" wrote:
On Thu, May 23, 2019 at 10:46:40PM -0400, Vasu Dasari wrote:
> Thanks for digging into this. My comments inline. I am sorry that I had to
> differ from your analysis.
Thank you for the correction. You ar
Please see the following documentation for getting ovs source and
installing it:
http://docs.openvswitch.org/en/latest/intro/install/general/
On Mon, Feb 4, 2019 at 6:28 AM 장예훈 wrote:
> Hi.
>
>
>
> I want to modify the ovs code and know the packet interval time.
>
> But the ovs source code coul
I am working on adding the OpenFlow14+ OFPT_MULTIPART / OFPMP_FLOW_MONITOR
support in OVS. (as you rightly said, the current OVS only supports OpenFlow10
STATS_REQUEST vendor extensions)
The time frame is around mid-October.
Thanks,
Ashish
On 9/21/18, 1:13 PM, "Ben Pfaff" wrote:
On Fri,
I tried out ODL (nitrogen SR3) with the latest OVS (2.10.90) with the
following configuration:
sudo ovs-vsctl show
c4f25e49-0e9c-4861-bd2d-e82f20a80864
Bridge "br20"
Controller "tcp:10.xx.xx.xx:6653" <-- ODL
is_connected: true
Port "br20"
Interface "br2
http://www.openvswitch.org/support/dist-docs/ovs-fields.7.txt has NSH
related match fields in addition to the information in the ovs-ofctl man
page.
Regarding NSH over IP transport, my understanding is that the latest NSH
RFC 8300 defines only the ethernet eth type of 0x894f for NSH.
I don't see a
out the *sctp_header* fields?
>
> PS: I turned off the kernel datapath and am using only the userspace path.
> Moreover, the SCTP traffic is being sent between the end hosts perfectly,
> no problem at all.
>
> Thanks in advance,
>
&
Try debugging from functions:
ofputil_pull_ofp11_match -->
oxm_pull_match
"ofputil_match_from_ofp11_match" is called for "OFPMT_STANDARD" case which
is deprecated in the openflow 1.4 standard.
Thanks,
Ashish
On Mon, May 21, 2018 at 10:32 AM, Pedro Hen
For every bridge created using ovs-vsctl command (ovs-vsctl add-br
), an internal port with the name same as gets
created.
You can set the ip address of this interface on the host running mininet.
e.g. just running "sudo mn" creates a switch s1 and hosts h1 and h2 with h1
ip 10.0.0.1 and h2 with
Appreciate your response to the questions Yi Yang. These are very helpful.
Would definitely going to try the ODL SFC demo as shown below (and maybe more
queries around this..)
-Ashish
From: Yang, Yi Y
Sent: Tuesday, April 24, 2018 5:52:11 PM
To: Ashish Varma
and #2 are also very useful.
We would be coming back to this thread for more information or questions and
any more comments to the questions are more than welcome.
Thanks Jan for your answers and input!
-Ashish
From: Jan Scheurich
Date: Friday, April 20, 2018 at 5:09 PM
To: Ashish Varma
dynamically put the
header back.
What are your thoughts on this?
Thanks,
Ashish Varma
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Encountered an OVS startup problem [self created :( ] and thought of
sharing this, and the solution, incase someone encounters this issue:
I was getting this error after I built / installed OVS.
The reason was that I had first built OVS using following configure
parameters:
./configure --enable-s
20 matches
Mail list logo
