Re: Should if_urtwm be imported?

[Kevin Lo]

On Sat, May 26, 2018 at 09:19:39AM -0700, Yuri wrote:
> 
> On 05/26/18 07:14, Kevin Lo wrote:
> > Yours is RTL8821AE mPCIe chip which is not supported.
> 
> 
> Do you know is it generally hard to port the diver for the chipset 
> available for USB interface to mPCIe interface, like in this case?

Why don't you give it a go and see if it's easy or hard to port the diver?

> Yuri
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Should if_urtwm be imported?

[Kevin Lo]

On Sat, May 26, 2018 at 02:35:05AM -0700, Yuri wrote:
> 
> On 05/26/18 01:09, Kevin Lo wrote:
> > It's already committed in r307529.
> 
> 
> But for some reason it doesn't recognize my card:
> 
> none2@pci0:1:0:0:   class=0x028000 card=0xa81417aa chip=0x882110ec 
> rev=0x00 hdr=0x00
>      vendor = 'Realtek Semiconductor Co., Ltd.'
>      device = 'RTL8821AE 802.11ac PCIe Wireless Network Adapter'
>      class  = network
> 
> if_rtwn_pci.ko/if_urtw.ko/rtwn.ko are loaded (at run time).

>From r307529:
- add support for RTL8812AU / RTL8821AU chipsets

Yours is RTL8821AE mPCIe chip which is not supported.

> Yuri
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Should if_urtwm be imported?

[Kevin Lo]

On Fri, May 25, 2018 at 11:59:36PM -0700, Yuri wrote:
> 
> This driver supports RTL8812AU/RTL8821A: https://github.com/s3erios/urtwm
> 
> Should it be imported?

It's already committed in r307529.

> Yuri

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Support to wireless dongle

[Kevin Lo]

On Wed, Mar 01, 2017 at 09:03:32AM -0300, Otacílio wrote:
> 
> Dears
> 
> I have a USB dongle that I'm unable to put to work. This is the device desc:
> 
> root@squitch:/home/ota # usbconfig -u 0 -a 2 dump_device_desc
> ugen0.2:  at usbus0, cfg=0 md=HOST 
> spd=FULL (12Mbps) pwr=ON (160mA)
> 
>bLength = 0x0012
>bDescriptorType = 0x0001
>bcdUSB = 0x0201
>bDeviceClass = 0x  
>bDeviceSubClass = 0x
>bDeviceProtocol = 0x
>bMaxPacketSize0 = 0x0040
>idVendor = 0x148f
>idProduct = 0x7601
>bcdDevice = 0x
>iManufacturer = 0x0001  
>iProduct = 0x0002  <802.11 n WLAN>
>iSerialNumber = 0x0003  <1.0>
>bNumConfigurations = 0x0001
> 
> Someone can confirm that this dongle is supported?

Your dongle (chipset: MT7601U) is not yet supported by FreeBSD.

> []'s
> 
> -Otacilio

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Add support for Realtek RTL8192EU

[Kevin Lo]

On Fri, Jan 20, 2017 at 02:14:09PM +0800, Kevin Lo wrote:
> 
> On Fri, Jan 20, 2017 at 01:26:37AM +0200, Andriy Voskoboinyk wrote:
> > 
> > Thu, 19 Jan 2017 10:36:43 +0200 було написано Kevin Lo :
> > 
> > Hi Kevin,
> 
> Hi Andriy,
> 
> > thanks for the patch! few notes to it:
> > - r92c_llt_write() seems to be used only in r92c_llt_init(); so,
> > it may be called without sc->sc_llt_write indirection from it;
> > - you can set rate for beacon directly in r12a_beacon_init()
> > (it will be overridden anyway by r12a_beacon_set_rate()) and drop
> > r92e_beacon_init() wrapper.
> 
> Fixed.  Thank you for the review :)
> 
> > Are there some plans for merging it to -HEAD?
> 
> I'd like to commit it next Tuesday, thanks.

Committed as r312680.

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Add support for Realtek RTL8192EU

[Kevin Lo]

On Fri, Jan 20, 2017 at 01:26:37AM +0200, Andriy Voskoboinyk wrote:
> 
> Thu, 19 Jan 2017 10:36:43 +0200 було написано Kevin Lo :
> 
> Hi Kevin,

Hi Andriy,

> thanks for the patch! few notes to it:
> - r92c_llt_write() seems to be used only in r92c_llt_init(); so,
> it may be called without sc->sc_llt_write indirection from it;
> - you can set rate for beacon directly in r12a_beacon_init()
> (it will be overridden anyway by r12a_beacon_set_rate()) and drop
> r92e_beacon_init() wrapper.

Fixed.  Thank you for the review :)

> Are there some plans for merging it to -HEAD?

I'd like to commit it next Tuesday, thanks.

> 
> > Hi,
> >
> > This adds support for the RTL8192EU Realtek wireless chipset:
> > https://people.freebsd.org/~kevlo/rtwn-rtl8192eu.diff
> >
> > Tested in station mode with D-Link DWA-131 rev E1 on amd64.
> >
> > Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Add support for Realtek RTL8192EU

[Kevin Lo]

Hi,

This adds support for the RTL8192EU Realtek wireless chipset:
https://people.freebsd.org/~kevlo/rtwn-rtl8192eu.diff

Tested in station mode with D-Link DWA-131 rev E1 on amd64.

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: What is the best choice of USB WiFi adapter working on FreeBSD?

[Kevin Lo]

On Fri, Oct 14, 2016 at 05:12:57PM -0700, Yuri wrote:
> 
> On 10/14/2016 16:26, Andriy Voskoboinyk wrote:
> >
> > https://github.com/s3erios/rtwn ? (I'm going to commit it soon). 
> 
> 
> But these are just USB IDs. This doesn't necessarily mean they actually 
> work well?

They work well.  Please see:
https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007087.html

> Yuri

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

On Fri, Oct 14, 2016 at 03:03:41AM +0300, Andriy Voskoboinyk wrote:
> 
> Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo :
> 
> Thanks for testing! (I have got another one to simplify the process)
> Can you approve that current tree (master) works without any (new)  
> problems?

Sure.  For usb wireless adapters, they work quite well :)  Thanks.

> P.S. Known issue (present in the current driver too):
>   - the card ACKs only some frames that were sent using CCK rates
> (whilst sees all retransmissions - that can be seen in 'rx discard 'cuz  
> dup'
> counter via wlanstats)
> 
> > I tried to use https://github.com/s3erios/rtwn/tree/pci_modified,
> > still no luck.  BTW, there's a compilation error:  
> > http://pastebin.com/hCFfYVSj
> >
> > To ensure that the adapter is not faulty, I tested with the snapshots  
> > image
> > (FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4)  
> > works fine.
> >
> > Kevin
> >
> > On Tue, Oct 11, 2016 at 11:21:24PM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Tue, 11 Oct 2016 04:27:02 +0300 було написано Kevin Lo  
> >> :
> >>
> >> I have created 'pci_modified' branch to speed-up the process (RTL881*AU
> >> will
> >> not work with it for now); right now it contains (mostly) unmodified
> >> initialization path from rtwn(4) driver.
> >>
> >> If this version will work, I will revert some 'RTWN_PCI_WORKAROUND'
> >> temporary blocks until the culprit is found.
> >>
> >> > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo
> >> >> :
> >> >>
> >> >> Hi!
> >> >
> >> > Hi Andriy,
> >> >
> >> >> Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ?
> >> >
> >> > I refreshed the tree and retested it, unfortunately it's still the  
> >> same.
> >> > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog
> >> >>
> >> >> P.S. If Rx is still broken (status is always 0) try to execute
> >> >> 'ifconfig wlan0 promisc'
> >> >
> >> > It doesn't help either :(
> >>
> 
> 
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

I tried to use https://github.com/s3erios/rtwn/tree/pci_modified, 
still no luck.  BTW, there's a compilation error: http://pastebin.com/hCFfYVSj

To ensure that the adapter is not faulty, I tested with the snapshots image
(FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4) works fine.

Kevin

On Tue, Oct 11, 2016 at 11:21:24PM +0300, Andriy Voskoboinyk wrote:
> 
> Tue, 11 Oct 2016 04:27:02 +0300 було написано Kevin Lo :
> 
> I have created 'pci_modified' branch to speed-up the process (RTL881*AU  
> will
> not work with it for now); right now it contains (mostly) unmodified
> initialization path from rtwn(4) driver.
> 
> If this version will work, I will revert some 'RTWN_PCI_WORKAROUND'
> temporary blocks until the culprit is found.
> 
> > On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo  
> >> :
> >>
> >> Hi!
> >
> > Hi Andriy,
> >
> >> Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ?
> >
> > I refreshed the tree and retested it, unfortunately it's still the same.
> > Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog
> >>
> >> P.S. If Rx is still broken (status is always 0) try to execute
> >> 'ifconfig wlan0 promisc'
> >
> > It doesn't help either :(
> 
> 
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote:
> 
> Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo :
> 
> Hi!

Hi Andriy,

> Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ?

I refreshed the tree and retested it, unfortunately it's still the same.  
Here's the log: https://people.freebsd.org/~kevlo/rtl8188ce-debuglog
> 
> P.S. If Rx is still broken (status is always 0) try to execute
> 'ifconfig wlan0 promisc'

It doesn't help either :(

> > On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote:
> >>
> >> hi,
> >
> > Hi Adrian,
> >
> >> can you turn on debugging? Do you see RX frames?
> >
> > No Rx frames.  The log is pretty much the same one I sent on the list:
> > https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html
> >
> >> -a
> >
> > Thanks,
> > Kevin
> >
> >> On 1 October 2016 at 08:09, Kevin Lo  wrote:
> >> > Strange, rtwn(4) stops working.  I tried to scan for the available  
> >> network,
> >> > but it just returns empty results.
> >> >
> >> > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo  
> >> :
> >> >>
> >> >> Few more questions:
> >> >> 1) does it work with h/w encryption support? (enabled by default)
> >> >> (if 'yes' - I will remove 'hardware crypto enabled' warning).
> >> >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then  
> >> transmit
> >> >> something - if it works then AMRR will print it's current status
> >> >> periodically)
> >> >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n)
> >> >> (see r92ce_adj_devcaps() in  
> >> sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c).
> >> >>
> >> >> > It works for me, thanks :)
> >> >> >
> >> >> > Kevin
> >> >> >
> >> >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote:
> >> >> >>
> >> >> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo
> >> >> >> :
> >> >> >>
> >> >> >> Thanks for the log file,
> >> >> >>
> >> >> >> Tx 'device timeouts' should be fixed in
> >> >> >>  
> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5
> >> >> >> (currently I'm reviewing PCI-specific code to see if there are any
> >> >> >> additional
> >> >> >> issues - e.g., there are no Rx events in the log file).
> >> >> >>
> >> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk  
> >> wrote:
> >> >> >> >>
> >> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo
> >> >> >> >> :
> >> >> >> >>
> >> >> >> >> Hi,
> >> >> >> >>
> >> >> >> >> So, the driver was fully tested. Thanks!
> >> >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how  
> >> big
> >> >> >> >> the problem is?
> >> >> >> >
> >> >> >> > Sure.  Here you go
> >> >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt
> >> >> >> >
> >> >> >> > Thanks,
> >> >> >> > Kevin
> >> >> >> >
> >> >> >> >> > Hi Andriy,
> >> >> >> >> >
> >> >> >> >> > First of all, THANK YOU!  You're doing amazing work!
> >> >> >> >> > Second, I've done some testing on the following devices,
> >> >> >> downloading
> >> >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from
> >> >> >> >> > ftp.freebsd.org:
> >> >> >> >> >
> >> >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS):
> >> >> >> >> >   rtwn0:  >> 2.00/2.00,
> >> >> >> addr
> >>

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote:
> 
> hi,

Hi Adrian,

> can you turn on debugging? Do you see RX frames?

No Rx frames.  The log is pretty much the same one I sent on the list:
https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html

> -a

Thanks,
Kevin

> On 1 October 2016 at 08:09, Kevin Lo  wrote:
> > Strange, rtwn(4) stops working.  I tried to scan for the available network,
> > but it just returns empty results.
> >
> > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo :
> >>
> >> Few more questions:
> >> 1) does it work with h/w encryption support? (enabled by default)
> >> (if 'yes' - I will remove 'hardware crypto enabled' warning).
> >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then transmit
> >> something - if it works then AMRR will print it's current status
> >> periodically)
> >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n)
> >> (see r92ce_adj_devcaps() in sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c).
> >>
> >> > It works for me, thanks :)
> >> >
> >> > Kevin
> >> >
> >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo
> >> >> :
> >> >>
> >> >> Thanks for the log file,
> >> >>
> >> >> Tx 'device timeouts' should be fixed in
> >> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5
> >> >> (currently I'm reviewing PCI-specific code to see if there are any
> >> >> additional
> >> >> issues - e.g., there are no Rx events in the log file).
> >> >>
> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote:
> >> >> >>
> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo
> >> >> >> :
> >> >> >>
> >> >> >> Hi,
> >> >> >>
> >> >> >> So, the driver was fully tested. Thanks!
> >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big
> >> >> >> the problem is?
> >> >> >
> >> >> > Sure.  Here you go
> >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt
> >> >> >
> >> >> > Thanks,
> >> >> > Kevin
> >> >> >
> >> >> >> > Hi Andriy,
> >> >> >> >
> >> >> >> > First of all, THANK YOU!  You're doing amazing work!
> >> >> >> > Second, I've done some testing on the following devices,
> >> >> downloading
> >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from
> >> >> >> > ftp.freebsd.org:
> >> >> >> >
> >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS):
> >> >> >> >   rtwn0:  >> >> addr
> >> >> >> > 3> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU):
> >> >> >> >   rtwn0:  on
> >> >> >> > usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - D-Link DWA-131 (RTL8192CU):
> >> >> >> >   rtwn0:  >> >> addr
> >> >> >> > 3> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> >> >> >> >
> >> >> >> > - TP-Link Archer T4U (RTL8812AU):
> >> >> >> >   rtwn0:  on
> >> >> >> > usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R
> >> >> >> >
> >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU):
> >> >> >> >   rtwn0: <802.11n WLAN Adapter> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - RTL8188CE mini pcie:
> >> >> >> > 

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

Strange, rtwn(4) stops working.  I tried to scan for the available network,
but it just returns empty results.

