#631: possibility to list/view ACL of MAC adresses either in proc entry or by
some iwpriv command
-----------------------------------------------+----------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: version
0.9.x - progressive release candidate phase
Component: madwifi: other | Version: trunk
Keywords: ACL, MAC authorizaction , feature | Patch_attached: 0
-----------------------------------------------+----------------------------
I am thinking about adding this feature - to be able to see, which MAC
adresses are actually allowed/disallowed to connect to madwifi based AP -
into madwifi driver.[[BR]]
This could be done in at least two ways. First way is to make it as
similar as possible to way, in which hostap driver show this information.
Hostap create /proc entry in /proc/net/ entry for each prism card -
similar to madwifi create /proc entries for each underlying device and
also for each vap in various parts of /proc tree - and under this
directory entry it creates file called ap_control , in which present
access control policy is shown and also blacklist/whitelist of MAC
adresses. Also, it has imo more pretty interface to statistics - every
connected station has it's own file , where all stats about are aggregated
, which is good for usage with tools like wewimo and stuff, but it is
probably matter for some other ticket / enhancement proposal.The second
way this could be implemented is to use iwpriv command - introduce some
new maccmd value , aka for examle iwpriv ath0 maccmd 6 would show internal
ACL on demand , or create some brand new iwpriv command , aka iwpriv ath0
listmac or something like that.[[BR]]
I would like to know your opinions about this, suggestions and other
comments before i will start to work on this for real. It is far from
critical issue, but could become handy in some cases, and also it should
not broke something or interfere with something - SHOULD not , but my
experiments on this resulted only into complete lock of systems . Also, if
someone more capable in coding would like to take this as his task, i will
appreciate it, because i am currently pretty busy and last but not least ,
not yet skilled enough to make it to work without big pain in brain ....
thx for all comments on advance - btw i intentionaly haven't written any
technical details of implementation, because i would like to hear general
suggestions of more experienced and capable ppl first and especially would
like to know, if there is anyone else who would like this in madwifi
--
Ticket URL: <http://madwifi.org/ticket/631>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
