X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-yh0-f52.google.com (mail-yh0-f52.google.com [209.85.213.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id D697DDC039B for ; Fri, 2 Aug 2013 11:35:56 +0000 (UTC) Received: by mail-yh0-f52.google.com with SMTP id f11so277097yha.11 for ; Fri, 02 Aug 2013 04:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=CpuuOLeUOWlAPEzOPyOHf8+ANDY5Ooe8M5E1qh3iEmI=; b=A1aeVnCaGqhdbfLIx4RBn6hPJT2euwxxNj5lplvzoMtGOp3f67FxMFtXN9zUR8npdm 5Lkt8op8+SPi/1Zhn7E6f0ufgEpeaPDHa8245UEX4Xwxemlk2OsNv5G4M0tmrbNjJavi qIP9RvlszbkMQseFYT8KhEl5WMTysLSLnv/352zhrioa3Zq8pTkyWvvO8CiZ28tnp4xC 5Oc8/2mqFZLBl+JoGfaP0w0hRofYflvZf5gaKzJTBROgzqOig+EhrMwbKETanIZuAVKV bE/E6BHk2eLTanG5xtiNsL0RaCBTgRNpz4cN5KSW07axlYAdDKIpHKi+f+RlwhUlERWE I8qA== X-Received: by 10.236.148.41 with SMTP id u29mr3715697yhj.77.1375443355282; Fri, 02 Aug 2013 04:35:55 -0700 (PDT) Received: from [10.11.102.70] ([186.233.140.106]) by mx.google.com with ESMTPSA id s65sm11529051yhs.14.2013.08.02.04.35.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 04:35:54 -0700 (PDT) References: <20130801083150.6b41dbab@ncopa-desktop.alpinelinux.org> <20130802085216.5b17ecde@ncopa-desktop.alpinelinux.org> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 (1.0) In-Reply-To: <20130802085216.5b17ecde@ncopa-desktop.alpinelinux.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <51DBC573-E8AA-4498-B9C3-3C522581D83B@gmail.com> Cc: Alpine Devel List X-Mailer: iPad Mail (10B329) From: Alan Messias Cordeiro Subject: Re: [alpine-devel] Feature for NETDOWN=no Date: Fri, 2 Aug 2013 08:35:53 -0300 To: Natanael Copa Hi, Option 2 makes more sense now... And I think one of this would be used: > RC_NO_NETDOWN Or > RC_KEEP_NET :wq! ---- Alan Messias Cordeiro Enviado pelo meu iPad On 02/08/2013, at 03:52, Natanael Copa wrote: > On Thu, 1 Aug 2013 13:32:56 -0300 > Alan Messias wrote: >=20 >> Hi, >>=20 >> I cant understand how useful it is but, in my opinion, Option 3 (with >> default as 'all') makes more sense. With Option 3 who doesnt want/know th= is >> feature will never worry about it. >>=20 >> :wq! >=20 > I didn't know that there was a need for this kind either til yesterday. > I think its used in some WOL scenarios, but i dont know why it might be > needed. (ah it just made sense, i suppose the switch keeps the ip/mac > mapping in its arp table, so you can WOL on IP instead of mac addr... > or something like that. If you take down the iface you tell the switch > to clear the ip from its arp table.) >=20 > I was thinking more of option 2. Also with this option, people who > don't need this will never know that it exists and people who needs it > will need to list which devices they want it on (rather than a list of > devices they dont want this feature for). >=20 > Option 2 also means that if you use this feature, and additional net > interface is added, the new interface will by default be taken down, > even if some other device is configured to stay up on shutdown. With > option 3, if you add an interface, it will be kept up unless you > manually add it to RC_NETDOWN) >=20 > I just feel that RC_PREVENT_NETDOWN, sounds weird :) >=20 > RC_NO_NETDOWN? >=20 > RC_KEEP_NET? >=20 > RC_KEEP_IP? >=20 > RC_NO_IFDOWN? >=20 >=20 > -nc >=20 >> On Thu, Aug 1, 2013 at 3:31 AM, Natanael Copa wro= te: >>=20 >>> Hi, >>>=20 >>> I got a feature request for preventing taking down an interface on >>> shutdown. I wonder how we should implement this. >>>=20 >>> Option 1: >>>=20 >>> set RC_NETDOWN=3Dno in /etc/rc.conf (or /etc/conf.d/networking) will >>> prevent taking down all the network interface on shutdown. No support >>> for preventing individual interfaces - its all or nothing. >>>=20 >>>=20 >>> Option 2: >>>=20 >>> Use a blacklist (eg RC_PREVENT_NETDOWN) of interfaces to not take >>> down. For example: RC_PREVENT_NETDOWN=3D"eth0 eth3" will take down eth1 >>> and eth2 but not eth0 and eth3. If set to 'all', all interfaces will >>> be kept up and if set to 'none' all interfaces will be taken down. >>> Deafult would be 'none'. >>>=20 >>> Alternative variable names are: RC_NET_KEEP_UP >>>=20 >>>=20 >>> Option 3: >>>=20 >>> Use a whitelist of interfaces to take down on shutdown. For example >>> RC_NETDOWN=3D"eth1 eth2" will keep eth0 and eth3 up on shutdown. If set >>> to 'all' then all interfaces will be taken down and if set to 'none', >>> all interfaces will be kept up on shutdown. Default would be 'all'. >>>=20 >>>=20 >>> What do you prefer? They are all very simple to implement. >>>=20 >>> What are good variable names? >>>=20 >>> -nc >>>=20 >>>=20 >>> --- >>> Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org >>> Help: alpine-devel+help@lists.alpinelinux.org >>> --- >>>=20 >>>=20 >>=20 >>=20 >=20 --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---