From owner-freebsd-bugs@FreeBSD.ORG Sun Nov 27 21:10:09 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B3B916A422 for ; Sun, 27 Nov 2005 21:10:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E9A043D64 for ; Sun, 27 Nov 2005 21:10:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jARLA6tl070582 for ; Sun, 27 Nov 2005 21:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jARLA6cA070581; Sun, 27 Nov 2005 21:10:06 GMT (envelope-from gnats) Date: Sun, 27 Nov 2005 21:10:06 GMT Message-Id: <200511272110.jARLA6cA070581@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Infomatik Cc: Subject: Re: kern/88882: [ndis] ndis IF tx/rx and other problems in 6.0-R (regression) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Infomatik List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Nov 2005 21:10:09 -0000 The following reply was made to PR kern/88882; it has been noted by GNATS. From: Infomatik To: bug-followup@freebsd.org, joao@matik.com.br Cc: Subject: Re: kern/88882: [ndis] ndis IF tx/rx and other problems in 6.0-R (regression) Date: Sun, 27 Nov 2005 19:09:15 -0200 I am with 6.0-STABLE now and the problem still exist but I can control this problem now setting=20 ifconfig ndis0 .... roaming manual ... means for me that if the ssid decision is let to the device or driver it ma= y=20 ocasionally associate itself to another access point, but I guess the defau= lt=20 should not be trying to associate to another AP so the problem what make it hard to find out is that even if the status sta= ys=20 as associated the ssid is not updated after associating to another AP BTW. what I reported as kern/88937 the correct channel is displayed now. Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br