>>I believe you should already be able to set the SLL and TLL options. Does
>>that not work for you?
>> In order to set up IPv6 NA responder we will be required to modify incoming
>> solicitations with SLL
>> option (multicast solicitations) to an Advertisement with TLL option. My
>>
You can create ifcfg-* files under /etc/network/interfaces.d/ in case of Ubuntu
and set the IP address there.
BTW which version of OVS are you using ?
Regards,
Vishal
From: ovs-discuss-boun...@openvswitch.org
On Behalf Of Tejali Bhujbal
Sent: Thursday, June 14, 2018 2:33 PM
To:
Hi Ben,
I have sent patch for review on dev mailing list. If approved for master please
backport it to 2.8 branch as well.
https://mail.openvswitch.org/pipermail/ovs-dev/2018-June/348266.html
Warm Regards,
Vishal Ajmera
___
discuss mailing list
Hi,
In bundle based resync, we try to apply all rules from the bundle one-by-one.
If a rule encounters any error, we revert back (undo) rules which were applied
successfully. This is accomplished in function add_flow_revert() ->
replace_rule_revert() -> ofproto_rule_insert__() using old_rule
>Thanks for the bug report.
>The comment is pretty clear that a rule may not be reinserted and the
>assertion matches that. The >comment probably reflects how it's not safe to
>cmap_remove() and then reinsert a cmap_node (before a >grace period has
>elapsed).
>Do you have an example of how
>> Zak had completed most of the work to set the RSO flags, so I'm sure he'd be
>> happy
>> to send it out if you want to take the patches in yourself. However, I
>> don't think it
>> makes sense to include that functionality more generally in OVS.
Hi Justin,
Can you please share the patch
> Zak is working on that feature; I expect patches will hit the mailing list in
> the next week or two.
>
> Hi Justin,
>
> As part of this feature, will it also enable us to rewrite the options
> tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to
> rewrite these fields in
>> Zak is working on that feature; I expect patches will hit the mailing list
>> in the next week or two.
>>
>> Hi Justin,
>>
>> As part of this feature, will it also enable us to rewrite the options
>> tlv:type field from SLL (1) to TLL (2) Or may be a set-field option to
>> rewrite these
Hi Steven,
Could you please dump the “ip route” table of kernel on the host ? I am
suspecting if gateway configuration (10.80.180.1) on kitbr0 is causing an
issue. Can you try removing the gateway configuration and verify again ?
Warm Regards,
Vishal Ajmera
From:
Hi Greg,
Please refer to “Common Configuration Issues” page on OpenvSwitch. This issue
is listed as very first one ☺.
http://docs.openvswitch.org/en/latest/faq/issues/
Warm Regards,
Vishal Ajmera
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf
...@openvswitch.org] On Behalf Of Vishal Deep Ajmera
Sent: Tuesday, January 02, 2018 3:43 PM
To: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports
Can someone help with route issue below ?
Warm Regards,
Vishal
From:
ovs-discuss-boun...@openvswitch.org
the issue.
Warm Regards,
Vishal Ajmera
-Original Message-
From: Flavio Leitner [mailto:f...@sysclose.org]
Sent: Tuesday, January 16, 2018 9:17 AM
To: Vishal Deep Ajmera <vishal.deep.ajm...@ericsson.com>
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] REDHAT: Route issue wit
Why is TC flow offload APIs being added in netdev-vport ?
For linux TC offloads I believe a device needs to be present in linux
to operate on. As per my understanding netdev-vport classes are used
to represent tunnels (vxlan, gre etc.) and none of them creates a linux device.
All the TC offload
Hi Flavio,
I tried to look closer into ifup-ovs script particularly for OVSDPDKPort &
OVSDPDKBOND cases.
With the change given below (git diff) at the end OVSDPDKBOND case, I see that
the routes
are getting installed again after adding dpdkbond port to the bridge. Perhaps
the same fix
needs
> OK, what about this patch instead? It should fix the issue without the
> errors. I have not tested.
I tried your patch but it does not re-add the routes. The reason is doing
$ ifup br0 will not invoke ifup-post since the bridge port is already UP and so
$OVSBRIDGECONFIGURED will be 'true'.
I
Hi Flavio,
I have sent a formal patch to mailing list. Sorry for submitting a little late.
Warm Regards,
Vishal Ajmera
-Original Message-
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Vishal Deep Ajmera
Sent: Saturday, January 20
Hi,
On Red-Hat, kernel IP Routes are getting deleted whenever a dpdk-bond port is
added to "netdev" type bridge. I understand that when a DPDK port is added to
ovs, the bridge port (LOCAL) is reconfigured with MAC address which requires
IOCTL calls to bring the device down and up. This causes
Can someone help with route issue below ?
Warm Regards,
Vishal
From: ovs-discuss-boun...@openvswitch.org
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Vishal Deep Ajmera
Sent: Tuesday, December 26, 2017 2:02 PM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] REDHAT: Route
> >
> > Vishal, will you send a patch to do that?
> >
>
> Thanks Ben and Ethan for reviewing. I will send a patch to fix this on
> dev-list.
>
Hi Ben, Ethan,
I have sent a patch fixing this issue on mailing list for review.
Warm Regards,
Vishal
___
Hi,
The udpif_revalidator function uses dump-duration time to determine the flow
limit and tunes it as per system conditions for e.g. if duration is more, flow
limit is reduced and vice-versa. However I notice one issue with the logic used
in the implementation:
if (duration >
>
> Thanks. After staring at it for a while, I think I'm comfortable with
> removing it.
>
> Vishal, will you send a patch to do that?
>
Thanks Ben and Ethan for reviewing. I will send a patch to fix this on dev-list.
___
discuss mailing list
>
> At first glance it looks like you're correct, but this code was added in
> 2013 with the following commit and hasn't changed since, so I wonder whether
> we're missing something important. Ethan, you wrote this code, do you have
> any thoughts?
>
> commit
> It looks good to me. I hope it does work for any number of ports
> and doesn't show any errors. If that's the case, please submit a
> formal patch to ovs-dev@ and don't forget to request to patch 2.9
> (if you need that) as it's branched off at this point.
Ok Flavio. I will send formal patch
> BTW, I suggested earlier but maybe I wasn't clear.
>
> Instead of adding networking configuration to the bridge's port, just
> leave it alone with a name that doesn't bother you.
>
> Then create an internal port with the name and the networking
> configuration you need. It won't change its MAC
Hi,
We are trying to setup Neighbor Solicitation Responder using OpenFlow pipeline
in OVS however it seems some of the fields in Neighbor Advertisement Message
Format cannot be set using OpenFlow set actions. Following is the frame format
of NA message:
0 1
On Wed, Apr 04, 2018 at 06:51:05AM +, Vishal Deep Ajmera wrote:
> Is there a way in OVS today, wherein we can set OpenFlow pipeline
> actions to write (copy) from a register to arbitrary location in the
> packet. The start offset for read (from register) & write (to packet)
>
> On Apr 8, 2018, at 9:55 AM, Ben Pfaff <b...@ovn.org> wrote:
>
> On Sun, Apr 08, 2018 at 04:34:16PM +0000, Vishal Deep Ajmera wrote:
>>
>> In the above message, fields R (Router flag), S (Solicited flag) and O
>> (Override flag) cannot be set. Is my
> Zak is working on that feature; I expect patches will hit the mailing list in
> the next week or two.
Hi Justin,
As part of this feature, will it also enable us to rewrite the options tlv:type
field from SLL (1) to TLL (2) Or may be a set-field option to rewrite these
fields in Options TLV.
Hi,
Currently in OVS we set "-1" for ofport field in interface table of OVS DB when
we fail to initialize the interface. This means if we had allocated any ofport
number earlier, it is released. When the above failed interface gets
initialized successfully later it gets a "new" ofport number
Anyone faced similar issue with other controllers?
From: ovs-discuss-boun...@openvswitch.org
On Behalf Of Vishal Deep Ajmera
Sent: Wednesday, November 21, 2018 2:14 PM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] Reg. ofport set to -1
Hi,
Currently in OVS we set "-1"
I think you need to set "fail-mode=secure" for the bridge connected to
controller. By default it will be set as "standalone".
From: ovs-discuss-boun...@openvswitch.org
On Behalf Of Alon Dotan
Sent: Tuesday, April 2, 2019 5:08 PM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] of rules
Hi Ben, Jarno,
I am not sure why we have to take a lock (ofproto_mutex) for processing
packet-out action. I think this action does not modify any open flow table. I
could see that lock is required for actions like flow_add/flow_mod etc. as they
are modifying the existing flow tables.
Any
Hi,
I think this issue can be hit always when controller sends a packet with
packet-out (output port as OFPP_TABLE) and any of the open-flow table entry
which gets hit results into learn action.
Am I missing something?
Warm Regards,
Vishal Ajmera
From: ovs-discuss-boun...@openvswitch.org
this make sense ?
Regards,
Vishal
From: Vishal Deep Ajmera
Sent: Tuesday, November 27, 2018 11:17 AM
To: Vishal Deep Ajmera ;
ovs-discuss@openvswitch.org
Subject: RE: Reg. ofport set to -1
Anyone faced similar issue with other controllers?
From:
ovs-discuss-boun...@openvswitch.org<mailto:ovs-disc
Hi,
Does anyone know of any performance impact of running OVS + DPDK in a docker
container environment v/s running it on bare-metal ?
Are there any known functional limitations when running inside a container ?
We primarily use "netdev" bridges with "vhostuserclient" ports to connect to
guest
Hi,
I was wondering if any official announcement had been made for OVS 2.13
release in Feb, 2020. I probably missed it but I could not locate it on the
official openvswitch.org webpage either.
Can someone help with the link to the ovs-2.13 tar ball?
Warm Regards,
Vishal Ajmera
36 matches
Mail list logo
