X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from localhost (180.224.189.109.customer.cdi.no [109.189.224.180]) (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 6536EDC15BD for ; Fri, 9 Mar 2012 21:50:37 +0000 (UTC) Date: Fri, 9 Mar 2012 22:50:41 +0100 From: Natanael Copa To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] Configuring bridges Message-ID: <20120309225041.43308a57@alpinelinux.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; i686-pc-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I created a package called "bridge" which has the if-pre-up.d script for creating bridges. I rewrote it from scratch because the debian version was a bit ugly. This version should support most of the options in debian. Some might require that you install brctl from bridge-utils. Example bridge config in /etc/network/interfaces: iface br0 inet static address 192.168.0.1 netmask 255.255.255.0 bridge-ports eth0 tap0 bridge-stp off The package is in edge/testing. 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. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---