On 3/19/19 9:39 AM, Ben Greear wrote:
On 3/14/19 4:09 PM, Ben Greear wrote:
On 3/14/19 4:00 PM, Jouni Malinen wrote:
On Thu, Mar 14, 2019 at 01:03:11PM -0700, Ben Greear wrote:
On 3/14/19 12:42 PM, Dennis Bland wrote:
hostapd implements an AP neighbor database (neighbor_db.c) that allows
you to add AP neighbors with the 'set_neighbor' and 'remove_neighbor'
CLI commands (with rrm_neighbor_report=1 in the .conf file).
Higher-level logic to periodically scan for nearby APs, filter for
neighbors within the same ESS, and build a neighbor list isn't
implemented.
I'd like to configure this in the .conf file so that I don't have to reload it
on vap restart, etc.
Currently, I don't see a way to do that. Anyone have opinions on adding
a 'cli' command to the config-file logic that would just pipe the rest of
the line into the hostapd_cli logic on startup?
That sounds pretty ugly.. If this really needs to come from the
configuration file, I think I'd rather go with a new config parameter
being added with a format that I guess would be quite similar to the
SET_NEIGHBOR control interface command and the parser would also be very
similar to hostapd_ctrl_iface_set_neighbor().
That said, I don't see why you would do this over the control
interface.. Normal use cases will need to update this information more
dynamically anyway, so the control interface is needed and whatever is
reloading/restarting an interface could as well run through number of
hostapd_cli calls or direct interaction with the control interface.
Ok, I got worried trying to load it at boot time would be problematic for
other reasons as well.
At least for the casual user, building the neighbor report IE to be passed
into the CLI seems a bit tricky. (And according to google, exactly no one has
ever posted a working example of that command :))
Is there any way to query a hostapd using hostapd_cli or similar to get
a dump of what it thinks is its own neigh report? Then, I could query
all of the hostapd in question, and just pipe the output into the other hostapd
neigh table through hostapd_cli without having to fully parse/build the IE?
So, I went ahead and built the way to show current neigh db, per previous patches,
and I rigged up my software to add neighbor entries to a group of APs.
# hostapd_cli -i vap0001 show_neighbor
04:f0:21:2f:46:c3 ssid=04f0212f46c3bf190000806409 nr=04f0212f46c3bf1900008064090603026a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:71:39:c3 ssid=04f0217139c3bf190000806409 nr=04f0217139c3bf1900008064090603026a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:c8:4e:c3 ssid=04f021c84ec3bf190000806409 nr=04f021c84ec3bf1900008064090603026a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:9d:47:c3 ssid=04f0219d47c3bf190000806409 nr=04f0219d47c3bf1900008064090603026a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:a3:6e:c3 ssid=04f021a36ec3bf190000806409 nr=04f021a36ec3bf1900008064090603026a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:f2:ea:b0 ssid=04f021f2eab0af190000802809 nr=04f021f2eab0af1900008028090603022a00 lci=[BLANK] civic=[BLANK] stationary=0
04:f0:21:25:e0:b0 ssid=04f02125e0b0af190000802809 nr=04f02125e0b0af1900008028090603022a00 lci=[BLANK] civic=[BLANK] stationary=0
I associated a station to this neigh show above, and requested a neighbor report:
./local/bin/wpa_cli -i sta0000 neighbor_rep_request
I see the action frame go to AP, and I see AP respond, but AP responds with exactly one IE
and it does not show the multiple neighbors that I expected to see.
So, *should* I see info about multiple neighbors returned? Am I using this wrong?
Gah, all I have to do is post publicly and then I find the mistake. ssid is being reported wrong by
my patch to show neighbors, and so then it gets set wrong.
Hopefully that is the only issue.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
