NIC per-frame RSSI reporting capability

Hi, How can I find out whether my NIC support per-frame RSSI reporting? I have a RelaTek 8168/8111 using the re driver. Thanks ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send

Re: AC support status

Hiya, Do we have any “how to port drivers to FerrBSD from OS xxx” document somewhere? Even a github repo with a good commit history would do it I think... Fehmi > On 27/01/2020, at 9:20 PM, Matthias Gamsjager wrote: > >  >> >> >> I think Adrian might still be working on it with athp and I

WPA3.0

It seems WPA3.0 is on its way… https://www.theverge.com/2018/1/9/16867940/wi-fi-alliance-new-wpa3-security-protections-wpa2-announced ___ freebsd-w

Re: ieee80211_waitfor_parent hangs forever

as you might have noticed, ieee80211_draintask() is a wrapper around taskqueue_drain(9). Have you had a look at taskqueue_drain(9) man page? https://www.freebsd.org/cgi/man.cgi?query=taskqueue_drain&apropos=0&sektion=0&manpath=FreeBSD+11.1-RELEASE+and+Ports&arch=default&format=html On Sun,

Re: ifconfig(8) and WPA functionality

r now. -a On 30 November 2016 at 00:33, Fehmi Noyan ISI via freebsd-wireless wrote: > hiya, > > I have been studying OpenBSD's implementation of ifconfig utility and > realized that many of the WPA functionality is provided by the OpenBSD's > ifconfig utility. >

ifconfig(8) and WPA functionality

hiya, I have been studying OpenBSD's implementation of ifconfig utility and realized that many of the WPA functionality is provided by the OpenBSD's ifconfig utility. Functionality is implemented as ioctl calls (SIOCS80211WPAPARMS / SIOGS80211WPAPARMS) and, as far as I have been told, is enou

Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name

Have you tried adding bssid into wpa_supplicant.conf? https://www.freebsd.org/cgi/man.cgi?wpa_supplicant.conf%285%29 From: Yuri To: freebsd-wireless Sent: Tuesday, November 22, 2016 11:35 AM Subject: wpa_supplicant + wpa_gui have troubles when many APs have the

Re: Using net80211/IEEE80211_C_BITS macro

Appreciate it! From: Adrian Chadd To: Fehmi Noyan ISI Cc: Freebsd Wireless Sent: Monday, November 21, 2016 7:12 AM Subject: Re: Using net80211/IEEE80211_C_BITS macro I'll try to find someone to back port the wifi bits to stable/11 before they get too proble

Re: Using net80211/IEEE80211_C_BITS macro

Thanks Adrian! Checked out revision 308871 and compiled the system from source. Had no issues during the built process. Also, verified the changes in the source tree Script started on Sun Nov 20 20:59:17 2016 root@test:~ # grep IEEE80211_C_BITS /usr/src/sbin/ifconfig/* /usr/src/sbin/ifconfig/i

Re: Using net80211/IEEE80211_C_BITS macro

Sounds reasonable, thanks! if you make the change and give the revision number, I will give it a go to see if the code compiles (can do it in a VM, which wont have wlan interface but I'd assume it is OK if the world can be built without any issues) the ddb(4) support included in net80211 (imple

Re: sourcecode of broadcom drivers up to 2011 yr sup

>> To porting need a license ? may be for USA or some other countrys but not >> for whole world To port any software, the original work should allow you to do so. This is called "Free Software License", which is different than "Open Source". Apparently, the Broadcom source files give no permissi

Re: sourcecode of broadcom drivers up to 2011 yr sup

Dont know how this code was leaked, but in the source files it is clearly stated that the work is proprietary and all rights are reserved. This prevents FreeBSD developers (or any open source developer - say Linux kernel guys) from porting the code into any open source project. Just compare the

Re: sourcecode of broadcom drivers up to 2011 yr sup

>>> the sourcecode can be porting to freebsd but not including to kernel not quite sure about this... obviously enough, licences are there for a reason. From: paradox via freebsd-wireless To: Felix Friedlander Cc: freebsd-wireless@freebsd.org Sent: Friday, Nov

Re: Using net80211/IEEE80211_C_BITS macro

17, 2016 7:11 PM Subject: Re: Using net80211/IEEE80211_C_BITS macro Hi! Uhm, we could totally break out more bits into separate header files if including ieee80211_var.h doesn't work for you. a On 16 November 2016 at 14:53, Fehmi Noyan ISI via freebsd-wireless wrote: > Hiya, > >

Using net80211/IEEE80211_C_BITS macro

Hiya, I am working on an API (hopefully will post something about it soon) that, beyond other stuff, checks wlan driver capabilities (just like ifconfig(1) does). However, the capabilities macro, which is IEEE80211_C_BITS, is defined in sys/net80211/ieee80211_var.h and I am not sure whether #in

struct ieee80211req_scan_result and couple of questions

Hi there, I have been digging into the IEEE 802.11 related code for a couple of days and need to clarify some points (or get my interpretation of the code confirmed :} ). So, here are some gray areas I have; 1 ) ioctl(2) returns a memory address (in i_data field of ireq structure) which point

Re: lib80211

+freebsd-wireless Thanks! Would be good to have a Wiki or maybe included in [1] :) [1] https://wiki.freebsd.org/WiFi - Original Message - From: Adrian Chadd To: Fehmi Noyan Isi Sent: Friday, April 15, 2016 2:56 PM Subject: Re: lib80211 "whenever I have some time" ? :P I dunno, l

Re: lib80211

___ 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"

lib80211

Hi there, I see that there is some activity (not very frequent, though) in the /lib/lib80211 section of the HEAD branch[1]. I wonder if there is any plans to move the code on GitHub as a seperate project? Similar to libifconfig [2]... PS : I am aware that there is a freebsd source repository