X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from ncopa-desktop.nor.wtbts.net (3.203.202.84.customer.cdi.no [84.202.203.3])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: nc@alpinelinux.org)
	by mail.alpinelinux.org (Postfix) with ESMTPSA id ED28ADC19B6;
	Mon, 12 Mar 2012 07:29:21 +0000 (UTC)
Date: Mon, 12 Mar 2012 08:29:19 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Nathan Angelacos <nangel@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Configuring bridges
Message-ID: <20120312082919.094415d6@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <4F5D5A17.2010505@alpinelinux.org>
References: <20120309225041.43308a57@alpinelinux.org>
	<4F5D5A17.2010505@alpinelinux.org>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; x86_64-unknown-linux-gnu)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sun, 11 Mar 2012 19:06:15 -0700
Nathan Angelacos <nangel@alpinelinux.org> wrote:

> 
> > I was thinking shipping this script and vlan and bonding scripts
> > with alpine-baselayout. However, those will consume a few kb and
> > generate a few extra forks every boot up - even if they are unused
> > - so I think it might make sense to ship them separately.
> >
> 
> <phb>
> 
> I'm in favor of a separate package; Alpine's great because it its 
> opt-in, vs opt-out.  When I need bonding and vlans and bridges I need 
> them.  But the other 90% of the time its nice to have a lean fast
> system.
> 
> Oh the other hand, what do you name the package so that someone like
> me remembers to load it when needed?

for bonding: apk add bonding
for bridge interfaces: apk add bridge
for vlans: apk add vlan

If you forget: apk search bridge bond vlan

Btw, I intend to add support for those in setup-interfaces.

Something like:

Available interfaces are: eth0 eth1.
Which one do you want to initialize? (or 'done') [eth0] bond0
Available slaves are: eth0 eth1.
Which slave(s) do you want to add to bond0? (or 'all') [all] all
Ip address for bond0? (or 'dhcp') [dhcp] none
Available interfaces are: bond0.
Which one do you want to initialize? (or 'done') [bond0] bond0.64
Ip adress for bond0.64 (or 'dhcp') [dhcp] 192.168.0.2/24
...


Or for bridges:
Available interfaces are: eth0 eth1.
Which one do you want to initialize? (or 'done') [eth0] br0
Available bridge ports are: eth0 eth1.
Which port(s) do you want to add to br0? (or 'all') [all] eth0 eth1
...

The idea is that if you enter bond[0-9]+ or br[0-9]+ or $IFACE.[0-9]+
it will create a bond, bridge or vlan interface.

The question:
Available interfaces are: eth0 eth1.
Which one do you want to initialize? (or 'done') [eth0]

Should probably give some hint about it. Ideas how?

I am thinking maybe:
Which one do you want to initialize? (or '?' for help) 



-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---