Is it possible to read NAS ID and Mobility Domain of third-party router?

[hnyman]

@rusty_router

Interesting thing though:

Mobility Domain had to be set as "6400" to become 0x0064 which seems little weird

It is likely a question byte order of numbers, of "little endian" vs. "big endian" CPUs.
Is 0x0064 stored in two bytes as is "00 64" or as "64 00" ?
That was something that I speculated three years ago at

802.11r mobility domain byte order

I am wondering if that currently causes us interoperability issues between little-endian and big-endian OpenWrt devices. Interesting if that flaw in hostapd has been undetected this long.

and like @jow summarized as

@jow

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.

Your other part about NASID is similar:

@rusty_router

"NAS ID": OpenWRT inserts "3"'s before each character, so
"633465353301" became "363333343635333533333031"

Hexadecimal characters for 0-9 are 30 31 ... 39
So, if one takes ASCII string of "6334..." it is actually hexadecimal values as "36 33 33 34 ..."
Apparently OpenWrt and your other router handle that aspect differently.
Other router want just ASCII numbers as the NASID and then stores it (naturally) as hex character, while OpenWrt directly takes/shows a hexadecimal string in config.

Ps.
I use a byte-symmetric Mobility ID myself for 802.11r...
something like "0D 0D"