On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote:
> 
> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo :
> 
> Few more questions:
> 1) does it work with h/w encryption support? (enabled by default)
> (if 'yes' - I will remove 'hardware crypto enabled' warning).
> 2) is there rate control support? (wlandebug -i wlan0 rate ; then transmit
> something - if it works then AMRR will print it's current status  
> periodically)
> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n)
> (see r92ce_adj_devcaps() in sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c).
> 
> > It works for me, thanks :)
> >
> > Kevin
> >
> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo  
> >> :
> >>
> >> Thanks for the log file,
> >>
> >> Tx 'device timeouts' should be fixed in
> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5
> >> (currently I'm reviewing PCI-specific code to see if there are any
> >> additional
> >> issues - e.g., there are no Rx events in the log file).
> >>
> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo
> >> >> :
> >> >>
> >> >> Hi,
> >> >>
> >> >> So, the driver was fully tested. Thanks!
> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big
> >> >> the problem is?
> >> >
> >> > Sure.  Here you go  
> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt
> >> >
> >> > Thanks,
> >> > Kevin
> >> >
> >> >> > Hi Andriy,
> >> >> >
> >> >> > First of all, THANK YOU!  You're doing amazing work!
> >> >> > Second, I've done some testing on the following devices,  
> >> downloading
> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from
> >> >> > ftp.freebsd.org:
> >> >> >
> >> >> > - ASUS USB-N10 NANO (RTL8188CUS):
> >> >> >   rtwn0:  >> addr
> >> >> > 3> on usbus0
> >> >> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> >> >> >
> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU):
> >> >> >   rtwn0:  on
> >> >> > usbus0
> >> >> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> >> >> >
> >> >> > - D-Link DWA-131 (RTL8192CU):
> >> >> >   rtwn0:  >> addr
> >> >> > 3> on usbus0
> >> >> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> >> >> >
> >> >> > - TP-Link Archer T4U (RTL8812AU):
> >> >> >   rtwn0:  on
> >> >> > usbus0
> >> >> >   rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R
> >> >> >
> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU):
> >> >> >   rtwn0: <802.11n WLAN Adapter> on usbus0
> >> >> >   rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> >> >> >
> >> >> > - RTL8188CE mini pcie:
> >> >> >   rtwn0:  port 0xd000-0xd0ff mem
> >> >> > 0x9080-0x90803fff irq 17 at device 0.0 on pci1
> >> >> >   rtwn0: r92ce_attach: warning: hardware crypto enabled
> >> >> >   rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R
> >> >> >
> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work:
> >> >> >
> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used
> >> >> > rtwn0: device timeout
> >> >> >
> >> >> >   Kevin
> >> >> >
> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote:
> >> >> >>
> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk
> >> >> >> :
> >> >> >>
> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn  
> >> (integrated
> >> >> >> into src tree, so it can be built with 

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

It works for me, thanks :)

Kevin

On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote:
> 
> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo :
> 
> Thanks for the log file,
> 
> Tx 'device timeouts' should be fixed in
> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5
> (currently I'm reviewing PCI-specific code to see if there are any  
> additional
> issues - e.g., there are no Rx events in the log file).
> 
> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo  
> >> :
> >>
> >> Hi,
> >>
> >> So, the driver was fully tested. Thanks!
> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big
> >> the problem is?
> >
> > Sure.  Here you go https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt
> >
> > Thanks,
> > Kevin
> >
> >> > Hi Andriy,
> >> >
> >> > First of all, THANK YOU!  You're doing amazing work!
> >> > Second, I've done some testing on the following devices, downloading
> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from
> >> > ftp.freebsd.org:
> >> >
> >> > - ASUS USB-N10 NANO (RTL8188CUS):
> >> >   rtwn0:  >> > 3> on usbus0
> >> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> >> >
> >> > - TP-Link TL-WN725N v2 (RTL8188EU):
> >> >   rtwn0:  on
> >> > usbus0
> >> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> >> >
> >> > - D-Link DWA-131 (RTL8192CU):
> >> >   rtwn0:  >> > 3> on usbus0
> >> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> >> >
> >> > - TP-Link Archer T4U (RTL8812AU):
> >> >   rtwn0:  on
> >> > usbus0
> >> >   rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R
> >> >
> >> > - D-Link DWA-171 rev A1 (RTL8821AU):
> >> >   rtwn0: <802.11n WLAN Adapter> on usbus0
> >> >   rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> >> >
> >> > - RTL8188CE mini pcie:
> >> >   rtwn0:  port 0xd000-0xd0ff mem
> >> > 0x9080-0x90803fff irq 17 at device 0.0 on pci1
> >> >   rtwn0: r92ce_attach: warning: hardware crypto enabled
> >> >   rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R
> >> >
> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work:
> >> >
> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used
> >> > rtwn0: device timeout
> >> >
> >> >  Kevin
> >> >
> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk
> >> >> :
> >> >>
> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn (integrated
> >> >> into src tree, so it can be built with 'make buildkernel' / 'make
> >> >> buildworld').
> >> >>
> >> >> This the last stage; once all reported issues will be resolved, I'm
> >> >> going to merge it into HEAD.
> >> >>
> >> >> > Hi everyone,
> >> >> >
> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were  
> >> merged
> >> >> > into a
> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the  
> >> code is
> >> >> > available on https://github.com/s3erios/rtwn repository. Among
> >> >> bugfixes /
> >> >> > code deduplication, there some new features too:
> >> >> >
> >> >> > 1) multi-vap support (one any wireless interface + one STA  
> >> interface +
> >> >> > any number of monitor mode interfaces).
> >> >> > 2) few new sysctls:
> >> >> >   * dev.rtwn.#.crypto - controls how to use hardware crypto
> >> >> acceleration
> >> >> >   * dev.rtwn.#.ratectl_selected
> >> >> >   * dev.rtwn.#.ratectl - selects current 'rate control' algorithm
> >> >> > (currently only 'none' and 'net80211' are supported; RTL8192CE  
> >> needs
> >> >> > testing
> >> >> > with the last).
> >> >> > 3) (incomplete) powe

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote:
> 
> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo :
> 
> Hi,
> 
> So, the driver was fully tested. Thanks!
> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big
> the problem is?

Sure.  Here you go https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt

Thanks,
Kevin

> > Hi Andriy,
> >
> > First of all, THANK YOU!  You're doing amazing work!
> > Second, I've done some testing on the following devices, downloading
> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from  
> > ftp.freebsd.org:
> >
> > - ASUS USB-N10 NANO (RTL8188CUS):
> >   rtwn0:  > 3> on usbus0
> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> >
> > - TP-Link TL-WN725N v2 (RTL8188EU):
> >   rtwn0:  on  
> > usbus0
> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> >
> > - D-Link DWA-131 (RTL8192CU):
> >   rtwn0:  > 3> on usbus0
> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> >
> > - TP-Link Archer T4U (RTL8812AU):
> >   rtwn0:  on  
> > usbus0
> >   rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R
> >
> > - D-Link DWA-171 rev A1 (RTL8821AU):
> >   rtwn0: <802.11n WLAN Adapter> on usbus0
> >   rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> >
> > - RTL8188CE mini pcie:
> >   rtwn0:  port 0xd000-0xd0ff mem  
> > 0x9080-0x90803fff irq 17 at device 0.0 on pci1
> >   rtwn0: r92ce_attach: warning: hardware crypto enabled
> >   rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R
> >
> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work:
> >
> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used
> > rtwn0: device timeout
> >
> > Kevin
> >
> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk
> >> :
> >>
> >> Now it resides on https://github.com/s3erios/freebsd-rtwn (integrated
> >> into src tree, so it can be built with 'make buildkernel' / 'make
> >> buildworld').
> >>
> >> This the last stage; once all reported issues will be resolved, I'm
> >> going to merge it into HEAD.
> >>
> >> > Hi everyone,
> >> >
> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged
> >> > into a
> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> >> > available on https://github.com/s3erios/rtwn repository. Among  
> >> bugfixes /
> >> > code deduplication, there some new features too:
> >> >
> >> > 1) multi-vap support (one any wireless interface + one STA interface +
> >> > any number of monitor mode interfaces).
> >> > 2) few new sysctls:
> >> >   * dev.rtwn.#.crypto - controls how to use hardware crypto  
> >> acceleration
> >> >   * dev.rtwn.#.ratectl_selected
> >> >   * dev.rtwn.#.ratectl - selects current 'rate control' algorithm
> >> > (currently only 'none' and 'net80211' are supported; RTL8192CE needs
> >> > testing
> >> > with the last).
> >> > 3) (incomplete) power management support for RTL8188EU (requires
> >> > firmware).
> >> > 4) Short Guard Interval support.
> >> >
> >> > It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; however,
> >> > it was never tested with RTL8192CE or RTL8812AU.
> >> >
> >> > How-to-build:
> >> > 1) download / checkout the repository.
> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src'
> >> > 3) build and install rtwn module:
> >> > cd $repository/sys/modules/rtwn && make && make install
> >> > 4) build and install rtwn_usb/rtwn_pci:
> >> > cd ../rtwn_usb && make && make install
> >> > cd ../rtwn_pci && make && make install
> >> > 5) unload previous && load current drivers:
> >> > kldunload if_urtwn if_rtwn
> >> > kldload /boot/modules/if_rtwn.ko /boot/modules/if_rtwn_usb.ko
> >> > /boot/modules/if_rtwn_pci.ko
> >> > 6) Use.
> >> ___
> >> freebsd-wireless@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to  
> >> "freebsd-wireless-unsubscr...@freebsd.org"
> >>
> 
> 
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Kevin Lo]

Hi Andriy,

First of all, THANK YOU!  You're doing amazing work!
Second, I've done some testing on the following devices, downloading
FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from ftp.freebsd.org:

- ASUS USB-N10 NANO (RTL8188CUS):
  rtwn0:  on 
usbus0
  rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R

- TP-Link TL-WN725N v2 (RTL8188EU):
  rtwn0:  on usbus0
  rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R

- D-Link DWA-131 (RTL8192CU):
  rtwn0:  on 
usbus0
  rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R

- TP-Link Archer T4U (RTL8812AU):
  rtwn0:  on usbus0
  rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R

- D-Link DWA-171 rev A1 (RTL8821AU):
  rtwn0: <802.11n WLAN Adapter> on usbus0
  rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R

- RTL8188CE mini pcie:
  rtwn0:  port 0xd000-0xd0ff mem 0x9080-0x90803fff irq 
17 at device 0.0 on pci1
  rtwn0: r92ce_attach: warning: hardware crypto enabled
  rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R

All seems to be ok, except RTL8188CE PCIe adapter doesn't work:

rtwn0: r92ce_post_init: warning: net80211 ratectl is used
rtwn0: device timeout

Kevin

On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote:
> 
> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk  
> :
> 
> Now it resides on https://github.com/s3erios/freebsd-rtwn (integrated
> into src tree, so it can be built with 'make buildkernel' / 'make  
> buildworld').
> 
> This the last stage; once all reported issues will be resolved, I'm
> going to merge it into HEAD.
> 
> > Hi everyone,
> >
> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged  
> > into a
> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> > available on https://github.com/s3erios/rtwn repository. Among bugfixes /
> > code deduplication, there some new features too:
> >
> > 1) multi-vap support (one any wireless interface + one STA interface +
> > any number of monitor mode interfaces).
> > 2) few new sysctls:
> >   * dev.rtwn.#.crypto - controls how to use hardware crypto acceleration
> >   * dev.rtwn.#.ratectl_selected
> >   * dev.rtwn.#.ratectl - selects current 'rate control' algorithm
> > (currently only 'none' and 'net80211' are supported; RTL8192CE needs  
> > testing
> > with the last).
> > 3) (incomplete) power management support for RTL8188EU (requires  
> > firmware).
> > 4) Short Guard Interval support.
> >
> > It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; however,
> > it was never tested with RTL8192CE or RTL8812AU.
> >
> > How-to-build:
> > 1) download / checkout the repository.
> > 2) apply 'patch-usbdevs.diff' against '/usr/src'
> > 3) build and install rtwn module:
> > cd $repository/sys/modules/rtwn && make && make install
> > 4) build and install rtwn_usb/rtwn_pci:
> > cd ../rtwn_usb && make && make install
> > cd ../rtwn_pci && make && make install
> > 5) unload previous && load current drivers:
> > kldunload if_urtwn if_rtwn
> > kldload /boot/modules/if_rtwn.ko /boot/modules/if_rtwn_usb.ko  
> > /boot/modules/if_rtwn_pci.ko
> > 6) Use.
> ___
> freebsd-wireless@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
> 
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-link wireless not detected

[Kevin Lo]

On Tue, Dec 29, 2015 at 03:02:35PM +0100, Hans Petter Selasky wrote:
> On 12/29/15 14:00, Daniel Braniss wrote:
> >
> >> On 29 Dec 2015, at 14:44, Hans Petter Selasky  wrote:
> >>
> >> On 12/29/15 13:36, Daniel Braniss wrote:
> >>>
> >>
> >> Until /etc/devd/usb.conf is regenerated, you'll need to manually load the 
> >> kernel module for urtwn. Did you do that?
> >>
> >> --HPS
> >>
> > ok, set if_urtwn_load=yes
> > and now I get:
> >
> > ugen0.4:  at usbus0
> > urtwn0:  on usbus0
> > urtwn0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
> > Fatal kernel mode data abort: 'Translation Fault (L1)' on write
> > trapframe: 0xda29fb88
> > FSR=0805, FAR=, spsr=6013
> > r0 =, r1 =, r2 =c0a72cb0, r3 =0165
> > r4 =c2cd, r5 =c0a86650, r6 =c2cd1a80, r7 =
> > r8 =c2cd1dd8, r9 =c2cd1a20, r10=c2a85dd0, r11=da29fc20
> > r12=, ssp=da29fc18, slr=0004, pc =c0a3f7cc
> >
> > [ thread pid 13 tid 100045 ]
> > Stopped at  ieee80211_ifdetach+0x4c:str r0, [r1]
> > db>
> >
> > btw, as long as you are willing to help, I will keep testing,
> > in other words, i’m ok.
> 
> Hi Andriy,
> 
> Can you fix the crash above and verify this error patch?
> 
> Andriy:
> 
> After:
>  usbd_transfer_unsetup(sc->sc_xfer, URTWN_N_TRANSFER);
> There is no need for:
>   usbd_transfer_drain(sc->sc_xfer[x]);

As I mentioned previously we don't support rtl8192eu.  One difference 
between those is the the number of endpoints and its addresses.

> --HPS
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-link wireless not detected

[Kevin Lo]

On Tue, Dec 29, 2015 at 12:12:26PM +0200, Daniel Braniss wrote:
> 
> > On 29 Dec 2015, at 11:53, Hans Petter Selasky  wrote:
> > 
> > On 12/29/15 10:42, Daniel Braniss wrote:
> >> 
> >>> On 29 Dec 2015, at 11:33, Vladimir Botka  wrote:
> >>> 
> >>> Hi Danny,
> >>> 
> >>> On Tue, 29 Dec 2015 11:16:27 +0200
> >>> Daniel Braniss  wrote:
>  Hi All,
>  I have a working tp-link usb (realtek), but can’t get a d-link(also 
>  realtek) to work.
>  usbconfig:
>   ugen0.4:  at usbus0, cfg=0 md=HOST 
>  spd=HIGH (480Mbps) pwr=ON (500mA)
>  This is on a raspberry pi running a resent current.
>  cheers & season greetings,
>   danny
> >>> 
> >>> I've added freebsd-wireless list.
> >>> 
> >>> My 2 cents. It might be helpful to see more details about the adapters.
> >>> For example:
> >>> 
> >>> # usbconfig -u 0 -a 7 dump_device_desc
> >>> ugen0.7: <802.11 n WLAN Ralink> at usbus0, cfg=0 md=HOST spd=HIGH
> >>> (480Mbps) pwr=ON (450mA)
> >>>  bLength = 0x0012
> >>>  bDescriptorType = 0x0001
> >>>  bcdUSB = 0x0200
> >>>  bDeviceClass = 0x  
> >>>  bDeviceSubClass = 0x
> >>>  bDeviceProtocol = 0x
> >>>  bMaxPacketSize0 = 0x0040
> >>>  idVendor = 0x148f
> >>>  idProduct = 0x5370
> >>>  bcdDevice = 0x0101
> >>>  iManufacturer = 0x0001  
> >>>  iProduct = 0x0002  <802.11 n WLAN>
> >>>  iSerialNumber = 0x0003  <1.0>
> >>>  bNumConfigurations = 0x0001
> >> 
> >> 
> >> so here it is:
> >> root@:~ # usbconfig -u 0 -a 4 dump_device_desc
> >> ugen0.4:  at usbus0, cfg=0 md=HOST 
> >> spd=HIGH (480Mbps) pwr=ON (500mA)
> >> 
> >>   bLength = 0x0012
> >>   bDescriptorType = 0x0001
> >>   bcdUSB = 0x0210
> >>   bDeviceClass = 0x  
> >>   bDeviceSubClass = 0x
> >>   bDeviceProtocol = 0x
> >>   bMaxPacketSize0 = 0x0040
> >>   idVendor = 0x2001
> >>   idProduct = 0x3319
> >>   bcdDevice = 0x0200
> >>   iManufacturer = 0x0001  
> >>   iProduct = 0x0002  
> >>   iSerialNumber = 0x0003  <00e04c01>
> >>   bNumConfigurations = 0x0001
> >> 
> >> thanks,
> >>danny
> >> 
> > 
> > Did you google the idVendor and idProduct values and see if Linux has a 
> > driver already?
> > 
> > —HPS
> > 
> 
> 
> https://github.com/Mange/rtl8192eu-linux-driver/blob/master/os_dep/linux/usb_intf.c
>  
> 
> and look at line 216

