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
