NIC per-frame RSSI reporting capability

[Fehmi Noyan ISI via freebsd-wireless]

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 any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: AC support status

[Fehmi Noyan ISI via freebsd-wireless]

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 am currently
>> trying
>> to finish two drivers for FreeBSD (and possibly add a 3rd one) and then
>> would
>> like to do whatever needs to be done to get us ac/ad/ax and by that time
>> probably ay support.
>> 
>> /bz
>> 
> 
> How difficult would it be to leverage the drivers in the Linux kernel like
> we are doing now with AMD and Intel drivers for graphics? I foresee the
> same issue in the wireless stack: Not enough people and fast moving
> hardware.
> 
> If this is even feasible with network components.
> ___
> 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"

WPA3.0

[Fehmi Noyan ISI via freebsd-wireless]

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-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: ieee80211_waitfor_parent hangs forever

[Fehmi Noyan ISI via freebsd-wireless]

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, Aug 20, 2017 at 11:48, Farhan Khan wrote:   Hi all,

I traced back where my driver-in-development hangs when I issue "ifconfig
wlan0 up", and it hangs on ieee80211_waitfor_parent(), specifically:

ieee80211_draintask(ic, &ic->ic_parent_task);

Reference:
http://src.illumos.org/source/xref/freebsd-head/sys/net80211/ieee80211_proto.c#1406

I am not familiar with the source just yet, What does this function do?
And, what is ic_parent_task?

It appears that Andriy reported this same issue here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208860 but I did not see
a resolution.

Thanks!

--
Farhan Khan
PGP Fingerprint: 782F 342B 5B08 0D2F F4E8 82C3 FFA1 CAE1 6536 51CA
___
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: ifconfig(8) and WPA functionality

[Fehmi Noyan ISI via freebsd-wireless]

Thanks Adrian...




- Original Message -
From: Adrian Chadd 
To: Fehmi Noyan ISI 
Cc: Freebsd Wireless 
Sent: Thursday, December 1, 2016 4:36 AM
Subject: Re: ifconfig(8) and WPA functionality

hiya,

nope - we're sticking with wpa_supplicant driving the wpa / 802.1x
state machine for 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.
>
> Functionality is implemented as ioctl calls (SIOCS80211WPAPARMS / 
> SIOGS80211WPAPARMS)
>
> and, as far as I have been told, is enough to provide basic wifi connectivity 
> and likes.
>
> Has something similar (embedding WPA functionality into ifconfig(8)) been 
> considered for FreeBSD before? This, of course, is a design matter than being 
> a coding issue.
>
> Thanks
> ___
> 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"

ifconfig(8) and WPA functionality

[Fehmi Noyan ISI via freebsd-wireless]

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 enough to provide basic wifi connectivity 
and likes.

Has something similar (embedding WPA functionality into ifconfig(8)) been 
considered for FreeBSD before? This, of course, is a design matter than being a 
coding issue.

Thanks
___
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: wpa_supplicant + wpa_gui have troubles when many APs have the same name

[Fehmi Noyan ISI via freebsd-wireless]

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 same name


I use wpa_supplicant + wpa_gui and it usually works fine. However, when 
many APs have the same name it often fails to connect or becomes very 
clunky.

When such network name (with many APs) is left in wpa_supplicant.conf, 
other networks often fail to connect until the multiple name is removed.

Anybody has any insight as of what the problem might be?


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"
___
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: Using net80211/IEEE80211_C_BITS macro

[Fehmi Noyan ISI via freebsd-wireless]

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 problematic.

A


