From owner-freebsd-wireless@freebsd.org Sun Jul 29 00:13:06 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDF5410628F3 for ; Sun, 29 Jul 2018 00:13:06 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 575E986F30 for ; Sun, 29 Jul 2018 00:13:06 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-it0-x233.google.com with SMTP id 72-v6so12657601itw.3 for ; Sat, 28 Jul 2018 17:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xw3nT/ta4PVX1U6V+8HvV761huMgH4YrP09a6/ikT5w=; b=b1eFd0C7Hg+xCHxxn1mpZhKu1yZpcRVs8wM/knX1M1ONA81thwTN7SQMWrC9Ha5688 T4kQhrrZN02JE4l15hsIfIT44lYVI5WnCuM77n0ZKgWSI21PckuCqYXKjPAA2i0CcQ4l QzwJGvrXyf8ocIll7XaMH7nsj4Cyj999mGrwpmwtumUMF0znfPXls4QL6DyT3adx9o3+ kVlCAQlYsPsdzrk3jo2KOX8971PO5r+E/meMFC5HH7/v3aAFald7WfjF9/aIYPt0nLTW pQO37XAmL2t924ahOtlOwLYnkE2FZeIpYRCdfthxZZBtmIadOMBXUSjCXpJKzb/0sa+1 fTgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xw3nT/ta4PVX1U6V+8HvV761huMgH4YrP09a6/ikT5w=; b=Dhhw9JI3NKmJ5njftP5XtsorVB5MLfEz/g0OyrA3srL51wKXvrHXEnUrIcjShB9aoW lCivp/jLTSF95BeWx0Z27INJvFRm1gc46r/cUCS3he+9N2tVRT4TPtpl0nTko+GV8zE+ wF9vKEJ+cdksVQRl16WT27JdZwGbih1oDUf1AXMusipFFb/dzfRkBtZEZpGLoXXYZErT qIrRDBG2BumRTlT919+bI2qhgSw/03Y193Sg4jUM5gQg6/idp6G+75qvk9VolAv6lpMh aBhPJyul6NXRH1G6dd4Uk7ok1Yd5Dcv8j5D2N6/TrJhm48kB1Ij91+vXESTvlicG6lyS 8AHQ== X-Gm-Message-State: AOUpUlGEuHVMhHAOh8NvyQ9QLJJXL2HKp3Hic48ECleQCdNcITwXl7Cg HihzfqwihQU3Nq8YOI8RXCDrJjwkzye58LsVskHN8Ck7 X-Google-Smtp-Source: AAOMgpc2QmGQEgiUBMyE1XXsytSSqEpL4iM5ZJuQsW0EmGSxTO/CD6W7p8ztRL5SlYwCEFjEUnNCf3MqGkQHnvskshg= X-Received: by 2002:a02:a1d9:: with SMTP id o25-v6mr11494534jah.86.1532823185443; Sat, 28 Jul 2018 17:13:05 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac0:8101:0:0:0:0:0 with HTTP; Sat, 28 Jul 2018 17:12:45 -0700 (PDT) From: Farhan Khan Date: Sat, 28 Jul 2018 20:12:45 -0400 Message-ID: Subject: What is the ieee80211_scanner variable? To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Sun, 29 Jul 2018 00:13:06 -0000 Hi all, What is "ieee80211_scanner *scanners", as defined in ieee80211_scan.c and how is it set? I am trying to figure out why my driver does not produce any results when I run "ifconfig wlan0 scan". I traced the ioctl that ifconfig(8) sends up to ieee80211_start_scan(). Here it will run ieee80211_scanner_get(), which appears to check if the "scanners" variable is set to not-NULL, and if so, return that value. Back in ieee80211_start_scan() if the value is NULL, it will return 0. The surrounding debug printf message suggests that this means the card is not able to scan. Where is this value set? What is it? It seems to be defined within net80211(4) and not at the driver-level? Am I missing something? Please explain. Thanks, -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-wireless@freebsd.org Sun Jul 29 15:55:35 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B7041059FD8 for ; Sun, 29 Jul 2018 15:55:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19D5884E66 for ; Sun, 29 Jul 2018 15:55:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id h20-v6so10870001wmb.4 for ; Sun, 29 Jul 2018 08:55:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EXrvPmy9uqqpHryCUfdw1HuKdR4LbWTNoyg/G2BhvvQ=; b=a0aOLCLQg/ozz8p4xG6cVELSBGCp4ijqoDOHJx7z7PCiquCyBNZ7NSkNp34tcWLyj3 PKuS3smEBlb/ciPPDgW/dGhSZtvJYQcx/qL7jpBb0RGGcnhQrpfh5Wrggi8hQxa2iXZM E090baqMMOeiUYKlTbeGLSRDuxNqTMTbGCtzF0/xnymgFQcU2Bv1Fmznl/MfZkj1jH3t RSFjH51QQ+ZCgLtcRSrvVlWERq0p8yDOP7PMZ4z/wrJTLNv17DeWa7/atZbpjMJORkDr RTh9eR+JYM2/3BWQ6XAz6XDAYGQfy1HXdUBkp2eqPN1n94Y8ZWt9vM+paRkkXt8cGkoJ 2VSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EXrvPmy9uqqpHryCUfdw1HuKdR4LbWTNoyg/G2BhvvQ=; b=JUyl91jYXd6E2vidRkn84oczq6Fxma2QV7cGid9h/m1NO2xCUmcdtJ3+4LSvKh2jIp Rxba9InQdWd74imWM7v4KVMi+fPAE1gzWLrPM40BAlrrVh6h/hDyh2STbwhx8lXwqdnd uZ+hK4WJptVFOi3HVteqCgxnusqB7eqLHt83ICvWxbDdkoS4DBeOIDjLQ96hceKPXMbo mieLqWut1J+p4P4zPI2+n+qOzOqWsNrgNZ91NXt+nVjdP5WXHD3p5haIER8vxwtEZ6YX P1pstaFnmPIUXv9uikIE84S0VA+V7a2Ecav8RHrzVoKXExPgcuNejWH8J0UGjAcRQ+/L fTZw== X-Gm-Message-State: AOUpUlHAsf42tY1t8MdqvDwWmbr2hH06kLYZM46SIshE7zLPYX5UavGK kTrLTQgkIOhO2Ew+zMvzxdPBR1Ia1jssOIg2Z4aNOw== X-Google-Smtp-Source: AAOMgpfIv1RVZZkdAXBXMXamWA29Po0XFfdFCa4TpKFKyJBVv5wkp+/iwcAsK3eU2TxqXkdiZJv3HSlvNyXajJJGjAE= X-Received: by 2002:a1c:2208:: with SMTP id i8-v6mr11449648wmi.105.1532879733994; Sun, 29 Jul 2018 08:55:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Sun, 29 Jul 2018 08:55:20 -0700 Message-ID: Subject: Re: What is the ieee80211_scanner variable? To: Farhan Khan Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Sun, 29 Jul 2018 15:55:35 -0000 hi, I replied on iRC but, for reference. The scanner array here is the per-mode scanner (AP, STA, etc.) that implements how you should do channel scanning and selection. It's set by net80211 by default and you normally don't need to go change it. -adrian On Sat, 28 Jul 2018 at 17:13, Farhan Khan wrote: > Hi all, > > What is "ieee80211_scanner *scanners", as defined in ieee80211_scan.c > and how is it set? > > I am trying to figure out why my driver does not produce any results > when I run "ifconfig wlan0 scan". I traced the ioctl that ifconfig(8) > sends up to ieee80211_start_scan(). Here it will run > ieee80211_scanner_get(), which appears to check if the "scanners" > variable is set to not-NULL, and if so, return that value. Back in > ieee80211_start_scan() if the value is NULL, it will return 0. The > surrounding debug printf message suggests that this means the card is > not able to scan. > > Where is this value set? What is it? It seems to be defined within > net80211(4) and not at the driver-level? > Am I missing something? Please explain. > > Thanks, > > -- > Farhan Khan > PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@freebsd.org Sun Jul 29 21:00:26 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4991A10632CF for ; Sun, 29 Jul 2018 21:00:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A9F4B79993 for ; Sun, 29 Jul 2018 21:00:23 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5F18710632C4; Sun, 29 Jul 2018 21:00:23 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B5D410632C3 for ; Sun, 29 Jul 2018 21:00:23 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5F1079970 for ; Sun, 29 Jul 2018 21:00:22 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EA7FA19DFA for ; Sun, 29 Jul 2018 21:00:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6TL0LUo069390 for ; Sun, 29 Jul 2018 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6TL0LxP069386 for wireless@FreeBSD.org; Sun, 29 Jul 2018 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807292100.w6TL0LxP069386@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: wireless@FreeBSD.org Subject: Problem reports for wireless@FreeBSD.org that need special attention Date: Sun, 29 Jul 2018 21:00:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Sun, 29 Jul 2018 21:00:26 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Tue Jul 31 01:54:16 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E504106A2A3 for ; Tue, 31 Jul 2018 01:54:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1B58673A35 for ; Tue, 31 Jul 2018 01:54:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D434B106A2A1; Tue, 31 Jul 2018 01:54:15 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3104106A2A0 for ; Tue, 31 Jul 2018 01:54:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6521C73A33 for ; Tue, 31 Jul 2018 01:54:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B2F549197 for ; Tue, 31 Jul 2018 01:54:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6V1sE21044211 for ; Tue, 31 Jul 2018 01:54:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6V1sE5X044210 for wireless@FreeBSD.org; Tue, 31 Jul 2018 01:54:14 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 228787] Intel 7260 bluetooth broken. Date: Tue, 31 Jul 2018 01:54:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ian.trudel@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 31 Jul 2018 01:54:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228787 Ian Trudel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian.trudel@gmail.com --- Comment #1 from Ian Trudel --- (In reply to dgilbert from comment #0) Same issue here. Brand new card. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Aug 2 03:34:08 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12EF61053FC3 for ; Thu, 2 Aug 2018 03:34:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A339797437 for ; Thu, 2 Aug 2018 03:34:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 645341053FC2; Thu, 2 Aug 2018 03:34:07 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52CD11053FC1 for ; Thu, 2 Aug 2018 03:34:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E53A797433 for ; Thu, 2 Aug 2018 03:34:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4F7212338B for ; Thu, 2 Aug 2018 03:34:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w723Y6G2060059 for ; Thu, 2 Aug 2018 03:34:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w723Y6F2060058 for wireless@FreeBSD.org; Thu, 2 Aug 2018 03:34:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 229738] [regression] [CURRENT] USB WiFi cards don't create wlan interfaces Date: Thu, 02 Aug 2018 03:34:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Thu, 02 Aug 2018 03:34:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229738 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sat Aug 4 22:32:34 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3D3A1055E0A for ; Sat, 4 Aug 2018 22:32:34 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DE358C32A for ; Sat, 4 Aug 2018 22:32:34 +0000 (UTC) (envelope-from khanzf@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id d9-v6so12914029itf.2 for ; Sat, 04 Aug 2018 15:32:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=JOrqKyz16VVVpkt5nHaH5/T5dhgv6LC3wzFzxGfu86Q=; b=R0+QySNLeJ7TbjtMCSRip9yI2rILgvXgBTBZQC3SCHnGK0qst8wXGmAWUem9G64n6K BPILlYwQKok/u0yxy+QUlLZWxDnYy4mCp1Fmf+8HXOs8+E1IGGWBWl3BjE82opyTyhAs eN2J+u7OOUECQtDLTF/+4/kTNRlqeyX2jd4JnmsWWoqa1dcD/b/oMUIZeLCt0xQ2D/Zs buSeR7dy4zv+hEDHxQJSmhnv0x46/8+BJ2BogAx2a6egYNqhAdxwM9VzJmf+Exenkh0+ BspNdaBv6MhrQSNt7MAgYLjkMnREllA2nyYtjG845GKJonX/c0nSa5rsXhs1ZqdLjAjq 4Peg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=JOrqKyz16VVVpkt5nHaH5/T5dhgv6LC3wzFzxGfu86Q=; b=kA3onHbPpQIh1RtuI72A7dKu0C2q+1Thkh8hdvfmD/Vo9qokersn7V6l2WWZv61s7s rdYL75DJOYhIde3QWB2X1LsdyXdqtI+4ZdBbxsAPuymwaKyjb19eya/6fZzudonv9HEo kraMi0wriRbS6hrg/I75ZhidMTdcV84SH2lnt3gojXwxXRuErtzAnEFwthHUTszucA4F Y/aLV3Oil3VcEAzgP/aC9Y9cbb+amxCjjt2U4mM5Vpy7xgaDKmry8k8Og3/ja8j8LTIm HoT4AaSVS8BkkDOk9m6z7Aq1vpVITrMx8UAYGQGihFCknkmiVLb1mJF1q67m7EZvHGzv lFxw== X-Gm-Message-State: AOUpUlGpa/nXou0zrQ1+qNx5tEm7VYqX7CL0ImUF667z6PoEX/UXLOYk fqqFf/teMB9UyZq5BbOrWj6FVAJVi++n4SmElPrBxy0Jlg4= X-Google-Smtp-Source: AAOMgpfQghywfPe/0AzaPltRwfiBZo6iRBOn167d0X42xXeQ/B/N/oeSOrLz9ckhDTbA1oY+jq/kafMNhP1bYPRIF7E= X-Received: by 2002:a24:f545:: with SMTP id k66-v6mr10770854ith.138.1533421953498; Sat, 04 Aug 2018 15:32:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac0:8101:0:0:0:0:0 with HTTP; Sat, 4 Aug 2018 15:32:13 -0700 (PDT) From: Farhan Khan Date: Sat, 4 Aug 2018 18:32:13 -0400 Message-ID: Subject: Where do monitor mode and STA mode begin to differ? To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Sat, 04 Aug 2018 22:32:35 -0000 Hi all, Is there anything in net80211(4)'s initialization that is different between STA and monitor mode, specially around Rx? Short explanation: My extension to rtwn(4)'s monitor mode works, I can see arbitrary frames with tcpdump, but STA mode does not receive anything except the probe requests it sends out itself. Every 30 seconds in STA mode I get this: "rtwn0: device timeout" and the device re-initializes. I suspect this is due to it not receiving any frames. What might be initializing differently depending on if its STA or Monitor mode? If I can find where that is, I might be able to make an adjustment. I do not see anything that stands out in rtwn(4)'s init sequence, but I'll give it another look. Is there anything in net80211(4) that happens different based on the mode of the vap? Verbose explanation: As Adrian suggested on IRC, I went through rtwn_scan_start and rtwn_scan_end. This matched the Linux code. All these lines did, however, was adjust the Rx filter to receive beacons/probes from any BSSID, then uses ieee80211's probe functions to send out probe requests for whatever the VAP's ssid is set to. Running "tcpdump -ni wlan0 -y IEEE802_11_RADIO" **only** shows probes from what the device is sending and dtrace probes do not show the net80211(4) functions you would expect to happen to classify the frame. On a separate device, I monitored for frames and saw the Probe requests and responses to and from a test AP I setup, followed by an empty probe requests, which is exactly what ieee80211_swscan_probe_curchan() does. So Tx works. Great! rtwn(4) performs filter initialization in rtwn_rxfilter_init(). I checked that code to see if anything was being filtered that should not and nothing stood out to me. I unfiltered everything using rtwn_write_2(sc, R92C-RXFLTMAP0/1/2, 0xffff), and #IFDEF 0'd out the entire function. Same result. I should also note that rtwn_rxfilter_init() is used by every rtwn(4) device and is probably standard for this Realtek series. This suggests to me that somewhere during the initialization STA fails. Again, I will look through rtwn(4)'s init sequence, but is there anything in ieee80211(4) that might be different depending on if its in monitor mode or STA mode? And if you don't know, can you kindly guide me to what net80211(4) function first discriminates between the device mode? Thank you and I apologize for the long email. -- Farhan Khan PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE From owner-freebsd-wireless@freebsd.org Sat Aug 4 22:48:54 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 258BC1056499 for ; Sat, 4 Aug 2018 22:48:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 846368CB69 for ; Sat, 4 Aug 2018 22:48:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id w24-v6so10230054wmc.1 for ; Sat, 04 Aug 2018 15:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6x/rbVkESHfYW5uB0MfZvhB49ntWMa4RlM5TEla3mVc=; b=oc+siLZpsldNnKTgZasclkV6id6qavYkDFYLIu6X247vEnZYk75aPoQelBvHiK+bij d6CbjrtBmcNcOhM41JJlsgbD95ex7LSkngoLG+cTeof/zsyNHswqkwQE1ImuON+9pG5C clToUBWJfWTJvS2zqGwm0T+dFenRRBMA8rbDE1BhNWVvbpxTmgM/VhAPuduERMx29qdr Jou543jlk12X1Y/mbFzOR0YdzpHa7Wmdeh0rNTURs4V7gF5EKtBhp4OluawteABNTbZb m7Ih0mUf/05vvKUyu7qTFccxk9BU6/uQw6GktE24EELq2btgGRFVKK2waOAbDemkCXus LNFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6x/rbVkESHfYW5uB0MfZvhB49ntWMa4RlM5TEla3mVc=; b=AEniejZl6LsxNJndfOpYXZ4DCsI+NP6GhGxchRV4GMb2FJcf2/p5hjlFt4AUTcxhNB JQxPS7hLmceqiiMa/Ezd21N74c1QDLKF+WA+N/0K9BCLf3cEVlV7D+d+oaUfYNInktsU zGj48X4CGTXZrHh0FygTffHSsoGLcs12/gCZU/AVTj92Jp/KwYOxoXuwrt1qGxA6ssJ0 dydDXNRd70ZD/GeRe3A1M6FSC0xwZ8F7JXOq0IWZOa9UOsabZYSPhLL2wn8JN7U1ZEQQ 3xggrfx0oFw+YRjt464hW4nW+B8KXPWRRtr7IZTlRdQvxg2cFvThXISkhOlRzrVeKuiE 8meA== X-Gm-Message-State: AOUpUlGZOfIALvNBiFSxL2cXxsi6S1lz4C8DTeDT8dAdEG5I4eorKz2b K4BJvEC5oXnWKEZ0miQw12dFBsWwIxViJ0THy4o= X-Google-Smtp-Source: AAOMgpcoD3D7bcgeQIhDU9QrO7aBK2SRcSzgvwxl+GBly5p/0nGHasDBun5rRrFNyNmno3Tzp/FEpaUZpvHXqMNdD8Q= X-Received: by 2002:a1c:c64f:: with SMTP id w76-v6mr8503678wmf.3.1533422931688; Sat, 04 Aug 2018 15:48:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Sat, 4 Aug 2018 15:48:38 -0700 Message-ID: Subject: Re: Where do monitor mode and STA mode begin to differ? To: Farhan Khan Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.27 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: Sat, 04 Aug 2018 22:48:54 -0000 hi! So, net80211 itself shouldn't really differ that much for this particular issue. There may be some functions that aren't called in monitor mode (like sta_join) but you're not yet there.s I'd look at the difference in the driver VAP setup and the newstate function for different operating modes. If RX works in monitor mode but it's not working in scanning mode then I'd look at how the hardware is programmed in STA versus monitor mode. Eg, there may not be a BSS Mask programmed in for monitor mode, or it's programmed to something like "all bits." -adrian On Sat, 4 Aug 2018 at 15:32, Farhan Khan wrote: > Hi all, > > Is there anything in net80211(4)'s initialization that is different > between STA and monitor mode, specially around Rx? > > Short explanation: My extension to rtwn(4)'s monitor mode works, I can > see arbitrary frames with tcpdump, but STA mode does not receive > anything except the probe requests it sends out itself. Every 30 > seconds in STA mode I get this: "rtwn0: device timeout" and the device > re-initializes. > > I suspect this is due to it not receiving any frames. What might be > initializing differently depending on if its STA or Monitor mode? If I > can find where that is, I might be able to make an adjustment. I do > not see anything that stands out in rtwn(4)'s init sequence, but I'll > give it another look. Is there anything in net80211(4) that happens > different based on the mode of the vap? > > Verbose explanation: As Adrian suggested on IRC, I went through > rtwn_scan_start and rtwn_scan_end. This matched the Linux code. All > these lines did, however, was adjust the Rx filter to receive > beacons/probes from any BSSID, then uses ieee80211's probe functions > to send out probe requests for whatever the VAP's ssid is set to. > > Running "tcpdump -ni wlan0 -y IEEE802_11_RADIO" **only** shows probes > from what the device is sending and dtrace probes do not show the > net80211(4) functions you would expect to happen to classify the > frame. On a separate device, I monitored for frames and saw the Probe > requests and responses to and from a test AP I setup, followed by an > empty probe requests, which is exactly what > ieee80211_swscan_probe_curchan() does. So Tx works. Great! > > rtwn(4) performs filter initialization in rtwn_rxfilter_init(). I > checked that code to see if anything was being filtered that should > not and nothing stood out to me. I unfiltered everything using > rtwn_write_2(sc, R92C-RXFLTMAP0/1/2, 0xffff), and #IFDEF 0'd out the > entire function. Same result. I should also note that > rtwn_rxfilter_init() is used by every rtwn(4) device and is probably > standard for this Realtek series. > > This suggests to me that somewhere during the initialization STA > fails. Again, I will look through rtwn(4)'s init sequence, but is > there anything in ieee80211(4) that might be different depending on if > its in monitor mode or STA mode? > > And if you don't know, can you kindly guide me to what net80211(4) > function first discriminates between the device mode? > > Thank you and I apologize for the long email. > > -- > Farhan Khan > PGP Fingerprint: B28D 2726 E2BC A97E 3854 5ABE 9A9F 00BC D525 16EE > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " >