Precedence: list
MIME-Version: 1.0
In-Reply-To: <1325182586-2051-1-git-send-email-roger.pau@entel.upc.edu>
References: <1325182586-2051-1-git-send-email-roger.pau@entel.upc.edu>
Date: Thu, 29 Dec 2011 19:28:14 +0100
Message-ID: <CAFivhPmcQVuR5pL2VzJCwdn9zvd4tkcNawyZGFS+yUDva=L+Ew@mail.gmail.com>
Subject: Re: [alpine-devel] [PATCH] alpine-conf: modify setup-interfaces to
 create simple bridges
From: Florian Heigl <florian.heigl@gmail.com>
To: Roger Pau Monne <roger.pau@entel.upc.edu>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

2011/12/29 Roger Pau Monne <roger.pau@entel.upc.edu>:
> Modified setup-interfaces to create simple bridges (works only with
> one interface per bridge). Useful when setting up a Xen system, since
> interfaces need to be bridged in order for guests to have networking.
> Some distributions automatically create one bridge for each interface
> when Xen is installed, but I think this is too aggressive.

Yup, I think that is deprecated by xen devs too. The XL stack tries to
avoid messing with the OS networking setup. It used to be a PITA if
you have many bridges.

Does anyone have OpenVswitch on Alpine yet?
Because in practice I'll often have lacp+vlans and then quite a few
bridges per Vlan, things being made worse by issues with the bridges
(low general performance and lacp load balancing)

Greetings,
Florian


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---