Send a Mac Command in the optionnal field of the downlink

Home Forums Conduit: mLinux Model Send a Mac Command in the optionnal field of the downlink

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #17757
    Amani Moussa
    Participant

    Hello,

    I use the mLinux Conduit for sending a dowlinks to my mDot.
    So i use the mosquitto command:
    $ mosquitto_pub -t lora/<DEV-EUI>/down -m ‘{ “data”:”” }’

    Otherwise, i need to do some tests like:
    – Sending a downlink with invalid MIC
    – Modify RxDelay, RX1DRoffset, RX2Data rate, CFList in the join-accept
    – Sending the command MAC in the optionnal field
    – Sending a downlink with invalid sequence number
    So, can you help me and tell me how can i develop this tests using the conduit.

    Thank you in advance

    #17758
    Jason Reiss
    Keymaster

    These test scenarios have been performed in the LoRaWAN certification testing. A certification network server implementation would be needed.

    – Modify RxDelay, RX1DRoffset, RX2Data rate, CFList in the join-accept
    See http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/conduit-mlinux-advance-lora-configuration/
    See rx1DatarateOffset, rx2Datarate
    See frequencyEU to change the CFList
    RxDelay cannot be modified with current network server. This will become available in next release.

    – Sending the command MAC in the optional field
    Sending AT+NLC will perform Link Check MAC command exchange.
    There is no way to inject MAC commands through the network server in the optional field. MAC commands can only be sent with port 0 from an application.

    – Sending a downlink with invalid sequence number
    – Sending a downlink with invalid MIC
    The network server will not generate these packets.

    The NetworkSessionKey could be reconfigured for the device to generate invalid MIC.

    One could add a UDP proxy between network server and packet forwarder and modify the packet to be transmitted. The MIC and FCNT values are in the clear. Changing the FCNT will create invalid MIC.
    https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT

    #17759
    Amani Moussa
    Participant

    thanks for your reply.
    can i access directly to the transciver of the conduit? ==> Is there a service which we can use to read/write/configure the transceiver of the conduit?

    #17760
    Jason Reiss
    Keymaster

    Our bitbake recipes for building lora support
    http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora

    Otherwise when the /opt/lora/lora_pkt_fwd process is running it will report received packets to the network server and packets can be scheduled for downlink. The protocol is explained in the link from the previous post. It communicates over UDP.
    https://github.com/Lora-net/packet_forwarder/

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.