ft: add debug prints for FT-over-DS
PATCH 1/1 ft: add debug prints for FT-over-DS
This is consistent with the over-Air path, and makes it clear when reading the logs if over-DS was used, if there was a response frame, and if the frame failed to parse in some way.
--- src/ft.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
src/ft.c +11 -3
@@ -825,15 +825,21 @@ void __ft_rx_action(uint32_t ifindex, const uint8_t *frame, size_t frame_len) ret =ft_over_ds_parse_action_response (frame, frame_len, &spa, &aa, &ies, &ies_len); -if (ret !=0 ) +if (ret !=0 ) { +l_debug ("Could not parse action response" );return ; + } info =ft_info_find (ifindex, aa); -if (!info) +if (!info) { +l_debug ("No FT info found for BSS " MAC ,MAC_STR (aa));return ; + } -if (!ft_parse_ies (info, hs, ies, ies_len)) +if (!ft_parse_ies (info, hs, ies, ies_len)) { +l_debug ("Could not parse action response IEs" ); goto ft_error; + } info->parsed = true;
@@ -931,6 +937,8 @@ static bool ft_send_action(struct wiphy_radio_work_item *work)memcpy (ft_req +2 , info->spa,6 );memcpy (ft_req +8 , info->aa,6 ); +l_debug ("" ); +if (!ft_build_authenticate_ies (hs, hs->supplicant_ocvc, info->snonce, ies, &len)) goto failed;
Signature · 1 line
2.25.1
Denis Kenzior
AppliedHi James,
Quoted 7 lines · James Prestwood
This is consistent with the over-Air path, and makes it clear when reading the logs if over-DS was used, if there was a response frame, and if the frame failed to parse in some way.
--- src/ft.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
Applied, thanks.
Regards,
-Denis