Louis CroisezI found a working solution at https://www.debian-fr.org/t/installation-de-clef-usb-wifi-netgear-wna1000m/68643/5
The rtl8192cufw_TMSC.bin file has to be put at /lib/firmware/rtlwifi directory.
Note: this is working in mLinux kernel version 3.12.27
Now ifconfig -a is showing wlan0 device.
Louis CroisezI wonder what is the actual impact of this network[“public”]=true parameter?
Does this mean that the LoRa communication is not fully encrypted?
What is changed in the LoRa communication when putting this param to true?
Louis CroisezHello Bryan,
thank you very much for answering me.
I just read the post you mentioned.
Just a last question:
is it absolutely required to configure network[“public”]=true, for RN2483 module to join and emit successfully?
Louis Croisezsorry, my mistake: do not read 512bit keys, but 128bit keys instead.
Louis CroisezI am reading chapter 6.3 from LoRaWAN standards, and I try to understand it well.
As concern my LoRa+Arduino case, I must enter two 512bit keys. I suppose that it is in fact the NwkSKey and the AppSKey, two sessions keys which are the result of the {DevEUI/AppEUI/AppKey} personalization.
This means that I have to do something on my gateway to produce a new couple of {NwkSKey/AppSKey}, that should “register”, or “activate” my new device.
I must do this by hand because the Microchip device does not share the same API like other Multitech systems.
But the question is: how can I activate my new device by hand?
