Hi Justin, Thank you very much for your help! I had similar configuration on my setup. I wanted to add a flow to ovs to forward to the gre0 when traffic is going to other host. ovs-ofctl has such command to add flow, with set_tunnel option to set the action. However, the option takes an 32-bits ID, and I am not sure what ID I should use? "gre0"?
Thanks! Yimin On Fri, May 25, 2012 at 3:03 PM, Justin Pettit <[email protected]> wrote: > On May 24, 2012, at 8:43 PM, Ethan Jackson wrote: > >>> Sorry I have so many questions. I couldn't find a detailed >>> documentation on how this tunneling feature works and still unclear >>> about the concept. If any of you have worked on tunneling, could you >>> please kindly shed lights on this? Thank you so much! >> >> Configuration of tunnels is documented thoroughly in the >> ovs-vswitchd.conf.db man page. They are pretty straight forward, when >> traffic is output to a tunnel, it is encaped, and then forwarded to >> the remote_ip configured in the database. > > There's also an example of actually creating the port in the ovs-vsctl man > page: > > Add a GRE tunnel port gre0 to remote IP address 1.2.3.4 to bridge br0: > > ovs-vsctl add-port br0 gre0 -- set Interface gre0 type=gre > options:remote_ip=1.2.3.4 > > --Justin > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