Your device (D-Link DWA-131 rev E1) is rtl8192eu, which is not supported by
FreeBSD.

> danny

Kevin
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn and hostap

[Kevin Lo]

On Thu, Sep 17, 2015 at 01:39:30AM -0500, Matthew Grooms wrote:
> Seems to behave better now and hostap appears to be working ...
> 
> #ifconfig wlan0 create wlandev urtwn0 wlanmode hostap
> #ifconfig wlan0 list caps
> drivercaps=2181c401
> 
> #ifconfig wlan0 up ssid freebsdap mode 11g channel 1
> #ifconfig bridge0 create up addm em0 addm wlan0
> 
> #ifconfig wlan0
> wlan0: flags=8943 metric 
> 0 mtu 1500
>  ether 00:c3:e1:16:11:32
>  nd6 options=29
>  media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
>  status: running
>  ssid freebsdap channel 1 (2412 MHz 11g) bssid 00:c3:e1:16:11:32
>  country US authmode OPEN privacy OFF txpower 0 scanvalid 60
>  protmode CTS dtimperiod 1 -dfs
>  groups: wlan
> 
> #ifconfig bridge0
> bridge0: flags=8843 metric 0 mtu 
> 1500
>  ether 02:df:20:d2:42:00
>  nd6 options=1
>  groups: bridge
>  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>  member: wlan0 flags=143
>  ifmaxaddr 0 port 3 priority 128 path cost 370370
>  member: em0 flags=143
>  ifmaxaddr 0 port 1 priority 128 path cost 2
> 
> The speed leaves a lot to be desired. Throughput for the associated host 
> is typically about 2Mbit down and 6Mbit up. I'm assume that's indicative 
> of a problem. Occasionally I also see the this message on the console 
> when I'm bringing the adapter up ...
> 
> wlan0: ieee80211_new_state_locked: pending INIT -> SCAN transition lost
> 
> If I down and up the adapter again, it seems to correct itself. Not sure 
> what that's all about. I am passing the USB adapter through to a VM 
> inside of ESXi to test the patch, so maybe that has something to do with 
> these quirks. I'll try to run some tests with the adapter associated to 
> a physical AP tomorrow to get a baseline.

I knew OpenBSD had patches about hostap support for urtwn(4), but those
don't look quite right.  I think that's why OpenBSD developers didn't 
commit them.  BTW, NetBSD adopted OpenBSD's patches, I tested it on NetBSD
about four months ago, the connection was not stable...

> Thanks,
> 
> -Matthew

Kevin

> On 9/16/2015 11:24 AM, Adrian Chadd wrote:
> > The only one to look at is ath(4). I've not fixed/hacked on any other
> > hostap chips. :)
> >
> > if_ath_beacon.c has the logic - it gets a reference when creating a
> > beacon frame.
> >
> >
> >
> > -adrian
> >
> >
> > On 16 September 2015 at 09:21, Matthew Grooms  wrote:
> >> On 9/16/2015 10:58 AM, Adrian Chadd wrote:
> >>> I think the net80211 beacon create routine doesn't allocate a node
> >>> ref. Yeah, it doesn't. You have to do ieee80211_ref_node() after
> >>> calling becaon_create(), and deref it if the tx fails. The TX success
> >>> will free the node ref for you.
> >>>
> >> Got it. I'll take another look at one of the drivers that support hostap to
> >> make sure I'm following the same pattern. Thanks again for the feedback!
> >>
> >> -Matthew
> >>
> >>
> >>> -adrian
> >>>
> >>>
> >>> On 16 September 2015 at 04:27, Idwer Vollering  wrote:
>  2015-09-16 8:06 GMT+02:00 Matthew Grooms :
> 
> > It looks like my screenshot got scrubbed. Here is my hopefully faithful
> > transcription ...
> >
> > Fatal trap 9: general protection fault while in kernel mode
> > cpuid = 3; apic id = 03
> > instruction pointer = 0x20:0x80a01105
> > stack pointer   = 0x28:0xfe0092fe86f0
> > frame pointer = 0x28:0xfe0092fe8740
> > code segment = base 0x0, limit 0xf, type 0x1b
> >= DPL 0, pres 1, long 1, def32 0, 
> > gran
> > 1
> > processor eflags = interrupt enabled, resume, IOPL = 0
> > current process  = 716 (ifconfig)
> > [thread pid 716 tid 100082 ]
> > Stopped at  __mtx_lock_flags+0x55:  movq(%r13),%rax
> > db> bt
> > Tracing pid 716 tid 100082 td 0xff800512814d0
> > __mtx_lock_flags() at __mtx_lock_flags+0x55/frame 0xfe0092fe8740
> > ieee80211_free_node() at ieee80211_free_node()_0x38/frame
> > 0xfe0092fe8780
> > ieee80211_node_vdetach() at ieee80211_node_vdetach()+0x2d/frame
> > 0xfe0092fe87a0
> > ieee80211_vap_detach() at ieee80211_vap_detach()+0x35e/frame
> > 0xfe0092fe87d0
> > urtwn_vap_delete() at urtwn_vap_delete()+0xe/frame 0xfe0092fe87f0
> > if_clone_destroyif() at if_clone_destroyif()+0x1aa/frame
> > 0xfe0092fe8840
> > if_clone_destroy() at if_clone_destroy()0x8e/frame 0xfe0092fe8860
> > kern_ioctl() at kern_ioctl()+0x230/frame 0xfe0092fe88c0
> > sys_ioctl() at sys_ioctl()+0x153/frame 0xfe0092fe89a0
> > amd64_syscall() at amd64_syscall()+0x282/frame 0xfe0092fe8ab0
> > Xfast_syscall() a

Re: CTF: wpa_supplicant/hostapd 2.4 import

[Kevin Lo]

On Sun, Apr 19, 2015 at 02:35:17PM -0700, Rui Paulo wrote:
> 
> Hi,
> 
> Please test the new wpa_supplicant/hostapd.  Here's the patch against FreeBSD 
> HEAD:
> 
>   https://people.freebsd.org/~rpaulo/wpa-2.4.diff

Seems to be working fine on amd64.  Tested on ral(4) and run(4).
Thanks.

> Thanks,
> -- 
> Rui Paulo

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: "run" card (RT3071) very slow connection

[Kevin Lo]

On Thu, Nov 27, 2014 at 05:08:15PM +, Miguel Clara wrote:
> 
> I've mailing the list before about and issue with 5Ghtz which I then found
> was actually the fact that 11n is not supported on USB cards!
> 
> Still I have a 100/10 fibre connection, and I've been testing some FreeBSD
> 11-current stuff on the laptop with this card (the on-board card is not
> supported by freebsd)
> 
> I'm very close to the router and can't get a better connection than 7-8M
> download and on local speeds its not better than that (tested with iperf).
> 
> The on-board card is a Broadcom 4333 and I got better performance with this
> one (using ndis) but it crashes a lot so its not really a better option.
> 
> To be clear the card is connected to the 2.4Ghtz network which accepts
> N/G/B, I have the 5Ghtz set to N only as this is currently the only device
> at home using 2.4Ghtz.
> 
> I don't expect getting the full 54M limit but this is really poor!
> 
> What info can I post to better investigate?

We answered your question, no?
https://lists.freebsd.org/pipermail/freebsd-wireless/2014-August/004912.html

> 
> Melhores Cumprimentos // Best Regards
> ---
> *Miguel Clara*

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: problem with wifi adapter TRENDNET TEW-646UBH

[Kevin Lo]

On Tue, Nov 18, 2014 at 10:14:41PM +, bolshakov_1--- via freebsd-wireless 
wrote:
> 
> Hello.
> Wi-fi adapter TRENDNET TEW_646UBH is not determined by the system freebsd 
> 10.1. Chipset Realtek RTL8188SU, that support driver RSU. Driver in the 
> kernel is loaded. In the log dmesg adapter is defined as: ugen0.3:  0x20f4> at usbus0
> In ifconfig new connection not appear. This problem is solved as follows:
> Add to /sys/dev/usb/usvdevs   "product TRENDNET TEW_646UBH 0x646b TEW_646IBN"
> Add to /sys/dev/usb/wlan/if_rsu.s   "RSU_DEV_HT (TRENDNET, TEW_646UBH)"
> And rebuild the module.
> Please add it to the tree updates, sorry for my bad english, thanks.Some 
> info:root@localhost:~ # usbconfig
> ugen2.1:  at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) 
> pwr=SAVE (0mA)
> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) 
> pwr=SAVE (0mA)
> ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) 
> pwr=SAVE (0mA)
> ugen0.2:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
> pwr=ON (100mA)
> ugen1.2:  at usbus1, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=SAVE (0mA)
> ugen2.2:  at usbus2, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=SAVE (0mA)
> ugen0.3:  at usbus0, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=ON (500mA)
> ugen2.3:  at usbus2, cfg=0 md=HOST spd=LOW 
> (1.5Mbps) pwr=ON (100mA)
> root@localhost:~ # 

Committed as r274684, thanks.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Kevin Lo]

Argh! I think I need more coffee.  rsu(4) does support this chipset.
Sorry for the noise.

Kevin

On Tue, Nov 18, 2014 at 03:08:37PM +0800, Kevin Lo wrote:
> I'm pretty sure.  See OpenBSD cvs log:
> http://marc.info/?l=openbsd-cvs&m=128897633210060&w=2
> 
> I'll be fixing rsu(4), thanks.
> 
>   Kevin
> 
> On Tue, Nov 18, 2014 at 02:41:18PM +0800, Ben Woods wrote:
> > 
> > Actually, the rsu(4) man page mentions the RTL8191SU chipset:
> > https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4
> > 
> > And it appears to be in the code:
> > http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_rsu.c?view=markup
> > 
> > Are you sure it is not supported?
> > 
> > Regards,
> > Ben
> > 
> > 
> > --
> > From: Benjamin Woods
> > woods...@gmail.com
> > 
> > On 18 November 2014 14:21, Ben Woods  wrote:
> > 
> > > There seems to be some misalignment with the official release notes, which
> > > specifically mention the D-Link DWA-131 A1 is supported:
> > > https://www.freebsd.org/releases/10.1R/hardware.html
> > >
> > > However, according to this page it is the RTL8191SU chipset:
> > > https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
> > >
> > > Apparently the RTL8191SU chipset is supported by the OpenBSD rsu(4) 
> > > driver:
> > > http://www.undeadly.org/cgi?action=article&sid=20101216231634
> > >
> > > Regards,
> > > Ben
> > >
> > >
> > >
> > >
> > > --
> > > From: Benjamin Woods
> > > woods...@gmail.com
> > >
> > > On 18 November 2014 13:56, Kevin Lo  wrote:
> > >
> > >> The RTL8191SU chipset is not supported.
> > >>
> > >> Kevin
> > >> On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:
> > >> >
> > >> > I should mention I am running FreeBSD 10.1-RELEASE
> > >> >
> > >> >
> > >> > --
> > >> > From: Benjamin Woods
> > >> > woods...@gmail.com
> > >> >
> > >> > On 18 November 2014 13:23, Ben Woods  wrote:
> > >> >
> > >> > > Hey guys,
> > >> > >
> > >> > > I am trying to get my D-Link DWA-131 A1 working, with some success
> > >> but no
> > >> > > network connectivity.
> > >> > >
> > >> > > It shows up in my usb list with device id 07d1:3303. The driver pages
> > >> > > suggest this should be working with the rsu(4) driver and potentially
> > >> > > the rsu-rtl8712fw firmware, according to these:
> > >> > > https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4
> > >> > > http://www.undeadly.org/cgi?action=article&sid=20101216231634
> > >> > > https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
> > >> > >
> > >> > > I have added the following to /boot/loader.conf and rebooted:
> > >> > > legal.realtek.license_ack=1
> > >> > > rsu-rtl8712fw_load="YES"
> > >> > >
> > >> > > It shows up in ifconfig, and even scans and finds wireless access
> > >> points.
> > >> > > I have my WPA ssid and psk details for my access point stored in
> > >> > > /etc/wpa_supplicant.conf. I can see from ifconfig that it is trying 
> > >> > > to
> > >> > > associate with the correct access point ssid and do DHCP, but it 
> > >> > > never
> > >> > > obtains an IP address.
> > >> > >
> > >> > > Has anyone had this issue before? Anyone know how can I go about
> > >> > > troubleshooting this further?
> > >> > >
> > >> > > Regards,
> > >> > > Ben
> > >> > >
> > >> > > --
> > >> > > From: Benjamin Woods
> > >> > > woods...@gmail.com
> > >> > >
> > >> > ___
> > >> > freebsd-wireless@freebsd.org mailing list
> > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > >> > To unsubscribe, send any mail to "
> > >> freebsd-wireless-unsubscr...@freebsd.org"
> > >> >
> > >>
> > >
> > >
> > ___
> > freebsd-wireless@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> > 
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Kevin Lo]

I'm pretty sure.  See OpenBSD cvs log:
http://marc.info/?l=openbsd-cvs&m=128897633210060&w=2

I'll be fixing rsu(4), thanks.

Kevin

On Tue, Nov 18, 2014 at 02:41:18PM +0800, Ben Woods wrote:
> 
> Actually, the rsu(4) man page mentions the RTL8191SU chipset:
> https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4
> 
> And it appears to be in the code:
> http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_rsu.c?view=markup
> 
> Are you sure it is not supported?
> 
> Regards,
> Ben
> 
> 
> --
> From: Benjamin Woods
> woods...@gmail.com
> 
> On 18 November 2014 14:21, Ben Woods  wrote:
> 
> > There seems to be some misalignment with the official release notes, which
> > specifically mention the D-Link DWA-131 A1 is supported:
> > https://www.freebsd.org/releases/10.1R/hardware.html
> >
> > However, according to this page it is the RTL8191SU chipset:
> > https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
> >
> > Apparently the RTL8191SU chipset is supported by the OpenBSD rsu(4) driver:
> > http://www.undeadly.org/cgi?action=article&sid=20101216231634
> >
> > Regards,
> > Ben
> >
> >
> >
> >
> > --
> > From: Benjamin Woods
> > woods...@gmail.com
> >
> > On 18 November 2014 13:56, Kevin Lo  wrote:
> >
> >> The RTL8191SU chipset is not supported.
> >>
> >> Kevin
> >> On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:
> >> >
> >> > I should mention I am running FreeBSD 10.1-RELEASE
> >> >
> >> >
> >> > --
> >> > From: Benjamin Woods
> >> > woods...@gmail.com
> >> >
> >> > On 18 November 2014 13:23, Ben Woods  wrote:
> >> >
> >> > > Hey guys,
> >> > >
> >> > > I am trying to get my D-Link DWA-131 A1 working, with some success
> >> but no
> >> > > network connectivity.
> >> > >
> >> > > It shows up in my usb list with device id 07d1:3303. The driver pages
> >> > > suggest this should be working with the rsu(4) driver and potentially
> >> > > the rsu-rtl8712fw firmware, according to these:
> >> > > https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4
> >> > > http://www.undeadly.org/cgi?action=article&sid=20101216231634
> >> > > https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
> >> > >
> >> > > I have added the following to /boot/loader.conf and rebooted:
> >> > > legal.realtek.license_ack=1
> >> > > rsu-rtl8712fw_load="YES"
> >> > >
> >> > > It shows up in ifconfig, and even scans and finds wireless access
> >> points.
> >> > > I have my WPA ssid and psk details for my access point stored in
> >> > > /etc/wpa_supplicant.conf. I can see from ifconfig that it is trying to
> >> > > associate with the correct access point ssid and do DHCP, but it never
> >> > > obtains an IP address.
> >> > >
> >> > > Has anyone had this issue before? Anyone know how can I go about
> >> > > troubleshooting this further?
> >> > >
> >> > > Regards,
> >> > > Ben
> >> > >
> >> > > --
> >> > > From: Benjamin Woods
> >> > > woods...@gmail.com
> >> > >
> >> > ___
> >> > freebsd-wireless@freebsd.org mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> > To unsubscribe, send any mail to "
> >> freebsd-wireless-unsubscr...@freebsd.org"
> >> >
> >>
> >
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: D-Link DWA-131 A1 (Realtek RTL8191SU) not working

