With the latest version of firmware, Dragino gateways like LPS8, LIG16… now are able to blacklist (or whitelist) dev addr’s or fport’s. This function has been implemented a few versions ago, but I never got it running until today.
Using this function, a pre-selection is done by the gateway. The blacklisted data are not sent to TTS , they don’t use internet bandwidth anymore.
1 Like
On this forum we have had multiple (lengthy) discussions on why filtering at gateway level is bad for the community network. Anyone interested: use search to find the discussions.
Please do not use filters at gateway level!
2 Likes
Good Morning, I appreciate this was posted some time ago but I haven’t yet worked out how to post my own topic. I wondered if you guys can help at all.
I’ve got a few of the Dragino gateways (DL0S8N& LPS8N) and have been trying to reduce gateway traffic, they are installed in an area where there are a number of 3rd party LoRa devices that are set up at higher transmission intervals than my own and keep eating through SIM data. I set up the device address filter to whitelist just my devices but as these are not a unique code I was still allowing some third party devices through and I was still seeing other dev addresses in the gateway traffic.
Dragino have recently allowed for dev eui packet filtering so I have set that up instead so to only allow the unique dev eui through the gateway. This now has devices that I was receiving data from hourly only successfully sending data every 24 hours or 48 hours.
I wondered if you had any issues like this or had any advice please. I can see above that you don’t recommend filtering at the gateway? I wondered why this might be? Or is this for gateways plugged directly into an ethernet port rather than being reliant on SIM data?
Any helps appreciated, I’m still relatively new to the LoRa world.
Thanks in advance
In that case (or when applying any other form of filtering) please use a private lorawan network server, not TTN.
A gateway on the community network is not useful to the community if it just forwards data for your devices. You effectively created a private gateway that should be on a private network, not the ‘public’ network.
Why? Because my devices can’t use your gateway because of the filtering. However I don’t know that so when I look at the map I assume there is a gateway in range. Now, I am not that ignorant, but new users may encounter issues because their traffic is not forwarded while everything points to the device being in range of a gateway, waste many hours and because of it become disappointed in the technology.
Your EUI filter can’t work because once a device joined the EUI is no longer transmitted. Just device addresses.
Thank you for getting back to me.
Apologies. I have it set up as a private server.
The issue is that I don’t believe the filter is actually being effective, other devices are still seen in the gateway traffic. I went away from using the dev add filtering as they are not unique and moved over to dev eui filtering to help this. The dev eui filtering is something that Dragino themselves has brought out and recommended that I use to help solve the traffic issues.
It’s interesting to know that the dev eui is no longer transmitted once connected, though seems odd that they would put this type of filter in place.
If it is private, what does it have to do with TTN?
How many cents are you saving? Suppose a lot, as you are useing a stack developed by others dev and you are not paying for it .
You can filter join requests using the deveui. If you somehow have access to the devaddr assigned by the network server you can use that for further filtering.
Questions: what is the netid being assigned to your devices?
What is the amount of traffic without a filter applied?
Hi, Thanks for getting back to me again.
Yes I have access to the dev address but unfortunately these aren’t unique and are unchangeable. Other devices outside of my own have the same dev add, so in whitelisting just my own dev add I am enabling others to come through the gateway.
I am unsure on total traffic but typically I would use around 1.5GB of data a month, currently the better located gateways are using >15GB.
I pay to use the stack but have the data coming back through to a private LoRaWAN server rather than TTN. Currently data is 10x over what I would expect of my devices, as are the costs associated.
Device addresses aren’t meant to be unique. However unchangable? The LNS assigns a new address every time a device (re)joins.
It sounds like you and the other network(s) are both using the 00 prefix. That is usual for private deployments but as you found it can lead to ‘conflicting’ device addresses that can’t be filtered at gateway level. You could look into the cost of getting your own private prefix if traffic is expensive. BTW, using a non-IoT SIM is usually a cheaper way to get connectivity. There should be mobile providers in the UK that offer multiple gigabyte plans below 10 pounds a month.
1 Like
Thanks you for all your help. I’ll have a look into it.