[ovs-discuss] Forwarding to controller's packet to another node!

Jesse Gross jesse at nicira.com
Wed Jul 24 16:29:22 UTC 2013


On Wed, Jul 24, 2013 at 2:20 AM, Muhammad Asad
<muhammad.asad at aisec.fraunhofer.de> wrote:
> On 07/23/2013 10:54 PM, Jesse Gross wrote:
>>
>> On Tue, Jul 23, 2013 at 5:16 AM, Muhammad Asad
>> <muhammad.asad at aisec.fraunhofer.de> wrote:
>>>
>>> Hello,
>>>
>>> I want to establish a network with 2 VMs connected to a bridge br0 and
>>> another VM connected to a different bridge br1. The nodes connected to
>>> br0
>>> communicate with each other and send packets to controller for installing
>>> flows. I want the packets coming to the controller to be forwarded to the
>>> node connected to br1.
>>>
>>> 1. If I do it in OVS and create a port mirroring, it will send all
>>> packets
>>> coming on a port to the other port. How can I mirror only those packets
>>> which are sent to the tunnel?
>>
>> You can use flows to direct packets to a tunnel port.
>>
>>> 2. How can I do it through tunneling? I tried to go through tunnelling
>>> example in ovs-vsctl but couldn't extract much.
>>
>> There are a number of tutorials available for creating GRE ports in
>> particular.
>
> Hi,
>
> The thing is that I have two VMs on br0 and another VM on br1. Whenever the
> first packet is sent from VM1 of br0 to VM2 of br0, the packet is sent to
> controller by OVS for installing the flow. Whichever packet goes to the
> controller from OVS should also go to the VM on br1. How can I use this by
> what you have said as use flows to direct packets to a tunnel port? I don't
> have any flows installed yet and I only want to send those packets to VM on
> br1 which comes from OVS to the controller.
>
> Alternatively, is there some way to code in OVS to check if a packet is
> being sent to the controller and if yes, then send this packet out to the VM
> or br1 as well?

Rather than allowing the packet to simply miss the flow table, you
could have a low priority flow that both sends it to the controller
and the GRE port.
X-CudaMail-Whitelist-To: discuss at openvswitch.org



More information about the discuss mailing list