Re: [ovs-discuss] OpenFlow enabled OpenWRT for TP Link 1043 ND

https://github.com/CPqD/ofsoftswitch13/wiki/OpenFlow-1.3-for-OpenWRT On Thu, Jun 12, 2014 at 3:34 PM, Ben Pfaff wrote: > On Thu, Jun 12, 2014 at 01:06:38AM +0500, Sayed Qaiser Ali Shah wrote: >> Hope all of you are doing well. I am working on TP Link 1043 ND v2.1 >> router. I want to make it open

Re: [ovs-discuss] Problem initiating TLS 1.2 hello from OVS client to NOX controller

On Thu, Jun 12, 2014 at 09:26:42PM +, Singhal, Abhinav wrote: > I have OVS (1.11.0) and the OpenSSL (1.0.1e-fips) installed on a > VM. I checked the OpenSSL release notes and it says that the version > I am using supports TLS 1.2. My NOX controller is running in passive > TLS mode. Problem is,

[ovs-discuss] Problem initiating TLS 1.2 hello from OVS client to NOX controller

Hi All, I have OVS (1.11.0) and the OpenSSL (1.0.1e-fips) installed on a VM. I checked the OpenSSL release notes and it says that the version I am using supports TLS 1.2. My NOX controller is running in passive TLS mode. Problem is, when my OVS initiates a SSL connection to the controller, it u

Re: [ovs-discuss] What if run vSwitches in guest OS's user mode, and give users more control?

On 6/12/14, 3:12 AM, Shen Li wrote: I worked on OS software, and know little about networking virtualization. I have a question. Assuming the following technologies come true, then we can let users install their own choice of vswitches(or such kind of "devices") in their own VM, without risk to

Re: [ovs-discuss] OpenFlow enabled OpenWRT for TP Link 1043 ND

On Thu, Jun 12, 2014 at 01:06:38AM +0500, Sayed Qaiser Ali Shah wrote: > Hope all of you are doing well. I am working on TP Link 1043 ND v2.1 > router. I want to make it openflow enable. I found the link of openwrt for > v2.x on the link given below but as openflow is not enabled by default. Can >

Re: [ovs-discuss] Adding a new option types in the interface table

On Thu, Jun 12, 2014 at 7:38 AM, Arthur BONI wrote: > Hi, > > I want to add a support for GTP tunneling in openvswitch. > So, I'd like to add in ovsdb some tunnel options only available for this > protocol (like > options:csum for GRE and IPSEC-GRE tunnels). > > I have some basic ideas about how t

[ovs-discuss] OpenVswitch GRE to physical interface

Hello, i have to test OpenVswitch on lab to study openvswitch GRE I have 2 openvswitch server on 2 Fedora 18 this is the configuration of the first one 52c4e81c-4d75-4118-81c0-e0d0055202ad Bridge virtualSwitch Port "tep01" Interface "tep01" type: inte

[ovs-discuss] Adding a new option types in the interface table

Hi, I want to add a support for GTP tunneling in openvswitch. So, I'd like to add in ovsdb some tunnel options only available for this protocol (like options:csum for GRE and IPSEC-GRE tunnels). I have some basic ideas about how to do it; using ovs-vsctl for example. Can someone tell me what i

Re: [ovs-discuss] OpenVswitch GRE to physical interface

Tarek, As a rule of thumb, you do not want the IP address on any interface on the Port lines, you want it on a Bridge. I'm doing the same thing you are, my names are different and I'm using vxlan, but it's similar. You want no ips on any interfaces from your example, except for br-int2 and virt

[ovs-discuss] OpenVswitch GRE to physical interface

Hello, I have to test OpenVswitch on lab to study openvswitch GRE I have 2 openvswitch server on 2 Fedora 18 this is the configuration of the first one 52c4e81c-4d75-4118-81c0-e0d0055202ad Bridge virtualSwitch Port "tep01" Interface "tep01" type: in

[ovs-discuss] What if run vSwitches in guest OS's user mode, and give users more control?

Hi, I worked on OS software, and know little about networking virtualization. I have a question. Assuming the following technologies come true, then we can let users install their own choice of vswitches(or such kind of "devices") in their own VM, without risk to influence CSP's hypervisor soft