From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 16:12:40 2005 Return-Path: X-Original-To: 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 6893E16A41F for ; Wed, 27 Jul 2005 16:12:40 +0000 (GMT) (envelope-from Kirk.Davis@epsb.ca) Received: from relay.epsb.ca (relay.epsb.ca [198.161.119.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA20D43D46 for ; Wed, 27 Jul 2005 16:12:39 +0000 (GMT) (envelope-from Kirk.Davis@epsb.ca) Received: from exchange03.epsb.ca (exchange03.epsb.ca [10.0.5.11]) by relay.epsb.ca (8.12.11/8.12.11) with ESMTP id j6RGCakO099033; Wed, 27 Jul 2005 10:12:36 -0600 (MDT) (envelope-from Kirk.Davis@epsb.ca) Received: by exchange03.epsb.ca with Internet Mail Service (5.5.2653.19) id ; Wed, 27 Jul 2005 10:12:36 -0600 Message-ID: <04C71268DFDAA8499EC1A248A44B6A2B34C006@Exchange21.EDU.epsb.ca> From: Kirk Davis To: Kirk Davis , "'Daniel O'Connor'" Date: Wed, 27 Jul 2005 10:12:33 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Cc: "'freebsd-current@freebsd.org'" Subject: RE: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently re boots X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2005 16:12:40 -0000 OK. I have moved my changes that I tried out of /etc/devd.conf and created a new iwi.conf file in /usr/local/etc/devd as Daniel suggested. It seems to work well and dhclient still attaches to the interface even when roaming. I was never able to get an /etc/start_if.iwi0 script to work correctly as Sam suggested because the dhclient dies on link down and there is nothing to detect the link up and reattach it. When I was roaming the dhclient would die as I re-associated. Using devd it works great. Here is the iwi.conf file: # devd configuration file for the iwi driver. # This file downloads the firmware on attach and starts up dhclient if configured. # attach 100 { device-name "iwi0"; action "/usr/local/sbin/iwicontrol -i iwi0 -d /usr/local/libdata/if_iwi -m bss"; }; # Try to start dhclient when the link comes up. # Only devices that are configured to support DHCP will actually # run it. No link down rule exists because dhclient automatically exits # when the link goes down. # notify 100 { match "system" "IFNET"; match "subsystem" "iwi0"; match "type" "LINK_UP"; action "/etc/rc.d/dhclient start iwi0"; }; I'll start working on a diff for the port and send it into the iwi-firmware port maintainer. ---- Kirk Kirk Davis Senior Network Analyst, ITS Edmonton Public Schools 1-780-429-8308 Kirk Davis wrote: > I agree and that is what I started to do but I needed to add the iwi device > to the ethernet-nic-regex variable in order for the dhclient to get the link > up/down notification. I'm not sure what the recommended way is for this. > I guess I could just create a new notify for that device in the included > file. > > ---- Kirk > > -----Original Message----- > From: Daniel O'Connor [mailto:doconnor@gsoft.com.au] > Sent: July 27, 2005 8:10 AM > To: freebsd-current@freebsd.org > Cc: Kirk Davis; 'Brandon S. Allbery KF8NH' > Subject: Re: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently re > boots > > On Wednesday 27 July 2005 01:54, Kirk Davis wrote: > > firmware early enough and that caused problems with dhclient. In stead I > > told devd to load the firmware on device detection. The following is a > > diff on the changed to devd.conf > > I strongly suggest you put this in /usr/local/etc/devd - no worries about > diffs then, and it makes any install doco much simpler ("copy this file to > X")