On Wed, Jul 27, 2016 at 5:37 PM, Luca Salvatore wrote:
> I've found some random articles which talk about GUE (generic UDP
> encapsulation) but can anyone give me a solid yes or no answer if OVS
> support GUE
> (https://tools.ietf.org/html/draft-ietf-nvo3-gue-04#section-5.10)
No.
I've found some random articles which talk about GUE (generic UDP
encapsulation) but can anyone give me a solid yes or no answer if OVS
support GUE (https://tools.ietf.org/html/draft-ietf-nvo3-gue-04#section-5.10
)
___
discuss mailing list
discuss@openvsw
Hi -
I have a curious situation. The environment is a Linux CentOS 7 system
with an ovs bridge (ovs-bridge) and two tap devices (abs-tap and
qemu-tap). When running a qemu vm attached to qemu-tap I can receive
(inside the qemu vm) arbitrary UDP packets. However, when I try to send a
UDP packet
When I configure kvm and openvswitch-2.5.0on the Ubuntu-15.10
(kernel:4.2.0-16-generic), I face a problem, I configure them on the base of
INSTALL.KVM. When I use the command ?? sudo kvm -m 512 -net
nic,macaddr=00:11:22:EE:EE:EE -net
tap,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdow
On Tue, Jul 26, 2016 at 6:32 PM, Mauricio Vasquez
wrote:
> Hello Sothy,
>
> Sorry for the delay in answering, some busy days here.
>
>
> On 07/25/2016 12:03 PM, sothy shan wrote:
>>
>> Hello Mauricio,
>>
>> On Sun, Jul 24, 2016 at 12:17 PM, Mauricio Vasquez
>> wrote:
>>>
>>> Hi Sothy,
>>>
>>>
>>>
Hi, All,
I am running openvswitch 2.5.0 on Ubuntu 14.04 LTS with kernel
3.13.0-92-generic.
I installed the two following rules to the switch:
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=2.183s, table=0, n_packets=0, n_bytes=0, idle_age=2,
priority=5,ip,in_port=1,nw_src=10.0.0.0/8,nw
Hi,
I added a field ( not related to the packet just like idle_timeout...) to
the flow in userspace, but when I wanted to add that field in datapath I
had problems, and I think because datapth still doesn't recognize that
field yet, so I want to ask if you had a document or steps to add a field
in
Hi All,
I am trying to add some flows include a arp reply flow on OVS2.5.0, but getting
a small probability error.
OFPT_ERROR (xid=0x4): OFPFMFC_BAD_COMMAND OFPT_FLOW_MOD (xid=0x4):
(***truncated to 64 bytes from 240***)
01 0e 00 f0 00 00 00 04-00 30 20 ef 00 00 00 00 |.0 .