Re: [ovs-discuss] can not create device problem
Hi, I found another problem about the tunnel, its about the gre-dev's mtu in OVS. Thanks a lot for your suggestions and GRE of OVS works fine , but when I tried to use it on a special path, it stopped working The special path is actually a physical tunnel network path so when I again use OVS's GRE over it, I think maybe the MTU is too big for OVS GRE port do deal with it properly.When I forwarded the packet to the GRE port in OVS, it couldn't get out from the destination side.(Between the two sides the physical path is a tunnel network already). I always appreciate for all your help and best regards yan On Thu, Jul 1, 2010 at 1:35 AM, Yan yan.p.b...@gmail.com wrote: Hi Ben Thanks a lot. Problem has been solved I used dp0 as it's name and of course I replaced the command with the name when I issued the command But just as you said it's because of the 16 bits hex, I made a mistake that I took it as 12 bits hex Thanks again Yan On 2010/06/30, at 2:01, Ben Pfaff b...@nicira.com wrote: On Tue, Jun 29, 2010 at 03:43:12PM +0900, Yan wrote: I tried ovs-vsctl set bridge br0 other-config:datapath-id=0123456789abcdef however, ovs doesn't really use this as its real dpid when I connect to NOX. Would you please give more suggestions for this? I just tested this, and it works fine for me. Did you replace br0 by the name of your bridge? Did you specify exactly 16 hex digits for 0123456789abcdef? ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
Re: [ovs-discuss] can not create device problem
Hi Ben Thanks a lot. Problem has been solved I used dp0 as it's name and of course I replaced the command with the name when I issued the command But just as you said it's because of the 16 bits hex, I made a mistake that I took it as 12 bits hex Thanks again Yan On 2010/06/30, at 2:01, Ben Pfaff b...@nicira.com wrote: On Tue, Jun 29, 2010 at 03:43:12PM +0900, Yan wrote: I tried ovs-vsctl set bridge br0 other-config:datapath-id=0123456789abcdef however, ovs doesn't really use this as its real dpid when I connect to NOX. Would you please give more suggestions for this? I just tested this, and it works fine for me. Did you replace br0 by the name of your bridge? Did you specify exactly 16 hex digits for 0123456789abcdef? ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
Re: [ovs-discuss] can not create device problem
Hi Jesse, I always appreciate your help. Sure I'm using kernel module, but since I let vswitchd start automatically and put it back ground, I'll change this and log its action. After that I'll send you mail again. Thanks again and best wishes. On Tue, Jun 22, 2010 at 6:48 AM, Jesse Gross je...@nicira.com wrote: On Sat, Jun 19, 2010 at 6:27 PM, Yan yan.p.b...@gmail.com wrote: Hi Jesse Thank you for your reply and I'll take care to add cc. Sorry for last time. I saw the information from the *Create a GRE interface* thread, so I did like following: ovs-vsctl create interface name=gre0 type=gre options:remote_ip=remote machine's IP 99c94566-ea4f-41d9-9f40-d2e9c9a6d386 ovs-vsctl create port name=gre0 interfaces=[99c94566-ea4f-41d9-9f40-d2e9c9a6d386] f75aa483-e0ea-42e8-bb96-93110d630838 ovs-vsctl add bridge dp0 ports f75aa483-e0ea-42e8-bb96-93110d630838 And I also did the same thing at another machine.I got no error message but NOX didn't get a port event when I add gre into bridge(by ovs-vsctl add bridge dp0 ports f75aa483-e0ea-42e8-bb96-93110d630838). I also tried ovs-vsctl add-port dp0 gre0 but it didn't inform nox either. It seems OVS doesn't send a event to NOX. In this case NOX will not tell the OVS to forward a flow via that tunnel even if the tunnel is correct. Would please offer some suggestions about how could this be solved? OVS treats GRE ports just like normal Ethernet ports when it comes to OpenFlow handling so if NOX isn't being notified it means that the port is not being created correctly. Your commands look correct, so can you post the contents of your ovs-vswitchd log file? Also, you're not using the userspace datapath are you? GRE is only implemented in the openvswitch_mod.ko kernel module. -- Yan Pu y...@nakao-lab.org +81-80-4164-9937 NAKAO LAB The university of Tokyo Graduate School of Interdisciplinary Information Studies ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
Re: [ovs-discuss] can not create device problem
(moving back on list) On Tue, Jun 1, 2010 at 6:46 PM, Yan yan.p.b...@gmail.com wrote: Thanks a lot for your reply. If I use ovs-vswitchd, it performs as common bridge right? I wanted to try the openflow things and since I saw ovs can be used as virtual openflow switch.. ovs-vswitchd can do everything that ovs-openflowd does and more - including OpenFlow. ovs-openflowd exists simply for backwards compatibility with the OpenFlow consortium's reference implementation. ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
Re: [ovs-discuss] can not create device problem
On Tue, Jun 1, 2010 at 7:44 PM, yan.p.b...@gmail.com wrote: Really nice to know that Are documents on the website old? No, they should be up to date. If you look at the man page for ovs-vsctl you'll see how to configure ovs-vswitchd to use an OpenFlow controller. ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
