Hi,
hostapd already has a table of r1kh and r0kh peers: r0kh / r1kh
configuration options.
You might be able to extend them to add an L3 address option.
There are two different FT AP-AP communication frames:
1. forwarding FT Action Frame content (RRB) for Over-DS (see
wpa_ft_rrb_send)
2. key distribution (using an OUI based protocol) (see
wpa_ft_rrb_oui_send)
Currently, only the latter (2.) is managed used r0kh/r1kh configuration.
Thus, forwarding FT Action Frame will need an extra lookup for L3 usage.
Possibly r1kh configuration might be reusable.
Obviously, configuring L3 addressing manually in r0kh/r1kh configuration
options will not work with current autodiscovery (l2 broadcasts).
Depending on your setup, you might want to have a look into linux bridge
tunnel_info (vxlan) feature.
Regards,
M. Braun
Am 01.10.2019 10:41, schrieb Pablo I. Pousada Rial:
Hello all.
I'm working in a deployment with a huge density of APs, where FT
transition times are required. The problem I've ran into is that, as
far as
I understand, the key exchange protocol works on L2, and I need it to
work
over different L2 networks. Using a single network, or merging them on
a
single VLAN is out of the question, due to the huge scale of the system
(
over 2000 APs).
Though I am working on a potential solution involving dedicated L2
tunneling for this purpose only, I would greatly appreciate any help on
a
more direct approach, or the viability of patching in native L3 support
myself.
Thank you for your time,
Pablo I. Pousada Rial
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