[Kevin Lo]

The RTL8191SU chipset is not supported.

Kevin
On Tue, Nov 18, 2014 at 01:29:57PM +0800, Ben Woods wrote:
> 
> I should mention I am running FreeBSD 10.1-RELEASE
> 
> 
> --
> From: Benjamin Woods
> woods...@gmail.com
> 
> On 18 November 2014 13:23, Ben Woods  wrote:
> 
> > Hey guys,
> >
> > I am trying to get my D-Link DWA-131 A1 working, with some success but no
> > network connectivity.
> >
> > It shows up in my usb list with device id 07d1:3303. The driver pages
> > suggest this should be working with the rsu(4) driver and potentially
> > the rsu-rtl8712fw firmware, according to these:
> > https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4
> > http://www.undeadly.org/cgi?action=article&sid=20101216231634
> > https://wikidevi.com/wiki/D-Link_DWA-131_rev_A1
> >
> > I have added the following to /boot/loader.conf and rebooted:
> > legal.realtek.license_ack=1
> > rsu-rtl8712fw_load="YES"
> >
> > It shows up in ifconfig, and even scans and finds wireless access points.
> > I have my WPA ssid and psk details for my access point stored in
> > /etc/wpa_supplicant.conf. I can see from ifconfig that it is trying to
> > associate with the correct access point ssid and do DHCP, but it never
> > obtains an IP address.
> >
> > Has anyone had this issue before? Anyone know how can I go about
> > troubleshooting this further?
> >
> > Regards,
> > Ben
> >
> > --
> > From: Benjamin Woods
> > woods...@gmail.com
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TL-WN722N support on FreeBSD.

[Kevin Lo]

That's because you are "a wireless guy" :-)

On Mon, Sep 08, 2014 at 11:33:31PM -0700, Adrian Chadd wrote:
> 
> Oh it is fun. :)
> 
> +a
> On Sep 8, 2014 10:54 PM, "Kevin Lo"  wrote:
> 
> > On Mon, Sep 01, 2014 at 11:11:20AM -0700, Adrian Chadd wrote:
> > >
> > > The problem -is- the money. The people will come when there's enough
> > > interest and enough money.
> > >
> > > The problem is that people think things like wifi drivers that are
> > > debugged, perform well and get updated as new standards appear is a
> > > few months effort - and I think the herculean efforts done in the past
> > > by people like Sam fuel this myth.
> > >
> > > I've spent almost two years of weekends and evenings hacking on
> > > net80211 and the atheros driver to get it to where it is. The 11n
> > > support for atheros chips appeared when someone (hi Hobnob!) paid me
> > > for six months to get 11n done. I'm still debugging weird corner cases
> > > with rate control and congestion handling even now. And this is _on
> > > top_ of all the work done by the Atheros team to write the HAL in the
> > > first place.
> > >
> > > I've spent almost 18 months of weekends/evenings hacking on the intel
> > > iwn driver to find all the little odd corner cases that make it
> > > unusable by a lot of people. I keep saying I'm not, but since the
> > > laptops I'm using have iwn in them, I end up getting annoyed enough to
> > > fix it. This has all been for free.
> > >
> > > Wireless stuff is a very complicated, very time consuming thing that's
> > > immensely fun if you're into this kind of thing. But please understand
> > > - it's a huge time commitment for each individual device and new
> > > standard.
> > >
> > > So yes, it's the money. I've jokingly said that it's $100k and 2 years
> > > for me in (evenings, weekends) time and equipment to port and debug
> > > one driver for a given NIC. Not just do a "oh look here's an openbsd
> > > driver ported from linux in a month" port - that's just the beginning
> > > (and I tend to quote something like $10k for that) - I mean, something
> > > that ends up implementing the updated standards (11n, 11ac soon);
> > > something that includes powersave, something that includes debugging,
> > > something that handles a multitude of bad environments that people see
> > > every day and complain about. Ie - the level of work that makes it "oh
> > > it just works, I can get on with work now" level of work.
> > >
> > > I don't want to let myself be dragged into another two years of
> > > weekends. I kind of need some sleep here and there.
> >
> > I can't find a reason why I disagree with you.
> > I have almost forgotten that wifi hacking can be fun if it results
> > in something working...
> >
> > > -a
> >
> > Kevin
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TL-WN722N support on FreeBSD.

[Kevin Lo]

On Mon, Sep 01, 2014 at 11:11:20AM -0700, Adrian Chadd wrote:
> 
> The problem -is- the money. The people will come when there's enough
> interest and enough money.
> 
> The problem is that people think things like wifi drivers that are
> debugged, perform well and get updated as new standards appear is a
> few months effort - and I think the herculean efforts done in the past
> by people like Sam fuel this myth.
> 
> I've spent almost two years of weekends and evenings hacking on
> net80211 and the atheros driver to get it to where it is. The 11n
> support for atheros chips appeared when someone (hi Hobnob!) paid me
> for six months to get 11n done. I'm still debugging weird corner cases
> with rate control and congestion handling even now. And this is _on
> top_ of all the work done by the Atheros team to write the HAL in the
> first place.
> 
> I've spent almost 18 months of weekends/evenings hacking on the intel
> iwn driver to find all the little odd corner cases that make it
> unusable by a lot of people. I keep saying I'm not, but since the
> laptops I'm using have iwn in them, I end up getting annoyed enough to
> fix it. This has all been for free.
> 
> Wireless stuff is a very complicated, very time consuming thing that's
> immensely fun if you're into this kind of thing. But please understand
> - it's a huge time commitment for each individual device and new
> standard.
> 
> So yes, it's the money. I've jokingly said that it's $100k and 2 years
> for me in (evenings, weekends) time and equipment to port and debug
> one driver for a given NIC. Not just do a "oh look here's an openbsd
> driver ported from linux in a month" port - that's just the beginning
> (and I tend to quote something like $10k for that) - I mean, something
> that ends up implementing the updated standards (11n, 11ac soon);
> something that includes powersave, something that includes debugging,
> something that handles a multitude of bad environments that people see
> every day and complain about. Ie - the level of work that makes it "oh
> it just works, I can get on with work now" level of work.
> 
> I don't want to let myself be dragged into another two years of
> weekends. I kind of need some sleep here and there.

I can't find a reason why I disagree with you. 
I have almost forgotten that wifi hacking can be fun if it results
in something working...

> -a

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Issues with urtwn

[Kevin Lo]

On Mon, Sep 08, 2014 at 12:16:53PM -0300, Thiago Farina wrote:
> 
> On Sun, Sep 7, 2014 at 11:36 PM, Adrian Chadd  wrote:
> > Hi,
> >
> > On 7 September 2014 19:16, Thiago Farina  wrote:
> >> On Sun, Sep 7, 2014 at 12:09 PM, Nathan Whitehorn
> >>  wrote:
> >>> I've been having some issues with connection stability in urtwn for 
> >>> several
> >>> months. The usual symptom is that after some period of time the connection
> >>> will apparently stall. If I'm running ping continuously, for instance, it
> >>> will at some point stop receiving replies. Then, sometime later, 
> >>> immediately
> >>> if I use the "reassociate" command in wpa_cli, the connection will fix
> >>> itself and all the packets I didn't get earlier get delivered at once:
> >>> hundreds of ping replies, for instance, some with time stamps minutes in 
> >>> the
> >>> past. No data is actually lost, though.
> >>>
> >>> I think the issue is that the driver does not actually support powersave
> >>> mode (maybe it should?) but reports to the AP that it does:
> >>>
>  ifconfig wlan0 list sta (this is on the AP)
> >>> ADDR   AID CHAN RATE RSSI IDLE  TXSEQ  RXSEQ CAPS FLAG
> >>> 80:1f:02:cc:47:a91   11  11M  8.50   5526  55712 EPS AE  RSN
> >>>
> >>> I don't know enough about wireless to fix this, but the AP waiting for a
> >>> powersave poll and never getting one seems consistent with the problem.
> >>
> >> I think what you are relating here is what I observed recently too.
> >> Sorry, I'm new to FreeBSD. Just installed it recently, and I noticed
> >> that after I left it idle (I went to do something for some hours) for
> >> some time it lost the connection. Only rebooting makes it connect
> >> again to my network.
> >
> > Which NIC are you seeing this on?
> >
> Mine is urtwn0: Realtek RTL8187L from my Gateway laptop.

Typo?  urtw(4) supports Realtek RTL8187L, not urtwn(4).

> --
> Thiago Farina

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-LINK TL-WN821N

[Kevin Lo]

On Sun, Aug 24, 2014 at 06:01:20PM +0200, Carlos Jacobo Puga Medina wrote:
> 
> Hi Kevin,

Hi,

Sorry for the late response.

> Sometimes my wireless device fails to connect at boot, and I need to restart 
> the system. Also it states that the device is not configured.
> 
> /boot/loader.conf
> if_urtwn_load="YES"
> legal.realtek.license_ack=1

You might add the following lines to /boot/loader.conf:

urtwn-rtl8192cfwT_load="YES"
urtwn-rtl8192cfwU_load="YES"

> It shows the following output:
> 
> urtwn0: timeout waiting for checksum report
> 
> Any thoughts?

I thought this problem was fixed in r263154, but apparently not.
Could you try this patch?  Thanks

Index: sys/dev/usb/wlan/if_urtwn.c
===
--- sys/dev/usb/wlan/if_urtwn.c (revision 271297)
+++ sys/dev/usb/wlan/if_urtwn.c (working copy)
@@ -2280,8 +2280,6 @@ urtwn_fw_reset(struct urtwn_softc *sc)
return;
urtwn_ms_delay(sc);
}
-   /* Force 8051 reset. */
-   urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN);
 }
 
 static void
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

Sorry no.

Kevin

On Wed, Aug 20, 2014 at 12:42:34AM +0100, Miguel Clara wrote:
> 
> Would hardware donation help? At least in you're case I mean :)
> 
> 
> Melhores Cumprimentos // Best Regards
> ---
> *Miguel Clara*
> *IT - Sys Admin & Developer*
> *E-mail:*miguelmcl...@gmail.com
>  www.linkedin.com/in/miguelmclara/
> 
> 
> On Mon, Aug 18, 2014 at 9:49 AM, Kevin Lo  wrote:
> 
> > Since there is no data sheets available, looking throught the source code
> > from the vendor makes slower development and is very time-consuming,
> > at least in my case.
> >
> > Kevin
> >
> > On Sun, Aug 17, 2014 at 05:03:50PM +0100, Miguel Clara wrote:
> > >
> > > Thanks for clarifying Kevin.
> > >
> > > I wonder whats the reason for this? Since its in all I guess something in
> > > the kernel makes this harder? or is it just lack of time/resources?
> > >
> > > thanks
> > >
> > >
> > >
> > >
> > > Melhores Cumprimentos // Best Regards
> > > -------
> > > *Miguel Clara*
> > > *IT - Sys Admin & Developer*
> > > *E-mail:*miguelmcl...@gmail.com
> > >  www.linkedin.com/in/miguelmclara/
> > >
> > >
> > > On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo  wrote:
> > >
> > > > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote:
> > > > >
> > > > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo  wrote:
> > > > >
> > > > > > All USB wifi dongles in FreeBSD don't support 11n yet.
> > > > > >
> > > > > > Kevin
> > > > > >
> > > > > >
> > > > >  I was not aware of that, is this really true for all USB wifi
> > dongles or
> > > > > do you mean ralink only?
> > > >
> > > > It's true for all USB wifi dongles in *BSD...
> > > >
> > > > Kevin
> > > >
> > > ___
> > > freebsd-wireless@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > > To unsubscribe, send any mail to "
> > freebsd-wireless-unsubscr...@freebsd.org"
> > >
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

Wireless drivers on FreeBSD have a manual page which lists the hardware 
supported by that driver.  For example: 
https://www.freebsd.org/cgi/man.cgi?query=run&apropos=0&sektion=0&manpath=FreeBSD+10.0-RELEASE&arch=default&format=html#HARDWARE

Does this help you?  Thanks.

Kevin

On Fri, Aug 15, 2014 at 06:30:43AM -0700, Patrick Powell wrote:
> 
> Is it possible to provide a SHORT list of a COUPLE that do,  and are 
> either supported
> out of the box or with a few simple mods to the driver (patch?). And 
> perhaps a link to
> a site where they might be purchased?
> 
> On 08/14/14 20:06, Kevin Lo wrote:
> > All USB wifi dongles in FreeBSD don't support 11n yet.
> >
> > Kevin
> >
> > On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote:
> >> Duh, I figured it out... by default the Asus Guest netwroks are created in
> >> "auto" mode, so both N and legacy, while my 5G network was set to N only
> >> (2.4 is set to auto too).
> >>
> >> This also explain the poor performance now... for some reason 11n is not
> >> working only 11g/a.
> >>
> >> ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This
> >> works fine for the ath card tough)!
> >>
> >>
> >> Melhores Cumprimentos // Best Regards
> >> ---
> >> *Miguel Clara*
> >> *IT - Sys Admin & Developer*
> >> *E-mail:*miguelmcl...@gmail.com
> >>   www.linkedin.com/in/miguelmclara/
> >>
> >>
> >> On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara 
> >> wrote:
> >>
> >>>
> >>> On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara 
> >>> wrote:
> >>>
> >>>> Hi, just wanted to report that the patch made no difference.
> >>>>
> >>>> However I created a guest network in my router with the same password and
> >>>> also using WPA2, and it connects to it.
> >>>>
> >>>> the only difference is the BSSID, so I wonder if this is a issue with wpa
> >>>> and nothing to to with the driver?
> >>>>
> >>> NOTE: it works well if using ath driivers so the problem is probably in
> >>> the driver indeed!
> >>>
> >>>
> >>>> But the performance is still horrible!
> >>>>
> >>>>
> >>>>
> >>>>
> >> ___
> >> freebsd-wireless@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> >>
> > ___
> > freebsd-wireless@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> >
> 
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

Since there is no data sheets available, looking throught the source code
from the vendor makes slower development and is very time-consuming,
at least in my case.

Kevin

