I’ve consulted with the author of that page and he says it’s not entirely random - for EUI’s it produces a properly formatted “locally administered address”. It is for the AppKey, but they are meant to be totally random.
Force the second digit (zero base counting) i.e. lower nibble of the most significant byte of the 16digit hex code to be a 2 thereby ensuring it gets recognised as a locally administered ‘address’/eui? (weak s/w skills here so always learning! ) If so I assume that the “2” could then be “6”, “A” or “E” for same effect?
Apart from the no small detail of being off topic for this thread, what is your actual point in quoting my own code to me??
You linked to it as a random generator, in a light hearted way I pointed out it was a little bit more than that. It’s OK to link to it as it is called and as you have done in the past, but it gives the wrong impression to call it a random generator. LoRaWAN is standards based, it’s not OK to give the impression that we can make things up.
And, as you may be aware, we don’t delete comments that take replies out of context.
Er, binary or two base counting, but yes, it sets that bit so that anything ending in 2, 6, A or E is valid.