Date: Fri, 2 Aug 2013 08:52:16 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Alan Messias <alancordeiro@gmail.com>
Cc: Alpine Devel List <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Feature for NETDOWN=no
Message-ID: <20130802085216.5b17ecde@ncopa-desktop.alpinelinux.org>
In-Reply-To: <CAFaTuVYeB2yTuNzL1LN2F=s8-wh+23Dx=ubVbaS1f2m88Sb3QQ@mail.gmail.com>
References: <20130801083150.6b41dbab@ncopa-desktop.alpinelinux.org>
	<CAFaTuVYeB2yTuNzL1LN2F=s8-wh+23Dx=ubVbaS1f2m88Sb3QQ@mail.gmail.com>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 1 Aug 2013 13:32:56 -0300
Alan Messias <alancordeiro@gmail.com> wrote:

> Hi,
> 
> 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 this
> feature will never worry about it.
> 
> :wq!

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.)

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).

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)

I just feel that RC_PREVENT_NETDOWN, sounds weird :)

RC_NO_NETDOWN?

RC_KEEP_NET?

RC_KEEP_IP?

RC_NO_IFDOWN?


-nc

> On Thu, Aug 1, 2013 at 3:31 AM, Natanael Copa <ncopa@alpinelinux.org> wrote:
> 
> > Hi,
> >
> > I got a feature request for preventing taking down an interface on
> > shutdown. I wonder how we should implement this.
> >
> > Option 1:
> >
> >  set RC_NETDOWN=no 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.
> >
> >
> > Option 2:
> >
> >  Use a blacklist (eg RC_PREVENT_NETDOWN) of interfaces to not take
> >  down. For example: RC_PREVENT_NETDOWN="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'.
> >
> >  Alternative variable names are: RC_NET_KEEP_UP
> >
> >
> > Option 3:
> >
> >  Use a whitelist of interfaces to take down on shutdown. For example
> >  RC_NETDOWN="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'.
> >
> >
> > What do you prefer? They are all very simple to implement.
> >
> > What are good variable names?
> >
> > -nc
> >
> >
> > ---
> > Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> > Help:         alpine-devel+help@lists.alpinelinux.org
> > ---
> >
> >
> 
> 



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---