On Sun, Aug 17, 2014 at 05:03:50PM +0100, Miguel Clara wrote:
> 
> Thanks for clarifying Kevin.
> 
> I wonder whats the reason for this? Since its in all I guess something in
> the kernel makes this harder? or is it just lack of time/resources?
> 
> thanks
> 
> 
> 
> 
> Melhores Cumprimentos // Best Regards
> ---
> *Miguel Clara*
> *IT - Sys Admin & Developer*
> *E-mail:*miguelmcl...@gmail.com
>  www.linkedin.com/in/miguelmclara/
> 
> 
> On Sun, Aug 17, 2014 at 3:43 PM, Kevin Lo  wrote:
> 
> > On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote:
> > >
> > > On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo  wrote:
> > >
> > > > All USB wifi dongles in FreeBSD don't support 11n yet.
> > > >
> > > > Kevin
> > > >
> > > >
> > >  I was not aware of that, is this really true for all USB wifi dongles or
> > > do you mean ralink only?
> >
> > It's true for all USB wifi dongles in *BSD...
> >
> > Kevin
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

On Sat, Aug 16, 2014 at 09:07:29PM +0100, Miguel Clara wrote:
> 
> On Fri, Aug 15, 2014 at 4:06 AM, Kevin Lo  wrote:
> 
> > All USB wifi dongles in FreeBSD don't support 11n yet.
> >
> > Kevin
> >
> >
>  I was not aware of that, is this really true for all USB wifi dongles or
> do you mean ralink only?

It's true for all USB wifi dongles in *BSD...

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

All USB wifi dongles in FreeBSD don't support 11n yet.

Kevin

On Thu, Aug 14, 2014 at 03:09:23PM +0100, Miguel Clara wrote:
> 
> Duh, I figured it out... by default the Asus Guest netwroks are created in
> "auto" mode, so both N and legacy, while my 5G network was set to N only
> (2.4 is set to auto too).
> 
> This also explain the poor performance now... for some reason 11n is not
> working only 11g/a.
> 
> ifconfig wlan0 mode 11na or 11ng gives me device is not configured (This
> works fine for the ath card tough)!
> 
> 
> Melhores Cumprimentos // Best Regards
> ---
> *Miguel Clara*
> *IT - Sys Admin & Developer*
> *E-mail:*miguelmcl...@gmail.com
>  www.linkedin.com/in/miguelmclara/
> 
> 
> On Thu, Aug 14, 2014 at 2:13 PM, Miguel Clara 
> wrote:
> 
> >
> >
> > On Wed, Aug 13, 2014 at 7:10 PM, Miguel Clara 
> > wrote:
> >
> >> Hi, just wanted to report that the patch made no difference.
> >>
> >> However I created a guest network in my router with the same password and
> >> also using WPA2, and it connects to it.
> >>
> >> the only difference is the BSSID, so I wonder if this is a issue with wpa
> >> and nothing to to with the driver?
> >>
> >
> > NOTE: it works well if using ath driivers so the problem is probably in
> > the driver indeed!
> >
> >
> >> But the performance is still horrible!
> >>
> >>
> >>
> >>
> >
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: old new device: another sample of DWA-125

[Kevin Lo]

On Wed, Aug 13, 2014 at 04:25:33PM +0300, Volodymyr Kostyrko wrote:
> 
> Hi all.

Hi,

> I have something called DWA-125 (model D1A, h/w ver: D1, f/w ver: 4.00).
> 
> # usbconfig -d 6.2 dump_device_desc
> ugen6.2:  at usbus6, cfg=0 md=HOST 
> spd=HIGH (480Mbps) pwr=ON (500mA)
> 
>bLength = 0x0012
>bDescriptorType = 0x0001
>bcdUSB = 0x0200
>bDeviceClass = 0x
>bDeviceSubClass = 0x
>bDeviceProtocol = 0x
>bMaxPacketSize0 = 0x0040
>idVendor = 0x2001
>idProduct = 0x330f
>bcdDevice = 0x
>iManufacturer = 0x0001  
>iProduct = 0x0002  
>iSerialNumber = 0x0003  
>bNumConfigurations = 0x0001
> 
> Patch to detect it:
> 
> Index: sys/dev/usb/usbdevs
> ===
> --- sys/dev/usb/usbdevs (revision 269923)
> +++ sys/dev/usb/usbdevs (working copy)
> @@ -1624,6 +1624,7 @@
>   productDLINK RTL8192CU_1   0x3307  RTL8192CU
>   productDLINK RTL8192CU_2   0x3309  RTL8192CU
>   productDLINK RTL8192CU_3   0x330a  RTL8192CU
> +productDLINK RTL8192CU_4   0x330f  RTL8192CU
>   productDLINK DWA131B   0x330d  DWA-131 rev B
>   product DLINK2 RTL8192SU_1 0x3300  RTL8192SU
>   product DLINK2 RTL8192SU_2 0x3302  RTL8192SU
> Index: sys/dev/usb/wlan/if_urtwn.c
> ===
> --- sys/dev/usb/wlan/if_urtwn.c (revision 269923)
> +++ sys/dev/usb/wlan/if_urtwn.c (working copy)
> @@ -112,6 +112,7 @@
>  URTWN_DEV(DLINK,RTL8192CU_1),
>  URTWN_DEV(DLINK,RTL8192CU_2),
>  URTWN_DEV(DLINK,RTL8192CU_3),
> +   URTWN_DEV(DLINK,RTL8192CU_4),
>  URTWN_DEV(DLINK,DWA131B),
>  URTWN_DEV(EDIMAX,   EW7811UN),
>  URTWN_DEV(EDIMAX,   RTL8192CU),
> 
> # kldload urtwn
> Aug 13 16:10:19 limbo kernel: urtwn0:  class 0/0, rev 2.00/0.00, addr 1> on usbus6
> Aug 13 16:10:20 limbo kernel: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> 
> urtwn0: flags=8802 metric 0 mtu 2290
>  ether 00:00:a8:1d:f3:b7
>  nd6 options=21
>  media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>  status: no carrier
> 
> # ifconfig wlan0 create wlandev urtwn0
> # ifconfig wlan0 country ua
> # ifconfig wlan0 up scan
> 
> Gives nothing.
> 
> # ifconfig wlan0
> wlan0: flags=8843 metric 0 mtu 1500
>  ether 00:00:a8:1d:f3:b7
>  inet6 fe80::200:a8ff:fe1d:f3b7%wlan0 prefixlen 64 scopeid 0x7
>  nd6 options=21
>  media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>  status: no carrier
>  ssid "" channel 1 (2412 MHz 11b)
>  regdomain NONE country UA authmode OPEN privacy OFF txpower 30
>  bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 
> roam:rssi 7
>  roam:rate 1 bintval 0
> 
> # ifconfig wlan0 list caps
> drivercaps=2181c001
> 
> Is there any easy way to make it work or should I just dump it?

The D-Link DWA-125 rev D1 uses the RTL8188EU chip.
Please try this patch, thanks.

Index: sys/dev/usb/usbdevs
===
--- sys/dev/usb/usbdevs (revision 270007)
+++ sys/dev/usb/usbdevs (working copy)
@@ -1592,6 +1592,7 @@ product DLINK DUBE100 0x1a00  10/100 Ethernet
 product DLINK DUBE100C10x1a02  DUB-E100 rev C1
 product DLINK DSB650TX40x200c  10/100 Ethernet
 product DLINK DWL120E  0x3200  DWL-120 rev E
+product DLINK DWA125D1 0x330f  DWA-125 rev D1
 product DLINK DWL122   0x3700  DWL-122
 product DLINK DWLG120  0x3701  DWL-G120
 product DLINK DWL120F  0x3702  DWL-120 rev F
