From owner-freebsd-ipfw@FreeBSD.ORG Thu Apr 7 09:26:54 2005 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D45AB16A4CE for ; Thu, 7 Apr 2005 09:26:54 +0000 (GMT) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D046D43D49 for ; Thu, 7 Apr 2005 09:26:53 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from [200.152.82.190] ([200.152.82.190]) by msrv.matik.com.br (8.13.1/8.12.11) with ESMTP id j379ULYF006780; Thu, 7 Apr 2005 06:30:22 -0300 (BRST) (envelope-from asstec@matik.com.br) From: Suporte Matik To: freebsd-ipfw@freebsd.org, sergei@gnezdov.net Date: Thu, 7 Apr 2005 06:26:20 -0300 User-Agent: KMail/1.7.2 References: <20050404090719.F2268544E1F@mail2-new.vianetworks.nl> <200504060733.50938.asstec@matik.com.br> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504070626.22614.asstec@matik.com.br> X-Virus-Scanned: ClamAV 0.80/777/Mon Mar 21 04:41:55 2005 clamav-milter version 0.80j on msrv.matik.com.br X-Virus-Status: Clean X-Spam-Status: No, score=-101.2 required=5.0 tests=ALL_TRUSTED,ISO_7BITS, MONOTONE_WORDS_2_15,NO_RDNS2,TW_PF,USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on msrv.matik.com.br X-Filter-Version: 1.11a (msrv.matik.com.br) Subject: Re: DHCP with ipfw X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 09:26:54 -0000 On Thursday 07 April 2005 01:56, Sergei Gnezdov wrote: > > You are probably right about timeout. I enabled rc.conf debuging > and captured the following console output: > > /etc/rc: DEBUG: run_rc_command: evaluating pccard_start(). > /etc/rc: DEBUG: run_rc_command: evaluating network_start(). -- you probably could have told your little secrets right away to get help on first shot you may try something like this in your dhclient.conf in order to get around your problem but set it to your WL settings, you can set several lines "ssid ..." if connecting to different APs interface "wi0" { media "ssid WIP-LUC nwkey 0x0101010111"; } Hans Infomatik http://info.matik.com.br