X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-in-14.arcor-online.net (mail-in-14.arcor-online.net [151.189.21.54]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id E2A49DC037D for ; Sat, 3 Nov 2012 10:52:18 +0000 (UTC) Received: from mail-in-12-z2.arcor-online.net (mail-in-12-z2.arcor-online.net [151.189.8.29]) by mx.arcor.de (Postfix) with ESMTP id 3754D9C607 for ; Sat, 3 Nov 2012 11:52:17 +0100 (CET) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mail-in-12-z2.arcor-online.net (Postfix) with ESMTP id 343E62E600A for ; Sat, 3 Nov 2012 11:52:17 +0100 (CET) Received: from [192.168.16.209] (85-127-78-147.dynamic.xdsl-line.inode.at [85.127.78.147]) (Authenticated sender: panthera.tigris@arcor.de) by mail-in-09.arcor-online.net (Postfix) with ESMTPA id C6AEB197C49 for ; Sat, 3 Nov 2012 11:52:16 +0100 (CET) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-09.arcor-online.net C6AEB197C49 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arcor.de; s=mail-in; t=1351939937; bh=X7vMoyH5LpFC/PHeu/VUzFQ4v3dWlQ6xWq/Xmz67Cjo=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=qmaIXfqE8Zg3ARqxmWslkTSyye2ZzLoNMabo6q1EGyV0UxF3o4ENu4dVCk31zXTg+ cGuVDPy0r0wfzhpxK+FAPjCrTV3O7tRnZyRDPnrb8wE53BuiTWqK5XB060ZMpZcj5L CBqAf/7udyzk5Wd49SwqsoXP/Xta4ie0qBXcN7Xs= Message-ID: <5094F760.4080604@arcor.de> Date: Sat, 03 Nov 2012 11:52:16 +0100 From: Der Tiger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 To: "alpine-devel@lists.alpinelinux.org" Subject: Fwd: Re: [alpine-devel] [Alpine 2.4] Network Interface Hotplugging Detection References: <5094F6FB.3050709@arcor.de> In-Reply-To: <5094F6FB.3050709@arcor.de> X-Forwarded-Message-Id: <5094F6FB.3050709@arcor.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit ReHi Natanael, > From the man page: > > static value > Configures a static value. If you set ip_address then > dhcpcd will not attempt to obtain a lease and just use the value > for the address with an infinite lease time. > > Here is an example which configures a static address, > routes and dns. > interface eth0 > static ip_address=192.168.0.10/24 > static routers=192.168.0.1 > static domain_name_servers=192.168.0.1 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. > Looks like it also has some support for ipv6. I dont know about static. dhcpcd in deed has IPv6 RA (router advertisement) and RS (router solicitation) capability for SLAAC (stateless address autoconfiguration) implemented. This can be used to assign an IPv6 address to a local interface with the help of an DHCPv6 server, that can even be installed on the same machine utilizing local interfacing (localhost). 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. Regards, Tiger --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---