Index: sys/dev/usb/wlan/if_urtwn.c
===
--- sys/dev/usb/wlan/if_urtwn.c (revision 270007)
+++ sys/dev/usb/wlan/if_urtwn.c (working copy)
@@ -152,6 +152,7 @@ static const STRUCT_USB_HOST_ID urtwn_devs[] = {
URTWN_DEV(TRENDNET, RTL8192CU),
URTWN_DEV(ZYXEL,RTL8192CU),
/* URTWN_RTL8188E */
+   URTWN_RTL8188E_DEV(DLINK,   DWA125D1),
URTWN_RTL8188E_DEV(REALTEK, RTL8188ETV),
URTWN_RTL8188E_DEV(REALTEK, RTL8188EU),
 #undef URTWN_RTL8188E_DEV
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

On Sun, Aug 03, 2014 at 11:05:54PM +0800, Kevin Lo wrote:
> 
> On Tue, Jul 29, 2014 at 11:35:00PM +0100, Miguel Clara wrote:
> > Hi,
> 
> Hi Miguel,
> 
> >
> > I just brought a TP-Link N600 Wireless Dual Band USB Adpater (model
> > TL-WDN3200) and its correctly recognized in FreeBSD as a ranlink.
> >
> > Dmesg shows:
> > wlan0: Ethernet address: e8:94:f6:12:98:9d
> > run0: firmware RT3071 ver. 0.33 loaded
> >
> >
> > So the module and firmware seem to be loaded fine and I'm able to connect
> > to my 2.4g wireless fine.
> >
> > However I'm having no luck connecting to the 5G network, I've pasted the
> > scans and wpa_supplicant log, and I see:
> > "wlan0: Authentication with 60:a4:4c:28:13:c4 timed out.
> > Added BSSID 60:a4:4c:28:13:c4 into blacklist"
> > which I'm guessing means that for some reason the auth time-out, but I
> > don't really know why, all other 5G devices connect fine!
> >
> > (Also if its important the router is a RT-N66U running the latest
> > Asus-Merlin firmware)
> >
> >
> > First Scan:
> >
> > ~% ifconfig wlan0 scan
> > SSID/MESH IDBSSID  CHAN RATE   S:N INT CAPS
> > **  a4:b1:e9:ef:1c:681   54M -36:-68  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  9c:97:26:34:b7:cd   11   54M -41:-78  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  24:ec:99:39:4a:12   11   54M -33:-62  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  26:ec:99:39:4a:13   11   54M -31:-60  100 ES   HTCAP WME
> > **  10:fe:ed:c3:77:517   54M -40:-76  100 EPS  RSN HTCAP
> > WPA WME ATH WPS
> > Mynetwork5G 60:a4:4c:28:13:c4   44   54M -12:-20  100 EP   RSN HTCAP WME
> >
> > Second Scan
> >
> > % ifconfig wlan0 scan
> > SSID/MESH IDBSSID  CHAN RATE   S:N INT CAPS
> > **  a4:b1:e9:ef:1c:681   54M -36:-68  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  9c:97:26:34:b7:cd   11   54M -41:-78  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  24:ec:99:39:4a:12   11   54M -33:-62  100 EP   RSN HTCAP
> > WPS WPA WME
> > **  26:ec:99:39:4a:13   11   54M -31:-60  100 ES   HTCAP WME
> > **  10:fe:ed:c3:77:517   54M -40:-76  100 EPS  RSN HTCAP
> > WPA WME ATH WPS
> > Mynetwork5G 60:a4:4c:28:13:c4   44   54M -12:-20  100 EP   RSN HTCAP WME
> > Mynetwork   60:a4:4c:28:13:c03   54M -18:-32  100 EP   RSN HTCAP WME
> >
> >
> > log from --> wpa_supplicant -i wlano -c /etc/wpa_supplicant.conf -d
> > NOTE: while doing this in wpa_supplicant.conf I only have my 5g network!
> 
> I have the same wlan dongle as yours but I have no problems connecting to
> the TL-WDR4300 on the 5 GHz band.  This email is sent over the 5 GHz.
> I'll investigate further, thanks.
> 
> # dmesg | grep run0
> run0: <1.0> on usbus0
> run0: MAC/BBP RT5592 (rev 0x0222), RF RT5592 (MIMO 2T2R), address 
> f8:1a:67:2a:df:3f
> run0: firmware RT3071 ver. 0.33 loaded
> 
> # ifconfig wlan0
> wlan0: flags=8843 metric 0 mtu 1500
>  ether f8:1a:67:2a:df:3f
>  inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255
>  nd6 options=29
>  media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a
>  status: associated
>  ssid wng_5g channel 149 (5745 MHz 11a) bssid 64:66:b3:c2:3b:d4
>  country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
>  TKIP 2:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 
> scanvalid 60
>  wme roaming MANUAL

Please try Akinori Furukoshi's patch, thanks.

Index: sys/dev/usb/wlan/if_run.c
===
--- sys/dev/usb/wlan/if_run.c   (revision 269566)
+++ sys/dev/usb/wlan/if_run.c   (working copy)
@@ -3255,13 +3255,13 @@ run_set_tx_desc(struct run_softc *sc, struct run_t
txwi = (struct rt2860_txwi *)(txd + 1);
txwi->len = htole16(m->m_pkthdr.len - pad);
if (rt2860_rates[ridx].phy == IEEE80211_T_DS) {
-   txwi->phy = htole16(RT2860_PHY_CCK);
+   mcs |= RT2860_PHY_CCK;
if (ridx != RT2860_RIDX_CCK1 &&
(ic->ic_flags & IEEE80211_F_SHPREAMBLE))
mcs |= RT2860_PHY_SHPRE;
} else
-   txwi->phy = htole16(RT2860_PHY_OFDM);
-   txwi->phy |= htole16(mcs);
+   mcs |= RT2860_PHY_OFDM;
+   txwi->phy = htole16(mcs);
 
/* check if RTS/CTS or CTS-to-self protection is required */
if (!IEEE80211_IS_MULTICAST(wh

Re: FreeBSD current RT3071 can't connect to 5G network

[Kevin Lo]

On Tue, Jul 29, 2014 at 11:35:00PM +0100, Miguel Clara wrote:

Hi,


Hi Miguel,



I just brought a TP-Link N600 Wireless Dual Band USB Adpater (model
TL-WDN3200) and its correctly recognized in FreeBSD as a ranlink.

Dmesg shows:
wlan0: Ethernet address: e8:94:f6:12:98:9d
run0: firmware RT3071 ver. 0.33 loaded


So the module and firmware seem to be loaded fine and I'm able to connect
to my 2.4g wireless fine.

However I'm having no luck connecting to the 5G network, I've pasted the
scans and wpa_supplicant log, and I see:
"wlan0: Authentication with 60:a4:4c:28:13:c4 timed out.
Added BSSID 60:a4:4c:28:13:c4 into blacklist"
which I'm guessing means that for some reason the auth time-out, but I
don't really know why, all other 5G devices connect fine!

(Also if its important the router is a RT-N66U running the latest
Asus-Merlin firmware)


First Scan:

~% ifconfig wlan0 scan
SSID/MESH IDBSSID  CHAN RATE   S:N INT CAPS
**  a4:b1:e9:ef:1c:681   54M -36:-68  100 EP   RSN HTCAP
WPS WPA WME
**  9c:97:26:34:b7:cd   11   54M -41:-78  100 EP   RSN HTCAP
WPS WPA WME
**  24:ec:99:39:4a:12   11   54M -33:-62  100 EP   RSN HTCAP
WPS WPA WME
**  26:ec:99:39:4a:13   11   54M -31:-60  100 ES   HTCAP WME
**  10:fe:ed:c3:77:517   54M -40:-76  100 EPS  RSN HTCAP
WPA WME ATH WPS
Mynetwork5G 60:a4:4c:28:13:c4   44   54M -12:-20  100 EP   RSN HTCAP WME

Second Scan

% ifconfig wlan0 scan
SSID/MESH IDBSSID  CHAN RATE   S:N INT CAPS
**  a4:b1:e9:ef:1c:681   54M -36:-68  100 EP   RSN HTCAP
WPS WPA WME
**  9c:97:26:34:b7:cd   11   54M -41:-78  100 EP   RSN HTCAP
WPS WPA WME
**  24:ec:99:39:4a:12   11   54M -33:-62  100 EP   RSN HTCAP
WPS WPA WME
**  26:ec:99:39:4a:13   11   54M -31:-60  100 ES   HTCAP WME
**  10:fe:ed:c3:77:517   54M -40:-76  100 EPS  RSN HTCAP
WPA WME ATH WPS
Mynetwork5G 60:a4:4c:28:13:c4   44   54M -12:-20  100 EP   RSN HTCAP WME
Mynetwork   60:a4:4c:28:13:c03   54M -18:-32  100 EP   RSN HTCAP WME


log from --> wpa_supplicant -i wlano -c /etc/wpa_supplicant.conf -d
NOTE: while doing this in wpa_supplicant.conf I only have my 5g network!


I have the same wlan dongle as yours but I have no problems connecting to
the TL-WDR4300 on the 5 GHz band.  This email is sent over the 5 GHz.
I'll investigate further, thanks.

# dmesg | grep run0
run0: <1.0> on usbus0
run0: MAC/BBP RT5592 (rev 0x0222), RF RT5592 (MIMO 2T2R), address 
f8:1a:67:2a:df:3f

run0: firmware RT3071 ver. 0.33 loaded

# ifconfig wlan0
wlan0: flags=8843 metric 0 mtu 1500
ether f8:1a:67:2a:df:3f
inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255
nd6 options=29
media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a
status: associated
ssid wng_5g channel 149 (5745 MHz 11a) bssid 64:66:b3:c2:3b:d4
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
TKIP 2:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 
scanvalid 60

wme roaming MANUAL




wpa_supplicant v2.0
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver
'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Priority group 145
id=0 ssid='PissnLove5G'
wpa_driver_bsd_capa: drivercaps=0x0d85c501,cryptocaps=0x001b
wlan0: Own MAC address: e8:94:f6:12:98:9d
bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=0
bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=1
bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=2
bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0
bsd_del_key: key_idx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wlan0: RSN: flushing PMKID list in the driver
wlan0: Setting scan request: 0 sec 10 usec
WPS: Set UUID for interface wlan0
WPS: UUID based on MAC address - hexdump(len=16): 49 97 f8 d3 b1 d4 56 1d
94 a4 d0 76 2e 1d 81 b3
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
wlan0: State: DISCONNECTED -> SCANNING
Scan SSID - hexdump_ascii(len=11):
  50 69 73 73 6e 4c 6f 76 65 35 47  PissnLove5G
wlan0: Starting AP scan for wildcard SSID
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
wlan0: Event SCAN_RESULTS (3) receiv

Re: Is anyone awere if the "Asus AC50 USB" Wireless card (RT2870)

[Kevin Lo]

On Wed, Jul 23, 2014 at 03:31:58AM +0100, Miguel Clara wrote:
> 
> Wonder if anyone knwos if there's support for this card on current?
> 
> Tried 10 and its seems it not, It seem to be a Ralink RT2870 or now
> Mediatek and they seem to provide linux support:
> http://www.mediatek.com/en/downloads/mt7610u-usb/
> 
> So I was hopping maybe it works on current and I'll give it a chance, If
> not I guess I'll try ndis!

The Asus AC50 wlan dongle (mt7610u chip) is currently not supported 
by FreeBSD.

> Thanks
> 
> Melhores Cumprimentos // Best Regards
> ---
> *Miguel Clara*
> *IT - Sys Admin & Developer*
> *E-mail:*miguelmcl...@gmail.com
>  www.linkedin.com/in/miguelmclara/

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-LINK TL-WN821N

[Kevin Lo]

On Thu, Jul 10, 2014 at 11:23:44AM +0200, Carlos Jacobo Puga Medina wrote:
> 
> On Thu, 10 Jul 2014 13:05:24 +0800
> Kevin Lo  wrote:
> 
> > Ok, I know where the problem lies.  Please try this patch, thanks.
> > 
> > Index: sys/dev/usb/wlan/if_urtwn.c
> > ===
> > --- sys/dev/usb/wlan/if_urtwn.c (revision 268479)
> > +++ sys/dev/usb/wlan/if_urtwn.c (working copy)
> > @@ -2281,9 +2281,6 @@ urtwn_fw_reset(struct urtwn_softc *sc)
> > }
> > /* Force 8051 reset. */
> > urtwn_write_2(sc, R92C_SYS_FUNC_EN, reg & ~R92C_SYS_FUNC_EN_CPUEN);
> > -   urtwn_write_2(sc, R92C_SYS_FUNC_EN,
> > -   urtwn_read_2(sc, R92C_SYS_FUNC_EN) |
> > -   R92C_SYS_FUNC_EN_CPUEN);
> >  }
> >  
> >  static void
> > @@ -2383,6 +2380,11 @@ urtwn_load_firmware(struct urtwn_softc *sc)
> > urtwn_write_1(sc, R92C_MCUFWDL, 0);
> > }
> >  
> > +   if (!(sc->chip & URTWN_CHIP_88E)) {
> > +   urtwn_write_2(sc, R92C_SYS_FUNC_EN,
> > +   urtwn_read_2(sc, R92C_SYS_FUNC_EN) |
> > +   R92C_SYS_FUNC_EN_CPUEN);
> > +   }
> > urtwn_write_1(sc, R92C_MCUFWDL,
> > urtwn_read_1(sc, R92C_MCUFWDL) | R92C_MCUFWDL_EN);
> > urtwn_write_1(sc, R92C_MCUFWDL + 2,
> >
> > I'm just rebuilding the kernel.
> 
> It works! Thanks a lot for your help :)

Excellent, glad to hear it’s working well for you.

> # ifconfig -v wlan0
> wlan0: flags=8843 metric 0 mtu 1500
>   ether 10:fe:ed:27:f6:5d
>   inet6 fe80::12fe:edff:fe27:f65d%wlan0 prefixlen 64 scopeid 0x4 
>   inet 192.168.1.42 netmask 0xff00 broadcast 192.168.1.255 
>   nd6 options=23
>   media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
>   status: associated
>   ssid XX channel 11 (2462 MHz 11g) bssid f8:8e:85:c7:11:3d
>   regdomain ETSI2 country ES anywhere -ecm authmode WPA -wps -tsn
>   privacy ON deftxkey UNDEF
>   TKIP 2:128-bit powersavemode OFF powersavesleep 100 txpower 30
>   txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7
>   11a ucast NONEmgmt  6 Mb/s mcast  6 Mb/s maxretry 6
>   11b ucast NONEmgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>   11g ucast NONEmgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>   turboA  ucast NONEmgmt  6 Mb/s mcast  6 Mb/s maxretry 6
>   turboG  ucast NONEmgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>   sturbo  ucast NONEmgmt  6 Mb/s mcast  6 Mb/s maxretry 6
>   11naucast NONEmgmt 12 MCS  mcast 12 MCS  maxretry 6
>   11ngucast NONEmgmt  2 MCS  mcast  2 MCS  maxretry 6
>   halfucast NONEmgmt  3 Mb/s mcast  3 Mb/s maxretry 6
>   quarter ucast NONEmgmt  1 Mb/s mcast  1 Mb/s maxretry 6
>   scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250
>   roam:11a rssi7dBm rate 12 Mb/s
>   roam:11b rssi7dBm rate  1 Mb/s
>   roam:11g rssi7dBm rate  5 Mb/s
>   roam:turboA  rssi7dBm rate 12 Mb/s
>   roam:turboG  rssi7dBm rate 12 Mb/s
>   roam:sturbo  rssi7dBm rate 12 Mb/s
>   roam:11narssi7dBm  MCS  1
>   roam:11ngrssi7dBm  MCS  1
>   roam:halfrssi7dBm rate  6 Mb/s
>   roam:quarter rssi7dBm rate  3 Mb/s
>   -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 64k
>   ampdudensity 8 -amsdu -shortgi htprotmode RTSCTS -puren -smps -rifs
>   -wme -burst -dwds roaming MANUAL bintval 100
>   groups: wlan 
> 
> # usbconfig -u 2 -a 3 dump_device_desc 
> ugen2.3:  at usbus2, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=ON (500mA)
> 
>   bLength = 0x0012 
>   bDescriptorType = 0x0001 
>   bcdUSB = 0x0200 
>   bDeviceClass = 0x 
>   bDeviceSubClass = 0x 
>   bDeviceProtocol = 0x 
>   bMaxPacketSize0 = 0x0040 
>   idVendor = 0x0bda 
>   idProduct = 0x8178 
>   bcdDevice = 0x0200 
>   iManufacturer = 0x0001  <802.11n>
>   iProduct = 0x0002  
>   iSerialNumber = 0x0003  <00e04c01>
>   bNumConfigurations = 0x0001 
> 
> # netstat -I urtwn0
> NameMtu Network   Address  Ipkts Ierrs IdropOpkts 
> Oerrs  Coll
> urtwn  2290   10:fe:ed:27:f6:5d0 0 0 1055 
> 0 0
> 
> Could you commit this little tweak to -HEAD?

Committed as r268487, thanks.

> Regards,
> -- 
> Carlos Jacobo Puga Medina 

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-LINK TL-WN821N

[Kevin Lo]

On Wed, Jul 09, 2014 at 03:42:23PM +0200, Carlos Jacobo Puga Medina wrote:
> 
> On Wed, 9 Jul 2014 18:02:29 +0800
> Kevin Lo  wrote:
> 
> > On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote:
> > > 
> > > On Tue, 8 Jul 2014 10:22:20 +0800
> > > Kevin Lo  wrote:
> > > 
> > > > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote:
> > > > > 
> > > > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina  wrote:
> > > > > > On Mon, 7 Jul 2014 11:48:36 -0700
> > > > > > Adrian Chadd  wrote:
> > > > > >
> > > > > >> I'd just look at porting over the openbsd driver. There's no 11n
> > > > > >> support in the openbsd code though!
> > > > > >
> > > > > > That's bad, I hope that the 802.11n protocol will be implemented 
> > > > > > since it was released in 2009.
> > > > > >
> > > > > > What do you recommend to do?
> > > > > 
> > > > > I'd be happy if the driver showed up from OpenBSD. We can always try
> > > > > to add 11n support.
> > > > > 
> > > > > I'm sorry, I don't have much else to say at the moment and as my day
> > > > > job is decidedly not wireless, I can't be much help. :(
> > > > 
> > > > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with  
> > > > latest OpenBSD snapshot (2014/07/06).  It seems to me that there's a 
> > > > problem with otus(4).
> > > > 
> > > > dmesg:
> > > > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2
> > > > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc
> > > > 
> > > > ifconfig otus0 scan doesn't yield any result.
> > > > 
> > > > # ifconfig otus0 scan
> > > > otus0: flags=28802 mtu 1500
> > > > lladdr 00:22:b0:57:fc:dc
> > > > priority: 4
> > > > groups: wlan
> > > > media: IEEE802.11 autoselect
> > > > status: no network
> > > > ieee80211: nwid ""
> > > > none
> > > > #
> > > > 
> > > > > -a
> > > > 
> > > > Kevin
> > > 
> > > Hi, 
> > > 
> > > OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g 
> > > mode for now. So this could be chew better if we work together with them. 
> > 
> > All OpenBSD wireless drivers don't support .11n yet.
> > What I mean is that driver is not stable.  At least for D-Link DWA-160 rev. 
> > A1.
> > 
> > > Anyway if you don't mind I'll send you some outputs from TL-WN821N.
> > 
> > No, I don't mind. :-)  Thanks.
> > 
> > > Regards,
> > > -- 
> > > Carlos Jacobo Puga Medina 
> > 
> > Kevin
> 
> I'm testing a TL-WN821N v4 device.

Wait a minute.  You mentioned OpenBSD otus(4), I thought we were talking 
about the Atheros AR9170 chipset, not the Realtek RTL8192CU chip.

> # uname -a
> FreeBSD box.underbuild.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r268070: Tue 
> Jul  1 14:05:40 CEST 2014 
> r...@box.underbuild.com:/usr/obj/usr/src/sys/PROD  i386
> 
> # dmesg | grep urtwn0
> urtwn0:  on 
> usbus2
> urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> urtwn0: timeout waiting for firmware readiness
> 
> # usbconfig -u 2 -a 3 dump_device_desc
> ugen2.3:  at usbus2, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=ON (500mA)
> 
>   bLength = 0x0012 
>   bDescriptorType = 0x0001 
>   bcdUSB = 0x0200 
>   bDeviceClass = 0x 
>   bDeviceSubClass = 0x 
>   bDeviceProtocol = 0x 
>   bMaxPacketSize0 = 0x0040 
>   idVendor = 0x0bda 
>   idProduct = 0x8178 
>   bcdDevice = 0x0200 
>   iManufacturer = 0x0001  
>   iProduct = 0x0002  
>   iSerialNumber = 0x0003  
>   bNumConfigurations = 0x0001 
> 
> # ifconfig urtwn0
> urtwn0: flags=8803 metric 0 mtu 2290
>   ether 10:fe:ed:27:f6:5d
>   nd6 options=21
>   media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
>   status: associated
> 
> I noticed that wireless never goes up. Not much luck here, I get the error: 
>   urtwn0: timeout waiting for firmware readiness

Ok, I know where the problem lies.  Please try this patch, thanks.

Index: sys/dev/usb/wlan/if_urtwn.c
=

Re: TP-LINK TL-WN821N

[Kevin Lo]

On Tue, Jul 08, 2014 at 12:45:50PM +0200, Carlos Jacobo Puga Medina wrote:
> 
> On Tue, 8 Jul 2014 10:22:20 +0800
> Kevin Lo  wrote:
> 
> > On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote:
> > > 
> > > On 7 July 2014 12:10, Carlos Jacobo Puga Medina  wrote:
> > > > On Mon, 7 Jul 2014 11:48:36 -0700
> > > > Adrian Chadd  wrote:
> > > >
> > > >> I'd just look at porting over the openbsd driver. There's no 11n
> > > >> support in the openbsd code though!
> > > >
> > > > That's bad, I hope that the 802.11n protocol will be implemented since 
> > > > it was released in 2009.
> > > >
> > > > What do you recommend to do?
> > > 
> > > I'd be happy if the driver showed up from OpenBSD. We can always try
> > > to add 11n support.
> > > 
> > > I'm sorry, I don't have much else to say at the moment and as my day
> > > job is decidedly not wireless, I can't be much help. :(
> > 
> > I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with  
> > latest OpenBSD snapshot (2014/07/06).  It seems to me that there's a 
> > problem with otus(4).
> > 
> > dmesg:
> > otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2
> > otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc
> > 
> > ifconfig otus0 scan doesn't yield any result.
> > 
> > # ifconfig otus0 scan
> > otus0: flags=28802 mtu 1500
> > lladdr 00:22:b0:57:fc:dc
> > priority: 4
> > groups: wlan
> > media: IEEE802.11 autoselect
> > status: no network
> > ieee80211: nwid ""
> > none
> > #
> > 
> > > -a
> > 
> > Kevin
> 
> Hi, 
> 
> OpenBSD doesn't support 802.11n yet, but some of this cards run in 11g mode 
> for now. So this could be chew better if we work together with them. 

All OpenBSD wireless drivers don't support .11n yet.
What I mean is that driver is not stable.  At least for D-Link DWA-160 rev. A1.

> Anyway if you don't mind I'll send you some outputs from TL-WN821N.

No, I don't mind. :-)  Thanks.

> Regards,
> -- 
> Carlos Jacobo Puga Medina 

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-LINK TL-WN821N

[Kevin Lo]

On Mon, Jul 07, 2014 at 12:16:12PM -0700, Adrian Chadd wrote:
> 
> On 7 July 2014 12:10, Carlos Jacobo Puga Medina  wrote:
> > On Mon, 7 Jul 2014 11:48:36 -0700
> > Adrian Chadd  wrote:
> >
> >> I'd just look at porting over the openbsd driver. There's no 11n
> >> support in the openbsd code though!
> >
> > That's bad, I hope that the 802.11n protocol will be implemented since it 
> > was released in 2009.
> >
> > What do you recommend to do?
> 
> I'd be happy if the driver showed up from OpenBSD. We can always try
> to add 11n support.
> 
> I'm sorry, I don't have much else to say at the moment and as my day
> job is decidedly not wireless, I can't be much help. :(

I'm trying to get D-Link DWA-160 rev. A1 usb wifi adapter working with  
latest OpenBSD snapshot (2014/07/06).  It seems to me that there's a 
problem with otus(4).

dmesg:
otus0 at uhub1 port 7 "ATHER USB2.0 WLAN" rev 2.00/1.07 addr 2
otus0: MAC/BBP AR9170, RF AR9104, MIMO 2T2R, address 00:22:b0:57:fc:dc

ifconfig otus0 scan doesn't yield any result.

# ifconfig otus0 scan
otus0: flags=28802 mtu 1500
lladdr 00:22:b0:57:fc:dc
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid ""
none
#

> -a

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: need your opnion about wifi device

[Kevin Lo]

On Tue, Jun 17, 2014 at 09:09:26AM -0700, Sean Bruno wrote:
> On Tue, 2014-06-17 at 23:44 +0800, Kevin Lo wrote:
> > On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote:
> > > On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote:
> > > > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote:
> > > > > 
> > > > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I am planning to buy one the following USB WiFi devices:
> > > > > > 
> > > > > > 1.Tenda W311U+
> > > > > > 2.TP-Link TL-WN7200ND
> > > > > > 
> > > > > > I would appriciate if anyone share his experiences with the above 
> > > > > > devices.
> > > > > > BTW, I plan to use the device on freebsd/8.
> > > > > > 
> > > > > 
> > > > > 
> > > > > These both appear to be Ralink based devices.  AFAIK there is no 
> > > > > FreeBSD
> > > > > support for either device.
> > > > 
> > > > I think there's a typo s/no// :) 
> > > > Both devices are in fact supported by FreeBSD.
> > > > 
> > > > > sean
> > > > 
> > > > Kevin
> > > 
> > > 
> > > Really?  I didn't see any indication in the driver that they were
> > > supported.
> > 
> > At line 265 of file if_run.c:
> > RUN_DEV(RALINK, RT3070)
> > 
> > > sean
> > 
> > Kevin
> 
> Oh, does the device report itself as a RALINK usb device?

Does it matter?

> sean

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: need your opnion about wifi device

[Kevin Lo]

On Tue, Jun 17, 2014 at 07:07:33AM -0700, Sean Bruno wrote:
> On Tue, 2014-06-17 at 10:45 +0800, Kevin Lo wrote:
> > On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote:
> > > 
> > > On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote:
> > > > Hi,
> > > > 
> > > > I am planning to buy one the following USB WiFi devices:
> > > > 
> > > > 1.Tenda W311U+
> > > > 2.TP-Link TL-WN7200ND
> > > > 
> > > > I would appriciate if anyone share his experiences with the above 
> > > > devices.
> > > > BTW, I plan to use the device on freebsd/8.
> > > > 
> > > 
> > > 
> > > These both appear to be Ralink based devices.  AFAIK there is no FreeBSD
> > > support for either device.
> > 
> > I think there's a typo s/no// :) 
> > Both devices are in fact supported by FreeBSD.
> > 
> > > sean
> > 
> > Kevin
> 
> 
> Really?  I didn't see any indication in the driver that they were
> supported.

At line 265 of file if_run.c:
RUN_DEV(RALINK, RT3070)

> sean

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: need your opnion about wifi device

[Kevin Lo]

On Mon, Jun 16, 2014 at 07:04:07AM -0700, Sean Bruno wrote:
> 
> On Mon, 2014-06-16 at 13:33 +0430, Hooman Fazaeli wrote:
> > Hi,
> > 
> > I am planning to buy one the following USB WiFi devices:
> > 
> > 1.Tenda W311U+
> > 2.TP-Link TL-WN7200ND
> > 
> > I would appriciate if anyone share his experiences with the above devices.
> > BTW, I plan to use the device on freebsd/8.
> > 
> 
> 
> These both appear to be Ralink based devices.  AFAIK there is no FreeBSD
> support for either device.

I think there's a typo s/no// :) 
Both devices are in fact supported by FreeBSD.

> sean

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Urtwn module and Realteck RTL8188CE support.

[Kevin Lo]

On 2014/04/25 00:51, Thiago F wrote:

Is RTL8188CE already supported by urtwn or other FreeBSD's module ?


Sorry, RTL8188CE is not supported yet.


There is a way to get this device to work on FreeBSD ?


Try ndis(4).  It may work for you.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: urtwn panic

[Kevin Lo]

Anthony Jenkins wrote:







From: Kevin Lo 
To: Anthony Jenkins 
Sent: Wednesday, April 23, 2014 10:28 PM
Subject: Re: urtwn panic


Anthony Jenkins wrote:


I'm getting a panic with the latest kernel (r264719) and the if_urtwn
driver.  I have a coredump available to triage.

Could you try attached patch? Thanks.


  Kevin

Nice, several insertions/extractions and no panics!


Cool!  Fixed in *r264864, thanks.

*** <http://svnweb.freebsd.org/base?view=revision&revision=264864>


Unfortunately the !@#$& dongle's so small I just now managed to separate the 
device from the metal sleeve...grrr.  Should be able to fix tho, and it's still 
functional.


Many thanks!
Anthony


Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode

[Kevin Lo]

Cool!  I committed a fix in r262465, thanks.

Kevin

On 2014/02/25 00:58, Alex Deiter wrote:

Hello Kevin,

Thank you very much!
Successfully tested!


2014-02-24 12:42 GMT+04:00 Kevin Lo :


On 2014/02/19 10:12, Kevin Lo wrote:


On 2014/02/18 14:17, Alex Deiter wrote:


Hello,


Hi Alex,



Thank you for your advice!
I found a workaround:

# ifconfig wlan0 create wlandev run0

then wait 5 minutes ;-)

