From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 23 21:37:23 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EEF3E28F for ; Wed, 23 Oct 2013 21:37:23 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id AC53622D9 for ; Wed, 23 Oct 2013 21:37:23 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:32601] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id D7/4B-19454-29148625; Wed, 23 Oct 2013 21:37:22 +0000 Date: Wed, 23 Oct 2013 21:37:22 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-wireless@freebsd.org References: Subject: Re: [rfc] removing the NDISulator X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: freebsd-current@freebsd.org, claudiu vasadi X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 21:37:24 -0000 > > On 23 October 2013 13:10, claudiu vasadi wrote: > > Hi, > > Still getting the "Cannot reset interface wlan0 - exit status 1" in > > wifimgr but no crash yet. Will keep trying :D > I have no idea about that. It's likely there's some net80211/iwn bug(s) but > I don't use wifimgr so I don't know what it's doing. > For that I'd bug the wifimgr people in PCBSD. they can always file bug > reports with me :) > Thanks, > -adrian I don't have wifimgr either, can't even install it until I get wifi set up. Does wifimgr have more functionality than wpa_cli? Why would some drivers not be ndisulatable/ndiswrappable? Would that be because the resulting driver would fail, or because of the lack of .inf and .sys files in Windows driver? Tom