OVS creates its own GRE tunnel so there is no need to have a pre-existing adapter or create an additional adapter as far as I know. I only suggested you use tunctl because I thought you would need to TAP a bridge like I do here:
https://drive.google.com/a/fiu.edu/?tab=mo#my-drive On Fri, Jul 26, 2013 at 2:23 PM, Cali Ente <calientepermane...@gmail.com>wrote: > Created tunnels using tunctl, but getting back to the original question > posted, when I asked about using GRE with tunnels, it was stated that OVS > creates it's own GRE tunnel to communicate, and does not use preexisting > tunnels, it seems like now you are contradicting this, so just so I'm sure, > what is the correct answer? > > Thanks, > Cal > > > On Fri, Jul 26, 2013 at 11:19 AM, Dmita Levy <dlevy...@fiu.edu> wrote: > >> How did you create the pre-existing tunnel? I would like to duplicate the >> issue you're having here on my test hosts. >> >> >> On Fri, Jul 26, 2013 at 2:16 PM, Cali Ente >> <calientepermane...@gmail.com>wrote: >> >>> tun0 is a preexisting tunnel, so what I'm trying to do is get OVS to >>> communicate with this preexisting tunnel. >>> >>> >>> On Fri, Jul 26, 2013 at 11:14 AM, Dmita Levy <dlevy...@fiu.edu> wrote: >>> >>>> I'm still a little confused as to what it is you're trying to >>>> accomplish; if you create a GRE port like this >>>> >>>> # ovs-vsctl add-port br0 tun0 -- set interface tun0 type=gre >>>> options:remote_ip=192.168.1.10 >>>> >>>> >>>> the tunnel should work with no problems. From what you're saying, it >>>> seems like you're creating a tunnel and trying to add an additional tunnel >>>> adapter? What does your topology look like? >>>> >>>> On Fri, Jul 26, 2013 at 2:05 PM, Cali Ente < >>>> calientepermane...@gmail.com> wrote: >>>> >>>>> Are you referring to something like this? >>>>> ifconfig >>>>> tun0 Link encap:UNSPEC HWaddr >>>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >>>>> UP BROADCAST POINTOPOINT RUNNING NOARP MULTICAST MTU:1424 >>>>> Metric:1 >>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 txqueuelen:10 >>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>>> ... >>>>> ... >>>>> ovs-vsctl add-br bro >>>>> >>>>> This creates a gre port named tun0 on the bridge device bro but it >>>>> does not seem to be associated with the actual tun0 net device in anyway >>>>> >>>>> >>>>> >>>>> On Fri, Jul 26, 2013 at 10:42 AM, Dmita Levy <dlevy...@fiu.edu> wrote: >>>>> >>>>>> Hello Cali, >>>>>> >>>>>> Have you tried using tunctl to create the tunnel adapter and then >>>>>> adding that adapter to the bridge the gre port is assigned to? That being >>>>>> said, what are you using the tun adapter for - is it tun/tap to tap VM's >>>>>> into the bridge? >>>>>> >>>>>> On Fri, Jul 26, 2013 at 1:33 PM, Cali Ente < >>>>>> calientepermane...@gmail.com> wrote: >>>>>> >>>>>>> As I thought, in that case, does anyone know of a way to connect a >>>>>>> linux tun device to OVS? >>>>>>> >>>>>>> >>>>>>> On Fri, Jul 26, 2013 at 9:19 AM, Jesse Gross <je...@nicira.com>wrote: >>>>>>> >>>>>>>> On Fri, Jul 26, 2013 at 8:54 AM, Cali Ente < >>>>>>>> calientepermane...@gmail.com> wrote: >>>>>>>> > Hey all quick question, when creating a tunnel port in OVS using >>>>>>>> the set >>>>>>>> > interface=gre does this connect to a preexisting tun or does OVS >>>>>>>> make it's >>>>>>>> > own? For example I have a tun0 device that I want to attach to my >>>>>>>> OVS port, >>>>>>>> > and it cannot be added (incompatible device), so I thought that I >>>>>>>> merely >>>>>>>> > needed to add it with the GRE option. >>>>>>>> >>>>>>>> OVS GRE does not use or require an existing device. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> discuss mailing list >>>>>>> discuss@openvswitch.org >>>>>>> http://openvswitch.org/mailman/listinfo/discuss >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
