Re: [ovs-discuss] need brcompat module in Fedora 17 or kernle 3.4

I haven't change anything in code I tried compile with master & branch 1.7. No luck :( gave following error : /opt/src/openvswitch/datapath/linux/datapath.c:65:2: error: #error Kernels before 2.6.18 or after 3.3 are not supported by this version of Open vSwitch. On Tue, Jun 12, 2012 at 11:59 AM,

Re: [ovs-discuss] need brcompat module in Fedora 17 or kernle 3.4

On Jun 12, 2012, at 2:25 PM, Avdhoot Dendge - BetterLabs wrote: > Is there any way to add bridge (brcompat not a bridge) compatibility in > (Linux BL-63 3.4.0-1.fc17.x86_64) kernel. > > Even tried compile openvswitch it give me following error OVS 1.5 doesn't support Linux 3.4 and should in

Re: [ovs-discuss] Problem with tap device on Virtualbox

On Jun 11, 2012, at 4:30 PM, Abhishek Chanda wrote: > I am trying to setup a topology similar to the one explained here: > http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/ > The only difference being, for me, all VMs are in one VLAN. Once I have > booted the VMs, I do

Re: [ovs-discuss] need brcompat module in Fedora 17 or kernle 3.4

Is there any way to add bridge (brcompat not a bridge) compatibility in (Linux BL-63 3.4.0-1.fc17.x86_64) kernel. Even tried compile openvswitch it give me following error [root@BL-63 openvswitch-1.5.0]# make make all-recursive make[1]: Entering directory `/opt/src/openvswitch-1.5.0' Making all

Re: [ovs-discuss] need brcompat module in Fedora 17 or kernle 3.4

On Jun 12, 2012, at 12:55 AM, Avdhoot Dendge - BetterLabs wrote: > I am happy user of openvswitch with brcompat in rhel 6.x > > now in fedora 17 i am not able load brcompat module. Is there any way so i > can compile brcompat for fedora17 or kernle 3.4. > > [root@BL-63 openvswitch-1.5.0]# ovs

[ovs-discuss] Problem with tap device on Virtualbox

Hi, I am trying to setup a topology similar to the one explained here: http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/ The only difference being, for me, all VMs are in one VLAN. Once I have booted the VMs, I do not see the TAP devices. So, do I have to create a TAP de

Re: [ovs-discuss] OpenVSwitch - No error is received for operation on non-exists queue (OFPQOFC_BAD_QUEUE ) or non-exists port (OFPQOFC_BAD_PORT )

On Fri, Jun 01, 2012 at 05:42:11AM +, Prabina Pattnaik wrote: > 1. When taking queue-stats for non-existing port following error should > generate from switch > > ovs-ofctl queue-stats tcp::6633 25 1 > OFPQOFC_BAD_PORT (port does not exists) with OFPET_QUEUE_OP_FAILED error > code. Fa

Re: [ovs-discuss] No buffer space available warning

On Mon, Jun 11, 2012 at 06:14:17PM +0500, Junaid Khalid wrote: > With the following are the platform specifications: > > OVS version: 1.4.0 > traffic type: MTU size UDP packets @7000packets per second, generating > 50,000 flows by changing UDP src Ports. > OS: Fedora release 12, Linux

[ovs-discuss] need brcompat module in Fedora 17 or kernle 3.4

I am happy user of openvswitch with brcompat in rhel 6.x now in fedora 17 i am not able load brcompat module. Is there any way so i can compile brcompat for fedora17 or kernle 3.4. [root@BL-63 openvswitch-1.5.0]# ovs-brcompatd --pidfile --detach ovs-brcompatd: could not open brcompat socket. Che

[ovs-discuss] No buffer space available warning

Hi, With the following are the platform specifications: OVS version: 1.4.0 traffic type: MTU size UDP packets @7000packets per second, generating 50,000 flows by changing UDP src Ports. OS: Fedora release 12, Linux 2.6.31.5-127.fc12.i686.PAE CPU: Intel Core i3 @ 2100 GHz Contr