X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from ncopa-laptop.res.nor.wtbts.net (3.203.202.84.customer.cdi.no [84.202.203.3]) (using SSLv3 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 CC254DC037B; Sun, 4 Nov 2012 15:28:59 +0000 (UTC) Date: Sun, 4 Nov 2012 16:28:56 +0100 From: Natanael Copa To: Der Tiger Cc: "alpine-devel@lists.alpinelinux.org" Subject: Re: [alpine-devel] [Alpine 2.4] Network Interface Hotplugging Detection Message-ID: <20121104162856.37e4e31a@ncopa-laptop.res.nor.wtbts.net> In-Reply-To: <5094F760.4080604@arcor.de> References: <5094F6FB.3050709@arcor.de> <5094F760.4080604@arcor.de> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; 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 On Sat, 03 Nov 2012 11:52:16 +0100 Der Tiger wrote: > While dhcpcd accepts multiple static ip_address statements, only the > last statement prevails nullifying all previous statements. > Therefore, I see no way to use dhcpcd to assign more than one ip > address to a single interface. ... > The IPv6 implementation of dhcpcd allows only a single IPv6 address > per interface. Furthermore, it is a highly unstructured (and therefore > unrecommended) way to assign the IPv4 address to an interface using a > static statement in /etc/dhcpcd.conf and retriving an IPv6 address for > the same interface through IPv6 RS/RA as part of the configuration of > a DHCP server. Thanks for clarifying. Also, I'd also guess that when using static ip is a case when you don't want the ip address removed when cable is unplugged. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---