On Nov 20, 2016 12:12 AM, "Fehmi Noyan ISI"  wrote:

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/ ifieee80211.c:   printb("drivercaps", 
>dc->dc_drivercaps, IEEE80211_C_BITS);
>root@test:~ # grep IEEE80211_C_BITS /usr/src/sys/net80211/*
>/usr/src/sys/net80211/_ ieee80211.h:#define  IEEE80211_C_BITS \
>/usr/src/sys/net80211/ ieee80211_ddb.c:  db_printf("\tcaps=%b\n", 
>vap->iv_caps, IEEE80211_C_BITS);
>/usr/src/sys/net80211/ ieee80211_ddb.c:  db_printf("\tcaps=%b\n", ic->ic_caps, 
>IEEE80211_C_BITS);
>root@test:~ # exit
>exit
>
>
>I used a VM (my only laptop has -RELEASE on it :{ , tried some bhyve trick 
>like iwn passthru but did not succeed), hence could not specifically test 
>"ifconfig wlan0 list caps" but since compilation went smooth, I would assume 
>it should be OK. After all, changes do not constitute any new features or 
>functions.
>
>Anything on the time frame till we could see this change on -RELEASE branch?
>
>Thanks
>
>
>- Original Message -
>From: Adrian Chadd 
>To: Fehmi Noyan ISI 
>Cc: Freebsd Wireless 
>Sent: Saturday, November 19, 2016 10:12 AM
>Subject: Re: Using net80211/IEEE80211_C_BITS macro
>
>Hi!
>
>Fixed in the latest -head. Two commits - one for net80211, one for ifconfig!
>
>
>
>-a
>
___
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: Using net80211/IEEE80211_C_BITS macro

[Fehmi Noyan ISI via freebsd-wireless]

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/ifieee80211.c:   printb("drivercaps", dc->dc_drivercaps, 
IEEE80211_C_BITS);
root@test:~ # grep IEEE80211_C_BITS /usr/src/sys/net80211/*
/usr/src/sys/net80211/_ieee80211.h:#define  IEEE80211_C_BITS \
/usr/src/sys/net80211/ieee80211_ddb.c:  db_printf("\tcaps=%b\n", vap->iv_caps, 
IEEE80211_C_BITS);
/usr/src/sys/net80211/ieee80211_ddb.c:  db_printf("\tcaps=%b\n", ic->ic_caps, 
IEEE80211_C_BITS);
root@test:~ # exit
exit


I used a VM (my only laptop has -RELEASE on it :{ , tried some bhyve trick like 
iwn passthru but did not succeed), hence could not specifically test "ifconfig 
wlan0 list caps" but since compilation went smooth, I would assume it should be 
OK. After all, changes do not constitute any new features or functions.

Anything on the time frame till we could see this change on -RELEASE branch?

Thanks


- Original Message -
From: Adrian Chadd 
To: Fehmi Noyan ISI 
Cc: Freebsd Wireless 
Sent: Saturday, November 19, 2016 10:12 AM
Subject: Re: Using net80211/IEEE80211_C_BITS macro

Hi!

Fixed in the latest -head. Two commits - one for net80211, one for ifconfig!



-a
___
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: Using net80211/IEEE80211_C_BITS macro

[Fehmi Noyan ISI via freebsd-wireless]

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 (implemented in ieee80211_ddb.c) also 
relies on data structures found in ieee80211_var.h, including 
IEEE80211_C_BITS(since this file includes lots of driver cap bits).

I am not quite sure why I got so many compiler errors (in fact clang gave up 
listing them after having a few dozen errors) by just #includ'ing 
ieee80211_var.h.



- Original Message -
From: Adrian Chadd 
To: Fehmi Noyan ISI 
Cc: Freebsd Wireless 
Sent: Friday, November 18, 2016 10:42 AM
Subject: Re: Using net80211/IEEE80211_C_BITS macro

Hiya,

Ok. How about I move that into _ieee80211.h with the rest of this
thing, and then remove the duplication from ifieee80211.c ?




-adrian
___
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: sourcecode of broadcom drivers up to 2011 yr sup

[Fehmi Noyan ISI via freebsd-wireless]

>> 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 permission to third parties for 
redistribution/modification of the work.


When you say "porting to FreeBSD", my interpretation of the phrase is "making 
the code or resulting binary work under FreeBSD". Below is what Wikipedia 
understands from "porting"
https://en.wikipedia.org/wiki/Porting

>> I do not think that broadсom will seek and pursue all users who wish to use 
>> porting code

Aye, they sure can "sue" somebody, not necessarily the users though. Have you 
heard about "AT&T Lawsuit" before?

https://en.wikipedia.org/wiki/FreeBSD#Lawsuit

There is also a nice reading here (if you are interested in a bit of UNIX 
history)
https://www.amazon.com/Daemon-Gnu-Penguin-Peter-Salus/dp/097903423X



- Original Message -
From: paradox via freebsd-wireless 
To: paradox ; Adrian Chadd 
Cc: "freebsd-wireless@freebsd.org" 
Sent: Friday, November 18, 2016 11:42 AM
Subject: 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

What you mean about porting ?

I mean, thats sourcecode can build and can generate a work binary
Create(generate) this binary from source or not, a user decides

I do not think that broadсom will seek and pursue all users who wish to use 
porting code


On Fri, 11/18/16, Adrian Chadd  wrote:

Subject: Re: sourcecode of broadcom drivers up to 2011 yr sup
To: "paradox" 
Cc: "freebsd-wireless@freebsd.org" 
Date: Friday, November 18, 2016, 12:26 AM

no, we don't have a
licence to port it open source and I don't have a
licence to generate binaries for other
people.



-adrian


On 17 November 2016 at 14:17,
paradox via freebsd-wireless

wrote:
> what you mean ? if we have
broadcom sourcecode, we can't porting and use it for
self ?
>
>

> On Fri, 11/18/16, Fehmi Noyan ISI 
wrote:
>
>  Subject:
Re: sourcecode of broadcom drivers up to 2011 yr sup
>  To: "paradox" ,
"Felix Friedlander" 
>  Cc: "freebsd-wireless@freebsd.org"

>  Date: Friday, November 18, 2016, 12:03
AM
>
>
>  >>> 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, November 18, 2016 9:42
AM
>  Subject: Re: sourcecode of
broadcom drivers up to 2011 yr
>  sup
>
>
>  if Anrian already have access to source
code of broadcom,
>  its great ! i
don't known about it
>
>  about of licensing, the sourcecode can
be porting to freebsd
>  but not
including to kernel, seems many people tobe
>  enougth this
>
>
> 

>  On Thu, 11/17/16, Felix Friedlander

>  wrote:
>
>  Subject: Re: sourcecode of broadcom
drivers up to 2011 yr
>  sup
>  To: "paradox" 
>  Cc: freebsd-wireless@freebsd.org
>  Date: Thursday, November 17, 2016, 10:32
PM
>
>
>  > On 18 Nov. 2016, at 05:36, paradox
via
>  freebsd-wireless
>  
>  wrote:
>  >
>  > seems all BCM WIFI PHY & MAC
sourcecode of
>  ABG/N/LP/NT/SSN
>  > hope your can build it or take part
for independ
>  module
>
>  > MAC
>  > 
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/sys
>  > PHY
>  > 
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/phy
>
>  There’s a
difference between finding the code, and having
>  a licence to use it… If I’m not
mistaken Adrian already
>  has access to
the proprietary Broadcom driver through his
>  work, it’s more of a licensing
issue.
>
>  Still a
nice find though, with this and the Cypress
>  datasheets some things may become a bit
easier.
>
>  --
>  Felix Friedlander 
> 
___
>  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"
___
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 

Re: sourcecode of broadcom drivers up to 2011 yr sup

[Fehmi Noyan ISI via freebsd-wireless]

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 license phrase in Broadcom source files with the one found in 
FreeBSD source files. You will see the difference (do not even attempt to 
compare it with GPL, you will get confused :/ )



- Original Message -
From: Adrian Chadd 
To: paradox 
Cc: "freebsd-wireless@freebsd.org" 
Sent: Friday, November 18, 2016 11:26 AM
Subject: Re: sourcecode of broadcom drivers up to 2011 yr sup

no, we don't have a licence to port it open source and I don't have a
licence to generate binaries for other people.



-adrian


On 17 November 2016 at 14:17, paradox via freebsd-wireless
 wrote:
> what you mean ? if we have broadcom sourcecode, we can't porting and use it 
> for self ?
>
> 
> On Fri, 11/18/16, Fehmi Noyan ISI  wrote:
>
>  Subject: Re: sourcecode of broadcom drivers up to 2011 yr sup
>  To: "paradox" , "Felix Friedlander" 
>  Cc: "freebsd-wireless@freebsd.org" 
>  Date: Friday, November 18, 2016, 12:03 AM
>
>
>  >>> 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, November 18, 2016 9:42 AM
>  Subject: Re: sourcecode of broadcom drivers up to 2011 yr
>  sup
>
>
>  if Anrian already have access to source code of broadcom,
>  its great ! i don't known about it
>
>  about of licensing, the sourcecode can be porting to freebsd
>  but not including to kernel, seems many people tobe
>  enougth this
>
>
>  
>  On Thu, 11/17/16, Felix Friedlander 
>  wrote:
>
>  Subject: Re: sourcecode of broadcom drivers up to 2011 yr
>  sup
>  To: "paradox" 
>  Cc: freebsd-wireless@freebsd.org
>  Date: Thursday, November 17, 2016, 10:32 PM
>
>
>  > On 18 Nov. 2016, at 05:36, paradox via
>  freebsd-wireless
>  
>  wrote:
>  >
>  > seems all BCM WIFI PHY & MAC sourcecode of
>  ABG/N/LP/NT/SSN
>  > hope your can build it or take part for independ
>  module
>
>  > MAC
>  > 
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/sys
>  > PHY
>  > 
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/phy
>
>  There’s a difference between finding the code, and having
>  a licence to use it… If I’m not mistaken Adrian already
>  has access to the proprietary Broadcom driver through his
>  work, it’s more of a licensing issue.
>
>  Still a nice find though, with this and the Cypress
>  datasheets some things may become a bit easier.
>
>  --
>  Felix Friedlander 
>  ___
>  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"
___
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: sourcecode of broadcom drivers up to 2011 yr sup

[Fehmi Noyan ISI via freebsd-wireless]

>>> 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, November 18, 2016 9:42 AM
Subject: Re: sourcecode of broadcom drivers up to 2011 yr sup


if Anrian already have access to source code of broadcom, its great ! i don't 
known about it

about of licensing, the sourcecode can be porting to freebsd but not including 
to kernel, seems many people tobe  enougth this



On Thu, 11/17/16, Felix Friedlander  wrote:

Subject: Re: sourcecode of broadcom drivers up to 2011 yr sup
To: "paradox" 
Cc: freebsd-wireless@freebsd.org
Date: Thursday, November 17, 2016, 10:32 PM


> On 18 Nov. 2016, at 05:36, paradox via freebsd-wireless

wrote:
> 
> seems all BCM WIFI PHY & MAC sourcecode of
ABG/N/LP/NT/SSN
> hope your can build it or take part for independ module

> MAC
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/sys
> PHY 
> https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/phy

There’s a difference between finding the code, and having
a licence to use it… If I’m not mistaken Adrian already
has access to the proprietary Broadcom driver through his
work, it’s more of a licensing issue.

Still a nice find though, with this and the Cypress
datasheets some things may become a bit easier.

-- 
Felix Friedlander 
___
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: Using net80211/IEEE80211_C_BITS macro

[Fehmi Noyan ISI via freebsd-wireless]

Well, including ieee80211_var.h and attempting to compile the code throws 
dozens of error messages.


In addition, I wonder why IEEE80211_C_BITS is re-defined in ifieee80211.c. 


- Original Message -
From: Adrian Chadd 
To: Fehmi Noyan ISI 
Cc: Freebsd Wireless 
Sent: Thursday, November 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,
>
> 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 #include'ing 
> ieee80211_var.h just for this macro is a good idea or not.
>
> I have noticed that IEEE80211_C_BITS is re-defined in 
> sbin/ifconfig/ifieee80211.c to be used by list_capabilities() function; does 
> this not require update of IEEE80211_C_BITS macro in multiple source files?
>
> What would be the best approach to use IEEE80211_C_BITS in my source file; 
> including ieee80211_var.h or re-defining the macro in the source file 
> (similar to ifconfig(1))?
>
> Thanks
> Fehmi
> ___
> 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"

Using net80211/IEEE80211_C_BITS macro

[Fehmi Noyan ISI via freebsd-wireless]

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 #include'ing 
ieee80211_var.h just for this macro is a good idea or not.

I have noticed that IEEE80211_C_BITS is re-defined in 
sbin/ifconfig/ifieee80211.c to be used by list_capabilities() function; does 
this not require update of IEEE80211_C_BITS macro in multiple source files?

What would be the best approach to use IEEE80211_C_BITS in my source file; 
including ieee80211_var.h or re-defining the macro in the source file (similar 
to ifconfig(1))?

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

struct ieee80211req_scan_result and couple of questions

[Fehmi Noyan ISI via freebsd-wireless]

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 
points a series of "ieee80211req_scan_result" structures when request type is 
IEEE80211_IOC_SCAN_RESULTS, and it is the programmer's responsibility to parse 
the returned data in a proper way?


The code for list_scan(int) in sbin/ifconfig/ifieee80211.c is a good example to 
this?


2 ) The "mesh" networking related parts of "ieee80211req_scan_result" structure 
are IEEE 802.11s additions?

3 ) A "ieee80211req_scan_result" structure can either have an SSID or a MESH 
ID? If so, in the code snippet below (from sbin/ifconfig/ifieee80211.c)


