802.11r mobility domain byte order

jow · July 10, 2021, 7:12am

I could also imagine that one side interprets the hexadecimal value in the configuration as binary byte string (essentially big endian) while the other side interprets the value numerically and sends it in platform endianess.

What exactly did you configure on the OpenWrt side? option mobility_domain 2710?

Edit:
Indeed, hostapd interprets the given value as binary string:

github.com

latelee/hostapd/blob/b97f32062c9a29fe6b12b5082832e34ed565b7de/hostapd/config_file.c#L2539

    
      
          		os_free(bss->rsn_preauth_interfaces);
          		bss->rsn_preauth_interfaces = os_strdup(pos);
          #endif /* CONFIG_RSN_PREAUTH */
          #ifdef CONFIG_PEERKEY
          	} else if (os_strcmp(buf, "peerkey") == 0) {
          		bss->peerkey = atoi(pos);
          #endif /* CONFIG_PEERKEY */
          #ifdef CONFIG_IEEE80211R
          	} else if (os_strcmp(buf, "mobility_domain") == 0) {
          		if (os_strlen(pos) != 2 * MOBILITY_DOMAIN_ID_LEN ||
          		    hexstr2bin(pos, bss->mobility_domain,
          			       MOBILITY_DOMAIN_ID_LEN) != 0) {
          			wpa_printf(MSG_ERROR,
          				   "Line %d: Invalid mobility_domain '%s'",
          				   line, pos);
          			return 1;
          		}
          	} else if (os_strcmp(buf, "r1_key_holder") == 0) {
          		if (os_strlen(pos) != 2 * FT_R1KH_ID_LEN ||
          		    hexstr2bin(pos, bss->r1_key_holder, FT_R1KH_ID_LEN) != 0) {
          			wpa_printf(MSG_ERROR,

So I suppose your only choice is to simply swap the bytes manually in the OpenWrt side config to accommodate for Cisco’s implied byte swapping of the mobility domain value.

Edit 2:
Just seen that @IanC digged out the proper standards definition, seems that hostapd should interpret the value numerically (strtoul() instead of hexstr2bin() and then convert the value to little endian in order to match Cisco‘s and likely other vendors behavior).