Re: [ovs-discuss] Help in understanding the code

2013-07-14 Thread Andy Zhou
On Sat, Jul 13, 2013 at 11:14 PM, sujith p s wrote: > Really sorry to bother you guys once again. ( I guess this won't be the > last time :P ) > I'm taking small steps into the code. Especially the kernel part. > > Consider the topology:$sudo mn --topo linear --switch=ovsk > > h1 -- s1 -- s2 -- h2

Re: [ovs-discuss] Help in understanding the code

2013-07-13 Thread sujith p s
Really sorry to bother you guys once again. ( I guess this won't be the last time :P ) I'm taking small steps into the code. Especially the kernel part. Consider the topology:$sudo mn --topo linear --switch=ovsk h1 -- s1 -- s2 -- h2 h1 is connected to s1-eth1. h2 is connected to s2-eth1. $ovs-dp

Re: [ovs-discuss] Help in understanding the code

2013-07-11 Thread sujith p s
Yes! That made it work as expected. Thanks! Found out that this command was mentioned in the older version of document in Internet (INSTALL.Linux). Running $sudo insmod datapath/linux/openvswitch.ko showed 'Unknown symbol in the module" error at first. Searching the archive of this mailing list ga

Re: [ovs-discuss] Help in understanding the code

2013-07-11 Thread Justin Pettit
Are you sure modprobe picked up your new kernel module? You may want to try running insmod with the path to your new ".ko". --Justin On Jul 11, 2013, at 12:56 AM, sujith p s wrote: > Need a hand here..Please.. > > Installed OpenvSwitch at first.Worked as expected. > Later made a few, small

Re: [ovs-discuss] Help in understanding the code

2013-07-11 Thread sujith p s
Need a hand here..Please.. Installed OpenvSwitch at first.Worked as expected. Later made a few, small changes (basically, inserting printk statements) in the ovs_dp_process_received_packet() of datapath.c in datapath directory. I compile using following commands: sudo kill `cd /usr/local/var/run/

Re: [ovs-discuss] Help in understanding the code

2013-07-10 Thread Andy Zhou
The remaining icmp packets are indeed processed in the kernel (via ovs_dp_process_received_packet()). ovs-vswitchd will install a flow entry in the kernel to handle those packets. You can inspect kernel flows with "ovs-dpctl dump-flows". VLOG_INFO is only for user space programs. I am surprised it

[ovs-discuss] Help in understanding the code

2013-07-10 Thread sujith p s
Hi everyone! I'm a newcomer to OpenvSwitch. I installed it in mininet-VM using the INSTALL guide provided. I am curious to understand the flow of the code in case of ping. Example topology: $ sudo mn --switch=ovsk --topo linear h1 -- s1 -- s2 -- h2 command: mininet> h1 ping -c5 h2 ofproto_run