[ovs-discuss] how to avoid loops

[Jesse Gross]

OVS bonding tends to be the best integrated.

On Thu, Aug 1, 2013 at 10:06 AM, Vasiliy Tolstov <v.tolstov at selfip.ru> wrote:
> Thanks for answer. What is best bond for my case - linux bonding or
> ovs bonding ?
>
> 2013/8/1 Jesse Gross <jesse at nicira.com>:
>> On Thu, Aug 1, 2013 at 3:45 AM, Vasiliy Tolstov <v.tolstov at selfip.ru> wrote:
>>> Hello again.
>>> I'm successeful using mptcp with openvswitch bridges (i'm create for
>>> eatch eth device own bridge device and connect it to main bridge with
>>> patch ports). But have strange loops
>>> My config for ovs is :
>>>
>>>     Bridge "ext0"
>>>         Port "ext0"
>>>             Interface "ext0"
>>>                 type: internal
>>>         Port "eth0"
>>>             Interface "eth0"
>>>         Port "ext0-data"
>>>             Interface "ext0-data"
>>>                 type: patch
>>>                 options: {peer="data-ext0"}
>>>     Bridge ovs
>>>         Port data
>>>             Interface data
>>>                 type: internal
>>>         Port ovs
>>>             Interface ovs
>>>                 type: internal
>>>         Port "data-ext1"
>>>             Interface "data-ext1"
>>>                 type: patch
>>>                 options: {peer="ext1-data"}
>>>         Port "data-ext0"
>>>             Interface "data-ext0"
>>>                 type: patch
>>>                 options: {peer="ext0-data"}
>>>     Bridge "ext1"
>>>         Port "eth1"
>>>             Interface "eth1"
>>>         Port "ext1-data"
>>>             Interface "ext1-data"
>>>                 type: patch
>>>         Port "ext1"
>>>             Interface "ext1"
>>>                 type: internal
>>>
>>>
>>> this means that
>>> eth0 connected to ext0 ovs device and have address 172.16.1.1
>>> eth1 connected to ext1 ovs device and have address 172.16.2.1
>>>
>>> ext0 and ext1 connected with ovs bridge that have ip from another
>>> network (external)
>>>
>>> All works but that i have another server with this config (another
>>> server that forwarding packets to external net) i have loops.
>>> Another server have ip 172.16.1.2 and 172.16.1.2.
>>>
>>> Earch server connects with
>>> srv1 eth0 to sw1p1 and eth1 to sw2p1
>>> srv2 eth0 to sw1p2 and eth1 to sw2p2
>>
>> This effectively amounts to a bond, so I think you would have better
>> luck configuring it that way directly.
>
>
>
> --
> Vasiliy Tolstov,
> e-mail: v.tolstov at selfip.ru
> jabber: vase at selfip.ru
X-CudaMail-Whitelist-To: discuss at openvswitch.org