From owner-freebsd-current Fri Jun 1 15:58:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 9C1DB37B423 for ; Fri, 1 Jun 2001 15:58:48 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id SAA71253 for current@freebsd.org; Fri, 1 Jun 2001 18:58:47 -0400 (EDT) (envelope-from mwlucas) Date: Fri, 1 Jun 2001 18:58:47 -0400 From: Michael Lucas To: current@freebsd.org Subject: wicontrol && ifconfig after wireless ifconfig changes Message-ID: <20010601185847.A71176@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, After updating to yesterday's current, my "victim" laptop's wireless card stopped working. It turns out that wicontrol wasn't setting the card correctly. Using the nifty new ifconfig commands worked perfectly. This started right after pkh's changes to ifconfig to replace the various wireless control programs. If the intent is to have both *control and ifconfig working, I'll be happy to document exactly what isn't working. If the intent is to replace *control, should a note be put in UPDATING that users might have problems? Thanks. ==ml PS: Using ifconfig, you can easily see when your card is misconfigured by the "no carrier" warning. That is really, really cool. Thank you! -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message