and only thereafter:

# ifconfig wlan0 up

run0: <1.0> on usbus1
run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address
30:85:a9:f4:52:bd
uhid0:  on
usbus1
wlan0: Ethernet address: 30:85:a9:f4:52:bd
run0: firmware RT3071 ver. 0.33 loaded

But found another issue: ifconfig wlan0 list scan command does not show
any
results:

root@test:~ # ifconfig wlan0 list scan
root@test:~ #

root@test:~ # wlandebug -i wlan0 scan
net.wlan.0.debug: 0x0 => 0x20

wlan0: sta_pick_bss: no scan candidate
wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend
2147963261]
wlan0: scan_task: chan 140a ->   1g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   1g ->   6g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   6g ->  11g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  11g ->   7g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   7g ->  52a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  52a ->  56a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  56a ->  60a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  60a ->  64a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  64a ->  36a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  36a ->  40a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  40a ->  44a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  44a ->  48a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  48a ->   2g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   2g ->   3g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   3g ->   4g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   4g ->   5g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   5g ->   8g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   8g ->   9g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   9g ->  10g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  10g -> 149a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms]
wlan0: sta_pick_bss: no scan candidate


I have an ZyxXEL NWD2705 working fine.  It has the exact same chipset as
the ASUS USB-N66.  So far I haven't been able to come up with a good
solution to your problem.  I purchased the ASUS USB-N66 and will arrive
in the next couple of days.  Hope I could find a new interesting bug :-)


After r258363, I forgot to add a flag to run's device list which uses a
standard scsi eject.  The ASUS USB-N66 has been tested to work on my
laptop.
The attached patch should fix your problem :-)  Please test it, thanks.

 Kevin






___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode

[Kevin Lo]

On 2014/02/19 10:12, Kevin Lo wrote:

On 2014/02/18 14:17, Alex Deiter wrote:

Hello,


Hi Alex,



Thank you for your advice!
I found a workaround:

# ifconfig wlan0 create wlandev run0

then wait 5 minutes ;-)

and only thereafter:

# ifconfig wlan0 up

run0: <1.0> on usbus1
run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address
30:85:a9:f4:52:bd
uhid0:  on
usbus1
wlan0: Ethernet address: 30:85:a9:f4:52:bd
run0: firmware RT3071 ver. 0.33 loaded

But found another issue: ifconfig wlan0 list scan command does not 
show any

results:

root@test:~ # ifconfig wlan0 list scan
root@test:~ #

root@test:~ # wlandebug -i wlan0 scan
net.wlan.0.debug: 0x0 => 0x20

wlan0: sta_pick_bss: no scan candidate
wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend
2147963261]
wlan0: scan_task: chan 140a ->   1g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   1g ->   6g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   6g ->  11g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  11g ->   7g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   7g ->  52a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  52a ->  56a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  56a ->  60a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  60a ->  64a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  64a ->  36a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  36a ->  40a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  40a ->  44a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  44a ->  48a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  48a ->   2g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   2g ->   3g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   3g ->   4g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   4g ->   5g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   5g ->   8g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   8g ->   9g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   9g ->  10g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  10g -> 149a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms]
wlan0: sta_pick_bss: no scan candidate


I have an ZyxXEL NWD2705 working fine.  It has the exact same chipset as
the ASUS USB-N66.  So far I haven't been able to come up with a good
solution to your problem.  I purchased the ASUS USB-N66 and will arrive
in the next couple of days.  Hope I could find a new interesting bug :-)


After r258363, I forgot to add a flag to run's device list which uses a
standard scsi eject.  The ASUS USB-N66 has been tested to work on my laptop.
The attached patch should fix your problem :-)  Please test it, thanks.

Kevin
Index: sys/dev/usb/wlan/if_run.c
===
--- sys/dev/usb/wlan/if_run.c   (revision 262433)
+++ sys/dev/usb/wlan/if_run.c   (working copy)
@@ -100,7 +100,8 @@ SYSCTL_INT(_hw_usb_run, OID_AUTO, debug, CTLFLAG_R
 static const STRUCT_USB_HOST_ID run_devs[] = {
 #defineRUN_DEV(v,p){ USB_VP(USB_VENDOR_##v, USB_PRODUCT_##v##_##p) 
}
 #defineRUN_DEV_EJECT(v,p)  \
-   { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, 0) }
+   { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, RUN_EJECT) }
+#defineRUN_EJECT   1
 RUN_DEV(ABOCOM,RT2770),
 RUN_DEV(ABOCOM,RT2870),
 RUN_DEV(ABOCOM,RT3070),
@@ -315,7 +316,7 @@ static const STRUCT_USB_HOST_ID run_devs[] = {
 RUN_DEV(ZINWELL,   RT3072_2),
 RUN_DEV(ZYXEL, RT2870_1),
 RUN_DEV(ZYXEL, RT2870_2),
-RUN_DEV(ZYXEL, NWD2705),
+RUN_DEV_EJECT(ZYXEL,   NWD2705),
 RUN_DEV_EJECT(RALINK,  RT_STOR),
 #undef RUN_DEV_EJECT
 #undef RUN_DEV
@@ -7

Re: Ralink RT3573 / ASUS USB-N66: run0: could not load 8051 microcode

[Kevin Lo]

On 2014/02/18 14:17, Alex Deiter wrote:

Hello,


Hi Alex,



Thank you for your advice!
I found a workaround:

# ifconfig wlan0 create wlandev run0

then wait 5 minutes ;-)

and only thereafter:

# ifconfig wlan0 up

run0: <1.0> on usbus1
run0: MAC/BBP RT3593 (rev 0x0402), RF RT3053 (MIMO 3T3R), address
30:85:a9:f4:52:bd
uhid0:  on
usbus1
wlan0: Ethernet address: 30:85:a9:f4:52:bd
run0: firmware RT3071 ver. 0.33 loaded

But found another issue: ifconfig wlan0 list scan command does not show any
results:

root@test:~ # ifconfig wlan0 list scan
root@test:~ #

root@test:~ # wlandebug -i wlan0 scan
net.wlan.0.debug: 0x0 => 0x20

wlan0: sta_pick_bss: no scan candidate
wlan0: scan_task: done, restart [ticks 487917, dwell min 20 scanend
2147963261]
wlan0: scan_task: chan 140a ->   1g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   1g ->   6g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   6g ->  11g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  11g ->   7g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   7g ->  52a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  52a ->  56a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  56a ->  60a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  60a ->  64a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  64a ->  36a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  36a ->  40a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  40a ->  44a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  44a ->  48a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  48a ->   2g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   2g ->   3g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   3g ->   4g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   4g ->   5g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   5g ->   8g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   8g ->   9g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan   9g ->  10g [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan  10g -> 149a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 149a -> 153a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 153a -> 157a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 157a -> 161a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 161a -> 100a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 100a -> 104a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 104a -> 108a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 108a -> 112a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 112a -> 116a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 116a -> 120a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 120a -> 124a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 124a -> 128a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 128a -> 132a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 132a -> 136a [active, dwell min 20ms max 200ms]
wlan0: scan_task: chan 136a -> 140a [active, dwell min 20ms max 200ms]
wlan0: sta_pick_bss: no scan candidate


I have an ZyxXEL NWD2705 working fine.  It has the exact same chipset as
the ASUS USB-N66.  So far I haven't been able to come up with a good
solution to your problem.  I purchased the ASUS USB-N66 and will arrive
in the next couple of days.  Hope I could find a new interesting bug :-)



Thank you!


Kevin

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: IWN performance very bad with 10.0-RC5

[Kevin Lo]

On 2014/01/12 14:36, Erich Dollansky wrote:

Hi,

On Fri, 10 Jan 2014 21:45:59 -0800
Adrian Chadd  wrote:


Please help dig up which change broke it. Even just test out the head
iwn code from 6 months ago.

I came to a very strange result. I have iwn in the kernel since June
2012 using 10. I also have had run in the kernel of another machine
since February 2011. I could not even add runfw to the kernel those
days running some 8 stable. I kept it that way until now.


This issue was solved by gonzo in r252064.



run was always working. iwn gave problems starting between August and
November of last year on my access point but still worked on other
places. I used iwn to connect successfully to another wireless network
mid November 2013.

After adding the firmware to the kernel for both iwn and run, I could
compile the kernel and iwn started to work. runfw did not break
compilation.

I wonder now if the iwn or run could even work without firmware or if
the firmware was automatically loaded even when iwn or run where
compiled into the kernel.


run(4) requires a firmware to function.  The firmware is automatically
loaded if and only if you compile runfw(4) as module and run(4)
compiled into the kernel.



Erich


Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything

[Kevin Lo]

Toomas Aas wrote:

Hello Kevin!


I hate debugging problems on the last day of the year :-)


Look at the bright side - one more problem fixed in 2013 :)


It seems like the firmware forgot to MFC. I just MFC'ed r256717.
Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device.


Confirmed, now it also works for me.


Cool!



BTW, for some reason I cannot build a kernel with "device runfw".

I added the following to my kernel config:

options IEEE80211_DEBUG
device run
device runfw
device wlan
device wlan_amrr
device wlan_wep
device wlan_ccmp
device wlan_tkip

and buildkernel failed:

clang -c -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
-Wno-error-tautological-compare -Wno-error-empty-body  
-Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS 
-include opt_global.h -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel 
-mno-red-zone -mno-mmx -mno-sse -msoft-float  
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector 
-Werror  /usr/src/sys/dev/usb/wlan/if_run.c
clang -O -pipe -march=athlon64 -std=c99 -g -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign 
-fformat-extensions  -Wmissing-include-dirs -fdiagnostics-show-option  
-Wno-error-tautological-compare -Wno-error-empty-body  
-Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS 
-include opt_global.h -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel 
-mno-red-zone -mno-mmx -mno-sse -msoft-float  
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -c 
runfw.c

