Is it possible to filter packets when using Basics Station?

[Rafael]

Hi,

Our gateways (MTCAP-L4E1) are configured to use Basics Station and a private network server (The Things Industries Stack).

Is it possible to filter the LoRaWAN packets before sending them to the cloud? For example, to only send packets coming from our devices and drop all the rest?

We only use 3G/4G for backhaul and we don’t know where the gateways will be installed so we’re looking for ways to reduce data consumption.

Regards,

Rafael

[Jason Reiss]

The router_config message from the LNS can contain a JoinEUI and NetID list to be used to filter packets. The NetID is unique per network operator, so TTI has one assigned, this NetID is used to assign the first 7-bits of the DevAddr used for uplink/downlink packets.

These settings cannot be added in the gateway configuration, they must be provided by the network server, TTI in this case. I do not know if they support these settings for basic station.

The gateway does not know which are your DevAddr/DevEUI to filter individually.

https://lora-developers.semtech.com/build/software/lora-basics/lora-basics-for-gateways/?url=tcproto.html

[Rafael]

Hi Jason, thanks!

Apparently, TTI has not implemented it yet:

https://github.com/TheThingsNetwork/lorawan-stack/issues/3909

But they do mention this problem in the documentation:

“In general, a gateway will receive all other LoRaWAN and non-LoRaWAN traffic from neighbouring devices, and it will forward that traffic to the Network Server. When it comes to filtering unwanted sensor data at the gateway level, users might consider using a gateway with a whitelisting function. This function can effectively reduce data traffic and operational costs. Please contact your gateway’s manufacturer for additional info.”

Is there another method for filtering packets while using a cloud-based LNS?

[Jason Reiss]

The chirpstack bridge has similar filtering options but only works with chirpstack server.

[Rafael]

Ok, thank you!

[Author]

Posts