[ovs-discuss] Best practices : openvswitch & tun interface (from openvpn)
Benoît
benoitne at gmail.com
Thu Dec 3 22:51:47 UTC 2015
Thanks Justin
I was probably not clear enough.
I try to find a way to connect a tun interface (from openvpn) to OVS
bridge mostly to use port mirroring capabilities.
Adding tun interface directly will not work but I would like to know if
there is any way (patch / via tap or another way) to send the traffic
from tun interface to an OVS bridge.
My idea is to use this interface on OVS as a source port of a mirroring.
The challenge is how to send all the traffic from a tun interface to
another fake / tap / parch interface on OVS?
Many thanks for any tips or idea-workaround
belette
On 03/12/15 22:43, Justin Pettit wrote:
>> On Nov 30, 2015, at 12:34 PM, Benoît <benoitne at gmail.com> wrote:
>>
>> Hi,
>>
>> I already searched and find some discussion about openvswitch and openvpn.
>> In fact I would like to add a tun port to openvswitch to be able to manage it like my other port in my ovs switch.
>>
>> Is there best practices to follow to do it? I know layer 3 on ovs is not a good idea and I am unable to make it work.
>> Is there a proper way to do it? Through patch or other bridged solutions?
> I'm not sure I understand the question. OVS is an L2 bridge. You can write policies based on L3 addresses or use a controller to implement routing, but it doesn't have that functionality "out of the box".
>
> --Justin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151203/e8bac3b0/attachment-0002.html>
More information about the discuss
mailing list