From owner-freebsd-current@FreeBSD.ORG  Tue Aug 12 01:53:03 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 49CBA37B401
	for <freebsd-current@freebsd.org>;
	Tue, 12 Aug 2003 01:53:03 -0700 (PDT)
Received: from mail.imp.ch (mail.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BB97143F75
	for <freebsd-current@freebsd.org>;
	Tue, 12 Aug 2003 01:53:01 -0700 (PDT)	(envelope-from mb@imp.ch)
Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7])
	by mail.imp.ch (8.12.6p2/8.12.3) with ESMTP id h7C8qwYc065854;
	Tue, 12 Aug 2003 10:52:59 +0200 (CEST)
	(envelope-from Martin.Blapp@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by nbs.imp.ch (8.12.8/8.12.3) with ESMTP id h7C8qwlH9066814;
	Tue, 12 Aug 2003 10:52:58 +0200 (MES)
Date: Tue, 12 Aug 2003 10:52:58 +0200 (CEST)
From: Martin Blapp <mb@imp.ch>
To: Mark Sergeant <msergeant@snsonline.net>
Message-ID: <20030812104605.G2686@cvs.imp.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Problem with dhclient & wi0 on resume.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Aug 2003 08:53:03 -0000


Hi,

>I've got a toshiba portege 4000 with inbuilt wi0 wireless card. On
>resume dhclient kicks off straight away which then breaks as the card

You mean dhclient gets killed ? One way could be to kill dhclient when you
sleep. Afterwords, devd should restart it, right ? Unfortunatly I cannot
test this myself as resume on my lapton is horribly broken.

>isn't loaded as yet. Is there anyway to specify a sleep value for
>dhclient on resume from suspend ? I'm running current from today, I
>should note I'm also seeing a bunch of wi0 bad_alloc messages as well
>with this card. It gets quite annoying to have to restart dhclient
>everytime I resume.

There is one:

/etc/dhclient.conf
#
#
#
omapi port 7911;

/etc/sleep_dhclient

#!/bin/sh

omshell > /dev/null << EOF
connect
new control
open
set state = 3
update
close

/etc/wakeup_dhclient

#!/bin/sh

omshell > /dev/null << EOF
connect
new control
open
set state = 4
update
close

Please tell me if you have success with these.

Martin

Martin Blapp, <mb@imp.ch> <mbr@FreeBSD.org>
------------------------------------------------------------------
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: <finger -l mbr@freebsd.org>
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
------------------------------------------------------------------