I do not think this is part of any standard at the moment, so this might be about creating somethign new…
would it be possible / sensible at the Network server to be able to send OUI restriction lists to all the gateways, so they could filter which OUI’s are accepted/rejected. Sort of like a routing protocol of sorts…
This could be further extended for a network server to ‘advertise’ OUI’s, to other NS’s… You could in effect ‘peer’ between Network Servers…
It’s a possible approach, sure. There is at least one unnamed proprietary LoRa implementation that does this by running a network server on each gateway. Personally, I care a lot less about using extra bandwidth to send unnecessary payloads than I do about the maintenance burden of filtering at the gateway level.
This is probably what the Basic Station is doing by filtering on NetID and JoinEUIs V3 (a test version has been released) of the LoRa Gateway Bride does support sending this information to the Basic Station when the gateway connects, see the config example below:
# NetIDs to filter on when receiving uplinks.
# JoinEUIs to filter on when receiving join-requests.
I didn’t have a specific reason. The way I read this was that the ‘restriction’ for Net Id’s / Join Id’s was being done on a LoRa Gateway Bridge. However I didn’t think this quite through and had assumed it was a ‘centralized’ bridge where UDP packet forwarders were pointed to. I can see that this could be implemented on the gateway device as well. Thanks for the explanation. ( and this just needed some more time to think it through )…
Which component of the architecture would send the list of Net_ids / join_euis to the gateway bridge?
I had a play with the example code and have a much better understand of how it works now. Is there any point in trying to integrate this with the NS? The NS, needs to know about its NetID; you doint’ really want to have to configure the same information twice?
Not sure to be honest. In some cases this might make sense, but ideally the LoRa Gateway Bridge should be able to work without a NS to provide an API to the gateway. Maybe for now it makes sense to keep this information in the lora-gateway-bridge.toml file.
Potentially CUPS, or other tools allowing you to do remote gateway management could help you to keep the gateway configuration in sync.