From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 7 07:25:57 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2FFF106564A for ; Sun, 7 Oct 2012 07:25:57 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm31-vm1.bullet.mail.gq1.yahoo.com (nm31-vm1.bullet.mail.gq1.yahoo.com [98.136.216.208]) by mx1.freebsd.org (Postfix) with SMTP id A2FCE8FC12 for ; Sun, 7 Oct 2012 07:25:57 +0000 (UTC) Received: from [98.137.12.191] by nm31.bullet.mail.gq1.yahoo.com with NNFMP; 07 Oct 2012 07:25:51 -0000 Received: from [98.136.185.45] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 07 Oct 2012 07:25:51 -0000 Received: from [127.0.0.1] by smtp106.mail.gq1.yahoo.com with NNFMP; 07 Oct 2012 07:25:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1349594751; bh=60B9wO3llYoiPKre4QhzZNNrxnSQP1mowqgq2+pK0bk=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=UDc6lHHiPp0ykjSQL+XqswVR2ggs8f7hG7DvfszBIJBPRDHM0v/6EkEMn8VERb57yP7Cqi4sYmTo8rHycIqa1NCsY302jt9o51stGvZnkp0ZgMQL9ab9L6ZmhU/8PdjCelE7dPfB/2roDl+PqiLR+Juvlz5X8t+eLEMR89bHV/A= X-Yahoo-Newman-Id: 419906.32963.bm@smtp106.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: D4F9LXgVM1kiGPLiwUWaD1SGW0ZQ9jUy4UsaliGi04Yqb0D GalYjrCasTLsM5b_I3WkPDLt.AAWTeWzVuyBTJcGfaHZ425yIPRHu11AmNXk M5FSEvy_wzj8dZOXHQaaKSvx9GWht664vM.Rjxp76q7_QrhtOo8rUB09X3ln KERASJuxwtWQdLpGj.4kRSrGyvsD0Dk9hNTkaN_4hGwmjscgefkTgdH5RGIG f9bvWBsuP6O8t0jAmdHNc.8WKjj80PBI1nInvZsREB5VCZyFlPytTlLYWJ1I zPGAaWAxIhYbOiXyQxdVN6JL2DcagbKueR3p4Q55rb6QKRH8c74CEu0YKUuC AW2a3Cf1vKdUmySybdvgb7GvAVPMnW7kuglByP3HN2GBdJmQuKjS.wnywSGp w7f1gQ30HXH2KHKkXcLuigapgVK_UJdVrfjvIyg7X_.UUsF0q2OqHUj0UNIM MiO_J8iQE.rPO.87k5BeIdKzokhYl6pT__9PdIAJvT9Wyu8b.rA751Ks5QD4 ATshEoFeoITABAcb2HAm52PWJbI_la26gT1NpKALRbRBXHsw3ZuKyU6_YvVL csrWofCmYXaIS7dLV X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-vb0-f54.google.com (moonlightakkiy@209.85.212.54 with plain) by smtp106.mail.gq1.yahoo.com with SMTP; 07 Oct 2012 00:25:51 -0700 PDT Received: by mail-vb0-f54.google.com with SMTP id v11so4097402vbm.13 for ; Sun, 07 Oct 2012 00:25:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.149.206 with SMTP id u14mr7698321vcv.63.1349594750039; Sun, 07 Oct 2012 00:25:50 -0700 (PDT) Received: by 10.58.182.72 with HTTP; Sun, 7 Oct 2012 00:25:49 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Oct 2012 01:25:49 -0600 Message-ID: From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: [RFC] How the TX path works; I'd like to fix this before 10.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Oct 2012 07:25:58 -0000 On Sat, Oct 6, 2012 at 3:00 PM, Adrian Chadd wrote: > Well, i would like to implement if_transmit for net80211 tx, then have the > tx routine queue the frame and wakeup the tx taskqueue or tasklet. Im not > sure yet whether to put the tx processing in the existing ic taskqueue or > not, but since the current tx path runs separate to the ic taskqueue, the > hard work is already done for us. If we forget about hooking ieee80211_output() and leave ether_ifattach() default hooks http://fxr.watson.org/fxr/source/net80211/ieee80211.c#L548 if_transmit will be called with packets encaped in ethernet header. Then, in a will-be-added ieee80211_transmit(), call ieee80211_encap(), IFQ_HANDOFF(), and call (or enqueue) driver's new tx task. This can be done by just teaching new tx path aware drivers correct functions to hook. (So, we don't have to change all wifi drivers.) > > In parallel I would like to kill the ieee80211_output and raw xmit code, > instead doing the encap and such in the tx tasklet. If all packets, whether data or mgmt, are queued to the same buff (i.e. if_snd), probably raw_xmit won't be needed. And, somehow attach txparam to all packets. Then, driver can handle the packets in the same tx function by using info in txparam. (I think the driver code will be simpler.) But, I wonder if waiting for all previously queued packets being processed causes any trouble for shorter buffer-life packets, i.e. addba/probe response packets. AK > > We could later allow encap before serialisation but delay seqno and > encryption. Thats a later thing. > > In parallel we do need to fix driver tx. It all has to stay in order... Ie > the order that the tx tasklet does encap must reflect the driver setup. Or, > we push seqno allocation to each driver. Ew. > > Adrian > > On Oct 6, 2012 3:01 PM, "PseudoCylon" wrote: >> >> > ------------------------------ >> > >> > Message: 4 >> > Date: Fri, 5 Oct 2012 23:44:10 -0700 >> > From: Adrian Chadd >> > Subject: [RFC] How the TX path works; I'd like to fix this before 10.x >> > To: freebsd-wireless@freebsd.org >> > Message-ID: >> > >> > >> > Content-Type: text/plain; charset=ISO-8859-1 >> > >> > Before I continue - if_transmit() is not the answer. if_transmit() >> > guarantess _no_ serialisation at all. So we'd stlil have to stuff >> > things into queues. And ensure only one thing is running at once. >> >> As far as I know, if_transmit/if_start are options for drivers, not >> for the serialisation. >> if_transmit to use device specific queue >> if_start to use if_snd queue >> i.e. >> http://fxr.watson.org/fxr/source/dev/e1000/if_em.c#L2941 >> >> > >> > I could wrap a big VAP TX lock around ieee80211_output() and >> > ieee80211_start(), ensuring they don't run over each other. But >> > long-held locks need to go away and die. yes, even the ones in the >> > ath(4) driver that I've introduced. They're there because of a lack of >> > synchronisation and queue design. A lot of the gige/10ge drivers use >> > long-held locks.. sigh. >> > >> > I could create a net80211 TX tasklet for each vap (or ic, _maybe_) >> > which serialises the TX path. ieee80211_start() would just schedule >> > the tasklet to run. That would serialise all of the parallel TX entry >> > points and solve a bunch of the subtle sequence number and other TX >> > state races that are occuring. That doesn't solve the ic_raw_xmit() or >> > ieee80211_output() problem, as both of those can also do TX 802.11 >> > encapsulation and kick off parts of the state machine. >> >> I prefer taskqueue over new lock. I have had enough of LORs already. >> >> We just need to decide where/how to funnel all tx entries. >> Currently, >> pseudo devices (i.e. if_bridge) \ >> IP stack --> ieee80211 stack --> >> driver >> ic_raw_xmit >> / >> so we need to ensure serialization (by lock or taskqueue) at 2 points, >> 1) between upper layer and ieee80211, >> 2) driver and ieee80211. >> If we solve the raw_xmit problem, there will be only 1 point to take care. >> >> >> An idea >> Guarantee only one thread is running at any moment. So, first queued >> first dequeued and tx'd without a lock. >> >> if_start() { >> if (sc_task == NOT_RUNNING) >> wakeup(sc_txtask); >> } >> >> if_txtask() { >> for (;sc_txtask_exit != DONE;) { >> IFQ_DRV_DEQUEUE(); >> if (m == NULL) { >> sc_txtask = NOT_RUNNING; >> tsleep(); >> sc_txtask = RUNNING; >> } else >> tx(); >> } >> } >> >> tx_callback() { >> ... >> if (sc_task == NOT_RUNNING) >> wakeup(sc_txtask); >> } >> >> iv_vap_create() { >> ... >> taskqueue_enqueue(sc_taskqueue); >> } >> >> iv_vap_delete() { >> ... >> sc_txtask_exit = DONE; >> if (sc_task == NOT_RUNNING) >> wakeup(sc_txtask); >> } >> >> > >> > It doesn't solve the same issues with the drivers .Yes, even if we >> > converted them to use if_transmit(). iwn(4) solves this by just having >> > a big IWN_LOCK() but it releases it when doing anything stack related. >> > I'm not sure if it holds it across the whole TX path through >> > iwn_start(). In any case, it's a big lock. ath(4) can and does have >> > multiple ath_start() instances running in multiple kernel threads, >> > fighting to dequeue frames from the ifnet. This still can cause issues >> > with non-aggregate sequence number and CCMP IV counter allocation. >> > Sigh. >> > >> > God even knows what to do about USB devices in all of this. >> > >> >> Similar to other drivers, i.e. iwn(4). The difference is USB drivers >> create per-USB-pipe queue in addition to if_snd queue. So that, tx >> path look like >> if_transmit -> queue -> if_start -> dequeue -> driver_tx -> usb_queue >> -> usb_stack >> It seems redundant. I'd like to change that to (for run(4)) >> if_transmit -> driver_tx -> usb_queue -> usb_stack >> >> >> AK >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://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 Oct 7 17:57:17 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A28E1065672 for ; Sun, 7 Oct 2012 17:57:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id BE71A8FC1D for ; Sun, 7 Oct 2012 17:57:16 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1279046dad.13 for ; Sun, 07 Oct 2012 10:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=IMh6QL1HFyApdwvKzUysYxWOmk/ERIzhpAADERaQrYU=; b=IhfeUJhSrgiBTmzk71WQhvEaiiLCFCCjqukSAa9gWfmnVPP7bLEf4TMuluWF2aRFvu 1wEdAXqF2RrdmXOr0P8BJowSjmk+JPJmiXW9tlpoWaZkI2j9Jh8IxklmoXGWtShoGdGo HK/O61+Eik4krk851dGUCsXgj03FcLVjUxcgv3N2WSBDYThJ/cXofukARA/Qx9Mw0GvD vGbSeDArvrXKFgKKrWyqLnz5NXPxhiEZmeUwpb4Qw83hYvKEghd8LjiM3FKFavReDUze 3kitCKArykzlQvKFRFBEP3NQZeQSOZkCORUq4hPusgFR0q8XMx/Mwlmf3mCYqHWW6suD t12w== MIME-Version: 1.0 Received: by 10.66.72.132 with SMTP id d4mr37128287pav.61.1349632636014; Sun, 07 Oct 2012 10:57:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.223.136 with HTTP; Sun, 7 Oct 2012 10:57:15 -0700 (PDT) Received: by 10.68.223.136 with HTTP; Sun, 7 Oct 2012 10:57:15 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Oct 2012 10:57:15 -0700 X-Google-Sender-Auth: 4uUBMqIf0YBpO3XQXs2G_Ju_w2o Message-ID: From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: [RFC] How the TX path works; I'd like to fix this before 10.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Oct 2012 17:57:17 -0000 Yes, the mgmt packet priority is worrying, but anything encrypted and/or with a sequence number needs to be serialised anyway. Maybe we can create per AC queues between the stack and driver. But that will need an API change. Hm! Adrian On Oct 7, 2012 3:25 AM, "PseudoCylon" wrote: > On Sat, Oct 6, 2012 at 3:00 PM, Adrian Chadd wrote: > > Well, i would like to implement if_transmit for net80211 tx, then have > the > > tx routine queue the frame and wakeup the tx taskqueue or tasklet. Im not > > sure yet whether to put the tx processing in the existing ic taskqueue or > > not, but since the current tx path runs separate to the ic taskqueue, the > > hard work is already done for us. > > If we forget about hooking ieee80211_output() and leave > ether_ifattach() default hooks > http://fxr.watson.org/fxr/source/net80211/ieee80211.c#L548 > if_transmit will be called with packets encaped in ethernet header. > > Then, in a will-be-added ieee80211_transmit(), call ieee80211_encap(), > IFQ_HANDOFF(), and call (or enqueue) driver's new tx task. This can be > done by just teaching new tx path aware drivers correct functions to > hook. (So, we don't have to change all wifi drivers.) > > > > > In parallel I would like to kill the ieee80211_output and raw xmit code, > > instead doing the encap and such in the tx tasklet. > > If all packets, whether data or mgmt, are queued to the same buff > (i.e. if_snd), probably raw_xmit won't be needed. And, somehow attach > txparam to all packets. Then, driver can handle the packets in the > same tx function by using info in txparam. (I think the driver code > will be simpler.) > > But, I wonder if waiting for all previously queued packets being > processed causes any trouble for shorter buffer-life packets, i.e. > addba/probe response packets. > > > AK > > > > > We could later allow encap before serialisation but delay seqno and > > encryption. Thats a later thing. > > > > In parallel we do need to fix driver tx. It all has to stay in order... > Ie > > the order that the tx tasklet does encap must reflect the driver setup. > Or, > > we push seqno allocation to each driver. Ew. > > > > Adrian > > > > On Oct 6, 2012 3:01 PM, "PseudoCylon" wrote: > >> > >> > ------------------------------ > >> > > >> > Message: 4 > >> > Date: Fri, 5 Oct 2012 23:44:10 -0700 > >> > From: Adrian Chadd > >> > Subject: [RFC] How the TX path works; I'd like to fix this before 10.x > >> > To: freebsd-wireless@freebsd.org > >> > Message-ID: > >> > > >> > > >> > Content-Type: text/plain; charset=ISO-8859-1 > >> > > >> > Before I continue - if_transmit() is not the answer. if_transmit() > >> > guarantess _no_ serialisation at all. So we'd stlil have to stuff > >> > things into queues. And ensure only one thing is running at once. > >> > >> As far as I know, if_transmit/if_start are options for drivers, not > >> for the serialisation. > >> if_transmit to use device specific queue > >> if_start to use if_snd queue > >> i.e. > >> http://fxr.watson.org/fxr/source/dev/e1000/if_em.c#L2941 > >> > >> > > >> > I could wrap a big VAP TX lock around ieee80211_output() and > >> > ieee80211_start(), ensuring they don't run over each other. But > >> > long-held locks need to go away and die. yes, even the ones in the > >> > ath(4) driver that I've introduced. They're there because of a lack of > >> > synchronisation and queue design. A lot of the gige/10ge drivers use > >> > long-held locks.. sigh. > >> > > >> > I could create a net80211 TX tasklet for each vap (or ic, _maybe_) > >> > which serialises the TX path. ieee80211_start() would just schedule > >> > the tasklet to run. That would serialise all of the parallel TX entry > >> > points and solve a bunch of the subtle sequence number and other TX > >> > state races that are occuring. That doesn't solve the ic_raw_xmit() or > >> > ieee80211_output() problem, as both of those can also do TX 802.11 > >> > encapsulation and kick off parts of the state machine. > >> > >> I prefer taskqueue over new lock. I have had enough of LORs already. > >> > >> We just need to decide where/how to funnel all tx entries. > >> Currently, > >> pseudo devices (i.e. if_bridge) \ > >> IP stack --> ieee80211 stack --> > >> driver > >> ic_raw_xmit > >> / > >> so we need to ensure serialization (by lock or taskqueue) at 2 points, > >> 1) between upper layer and ieee80211, > >> 2) driver and ieee80211. > >> If we solve the raw_xmit problem, there will be only 1 point to take > care. > >> > >> > >> An idea > >> Guarantee only one thread is running at any moment. So, first queued > >> first dequeued and tx'd without a lock. > >> > >> if_start() { > >> if (sc_task == NOT_RUNNING) > >> wakeup(sc_txtask); > >> } > >> > >> if_txtask() { > >> for (;sc_txtask_exit != DONE;) { > >> IFQ_DRV_DEQUEUE(); > >> if (m == NULL) { > >> sc_txtask = NOT_RUNNING; > >> tsleep(); > >> sc_txtask = RUNNING; > >> } else > >> tx(); > >> } > >> } > >> > >> tx_callback() { > >> ... > >> if (sc_task == NOT_RUNNING) > >> wakeup(sc_txtask); > >> } > >> > >> iv_vap_create() { > >> ... > >> taskqueue_enqueue(sc_taskqueue); > >> } > >> > >> iv_vap_delete() { > >> ... > >> sc_txtask_exit = DONE; > >> if (sc_task == NOT_RUNNING) > >> wakeup(sc_txtask); > >> } > >> > >> > > >> > It doesn't solve the same issues with the drivers .Yes, even if we > >> > converted them to use if_transmit(). iwn(4) solves this by just having > >> > a big IWN_LOCK() but it releases it when doing anything stack related. > >> > I'm not sure if it holds it across the whole TX path through > >> > iwn_start(). In any case, it's a big lock. ath(4) can and does have > >> > multiple ath_start() instances running in multiple kernel threads, > >> > fighting to dequeue frames from the ifnet. This still can cause issues > >> > with non-aggregate sequence number and CCMP IV counter allocation. > >> > Sigh. > >> > > >> > God even knows what to do about USB devices in all of this. > >> > > >> > >> Similar to other drivers, i.e. iwn(4). The difference is USB drivers > >> create per-USB-pipe queue in addition to if_snd queue. So that, tx > >> path look like > >> if_transmit -> queue -> if_start -> dequeue -> driver_tx -> usb_queue > >> -> usb_stack > >> It seems redundant. I'd like to change that to (for run(4)) > >> if_transmit -> driver_tx -> usb_queue -> usb_stack > >> > >> > >> AK > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to > >> "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 8 10:15:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70DDF106566B for ; Mon, 8 Oct 2012 10:15:12 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2858C8FC14 for ; Mon, 8 Oct 2012 10:15:12 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so5052423vbm.13 for ; Mon, 08 Oct 2012 03:15:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=W7qvbsM7D3ZuwO8P5SjHiqApIbJMUShp57+dziAPXKs=; b=VB2eZP0yNX347UwMFH2y9eCDUz/X8CdJCbriajvFzBDKlIR48yekDfR745vNlNyDNf wn3BhUXa1X+tISyLqM6pynREPet6fMJ4ukIEaqYUEwjgskBQ6FlBhgJPxH1TnCNs54C3 HT7Qo+n6xHmbvfv0ULbXNWmSkDvTRvZe/2SA1oDxuypGk4QjTNfNzH7RRTonvNLU5JYG yhyQiV8ao8TxskHLhmMJbB3Y1EsGFgxhbSfZ58u2kx48L1DHazf48SMjnZeb66OUYlM1 06d3mphmdMnX/mjF3yudEgbs9O1Q3D4fo1KhBdi7/ZURnmB2+ks8tuDjynhGMsUCsIU4 iR9A== MIME-Version: 1.0 Received: by 10.220.150.145 with SMTP id y17mr9460656vcv.11.1349691311255; Mon, 08 Oct 2012 03:15:11 -0700 (PDT) Received: by 10.220.141.82 with HTTP; Mon, 8 Oct 2012 03:15:11 -0700 (PDT) X-Originating-IP: [95.97.75.178] Date: Mon, 8 Oct 2012 12:15:11 +0200 Message-ID: From: Sven Hazejager To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkx/8+176BG5tbzXraBtiNqQKoDBMqPyrD6HjV55KrtiGvge1MU8Ej/ftEY/p5YtlPvqjPh Subject: Spectrum analysis? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 08 Oct 2012 10:15:12 -0000 Is there a way to do a spectrum analysis for the wifi band with ath on CURRENT? I would like to understand which channels give me the best signal/noise ratio (my baby monitor completely blows our wifi away) above and beyond other 802.11 activities. Does not need to be fast. Mikrotik has something like this; they use standard Wifi equipment to analyze 20MHz at a time with 10MHz increments, creating a nice heat map of the available spectrum... Thanks! From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 8 11:07:33 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 242371065687 for ; Mon, 8 Oct 2012 11:07:33 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0D4768FC12 for ; Mon, 8 Oct 2012 11:07:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q98B7W6i029514 for ; Mon, 8 Oct 2012 11:07:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q98B7WC1029512 for freebsd-wireless@FreeBSD.org; Mon, 8 Oct 2012 11:07:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Oct 2012 11:07:32 GMT Message-Id: <201210081107.q98B7WC1029512@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 08 Oct 2012 11:07:33 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171394 wireless [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 129 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 8 16:09:19 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CBE491065673 for ; Mon, 8 Oct 2012 16:09:19 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2CA8FC08 for ; Mon, 8 Oct 2012 16:09:19 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so4626863pbb.13 for ; Mon, 08 Oct 2012 09:09:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=U74Cv/9UJnoHyiLP/d9+STUEai5viEZ1vlHiembOeF8=; b=HB6NNqUJ6NmWBEkZzEMxa3S44tlQq/+3m/ukWkoertJj/CqOQA7JzxwIYFcrAjTND2 CO3MzrtcSlhOq0Mu4aQzlbDtAKUdSTUpC/pyJg5p+eKyum5OYuBO3ipbloQt+An25mw3 s5SNasYNtdxdIFrpP/AZ/WZIkD8qo8A0Z3bb4FqcalctUbgUnIFKJ0cO4Z32359DR4U4 UVHZlS8h5KRVCpGANGxte55jbtPuUVQL31T9wD2Uq3p0uasFLK5VcO0QphcZFXXe0eUk 8m/uki28bzPkXNMAgZBohNTJYZi1Reug3Sr9eABVV2+0IP+u9gZBWfegS96qwtElr/Rz HyNQ== Received: by 10.66.77.199 with SMTP id u7mr32064525paw.7.1349712554714; Mon, 08 Oct 2012 09:09:14 -0700 (PDT) Received: from bakeneko.local (gateway.northcoasths.com. [69.12.252.2]) by mx.google.com with ESMTPS id o7sm7797974pay.14.2012.10.08.09.09.12 (version=SSLv3 cipher=OTHER); Mon, 08 Oct 2012 09:09:13 -0700 (PDT) Message-ID: <5072FA32.8030905@gmail.com> Date: Mon, 08 Oct 2012 09:07:14 -0700 From: matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.7) Gecko/20120913 Thunderbird/10.0.7 MIME-Version: 1.0 To: Sven Hazejager References: In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: Spectrum analysis? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 08 Oct 2012 16:09:19 -0000 On 10/08/12 03:15, Sven Hazejager wrote: > Is there a way to do a spectrum analysis for the wifi band with ath on > CURRENT? I would like to understand which channels give me the best > signal/noise ratio (my baby monitor completely blows our wifi away) > above and beyond other 802.11 activities. Does not need to be fast. > Mikrotik has something like this; they use standard Wifi equipment to > analyze 20MHz at a time with 10MHz increments, creating a nice heat > map of the available spectrum... > > Thanks! > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" Kismet in ports has a view mode which does this fairly well. Matt From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 8 18:58:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7D6F106564A for ; Mon, 8 Oct 2012 18:58:52 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6EF288FC0C for ; Mon, 8 Oct 2012 18:58:52 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so13261529iea.13 for ; Mon, 08 Oct 2012 11:58:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kABNt6QyGrMVM1qQZfbzMOqlq0bhILxkl2VMoU8Oe1g=; b=Ksfzw+UUhcMAvKOGxxZE7SliFvOHV7u1g/UM/LcvH9q0l9BQ7Q52WsFKRF/1LwAUcO fsOxjOp9fCcybMi7PFSBWWK2/OmaOVOebG+nQ/jbN1FEhTgYnxHvpXL8Ct9vgLs0dqPN GSGRg+IsIVlVGmDq2IpsowLGAnsjblqy0kIKAnurUMBBbn2tolxKM2CqxEPdbcl8kYVw qzpLClnpljwVzRnIqa1rz8AfLYkXRdV0eKgc23sc06ZgRsGufV3p8jIIjKRr53zY4h+R uad3XWAkUtJjIguJHnatMLQpNI0DVP3JF/v6DKas1Y4bkzGosmqpVIWbFp71VdL10a+H C+Vg== MIME-Version: 1.0 Received: by 10.50.216.234 with SMTP id ot10mr9074472igc.71.1349722731619; Mon, 08 Oct 2012 11:58:51 -0700 (PDT) Received: by 10.64.72.135 with HTTP; Mon, 8 Oct 2012 11:58:51 -0700 (PDT) In-Reply-To: <5072FA32.8030905@gmail.com> References: <5072FA32.8030905@gmail.com> Date: Mon, 8 Oct 2012 14:58:51 -0400 Message-ID: From: Outback Dingo To: matt Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Spectrum analysis? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 08 Oct 2012 18:58:52 -0000 On Mon, Oct 8, 2012 at 12:07 PM, matt wrote: > On 10/08/12 03:15, Sven Hazejager wrote: >> Is there a way to do a spectrum analysis for the wifi band with ath on >> CURRENT? I would like to understand which channels give me the best >> signal/noise ratio (my baby monitor completely blows our wifi away) >> above and beyond other 802.11 activities. Does not need to be fast. >> Mikrotik has something like this; they use standard Wifi equipment to >> analyze 20MHz at a time with 10MHz increments, creating a nice heat >> map of the available spectrum... >> >> Thanks! >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > Kismet in ports has a view mode which does this fairly well. > > Matt > http://blog.brixandersen.dk/2006/12/14/wi-spy-spectrum-analyzer-usable-under-freebsd/ Wi-Spy USB 2.4 Ghz Spectrum Analyzer, I believe the software builds on FreeBSD Ive used an application called Insidder also from Metageek, it was available for linux, theres also a window, mac and android version _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 8 11:07:33 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 242371065687 for ; Mon, 8 Oct 2012 11:07:33 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0D4768FC12 for ; Mon, 8 Oct 2012 11:07:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q98B7W6i029514 for ; Mon, 8 Oct 2012 11:07:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q98B7WC1029512 for freebsd-wireless@FreeBSD.org; Mon, 8 Oct 2012 11:07:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Oct 2012 11:07:32 GMT Message-Id: <201210081107.q98B7WC1029512@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 08 Oct 2012 11:07:33 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171394 wireless [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 129 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 10 02:52:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 460A415B for ; Wed, 10 Oct 2012 02:52:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 130608FC0A for ; Wed, 10 Oct 2012 02:52:52 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so68753pad.13 for ; Tue, 09 Oct 2012 19:52:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sem44+tFfobLJZ/75vMznkUr/x1Ya5oH16pSj1jK56U=; b=jOnnEgyuurQuQ1xQsqwqns+RAd8AgvKo9+U2fCzYr8y3SSeU1yxwWIKzE0ky1fRQmh BQEH2uQJEY+VHD3Zse++1LRtrpPtHyyWvjBPTc1fHmJANZ6Cq5iM388UrPYjO7Ls75zM DYZ/B/7UOSbmpj+IJw2fl/aPjLSCmSAGX8o3GqKjhy7s7b0VisNDkWhgXoJ9i+6uTdfA 6tInDYIqyATsOa4DSIVCrFuKB+J2fwSTaH9aK95++6uD/CnXJzPjJHlY9hEIz8Cipew2 ag/TEA2+bdwU4Oz3xnef+9xxVpR9C5R1hs3DbuJ3s2ciSHMRdjcJLvx0lMZ2+N205ZER vLSg== MIME-Version: 1.0 Received: by 10.68.202.6 with SMTP id ke6mr68808254pbc.82.1349837572333; Tue, 09 Oct 2012 19:52:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.223.136 with HTTP; Tue, 9 Oct 2012 19:52:52 -0700 (PDT) In-Reply-To: References: <5072FA32.8030905@gmail.com> Date: Tue, 9 Oct 2012 19:52:52 -0700 X-Google-Sender-Auth: MUhPss8bTmSpG9opK9EodtU6xks Message-ID: Subject: Re: Spectrum analysis? From: Adrian Chadd To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org 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, 10 Oct 2012 02:52:53 -0000 The AR9280 and later chips have the ability to access spectral FFT information; but it's not yet in the open source driver. I'll make noise if/when that happens. :) adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 10 14:27:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 96A8611C; Wed, 10 Oct 2012 14:27:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5A5018FC14; Wed, 10 Oct 2012 14:27:41 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so821215pbb.13 for ; Wed, 10 Oct 2012 07:27:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Xkj3eV5vbtfOxnlq74kppt18cXiigH66wUaYmhsj00Y=; b=twcw+c/N2tI+rgD4r4HElOxJBgUI3uVwmEkD5g47iNl7YWi1Gt7MVPG1h1WjKd9y8Y lc+m8gPEe56J0t3hu0hUr7+ndiyaCdN3uj9uC3LCI7oKL6MmoqF1X9/EGAAZhTwkK2A6 U2IlaGu/ZZMBr3trx056DUbTgkInRFX3d671yMgVnhgKSYVuUkbEpwROHhhhdHqBZ9H3 LzAmS0czwHueVMmKU3Dxeg7lePPLScScvv7VsDsqB7vzBtzvvNa1wRaZ2y1Wt14DbBsa F4W5RCywN0n82/HJ3bnmzsz+A3pRyTnkU3KSCAosYXss4ooPtLpfv08Ggd3rVFxGmNBV i74g== MIME-Version: 1.0 Received: by 10.66.89.37 with SMTP id bl5mr63311822pab.55.1349879260878; Wed, 10 Oct 2012 07:27:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.223.136 with HTTP; Wed, 10 Oct 2012 07:27:40 -0700 (PDT) In-Reply-To: <86txu277vn.fsf@venux.xbsd.name> References: <86ehl96o4i.fsf@venux.xbsd.name> <86y5jfye1u.fsf@venux.xbsd.name> <86txu277vn.fsf@venux.xbsd.name> Date: Wed, 10 Oct 2012 07:27:40 -0700 X-Google-Sender-Auth: LLPfvK5-UdmWUh7IUaSBIqJpZwo Message-ID: Subject: Re: What driver should I use for 'intel centrino wireless-N 2200 BGN' ? From: Adrian Chadd To: Kevin Oberman , Andreas Nilsson , freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org 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, 10 Oct 2012 14:27:41 -0000 No, just give Bermhard time to see and reply :) adrian On 10 October 2012 06:51, Denise H. G. wrote: > > On 2012/10/10 at 12:32, Kevin Oberman wrote: >> >> On Tue, Oct 9, 2012 at 6:23 AM, Denise H. G. wrote: >>> >>> On 2012/10/09 at 00:44, Kevin Oberman wrote: >>>> >>>> On Mon, Oct 8, 2012 at 9:36 AM, Andreas Nilsson wrote: >>>>> On Mon, Oct 8, 2012 at 2:21 PM, Denise H. G. wrote: >>>>> >>>>>> Hi list, >>>>>> >>>>>> I tried ipw, iwn, and iwi, but ended up with no luck. What's more, it >>>>>> seems that the wireless adapter has not been even detected by the >>>>>> system. I ran 'pciconf -l' and got this line which seems to be my >>>>>> wireless adapter: >>>>>> >>>>>> none3@pci0:3:0:0: class=0x028000 card=0x42228086 chip=0x08918086 >>>>>> rev=0xc4 hdr=0x00 >>>>>> >>>>>> Is there a driver for that under FreeBSD 9.1-PRERELEASE? >>>>>> >>>>>> Thanks! >>>>>> >>>>> >>>>> Man page for iwi says >>>>> The iwi driver provides support for Intel PRO/Wireless 2200BG/2915ABG >>>>> >>>>> Do you have legal.intel_iwi.license_ack=1 in loader.conf ? >>>>> >>>>> Perhaps you need to check if the device id is listed in the source code? >>>> >>>> Yes. Some vendors (e.g. Lenovo, HP) have private PCIIDs on their >>>> cards, so they may not be in the source. Adding them is trivial, but, >>>> should this be the issue, please open a PR to have it added to the >>>> source in SVN. >>> >>> I tried to add some device ids into the source code of the drivers, but >>> with no luck. Maybe I am doing it the wrong way. >> >> The card ID in the code is 4220 and yours has is 4222. Edit >> /sys/dev/iwi/if_iwi.c and add: >> { 0x8086, 0x4222, "Intel(R) PRO/Wireless 2200BG" }, >> after line 123. >> >> If you are loading the module, you can just rebuild that. Otherwise >> you will need to rebuild the kernel. If you are not familiar with >> building a module, rebuilding the whole thing, kernel and modules, is >> probably the best idea. >> >> Note that I don't currently have any 2200BG card, so I have not done >> any testing. I looked at the pci.ids file and it does not seem to have >> an entry for 0x4220, but does have one for 0x4222, so I am a bit >> confused, but the pci.ids file is not relevant to the driver. It's >> just an oddity. > > Thanks for your help. I've added the card's id to if_iwn.c and rebuilt > the kernel. When system boots, the card is recognized. But the driver > says it cannot load the firmware for this specific card. I guess more > work is to be done to get this card running. > > I took a look at the code in if_iwn.c. It seems it is pretty hard coded > for the known cards. If a new card is to be supported, much work may be > needed to do it. > > Anyway, thank you. I think I might need a USB wireless solution now. > >> -- >> R. Kevin Oberman, Network Engineer >> E-mail: kob6558@gmail.com >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 10 19:28:29 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D2465BA0 for ; Wed, 10 Oct 2012 19:28:29 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 782D18FC0C for ; Wed, 10 Oct 2012 19:28:28 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fw7so1567987vcb.13 for ; Wed, 10 Oct 2012 12:28:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=d4v15B7y5bjJCUrBrg86NKFXrZJxTdZmtROFObpvfeQ=; b=cfptyZwMozs5NVCjeg0frkGObZEiT0sPPkHs8d9JPTD4dSgJkrIgu7XQ+QtvXxV5yA vtHeb9lhb/pbTj9SmpZ5Ocv/KYAph1C+d9YQeHMwgP7GoybzDa/lKhsr5rhqjK7+ABCH 8jBjOUabkciHqdx8NCFf29sYsHpkXhlGkK2N/bktPZ1zRmFidaa+WW4IFGZf81QgCMsx sdT3+fNyYFxEtJIGQjyIjVZm524faUQzIOa5LBS4l3/zqFyOes68ATuDrQjDQJCA5YS3 aSQcf+/zCUd0IRJjHNj+190NbpE8SPjbcAgqd76psaCU4Cpyr1+J+IkjafVKt2XTfMoW Uflg== MIME-Version: 1.0 Received: by 10.52.29.233 with SMTP id n9mr3758344vdh.30.1349897307433; Wed, 10 Oct 2012 12:28:27 -0700 (PDT) Received: by 10.220.141.82 with HTTP; Wed, 10 Oct 2012 12:28:27 -0700 (PDT) X-Originating-IP: [212.123.177.47] In-Reply-To: References: <5072FA32.8030905@gmail.com> Date: Wed, 10 Oct 2012 21:28:27 +0200 Message-ID: Subject: Re: Spectrum analysis? From: Sven Hazejager To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnWg5aSB3+UUowmRT7nCXe5kOKpRUKYgr36X06fXWPROCXKNsTdfKYA5xKGWppSNUmznaGB Cc: freebsd-wireless@freebsd.org 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, 10 Oct 2012 19:28:29 -0000 On Wed, Oct 10, 2012 at 4:52 AM, Adrian Chadd wrote: > The AR9280 and later chips have the ability to access spectral FFT > information; but it's not yet in the open source driver. Bummer, I'm on an AR9160. Is there a simple way to show noise levels for each channel? That should give me the information I need... Thanks! From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 11 14:01:25 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DCE6FC88 for ; Thu, 11 Oct 2012 14:01:25 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2D38FC17 for ; Thu, 11 Oct 2012 14:01:25 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b4c8:3cd0:d54b:d17c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 6FE954AC2D; Thu, 11 Oct 2012 18:01:16 +0400 (MSK) Date: Thu, 11 Oct 2012 18:01:00 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1545199746.20121011180100@serebryakov.spb.ru> To: Outback Dingo Subject: Re: Spectrum analysis? In-Reply-To: References: <5072FA32.8030905@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org 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: Thu, 11 Oct 2012 14:01:25 -0000 Hello, Outback. You wrote 8 =EE=EA=F2=FF=E1=F0=FF 2012 =E3., 22:58:51: OD> Wi-Spy USB 2.4 Ghz Spectrum Analyzer, I believe the software builds on = FreeBSD It is not true Spectrum Analyzer. It is 2.4Ghz modem, sampled for each channel's RSSI in round-robin algorithm (256 channels for full 2.4Ghz diapason, maybe less), with large delays (as modem need to be resetted on channel change). It is very cheap hardware with very inaccurate results :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 12 16:51:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FA36E40 for ; Fri, 12 Oct 2012 16:51:41 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF408FC14 for ; Fri, 12 Oct 2012 16:51:41 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:b4c8:3cd0:d54b:d17c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 07FC94AC31 for ; Fri, 12 Oct 2012 20:51:33 +0400 (MSK) Date: Fri, 12 Oct 2012 20:51:17 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1659340494.20121012205117@serebryakov.spb.ru> To: freebsd-wireless@freebsd.org Subject: r241483 ath can not be built MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Fri, 12 Oct 2012 16:51:41 -0000 Hello, Freebsd-wireless. Can not build fresh sources on i386: /data/src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_handoff_hw': /data/src/sys/dev/ath/if_ath_tx.c:812: error: 'qbusy' undeclared (first use in this function) /data/src/sys/dev/ath/if_ath_tx.c:812: error: (Each undeclared identifier is reported only once /data/src/sys/dev/ath/if_ath_tx.c:812: error: for each function it appears in.) -- // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 13 06:15:12 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8220FBAA; Sat, 13 Oct 2012 06:15:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4E5DF8FC08; Sat, 13 Oct 2012 06:15:12 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1786098dad.13 for ; Fri, 12 Oct 2012 23:15:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=d+xYimUDCnWnth6WiUyyQ61nkLX89twQxmxJIWgNFAg=; b=T3qlQQ3d/k8jozfcIBIK+ahuKlGY1elSNyzUyozLUfpOay0pn3FQkmxd7+VOPy5q9y obyauNVIRxtx+TUONAHnlddUpGrznHSvKNT1/zcMQsGMz2E9hrwYOfoEb59G7f+wmmEa JjliQgGcP+WVMunaV77W0NRcy0tQQ00M/aPaijGcZkk192tnM5LKtMT4obfWoD+vqj2u IMiyqkX8EjntmEN15XUF3NMfFHjLEaGw8SJoIhdWO8YZdQRJOHUBJ023HuysTvNgtLgO VWE7cuwmsq/fZarjJ9Ow820r5wuUxnr/EJod5IzT1cny0eQ1JbJvDnMnalN3aTqDjNcN bswg== MIME-Version: 1.0 Received: by 10.68.135.168 with SMTP id pt8mr20308008pbb.24.1350108911727; Fri, 12 Oct 2012 23:15:11 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Fri, 12 Oct 2012 23:15:11 -0700 (PDT) In-Reply-To: <1659340494.20121012205117@serebryakov.spb.ru> References: <1659340494.20121012205117@serebryakov.spb.ru> Date: Fri, 12 Oct 2012 23:15:11 -0700 X-Google-Sender-Auth: Lam5NaoamsnGZZcFPjUpVrCO9YY Message-ID: Subject: Re: r241483 ath can not be built From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org 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: Sat, 13 Oct 2012 06:15:12 -0000 oh ugh, that's the TDMA-build breakage. I'll fix that tomorrow. Sorry, adrian On 12 October 2012 09:51, Lev Serebryakov wrote: > Hello, Freebsd-wireless. > > > Can not build fresh sources on i386: > > /data/src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_handoff_hw': > /data/src/sys/dev/ath/if_ath_tx.c:812: error: 'qbusy' undeclared (first use in this function) > /data/src/sys/dev/ath/if_ath_tx.c:812: error: (Each undeclared identifier is reported only once > /data/src/sys/dev/ath/if_ath_tx.c:812: error: for each function it appears in.) > > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 13 22:24:41 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90C20E09; Sat, 13 Oct 2012 22:24:41 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 6104D8FC0C; Sat, 13 Oct 2012 22:24:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9DMOfse090842; Sat, 13 Oct 2012 22:24:41 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9DMOfkc090838; Sat, 13 Oct 2012 22:24:41 GMT (envelope-from linimon) Date: Sat, 13 Oct 2012 22:24:41 GMT Message-Id: <201210132224.q9DMOfkc090838@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/172661: hostapd(8) securing wireless adapter in HostAP mode is started too late 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: Sat, 13 Oct 2012 22:24:41 -0000 Old Synopsis: hostapd securing wireless adapter in HostAP mode is started too late New Synopsis: hostapd(8) securing wireless adapter in HostAP mode is started too late Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Oct 13 22:24:20 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=172661 From owner-freebsd-wireless@FreeBSD.ORG Sat Oct 13 22:26:04 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC3D3E7E; Sat, 13 Oct 2012 22:26:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id AD0088FC08; Sat, 13 Oct 2012 22:26:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9DMQ4md090902; Sat, 13 Oct 2012 22:26:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9DMQ4nL090898; Sat, 13 Oct 2012 22:26:04 GMT (envelope-from linimon) Date: Sat, 13 Oct 2012 22:26:04 GMT Message-Id: <201210132226.q9DMQ4nL090898@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/172672: [ubt] Bluetooth device recognised but not working 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: Sat, 13 Oct 2012 22:26:04 -0000 Old Synopsis: Bluetooth device recognised but not working New Synopsis: [ubt] Bluetooth device recognised but not working Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Oct 13 22:25:28 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=172672