local network settings?

[openclosed@samwooeleco.com]

Hi.
I want to connect a MultiConnect Conduit lora gateway and a generic Lora device.
Please check the settings because the connection is not established.

Model: MTCDT-246A Firmware 1.6.4
1. Network Settings
   Mode -> NETWORK SERVER
   Channel Plan -> KR920, Channel Mask -> 00FF
2. Key Management
   Join Server -> Location -> Local Keys
   Settings -> Network ID -> EUI
                  EUI -> 00-00-00-00-00-00-00-03
                  Nework Key -> Key
                  Key -> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-01
                  Default Profile -> DEFAULT-CLASS-A
3. Device
   End Device -> Device EUI Add
        Dev Eui -> 00-00-00-00-00-00-00-01
        Name -> a
        Device Profile -> LW102-OTA-KR920
        Network Profile -> DEFAULT-CLASS-A
I do not know why I can not connect.
It is normally connected to other LoRa Gateway.

And KeyManager -> Local End-Device Credentials here
Is it appropriate to add terminal information?
Of course, registration is not possible even if you register here.

[Nicolas Carvallo]

Hello I second this post.
After looking on all the web avilable material I cannot find a “good explanation” of how to configure the key management on local.
The best I found is this:

LoRa Network Server

The first one to succeed will provide the appkey and configuration used for creating the session keys.

1- Network ID and Network Key are checked if the JoinEUI/AppEUI in the Join Request matches the NetworkID
2- If Join Server Location is set to Local Keys, or in mLinux whitelist is enabled
The whitelist is searched for the DevEUI and the AppKey and Class setting are used for the device
3- If Join Server Location is set to Cloud Key Store, or in mLinux whitelist is disabled and Lens settings are correct
The Join Request is sent to the Join Server to be authenticated, the Lens end-device configuration is returned to the Conduit including the Class setting.

Can somebody please explain me what means point 1?

And when I’m on the conduit AEP 5.0.0, they ask me for :
Network ID (AppEUI)
Network Key (AppKey)
Why it’s asking this? Each device has it’s own AppEUI and AppKey, why the network server need a unique value?

Thanks

[Steve Kovarik]

For an “Over The Air”(OTA) join, the LoRa endpoint will need a DevEUI, AppEUI and AppKEY. Program the LoRa end node DevEUI, AppKEY and AppEUI into
the Conduit_AEP “LoRaWAN” “Key Management” local end-device credential so the
LoRa endpoint can successfully “join” over the air. “LoRaWAN” “Network settings”
“Network Mode” should be configured for “Public LoRaWAN” and the
“Join delay” configured for 5 seconds.

-Best Regards

[Nicolas Carvallo]

Hello,

But why it ask for :
– Network ID (AppEUI)
– Network Key (AppKey)
under Local Network Settings ?
What is this for?

https://drive.google.com/file/d/1g8rz1gZ7dO0ccQVoD1UkL_05advovSSG/view?usp=sharing” alt=”https://drive.google.com/file/d/1g8rz1gZ7dO0ccQVoD1UkL_05advovSSG/view?usp=sharing

• This reply was modified 5 years, 3 months ago by Nicolas Carvallo.

[Steve Kovarik]

Hi Nicolas

“Local Network settings” is an alternative that can be used and will work.
However that only allows for a single AppEUI and AppKEY to be configured.
When I configure multiple LoRa endpoints I like to use different AppEUI and
AppKEY for different endpoints. Configuring “local end-device credentials”
allows me to do that.

-Best Regards

[Nicolas Carvallo]

Thank you Steve,

I don’t know if you work for Multitech, but it would be much help to add this on http://www.multitech.net/developer/software/lora/lora-network-server/

or on the help page of the AEP version that is embedded on the GTW.

Regards,

[Author]

Posts