ugh, I wonder why 11n is not working for you. hm. ;(
On Wed, 12 Dec 2018 at 13:30, Volodymyr Kostyrko wrote:
> On 21.11.18 18:50, Volodymyr Kostyrko wrote:
> > On 21.11.18 18:29, Adrian Chadd wrote:
> >> what's a channel survey give? is it on a very busy channel? Is t
what's a channel survey give? is it on a very busy channel? Is there a
On Wed, 21 Nov 2018 at 07:28, Volodymyr Kostyrko wrote:
> On 16.11.18 00:02, Adrian Chadd wrote:
> > ok, interesting. I'll see if I can reproduce it later next week. I
ok, interesting. I'll see if I can reproduce it later next week. I haven't
changed much on the AR9220 HAL...
On Thu, 15 Nov 2018 at 14:01, Volodymyr Kostyrko wrote:
> On 15.11.18 23:31, Adrian Chadd wrote:
> > Hi!
> > 11-stable to 12-stable shouldn't have res
11-stable to 12-stable shouldn't have resulted in a regression?
interesting, okay. Which devices are they?
On Thu, 15 Nov 2018 at 12:56, Volodymyr Kostyrko wrote:
> I'm not quite sure what happens so I'll just dump here what I have in
> mind so it would be easier to
yeah, that we'll have to look into..
On Mon, 12 Nov 2018 at 13:33, tech-lists wrote:
> On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote:
> >If it's showing up like that then it's not an AR9170 device; it's a
> >broadcom firmware device. :(
> yeah. In
If it's showing up like that then it's not an AR9170 device; it's a
broadcom firmware device. :(
On Mon, 12 Nov 2018 at 12:08, tech-lists wrote:
> freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now
> with amd64 r340354.
> I have a Netgear WNDA3100
it should be fine; have you loaded if_ath_pci and the rest of the ath
driver bits? (ath_hal, ath_hal_ar5416, ath_hal_ar9280) ?
On Sat, 3 Nov 2018 at 15:55, Volodymyr Kostyrko wrote:
> I have this card:
> ath0@pci0:4:5:0:class=0x028000 card=0x2093168c
It'd be interesting to figure out how much each step is taking. Eg, USB
detect, firmware load, create interface, bstart wpa_supplicant, etc - that
should be quick. I wonder if scan is taking forever..
On Tue, 30 Oct 2018 at 16:03, Yuri wrote:
> I just measured: 20-40 seconds elapse between the
ok, hm. So, I wonder if there are some issues with the busdma code. Boot
your test device with say, 1G of memory instead (there's some boot hint you
can set that limits physical memory) which should avoid things like 64 bit
bounce buffer stuff into 32 bit memory space. Booting with 1G
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
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.
On Sat, 28 Jul 2018 at 17:13, Farhan
options INTRNG" to my kernel config, so that this "Unimplemented
> nexus_teardown_intr" code path isn't taken, but now I get several errors
> during compilation, so I guess that was a mistake.
> On 18-07-04 16:39:42, Adrian Chadd wrote:
You should also load ath_hal_ar5212 and ath_hal_ar5416. That should do it!
On Wed, 4 Jul 2018 at 13:10, Piotr Kubaj via freebsd-wireless
> Hi all,
> what are the kernel modules necessary for running AR9132 card (present on
> TL-WR1043ND v1.x)?
> I'm currently loading
And Tim - is this really mini-pci? or is it mini-pcie? (can you take a
On Mon, 21 May 2018 at 13:34, Adrian Chadd <adrian.ch...@gmail.com> wrote:
> warner says "pcie interrupts aren't shared." :-)
> So why is this working? You're saying this is
warner says "pcie interrupts aren't shared." :-)
So why is this working? You're saying this is a mini-pci slot?
Would you please file a PR so we can get some more eyeballs on this? thanks!
On Mon, 21 May 2018 at 12:55, Tim Chase wrote:
> I've been
It sounds like you need to ignore it!
On Mon, 14 May 2018 at 09:48, Farhan Khan wrote:
> Hi all,
> I have a question regarding catching an unhandled C2H event interrupt.
> rtwn(4) receives C2H interrupts from the device. One type
> is R92C_C2H_EVT_DEBUG as defined
018-05-02 23:21, Adrian Chadd wrote:
> > > CAn you try booting freebsd-head and see if it's any better?
> > At your advice, I created a boot image of 12.0-CURRENT r333017 but
> > see the same "could not map interrupt" in my dmesg that I got on
I'm not sure. It should be able to map it as a shared interrupt because
plenty of things could be downstream of that using a legacy interrupt. I
wonder if it's being mapped as a shared interrupt.
CAn you try booting freebsd-head and see if it's any better?
3:35:51PM -0700, Adrian Chadd wrote:
>> Try disabling 11n and see if that fixes it?
> Thanks, but that doesn't seem to do it.
> I changed the "ifconfig_wlan0" line in /etc/rc.conf from:
> ifconfig_wlan0="WPA DHCP"
Try disabling 11n and see if that fixes it?
On 4 April 2018 at 05:51, David Wolfskill wrote:
> I seem to be seeing a fair number of these, especially running head
> (at the moment, running:
> FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #149
Just do ifconfig wlan0 up - then wait; it'll do scan itself. then
"ifconfig wlan0 list scan"
On 1 April 2018 at 05:24, Alex Andrews wrote:
> Sorry, I got your contact details from the FreeBSD Wiki page for WiFi ideas.
> I am a newbie to FreeBSD
So hm, where are your patches to start getting rtl8188ee into the tree?
We can at least get the RF initialisation and device side of things in there.
On 28 March 2018 at 14:31, Farhan Khan wrote:
> Hi all,
> As discussed in the IRC channel, I finally got the
there's no support in it in open source drivers unfortunately, so we
won't have open source support in freebsd for it. Sorry :(
(broadcom didn't realise support in either brcmfmac or brcmsmac for it
On 31 January 2018 at 10:09, حبيب محمد ألأمين محمد ألهـاد
Yeah, I thought I remember some issues in the past with output handling..
On 3 January 2018 at 09:04, David Wolfskill wrote:
> As a possibly-interesting additional data point, here's what the script
> shows for another "speed" test (same URL as before), but from
So it looks like the thing that's generating the interrupt isn't being cleared.
So, what do the bits in R88EE_HIMR mean? What about HIRME? Let's
figure out which it is.
Also, is it something in C2H (the target to host event channel) that's
not being handled?
On 21 December
I'm busy and there isn't a specific maintainer!
Bug me in a couple days; we need to figure out how to enable the right
command to enable debugging the firmware messages. Hopefully we can
narrow down which firmware message its erroring out on!
So, the scan portion works a couple ways.
Firstly, the interface moves to mode IEEE80211_S_SCAN . That's when
it's looking for networks to connect to.
Secondly, it marks a FEXT or a normal flag SCAN, which says "i'm doing
scanning as well as normal receive." Think of this for example like
It looks like the NIC is retrying enough that rate control just keeps
dropping the rate. Or, the NIC isn't retrying but the rate control is
being told lies. :-)
We'll have to look at the driver to see what's going on!
Please bug us in #freebsd-wifi in efnet. :)
On 9 October 2017
gines boards Ruben
> mentioned (thank you!).
> Since I'm still researching, I'd still like to continue searching for a
> single SoC solution as well. Do you know of any SoCs that're AR9280 based?
> Thank you!
> On Fri, Sep 8, 2017 at 12:27 PM, Adrian Cha
Do you have experience with this board or do you know of anything similar
> that also supports 5 GHz?
> Thank you,
> On Fri, Sep 8, 2017 at 9:02 AM, Adrian Chadd <adrian.ch...@gmail.com> wrote:
>> For now, stick with A
For now, stick with AR9280 devices. AR9380 and later doesn't work well
due to chip design :(
On 7 September 2017 at 20:42, Goo Gle wrote:
> I'd like to test some long distance Wi-Fi links (a few kilometers) and
> heard that FreeBSD has built-in
> @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found
> #include "ah_osdep.h"
> 1 error generated.
> In file included from
> In file included from @/dev/ath/i
please do this!
On 5 September 2017 at 14:53, Kamil Choudhury
> I've had this change floating around for a while to allow hostapd(8)
> to manage multiple wireless interfaces using rc.conf...
> In rc.conf, we specify our wireless interfaces:
It's coming! Landon is going to start on the SIBA bus code and will
start on the MAC core integration. I'll then do the PHY testing!
On 3 September 2017 at 09:56, wrote:
> Is there a change to get the Broadcom Wireless BCM43228 card working? At the
>> I did not really get your question. Do you mean if other modules are
>> getting compiled properly? Won't it build the modules as part of the entire
>> buildkernel process?
>> Do you want more information about the system I am compiling it on?
Weird, is it building modules without a kernel?
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
there's no support for ity et, sorry :(
On 8 August 2017 at 18:53, Serge Suvorov via freebsd-wireless
> I want to buy an USB WiFi adapter TP_LINK TL-WN727N v4. I'd like to know
> it support FreeBSD P.S It's chipset is based on the mt7601u
For reference, we chatted on IRC.
I think it's the NIC disappearing because giving it an iP brings it
link 'up' and something in the 'up' path is causing the firmware to
crash and the NIC to disappear.
which bus is it on btw? eg, you could try 'devctl rescan pcib3' if
it's on pcib3..
I'm glad you got it working :)
I haven't done the 'mode 11n' ; I've always just specified it in the
channel configuration (eg 6:ht/20).
On 22 July 2017 at 07:40, Georg Bege wrote:
> Hi guys,
> just wanted to tell that I got it up and running.
> Rather than
QCA9377 will require ath10k to show up in freebsd-head. It's not an
11n part like the other AR93xx / AR95xx series part numbers.
On 20 July 2017 at 19:00, Da Rock
> I just got a new laptop which I went to the trouble of testing
I've updated iwm some more again. It's not quite up to date with
dragonflybsd - I've hit a merge conflict set that requires a little
So I'd appreciate some more iwm testing.
I'm about 20 patches away from getting us to iwm in DFbsd circa
January, and then I'll forward
you should just be able to configure the channel as 11:ht/20 before
you start hostapd.
On 3 June 2017 at 13:52, Pietro Sammarco via freebsd-wireless
> Hello folks.
> I am here once again trying to figure out how to enable 802.11n in HOSTAPD
> instances of hostapd.conf, one per wireless card.
> I took hint from this guy here
> Please let me know sure there be a cleaner way to do it.
> Best Regards,
> Pietro Sammarco
the TL;DR is - we do support 11n, it's just done in net80211. So no,
you don't need to tell hostapd anything special about it for now.
On 28 May 2017 at 23:11, Pietro Sammarco via freebsd-wireless
> Hello folks. I recently bought a APU2C4 for the
I still recommend sticking with the AR9280. The QCA988x 11ac stuff is
coming, but I wouldn't at all recommend trying my driver out in hostap
It's a sufficiently different card (ie requires firmware API) that it
requires a new driver.
(Do buy one to do some local testing though!)
On 22 May 2017 at 13:17, John Baldwin wrote:
> Why not have if_ath.ko just be a wrapper module that depends on everything
> like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading
> code in ifconfig still DTRT. You could name the "only the driver" module
I've been putting this off for a few years, but now I've reached a
point where I kind of need to do this.
The TL;DR is this - I'd like to break the ath driver /back/ out into
separate modules, and then have them be run-time loadable. It's part
for space savings, and part for the upcoming
if it's 3g/4g then it'll be a USB device rather than a wifi device.
We don't have a wimax stack, so just be aware if you want to also use WiMax :(
On 22 April 2017 at 00:37, Orka Edison wrote:
> Le samedi 22 avril 2017 à 09:28 +0200, Orka Edison a écrit :
AR9287/AR9227 should work fine. I even have laptops using it.
What's inyour /etc/hostapd.conf file?
On 13 April 2017 at 22:23, Chris H wrote:
> I got the feeling from all my research that this PCIe NIC
> was pretty well supported. So went out and got one. I
> The linux ath9k do not use any HAL, so does Qualcomm provide an HAL only for
> BSD ?
> - Mail original -
>> De: "Adrian Chadd" <adrian.ch...@gmail.com>
>> À: "Valentin VERGEZ" <valentin.ver...@stormshield.eu>
heh, not yet. been busy catching up on other things.
digging into rtwn/urtwn performance is on the list now though!
On 23 April 2017 at 11:05, Matthias Apitz <g...@unixarea.de> wrote:
> El día lunes, abril 17, 2017 a las 12:22:32p. m. -0700, Adrian Chadd escribió:
>> discard the first when starting to process the second.
>> So only the second SSID can establish an association.
>> It still works if the first interface handles an OPEN SSID.
>> By the way, I will soon work on HEAD and try to reprodu
there's no DFS mode publicly available for ath. Everything but the
radar detector is in freebsd-head.
Oh, if it's talking about adaptive being "transmit rate" then yes, you
can configure a static transmit rate (ifconfig wlanX ucastrate Y).
Listen before talk is normal atheros CCA. it's
at 09:16, zsolty szasz <zsolty_sz...@yahoo.com> wrote:
> Well, ifconfig wlan0 ampdu -ampdutx it's okey
> ifconfig wlan0 ampdu ampdutx -ampdurx it's not okey!
> On Monday, April 17, 2017 8:46 PM, Adrian Chadd <adr...@freebsd.org> wrote:
Good catch on wme. Maybe some configuration is wrong.
Can you do an iperf udp test in both directions and see what you find?
On Apr 17, 2017 2:38 PM, "epmak epmak" wrote:
> Ping packet loss w/Intel 2200BG (iwi) on FreeBSD 11.0
> Sorry if it’s a repost.
It looks like there are enough errors to convince amrr to drop the rate.
Ill look into it later.
On Apr 17, 2017 11:29 AM, "Matthias Apitz" <g...@unixarea.de> wrote:
El día lunes, abril 17, 2017 a las 08:49:37a. m. -0700, Adrian Chadd
> Can you paste in a few li
right track :)
> On Sunday, April 16, 2017 7:18 PM, Adrian Chadd <adrian.ch...@gmail.com>
> oh it's fine! the fact 11n fails but 11g dosn't is a good start.
> Do ifconfig wlan0 -ampdu and see if that makes a change. Clients will
> have to
Can you paste in a few lines? I'm on my cell phone atm
On Apr 17, 2017 8:27 AM, "Matthias Apitz" <g...@unixarea.de> wrote:
> El día lunes, abril 17, 2017 a las 08:20:01a. m. -0700, Adrian Chadd
> > Sorry I meant wlandebug +rate and check dmesg
Sorry I meant wlandebug +rate and check dmesg
On Apr 17, 2017 2:08 AM, "Matthias Apitz" <g...@unixarea.de> wrote:
> El día domingo, abril 16, 2017 a las 01:11:51p. m. -0700, Adrian Chadd
> > hi, sorry, was on my phone
> > * recompile w
2017 at 12:47, Matthias Apitz <g...@unixarea.de> wrote:
> El día domingo, abril 16, 2017 a las 12:22:39p. m. -0700, Adrian Chadd
>> Compile with ieeei0211 debug and then use
> How do I do that exactly? I run:
> # find /usr/src/sys/dev -exe
Compile with ieeei0211 debug and then use
On Apr 16, 2017 10:47 AM, "Matthias Apitz" wrote:
> I have some laptops and servers in my WLAN/LAN, all connected to the
> same router and same subnet 192.168.2.x; they all run the same
can someone else verify this keyboard-light control patch set is OK? I
can merge it if needed.
On 6 April 2017 at 11:17, John O. Brickley wrote:
> Hi -
> I would be very interested in hearing how that goes! The BCM4331---along
> with some fan and
I don't know of anyone actively using it, sorry. :(
On 2 April 2017 at 18:41, Kiernan Hager wrote:
> I am the not-so-proud owner of a BCM43224 wireless card, which is in my
> MacBook and, I am told, not easily replaced due to it having an odd shape.
> I am
kinda. I think 43224 is PHY-N but uses the newer internal bus
structure (not SIBA)..
On 2 April 2017 at 19:07, Kiernan Hager wrote:
> In gnu/dev/bwn/phy_n/if_bwn_phy_n_tables.c, i found this code lurking:
> /* Auto increment broken + caching issue
sorry I don't know what else is going on right now. sorry :(
On 2 April 2017 at 04:47, Trev wrote:
> Never received your post Adrian - found it in the archives ... hence the
> Trev wrote on 09/03/2017 17:55:
>> 1A, uname -a shows:
i fixed bugs in -head. please update!
On 27 March 2017 at 10:28, zsolty szasz via freebsd-wireless
> Hello people,
> I have ar9227 in hostap mode in my home server. My config is:
> wlan0: flags=8843
Did you recompile with ATH_DEBUG, AH_DEBUG, ATH_DIAGAPI?
On 27 March 2017 at 02:06, Luciano Mannucci wrote:
> On Thu, 23 Mar 2017 11:35:43 +0100
> Luciano Mannucci wrote:
>> Now I'm waiting for the hang to reappear and I'll report
I'm working on an ath10k port from linux. It'll do QCA6174 and QCA9880v2 soon.
On 23 March 2017 at 14:19, Stephen G. wrote:
> Dear FreeBSD worker,
> Thanks for giving a young future engineer a chance of working with a free
> way to configure a
That is HAL_ESELFTEST. That means that the NIC failed to self-test.
CAn you compile up tools/tools/ath/athregs and run athregs -i wlan0
when this happens?
On 22 March 2017 at 03:36, Luciano Mannucci wrote:
> Hello to everybody,
yay great progress!
On 18 March 2017 at 19:26, Farhan Khan wrote:
> That was it!!! Thank you! Wow! I have been on this for weeks now! My
> debugging output displays as follows:
> id: 8129
> hpon: Render How?
ATH_ENABLE_11N # Enable 802.11n support for AR5416
> and later
> options AH_DEBUG #Adrian Chadd
> options ATH_DEBUG #Adrian Chadd
> options ATH_DIAGAPI #Adrian Chadd
> Compiled and svned today:
CAn you try freebsd-head? I'm sure I fixed bwn enough to work in
freebsd-head. I don't know how things could've broken in freebsd-11
On 8 March 2017 at 22:55, Trev wrote:
> 1A, uname -a shows:
> FreeBSD citadel.sentry.org 11.0-STABLE FreeBSD
eless AC 3160
> Kernel driver in use: iwlwifi
> Kernel modules: iwlwifi
> Thanks! :) !
> On 5 March 2017 at 02:26, Adrian Chadd <adrian.ch...@gmail.com> wrote:
>> Which ch
Which chipset is it!
porting a driver is a big task, but it all depends on what it is!
On 4 March 2017 at 17:17, Mateusz Piotrowski <0...@freebsd.org> wrote:
> Recently, I've tried installing FreeBSD on Lenovo Yoga 3 14. It turned out
> its wireless device
hows head behaving now?
On 16 February 2017 at 14:56, Olivier Houchard wrote:
> Since r313430, the one that removed the delay after fw loading, my iwm
> device became unusable.
> When loading the module, I get :
> iwm0: mem 0xdcd0-0xdcd01fff at
> device 0.0
can you do this:
* ifconfig -v wlan0 list sta
and, compile tools/tools/ath/athstats, and run 'athstats -i wlan0'
On 26 February 2017 at 17:43, wrote:
> Hi all, I'm using FreeBSD 12-CURRENT and I get a very slow speed connection
> since when
I'm still updating our driver to pull in changes from dragonflybsd.
We're a bit behind. Once that's done, I'll email out to
freebsd-wireless@ for some more testing.
Hopefully the 8xxx series stuff will work better once the changes are in!
On 7 February 2017 at 11:23, clutton <clut...@zoho.com> wrote:
> On Sat, 2017-02-04 at 11:12 -0800, Adrian Chadd wrote:
>> thanks! please do update and let me know.
> Solved. Updating both endpoints to the latest CURRENT he
thanks! please do update and let me know.
On 4 February 2017 at 11:06, clutton <clut...@zoho.com> wrote:
> On Sat, 2017-02-04 at 10:57 -0800, Adrian Chadd wrote:
>> ok, so far it indeed looks like a block-ack window issue. Which is
>> weird, because i th
issues. It needs to be done on both the STA and AP side.
On 4 February 2017 at 10:15, clutton <clut...@zoho.com> wrote:
> They are too big for hosting now. I'll attach.
> falling time around: Sat 4 Feb 2017 20:03:29 EET
> On Sat, 2017-02-04 at 10:02 -
all of em togethe.
(I'm going to go look at the element ids that aren't being processed,
in case it's something stupid I missed.)
On 4 February 2017 at 10:00, clutton <clut...@zoho.com> wrote:
> On Sat, 2017-02-04 at 09:48 -0800, Adrian Chadd wrote:
>> ugh, uhm, redo this on th
hm! attachments are stripped. can you please put it up somewhere for download?
Is that log from the AP side?
On 4 February 2017 at 06:34, clutton wrote:
> Hi list.
> The hosts are CURRENT both AP and client, after some time of usage
> client (my laptop)
* You want to run fft_eval before you run 'start', or it'll not get any samples
* there were issues in the ar9380 HAL for spectral scan, which I fixed
* i fixed some tool/driver issues
* i fixed issues in the ath_radar_stuff github repository
So, please update tools/tools/ath,
This is an initial patch to allow drivers to handle sequence number
allocation. This is important for higher throughput because it
eliminates the need for the TX serialisation lock in net80211 for
It's only done for ath(4) right now.
The 11ac support has been slowly leaking into -HEAD as I write it. I'm
only testing STA mode right now and trying to make sure it doesn't
introduce any regressions.
If you can run -HEAD and keep up to date then please do that and let
me know if wifi goes weird for you. Again, it should be
Right, that's the known lock order issue with lagg. :(
On 23 December 2016 at 11:37, J.R. Oldroyd <f...@opal.com> wrote:
> On Fri, 23 Dec 2016 10:17:34 -0800 Adrian Chadd <adrian.ch...@gmail.com>
>> On 20 December 2016 at 08:18, J.R.
can you compile with witness and invariants? I'd like to see if its
On 20 December 2016 at 08:18, J.R. Oldroyd wrote:
> On Thu, 8 Dec 2016 17:19:26 -0500 "J.R. Oldroyd" wrote:
>> On Thu, 08 Dec 2016 21:29:32 +0200 "Andriy
I'm finally at the point where I'm happy to share my driver progress
I've been working on an ath10k port since october last year. there's
.. a lot of stuff to port, and quite a bit of the ath10k functionality
required net80211 changes. It's been a long trip but I'm happy to
Try "kldload if_iwm"
It looks like it's supported in the -HEAD driver.
On 20 December 2016 at 09:22, Philip Jocks wrote:
> Adrian asked me to e-mail my X240's pciconf -lv output, so here it is:
> hostb0@pci0:0:0:0: class=0x06 card=0x221417aa
Andriy is figuring it out with you :) It sounds like it's a key
On 12 December 2016 at 22:16, Yuri wrote:
> I created the bug report for this
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215265 since there is no
> known solution.
You're using the AR9580 in hostap mode?
On 9 December 2016 at 18:12, laszlo wrote:
> running 11.0 on a mini ITX as a router in hostap mode
> getting error messages in log
> usually once i start seeing these errors things go down hill fast, like
ry compiling with IEEE80211_DEBUG and then wlandebug +crypto +assoc +state
let's see if it's something to do with going rx deaf, or RX crypto errors :(
On 6 December 2016 at 21:47, Yuri wrote:
> This device
> ugen3.2: <802.11 n WLAN Ralink> at usbus3, cfg=0 md=HOST
it's totally possible some endian clean stuff is missing from the driver :(
On 4 December 2016 at 15:32, Oleksandr Tymoshenko wrote:
> I am trying to get Intel Centrino Wireless-N 1000 working on one of
> my ARM boards. iwn(4) recognizes it but I
On 21 November 2016 at 18:06, Adrian Chadd <adrian.ch...@gmail.com> wrote:
> all on the same band, or on different bands?
> next time, do this:
> ifconfig -v wlan0 list scan
> .. when it's happening. that way I can see how many t
nope - we're sticking with wpa_supplicant driving the wpa / 802.1x
state machine for now.
On 30 November 2016 at 00:33, Fehmi Noyan ISI via freebsd-wireless
> I have been studying OpenBSD's implementation of ifconfig utility and
... and FYI - one of them is wrong - i'll back it out once i figure
out why the FreeBSD AP side is being garbage and commit a better "spec
On 27 November 2016 at 21:29, Peter Wemm wrote:
> There were two commits in the window where src-committers@
Weird, ok. Wonder why ath(4) and my ath10k branch both see duplicate
On 27 November 2016 at 22:29, Andriy Voskoboinyk <s3er...@gmail.com> wrote:
> Mon, 28 Nov 2016 08:26:28 +0200 було написано Adrian Chadd
ok, hm. how'd we end up with duplicates?
On 25 November 2016 at 13:47, Andriy Voskoboinyk <s3er...@gmail.com> wrote:
> Fri, 25 Nov 2016 21:33:24 +0200 було написано Adrian Chadd
> 12.0-CURRENT (r308862), rtwn(4) (RTL8188CE),
I've noticed something weird lately - it seems wlan radiotap (both
802.3 and 802.11 radiotap sessions) are now doubling up on RX'ed
Has anyone seen this?
email@example.com mailing list
all on the same band, or on different bands?
next time, do this:
ifconfig -v wlan0 list scan
.. when it's happening. that way I can see how many there are and what
On 21 November 2016 at 18:05, Yuri <y...@rawbw.com> wrote:
> On 11/21/2016 18:01, Adrian Ch
1 - 100 of 1189 matches
Mail list logo