Gateway receives a lot of incompatible LoRaWan data?

One of my gateways is using a lot of (cellular) data, and I found out it is receiving lots of messages that don’t seem to follow the LoraWan protocol.

The gateway is a Dragino DLOS8.
I’m wondering if the receiver could be defect, or that it maybe is just seeing messages from a private LoRa network?

The ‘wrong’ messages show up like this in the TTN terminal:

"data": {
      "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
      "namespace": "pkg/encoding/lorawan",
      "name": "field_length_with_multiple_choices",
      "message_format": "`{lorawan_field}` length `{value}` should be equal to `{expected_1}` or `{expected_2}`",
      "attributes": {
        "expected_1": 17,
        "expected_2": 33,
        "lorawan_field": "JoinAcceptPHYPayload",
        "value": 19
      },
      "correlation_id": "442d755cc86d4e369238d3a33a069ca4",
      "code": 3
    }
"data": {
      "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
      "namespace": "pkg/encoding/lorawan",
      "name": "decode",
      "message_format": "could not decode `{lorawan_field}`",
      "attributes": {
        "lorawan_field": "RejoinRequestPayload"
      },
      "correlation_id": "13bc2b42ea7b44b5891c04f13f859231",
      "cause": {
        "namespace": "pkg/encoding/lorawan",
        "name": "unknown_field",
        "message_format": "unknown `{lorawan_field}`",
        "attributes": {
          "lorawan_field": "RejoinType",
          "value": "92"
        },
        "correlation_id": "5a2819c420a541cb8b5b3dc6b2905cca",
        "code": 3
      },
      "code": 3
    },
"data": {
      "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",
      "namespace": "pkg/errors",
      "name": "validation",
      "message_format": "invalid `{field}`: {reason}",
      "attributes": {
        "field": "m_hdr",
        "name": "MessageValidationError",
        "reason": "embedded message failed validation"
      },
      "correlation_id": "285ff2f83bbc47119bbb10f7a4bd94a6",
      "cause": {
        "namespace": "pkg/errors",
        "name": "validation",
        "message_format": "invalid `{field}`: {reason}",
        "attributes": {
          "field": "major",
          "name": "MHDRValidationError",
          "reason": "value must be one of the defined enum values"
        },
        "correlation_id": "04023f10ffc34f0d836f492b5ce73b63",
        "code": 3
      },
      "code": 3
    },

Check to see if you have “do not send packets with CRC errors” and “do not send packets with no CRC” set to on - that will stop badly formed packets and packets that don’t meet the normal format from being sent over cellular.

It will still send proper LoRaWAN packets as gateways can’t tell who they are for - but it will at least filter out these ones.

Couldn’t find the settings you mention in the UI of dragino, but from the logread I can tell that it is only forwarding packets with a valid CRC:

daemon.info lora_pkt_fwd[7797]: REPORT~ # RF packets received by concentrator: 6
daemon.info lora_pkt_fwd[7797]: REPORT~ # CRC_OK: 50.00%, CRC_FAIL: 50.00%, NO_CRC: 0.00%
daemon.info lora_pkt_fwd[7797]: REPORT~ # RF packets forwarded: 3 (57 bytes)
daemon.info lora_pkt_fwd[7797]: REPORT~ # PUSH_DATA datagrams sent: 3 (765 bytes)

If the data-package is forwarded by the gateway it is a LoRaWAN-package with a valid CRC. But TTN is not the only one using LoRaWAN, there are a few other providers e.g. Helium, Loriot… using LoRaWAN technologies of Semtech.
The Gateways do not inspect the contents of a valid LoRaWAN -package, they just forward it to e.g. TTS (The Things Stack). There the decision is made whether to discard the data-package or to use it.
I receive a LoRaWAN -beacon that is transmitting 19 byted every 12 seconds and several Helium-devices. They all are causing traffic not intended for TTN. But the data-packages are all sent to TTS.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.