>> 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 fie
Hi Guru,
Thanks for your reply, but I can’t make sure what MAC address for Gateway,
doesn’t this should be automatic done by OVS NAT function?
---
Best Regards,
Wei-Yu Chen
Wireless Internet Laboratory
Department of Computer Science
National Chiao Tung University
On 30 April 2018 at 11:49:29
> On May 2, 2018, at 2:50 AM, Vishal Deep Ajmera
> wrote:
>
>> 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)
> On May 2, 2018, at 8:40 AM, Sh j wrote:
>
> For example, if an OVS receives a ICMP_reply and it is the destination of
> this ICMP_reply, it does not need to send a packet_in to the controller.
> So I want to install some flow rules or configure OVS to not send packet_in
> messages in this c
Dear All,
I am trying to create multiple dpdk-netdev based data paths with OVS 2.9 and
DPDK 16.11 running on CentOS 7.4. I am able to create multiple data paths
using "ovs-appctl dpctl/add-dp netdev@netdev1" and I can see a new data path
created with "ovs-appctl dpctl/show". However I cannot a
You don't want to do that. The controller should always initiate the flow
rules on switch connection to ensure stale or unwanted rules aren't present.
If you want to "force" a set of base rules, have ONOS push them to every
switch on connection.
On Wed, May 2, 2018 at 11:40 AM, Sh j wrote:
> Fo
For example, if an OVS receives a ICMP_reply and it is the destination of
this ICMP_reply, it does not need to send a packet_in to the controller.
So I want to install some flow rules or configure OVS to not send packet_in
messages in this case.
I am using ONOS as a controller. The problem is that
Update:
I seem to be between a rock and a hard place. The link I referenced in
my first post specifically says:
Wicked 0.6.23+
Please ensure that the OpenvSwitch service starts before the Network
service by verifying/editing the OpenvSwitch service file:
# /usr/lib/systemd/system/openvswitch.s
Hi,
I have a question about file descriptors used by the ovs-vswitchd process.
I created a simple topology using Mininet, consisting of two vhosts (i.e.,
net namespaces) connected to a single kernel OVS instance via veth pairs.
Before creating the topology, there are 20 FDs used by ovs-vswitchd
> 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 O
Sorry, more information.
If I configure the environment and then reboot without performing the
ifup part the database is entact after reboot.
If I configure the environment perform:
ifup ovsbr0
ifdown ovsbr0 (whether I have stopped the openvswitch.service or not)
The database is empty.
I assume
Apologies, please ignore the $'s in port$0 and port $1. That is a cut
and paste error since I actually utilized a bash script recommended in
the openvswitch documentation.
Those lines should read:
ovs-vsctl add-port ovsbr0 port0 -- set Interface port0
type=internal
ovs-vsctl add-port ovsbr0 port1
My apologies in advance if this has been asked and answered. I would
appreciate instructions if there is a way to search the archive.
Also, to the developers thank you for this software.
I am building a development environment on a laptop.
OS: openSUSE LEAP 42.3
openvswitch version: 2.7.0-7.1
T
13 matches
Mail list logo