Re: [ovs-discuss] Unable to make Netflow v5 working

2014-08-06 Thread Duy Bach Ha
Dear Ben, I will have an eye on this matter. It's sorry to say that it has taken me a lot of time and I have to move on with a very late schedule. I will contact you again if I can reproduce the crashwhen I tackle back the problem later these 4 months. Just as a last note for me: If you can

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-08-01 Thread Ben Pfaff
On Fri, Aug 01, 2014 at 09:46:58AM +0200, Duy Bach Ha wrote: > I'm sorry for now I have so many kernel versions and 3 gcc that I > cannot remember at what version and gcc didI have it. But I will try > to reproduce the crash. How can I have a backtraceso that I can > provide it for you? Usually yo

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-08-01 Thread Duy Bach Ha
Dear Nick, With your explanation, I tryboth commands, and I get the same result when I use "sh ovs-vsctl list NetFlow". The targets is just the same, ["192.168.1.2:5556"]. With "list Bridge", I can see that the switch s1 was netflow enabled with both commands. mininet> sh ovs-vsctl list NetF

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-08-01 Thread Nicholas Bastin
On Sun, Jul 27, 2014 at 4:01 AM, Duy Bach Ha wrote: > *sh ovs-vsctl -- set Bridge s1 netflow=@nf -- --id=@nf create NetFlow > targets=\"192.168.1.2:5566 \" active-timeout=10* > Assuming your 'sh' is a POSIX 1003.2-compliant shell, you need to escape the colon in the targ

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-08-01 Thread Duy Bach Ha
Dear Ben, I'm sorry for now I have so many kernel versions and 3 gcc that I cannot remember at what version and gcc didI have it. But I will try to reproduce the crash. How can I have a backtraceso that I can provide it for you? Actually on kernel 3.11.0 or 3.11.10 and some other, and on ubu

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-07-31 Thread Ben Pfaff
On Tue, Jul 29, 2014 at 05:10:49PM +0200, Duy Bach Ha wrote: > Just to sum up and ask for help since I'm doing a thesis and have > stuck here for a long time. You guys don't have to follow the other > 2 emails because I sum all here. Sincerely thanks for your support. > > Experimental mininet 2.1.

Re: [ovs-discuss] Unable to make Netflow v5 working

2014-07-29 Thread Duy Bach Ha
Hello, Just to sum up and ask for help since I'm doing a thesis and have stuck here for a long time. You guys don't have to follow the other 2 emails because I sum all here. Sincerely thanks for your support. Experimental mininet 2.1.0 network of 6 ovs switches 2.1.2 and some hosts (with ip

[ovs-discuss] Unable to make Netflow v5 working

2014-07-27 Thread Duy Bach Ha
Hello, An update on the matter, I discovered that the cause of my crashing is not from connecting to the controller, but because of this command: /sh ovs-vsctl -- set Bridge s1 netflow=@nf -- --id=@nf create NetFlow targets=\"192.168.1.2:5566\" active-timeout=10/ I'm on ovs 2.1.2, linux ker

[ovs-discuss] Unable to make Netflow v5 working

2014-07-26 Thread Duy Bach Ha
Hi all, I'm running an experimental mininet network of 6 ovs switches and some hosts (with ip in 192.168.1.0/24) and try to deploy Netflow on the switches. The controller I'm using is opendaylight. So for example: /sudo mn --switch ovsk --controller remote --custom /smile/ncstestmap.py --top