/* cp points a memory location returned by ioctl(2)

 * when request = IEEE80211_IOC_SCAN_RESULTS

 */

const uint8_t *vp, *idp;
sr = (const struct ieee80211req_scan_result *) cp;
vp = cp + sr->isr_ie_off;
if (sr->isr_meshid_len) {
 idp = vp + sr->isr_ssid_len;
 idlen = sr->isr_meshid_len;
} else {
 idp = vp;
 idlen = sr->isr_ssid_len;
}

why don't we have 

if (sr->isr_meshid_len) {
  idp = vp + sr->isr_meshid_len; /* THIS LINE */
  idlen = sr->isr_meshid_len;
} else {
   idp = vp;
   idlen = sr->isr_ssid_len;
}

Assuming the memory is organized like this

+---++--+-+
| Fixed Size struct | IE | SSID | MESH ID |
+---++--+-+

4 ) NET80211(4) manual page does not include the description of 
ieee80211req_scan_result structure. Would be good to have in the manual page 
rather than reading the net80211/ieee80211_ioctl.h file. 

I am happy to submit a patch if you aggree that a definition of 
ieee80211req_scan_result should appear in net80211(4). This will be freebsd-doc 
related issue then.

Regards
Fehmi
___
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: lib80211

[Fehmi Noyan ISI via freebsd-wireless]

+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, likely in a few weeks. I need to talk with Marie (who's doing
libifconfig right now) so we don't trample over each other!


-a


On 14 April 2016 at 19:55, Fehmi Noyan Isi  wrote:

> Thanks,
>
> Is there any rough time frame for the "second pass"?
___
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: lib80211

[Fehmi Noyan Isi via freebsd-wireless]

___
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

[Fehmi Noyan ISI via freebsd-wireless]

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 in GitHub[3].


[1] https://svnweb.freebsd.org/base/head/lib/lib80211/
[2] https://github.com/Savagedlight/libifconfig
[3] https://github.com/freebsd/freebsd
___
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"