Hi! From what I can see on my gateway data, some devices uses much more than the DC they should respect. About a message of 26 bytes every 3 seconds using SF11… giving an airtime of 823ms/message and giving a total airtime per day of more than 23 k seconds per day. Is there any way to report this…

and another one. seen at GW funlab (B827EBFFFEA00A83) [Abuse-2]

In Haarlem I’m seeing abuse too, but it’s not actually the uplinks on SF12 I’m worried about. (If all is well then I won’t be using SF12 at all, and gateways can decipher simultaneous messages on the same frequencies if they use different spreading factors. Of course, maybe they cannot handle all 6 …

Good that you noticed. This indeed seems to be the backend desperately trying to get that device off SF12 using ADR. Not sure why it just keeps doing that even when the device doesn’t respond… I’ll look into that.

[image] htdvisser: This indeed seems to be the backend desperately trying to get that device off SF12 using ADR. Like you wrote elsewhere: TTN deployed a fix to send commands on SF12 if a node is erroneously expecting RX2 to use the LoRaWAN default SF12 rather than the TTN EU868 SF9 , and is n…

[image] htdvisser: list to the wiki: http://www.thethingsnetwork.org/wiki/LoRaWAN/Address-Space#address-space-in-lorawan_devices_prefix-assignments Any chance you can find an updated list? (Apparently some parking sensor is using 0x70.)

[airPollution] This guy is using up its 30sec airtime per day every 3 minutes… in zurich, switzerland

This particular device is not registered to TTN as far as I can see, so unfortunately there’s not much we can do except hope that it quickly runs out of battery.

I think all ttn gateways should blacklist such addresses in a way, that the gateway’s and backend’s processing power ist only minimally used… i consider this also as misuse of my internet and lan infrastructure if it is not blocked in the future…

The address itself is not the problem, it’s a perfectly valid address that could be registered to TTN. Blocking devices by address introduces a DoS attack surface, as anyone can transmit data with the same address as an authentic device. The gateway won’t be able to tell the difference, and we don’…

LoRaWAN duty cycle abuse

LoRaWAN LoRaWAN Discussions

htdvisser (Hylke Visser) December 14, 2017, 8:13am 27

Updated the list with three new allocations. 0x70 is not allocated yet.

Parking Sensor with TTN Gateway