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