uudecode -o runfw /usr/src/sys/contrib/dev/run/rt2870.fw.uu
ld -b binary --no-warn-mismatch -d -warn-common -r  -o runfw.fwo
ld: no input files
*** [runfw.fwo] Error code 1

I removed "device runfw" from kernel config, leaving everything else 
as is. Kernel built successfully and runfw seems to work as loadable 
module.


Problem fixed by gonzo in r252064.  It's just MFC'ed to stable/9 as 
r260134. :-)




Happy end_of_the_year!


Happy New Year!

Kevin

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: Ralink RT5372l support

[Kevin Lo]

On 2013/12/26 17:01, Kevin Lo wrote:

On 2013/12/26 14:53, Anton Mazunin wrote:
Hello everybody. Recently I was choosing usb wifi adapter for my pc, 
and decided the best way to be happy in this things is to buy one 
which is in freebsd supported hardware list. After few minutes of 
searching, the choise was done and I went to the closest shop and 
bought D-Link DWA-140.
I have to say that I was very upset when my OS only showed me: 
 at usbus1 (connected) but no device appeared in ifconfig. 
The only string appeared in dmesg was  at usbus1 (connected). 
Ok, lets see what my linux laptop would show me. And you know what? 
The same thing!
Then I decided to open the cover and see which chip is on the board. 
It was Ralink RT5372l. After some time of googling I recognized there 
is no support for this chip in run driver.
So here is the question: is there any way to make this device work on 
my pc? btw I'm using freebsd 9.2

Thank you for help! Hope I didn't get much of your time.


Hi Anton,

RT5372 is supported in -HEAD:
http://lists.freebsd.org/pipermail/svn-src-head/2013-November/053372.html

If you want to give it a try, you can install FreeBSD -CURRENT using the
snapshots images which you can find here:
https://pub.allbsd.org/FreeBSD-snapshots/i386-i386/11.0-HEAD-r259869-JPSNAP/ 



Let me know if it works for you, thanks.


Just for the record, run(4) works for Anton after r259939.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: TP-Link TL-WN727N V3 - cannot scan or connect to anything

[Kevin Lo]

On 2013/12/31 02:36, Toomas Aas wrote:

Hello!


Hi Toomas,



I posted a request on the FreeBSD forums on this topic, but got no 
responses:

http://forums.freebsd.org/viewtopic.php?f=46&t=43895

So, I'll repeat it here hoping that it may catch the attention of some 
experts who are maybe not following the forums.


I'm trying to get TP-Link TL-WN727N V3 USB wifi adapter working with 
my FreeBSD 9.2-STABLE amd64 system (r259472). It seems to me that this 
adapter uses Ralink RT5370 chipset, and support for this was merged to 
9-STABLE in r259457.


I plug in the adapter and it seems to be recognized:

Dec 18 18:13:15 kernel: ugen2.2:  at usbus2
Dec 18 18:13:15 kernel: run0: <1.0> on usbus2
Dec 18 18:13:15 kernel: run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 
(MIMO 1T1R), address f8:1a:67:19:40:24


I create the wlan device:

# ifconfig wlan0 create wlandev run0

Then I try to scan, but both of the below commands return immediately 
without any result:


# ifconfig wlan0 up scan
# ifconfig wlan0 list scan

I tried running wlandebug -i wlan0 +scan, and an endless supply of 
following is recorded in /var/log/messages:


Dec 18 21:47:26 kernel: wlan0: ieee80211_check_scan: active scan, append
Dec 18 21:47:26 kernel: wlan0: ieee80211_scanreq: flags 0x1b duration 
0x7fff mindwell 0 maxdwell 0 nssid 0
Dec 18 21:47:26 kernel: wlan0: scan_update_locked: current scanner is 
, switch to 
Dec 18 21:47:26 kernel: wlan0: start_scan_locked: active scan, 
duration 2147483647 mindwell 0 maxdwell 0, desired mode auto, flush
Dec 18 21:47:26 kernel: wlan0: scan set 1g, 6g, 11g, 7g, 2g, 3g, 4g, 
5g, 8g, 9g, 10g dwell min 20ms max 200ms
Dec 18 21:47:26 kernel: wlan0: start_scan_locked: active scan already 
in progress
Dec 18 21:47:26 kernel: wlan0: scan_task: chan   1b ->   1g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:26 kernel: wlan0: scan_task: chan   1g ->   6g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:27 kernel: wlan0: scan_task: chan   6g ->  11g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:27 kernel: wlan0: scan_task: chan  11g ->   7g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:27 kernel: wlan0: scan_task: chan   7g ->   2g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:27 kernel: wlan0: scan_task: chan   2g ->   3g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:27 kernel: wlan0: scan_task: chan   3g ->   4g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:28 kernel: wlan0: scan_task: chan   4g ->   5g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:28 kernel: wlan0: scan_task: chan   5g ->   8g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:28 kernel: wlan0: scan_task: chan   8g ->   9g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:28 kernel: wlan0: scan_task: chan   9g ->  10g [active, 
dwell min 20ms max 200ms]

Dec 18 21:47:29 kernel: wlan0: sta_pick_bss: no scan candidate
Dec 18 21:47:29 kernel: wlan0: scan_task: done, restart [ticks 
1706420, dwell min 20 scanend 2149187524]
Dec 18 21:47:29 kernel: wlan0: scan_task: chan  10g ->   1g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:29 kernel: wlan0: scan_task: chan   1g ->   6g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:29 kernel: wlan0: scan_task: chan   6g ->  11g [active, 
dwell min 20ms max 200ms]
Dec 18 21:47:29 kernel: wlan0: scan_task: chan  11g ->   7g [active, 
dwell min 20ms max 200ms]


I've watched this output for 10 minutes and it just seems to go on 
indefinitely. I'm not sure what to think of this. There are several 
access points near me that the scan should find, but it doesn't. When 
I plug in the same adapter to a laptop with Windows 7, it successfully 
shows the nearby access points and allows me to connect to one, so the 
adapter is not broken. Any ideas for further troubleshooting are welcome.


I hate debugging problems on the last day of the year :-)
It seems like the firmware forgot to MFC.  I just MFC'ed r256717.
Tested on the 9.2-STABLE (r260119) with the TL-WN727N wlan device.

Please give it a try, thanks.

Kevin

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Ralink RT5372l support

[Kevin Lo]

On 2013/12/26 14:53, Anton Mazunin wrote:
Hello everybody. Recently I was choosing usb wifi adapter for my pc, 
and decided the best way to be happy in this things is to buy one 
which is in freebsd supported hardware list. After few minutes of 
searching, the choise was done and I went to the closest shop and 
bought D-Link DWA-140.
I have to say that I was very upset when my OS only showed me: 
 at usbus1 (connected) but no device appeared in ifconfig. The 
only string appeared in dmesg was  at usbus1 (connected). Ok, 
lets see what my linux laptop would show me. And you know what? The 
same thing!
Then I decided to open the cover and see which chip is on the board. 
It was Ralink RT5372l. After some time of googling I recognized there 
is no support for this chip in run driver.
So here is the question: is there any way to make this device work on 
my pc? btw I'm using freebsd 9.2

Thank you for help! Hope I didn't get much of your time.


Hi Anton,

RT5372 is supported in -HEAD:
http://lists.freebsd.org/pipermail/svn-src-head/2013-November/053372.html

If you want to give it a try, you can install FreeBSD -CURRENT using the
snapshots images which you can find here:
https://pub.allbsd.org/FreeBSD-snapshots/i386-i386/11.0-HEAD-r259869-JPSNAP/

Let me know if it works for you, thanks.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: r257955 breaks my if_run device

[Kevin Lo]

On 2013/11/26 21:22, Mikaël Urankar wrote:

2013/11/26 Kevin Lo :

There's a patch in my tree that I forgot to commit.  Would you try the
patch at http://people.freebsd.org/~kevlo/patch-if_run.c ? Thanks.


The patch doesn't fix my problem...



All right, I just committed a fix as r258732.
Please test it and see if it works for you, thanks again.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: r257955 breaks my if_run device

[Kevin Lo]

On 2013/11/22 03:45, Mikaël Urankar wrote:

2013/11/21 Kevin Lo :

Mikaël Urankar wrote:

Hi,

I've tried with the following revision of if_run.c, if_runreg.h,
if_runvar.h but the problem is still there. (258082, 258083, 257955)
I've created a PR : kern/184122

Could you use usbconfig(8) to show your USB vendor id and device id? Thanks.

here it is :
idVendor = 0x148f
idProduct = 0x2770


There's a patch in my tree that I forgot to commit.  Would you try the
patch at http://people.freebsd.org/~kevlo/patch-if_run.c ? Thanks.

Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: r257955 breaks my if_run device

[Kevin Lo]

Mikaël Urankar wrote:

Hi,

I've tried with the following revision of if_run.c, if_runreg.h,
if_runvar.h but the problem is still there. (258082, 258083, 257955)
I've created a PR : kern/184122


Could you use usbconfig(8) to show your USB vendor id and device id? Thanks.


Thanks,
Mikaël


Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: r257955 breaks my if_run device

[Kevin Lo]

Handling.

Kevin

On 2013/11/20 04:11, Adrian Chadd wrote:

Yup

Kevin?


-adrian


On 19 November 2013 07:35, Mikaël Urankar  wrote:

Hi,

Please CC: me on replies, I am not subscribed to freebsd-wireless.

The subject says it all, since r257955 my run device is unable to scan
the network, associate to an AP, etc. The patch at [1] fixes the
problem.

I've put some debugging info at [2] and [3] if it has any use
(wlandebug +scan +auth +assoc +debug)

I'm running : FreeBSD desktop-xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #5
r258085M: Wed Nov 13 10:27:33 CET 2013
mik@xxx:/usr/obj/usr/src/sys/ACHERON  amd64
kernel and world in sync.

my run card :
run0: <1.0> on usbus3
run0: MAC/BBP RT2872 (rev 0x0202), RF RT2750 (MIMO 1T2R), address
xx:xx:xx:xx:xx:xx
run0: firmware RT2870 ver. 0.33 loaded

Should I submit a PR?

Thanks in advance,
Mikaël

[1] http://mikael.urankar.free.fr/FreeBSD/if_runreg.h.patch
[2] http://mikael.urankar.free.fr/FreeBSD/wlandebug.working
[3] http://mikael.urankar.free.fr/FreeBSD/wlandebug.notworking
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"




___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: r257955 breaks my if_run device

[Kevin Lo]

On 2013/11/19 23:35, Mikaël Urankar wrote:

Hi,


Hi,



Please CC: me on replies, I am not subscribed to freebsd-wireless.

The subject says it all, since r257955 my run device is unable to scan
the network, associate to an AP, etc. The patch at [1] fixes the
problem.


r258082 should fix your problem. :-)



I've put some debugging info at [2] and [3] if it has any use
(wlandebug +scan +auth +assoc +debug)

I'm running : FreeBSD desktop-xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #5
r258085M: Wed Nov 13 10:27:33 CET 2013
mik@xxx:/usr/obj/usr/src/sys/ACHERON  amd64
kernel and world in sync.

my run card :
run0: <1.0> on usbus3
run0: MAC/BBP RT2872 (rev 0x0202), RF RT2750 (MIMO 1T2R), address
xx:xx:xx:xx:xx:xx
run0: firmware RT2870 ver. 0.33 loaded

Should I submit a PR?


If r258082 doesn't work for you, please file a PR, thanks.



Thanks in advance,
Mikaël

[1] http://mikael.urankar.free.fr/FreeBSD/if_runreg.h.patch
[2] http://mikael.urankar.free.fr/FreeBSD/wlandebug.working
[3] http://mikael.urankar.free.fr/FreeBSD/wlandebug.notworking


Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: [rfc] removing the NDISulator

[Kevin Lo]

Thomas Mueller wrote:
  

The later driver model isn't supported by ndisulator. We'd have to
implement all the newer NDIS stuff for wifi and ethernet.
 

In the later NDIS layer the Microsoft Wireless Services implement a bunch
of stuff that used to be up to the driver. Ie, the driver just exposed an
ethernet "device" with some extra bits for wifi. Ie, the whole stack runs
in the driver. That has changed.
 
...



This is why I'd rather us bite the bullet now and deprecate it, versus have
it in there and put in the work to upgrade it to handle NDIS 6.x drivers
with the Microsoft wireless extensions stuff.
 


-adrian

How much extra work would there be to update the ndis(ulator/wrapper)?

Would it be more than writing native FreeBSD drivers which might be ported
from NetBSD, OpenBSD and Linux?

What about cases where specifications might be a trade secret?

How difficult is it to port or write a wifi or Ethernet driver for FreeBSD?

I have no experience writing device drivers but have some experience with C and 
C++.

I notice NetBSD and OpenBSD have drivers for some chips that FreeBSD lacks.

I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to
connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and
Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only)
and OpenBSD.


No offence, but you have mentioned several times that Realtek 8111E Ethernet
and athn(4) do not work on FreeBSD, just wondering why you don't sit down
and start coding then all your questions will be answered.



Tom




Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: Re: porting urtwn from openbsd to freebsd for RTL8188CE Driver Support

[Kevin Lo]

On 2012/11/11 12:22, Adrian Chadd wrote:

On 8 November 2012 02:07, Kevin Lo  wrote:

Kevin Lo wrote:

I am by no means a serious wireless expert. After hours of porting/hacking,
I came up with code what finally compiled and a basic function worked
for me.
Wish I had more free time to finish it.

Sweet! Does it pass packets?


It hangs when associating with an access point, but I have an idea
where the problem lies. This is just a quick port of OpenBSD urtwn,
a lot of work needs to be done. :-)

Note that urtwn doesn't support RTL8188CE. RTL8188CE is a mini PCIe device.




adrian



Kevin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: porting urtwn from openbsd to freebsd for RTL8188CE Driver Support

[Kevin Lo]

Kevin Lo wrote:
> I am by no means a serious wireless expert. After hours of porting/hacking,
> I came up with code what finally compiled and a basic function worked 
> for me.
> Wish I had more free time to finish it.
> 
> # dmesg |grep urtwn
> urtwn0:  
> on usbus1
> urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> 
> # ifconfig urtwn0
> urtwn0: flags=8802 metric 0 mtu 2290
>  ether 00:1f:1f:dd:35:43
>  nd6 options=29
>  media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>  status: no carrier

Oops, forgot to mention, the code is available at
http://people.freebsd.org/~kevlo/patch-urtwn

The code is ugly and not fully functional for sure. 
If anyone wants to finish it, please go ahead. :-)

Kevin

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Re: porting urtwn from openbsd to freebsd for RTL8188CE Driver Support

[Kevin Lo]

I am by no means a serious wireless expert. After hours of porting/hacking,
I came up with code what finally compiled and a basic function worked 
for me.

Wish I had more free time to finish it.

# dmesg |grep urtwn
urtwn0:  
on usbus1

urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R

# ifconfig urtwn0
urtwn0: flags=8802 metric 0 mtu 2290
ether 00:1f:1f:dd:35:43
nd6 options=29
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier

Kevin

On 2012/11/08 14:15, Adrian Chadd wrote:

I'd love if someone would do this. Anyone?



Adrian


On 7 November 2012 21:09, Christopher Patrick  wrote:


I was wondering If you would be kind enough to port urtwn from Openbsd. I would 
be willing to test it if you would please port it.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"



___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"