On Thu, Sep 09, 2010 at 11:29:06AM +0530, Vishal Swarankar wrote: > I am using ovs-controller as a replacement of basic NOX.
This is probably a mistake. > I want to know the capabilities of ovs-controller as a NOX. Hardly any at all. > I have setup a flow rule > as*"in_port=2,nw_proto=1,idle_timeout=0,actions=output:controller" > *, where port =2 is attached to one of my VM. This flows says I want to > forward every packet to my controller. Now when I ping from a distant > machine(.60) from my VM(.80), controller shows the log that these ping > packets are coming to it. > > Sep 09 11:14:32|00258|vconn|DBG|tcp:172.16.10.62:53860: received: packet_in > (xid=0x0): total_len=98 in_port=2 (via action) data_len=98 (unbuffered) > icmp,in_port=2,dl_vlan=65535,dl_vlan_pcp=0,dl_src=52:54:00:21:75:18,dl_dst=00:26:82:85:44:ef,nw_src=172.16.10.80,nw_dst=172.16.10.60,icmp_type=8,icmp_code=0, > Sep 09 11:14:33|00259|poll_loop|DBG|[POLLIN] on fd 10: > Sep 09 11:14:33|00260|vconn|DBG|tcp:172.16.10.62:53860: received: packet_in > (xid=0x0): total_len=98 in_port=2 (via action) data_len=98 (unbuffered) > icmp,in_port=2,dl_vlan=65535,dl_vlan_pcp=0,dl_src=52:54:00:21:75:18,dl_dst=00:26:82:85:44:ef,nw_src=172.16.10.80,nw_dst=172.16.10.60,icmp_type=8,icmp_code=0, > Sep 09 11:14:33|00261|poll_loop|DBG|[POLLIN] on fd 8: > > Now I want that this controller should forward these packet to some other > machine X. > > Is there any way supported in current ovs-controller to setup this kind of > behaviour? ovs-controller doesn't have a way to do that. (But why doesn't your flow just do that directly, instead of forwarding it to the controller?) > Curretnly ovs-controller does not do anything with this packet ( I tried > tcpdump on the eth0/br0). That's right, ovs-controller ignores packets sent to the controller by actions. > In my setup, I have vswitch and ovs-controller running on the same machine > and I have only one NIC and both are binded to the same IP. > > If I setup my ovs-controller on a different machine then will it pass these > packets to the underlying switch which will take the action on the MAC > learning basis ?? ovs-controller does MAC learning, but ovs-vswitchd can also do MAC learning without a controller, so there is not much benefit in ovs-controller. ovs-controller is just a simple controller, mostly for developer testing of OVS itself. It's not going to be very useful in production. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
