LoRa Gateway Bridge v3.2.0
Features
NetID and JoinEUI filters
Configuration options have been implemented to filter uplink messages on netID
and JoinEUI. This makes it possible to ignore messages from neighboring networks
to save on bandwidth usage (e.g. when the gateway is using a cellular backhaul).
Execute commands
This feature makes it possible to execute commands on the gateway (when the
LoRa Gateway Bridge is running on the gateway). Note: commands must be
pre-configured in the LoRa Gateway Bridge configuration file.
Improvements
Basic Station backend
- Verify Common Name when using client certificates. (#129)
1 Like
@brocaar
NetID and JoinEUI
filters are working with semtech packet forwarder?
Yes, in case of the UDP packet-forwarder, LoRa Gateway Bridge will take care of the filtering
Thank you @brocaar
but i have seen below configuration for filter and it’s shows basic_station.filters
# Filters.
[backend.basic_station.filters]
# NetIDs to filter on when receiving uplinks.
net_ids=[
"000000",
]
# JoinEUIs to filter on when receiving join-requests.
join_euis=[
["0000000000000000", "ffffffffffffffff"],
]
can you please guide us forUDP packet-forwarder filter configurations
Thank you
Please see https://www.loraserver.io/lora-gateway-bridge/install/config/. These have been made global (if you have configured them under the basic_station
section, then these remain working but are applied to the Basic Station only so this is fully backwards compatible).
I see configuration file but it’s shows under basic_station
below is my configuration for global filters (can you please check)
# Filters.
[backend.filters]
# NetIDs to filter on when receiving uplinks.
net_ids=[
"000000",
]
# JoinEUIs to filter on when receiving join-requests.
join_euis=[
["0000000000000000", "ffffffffffffffff"],
]
Local cache of the page? This is what I see:
2 Likes