Initial implementation for the Autoconfig WSC M1+M2 flow in prplMesh.
Goal is to see M1 and M2 (none-encrypted) in wireshark, which will prove our controller is ready for certification.
In order to keep the controller operational, the current slave join flow will remain, but the vendor specific CMDU which is used to send the join message will be replaced by Autoconfiguration WSC M1 message followed by vendor specific TLV which contains the Intel join message.
The response from the controller will be the M2, none encrypted, with the intel vendor specific TLV at the end, which will be used for slave response.
Sub Tasks
[x] Replace slave join request VS CMDU with autoconfig CMDU containing WSC M1 + Intel VS TLV
[x] Replace slave join response VS CMDU with autoconfig CMDU containing WSC M2
[ ] Move all parameters that exist in M1 from slave join TLV to WSC M1 TLV
[ ] Move all parameters that exist in M2 from slave join response TLV to WSC M2 TLV
Exit criteria
Controller and remote agent pass m1/m2 and get to operational. Autoconfig packets caprured in wireshark and are valid.
Test using docker "runner".
tomereli
commented
5 years ago
Description
Initial implementation for the Autoconfig WSC M1+M2 flow in prplMesh. Goal is to see M1 and M2 (none-encrypted) in wireshark, which will prove our controller is ready for certification. In order to keep the controller operational, the current slave join flow will remain, but the vendor specific CMDU which is used to send the join message will be replaced by Autoconfiguration WSC M1 message followed by vendor specific TLV which contains the Intel join message.
The response from the controller will be the M2, none encrypted, with the intel vendor specific TLV at the end, which will be used for slave response.
Sub Tasks
Exit criteria
Controller and remote agent pass m1/m2 and get to operational. Autoconfig packets caprured in wireshark and are valid. Test using docker "runner".
Detailed description
Section 5.7.1 in beerocks_1.4 architecture.pdf