Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
From: Timo =?ISO-8859-1?Q?Ter=E4s?= <timo.teras@iki.fi>
Reply-To: Timo =?ISO-8859-1?Q?Ter=E4s?= <timo.teras@iki.fi>
To: Der Tiger <der.tiger.alpine@arcor.de>, Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] [Alpine 2.4] Network Interface Hotplugging
	Detection
References: <509147AC.8030105@arcor.de>
	 <20121031205406.79aa5da2@ncopa-laptop.res.nor.wtbts.net>
	  <509188C2.7080209@arcor.de>
In-Reply-To: <509188C2.7080209@arcor.de>
Content-Type: text/plain; charset=utf-8
Content-ID: <1351715904.10131.1.camel@Nokia-N900>
Date: Wed, 31 Oct 2012 22:38:24 +0200
Message-Id: <1351715904.10131.2.camel@Nokia-N900>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi,

> > > It seems Alpine does not detect link up and down events on NICs.
> > What kernel is it?
> That's 3.4.13, but I can reproduce the behaviour at least down to 3.3.

Kernel detects it for me. But often dhcpd exits if it does not get lease within some time.

> > > AFAIK, link up and down events are usually handled by daemons like
> > > ifplugd, netplugd or hotplug
> > add dhcpcd to that list.
> Didn't know that. That's, of course, a lead to follow. I'm going to
> check the dhcpcd configuration, tomorrow.

I just configured my dhcpd to never exit, and it handles the link state changes properly.

But if you want net specific static ip or dhcp params you probably need one of those hotplug things.

-Timo



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---