I’m trying to implement multiple frequencies schema using only one AS and one GW Bridge.
The idea is to keep only one port opened (i.e. 1700) on our UDP rule and all gateways from all different frequencies being connecting to same address/port.
On GW Bridge, I would need to route the traffic to the right NS instance.
Is there any possibility to achieve that ?
Route all traffic to all NS is an option ?
I did the test:
2 NS instances, 1 AU915 and 1 US915. Both subscribed to same gateway topic.
2 Gateways pointing to same topic.
Provisioned both gateways on AU915.
Provisioned one device to AU915.
US915 NS still empty, no gateways, no devices, no profiles.
For some unknown (yet) reason, the logs on NS US915 (the empty one) shows some activity, like it was accepting the join request:
12/7/2021 12:29:29 PMINFO gateway/mqtt: uplink frame received gateway_id=7076ff02acb2ff00 uplink_id=914835ce-5bee-4dab-bae0-ed1568656666 12/7/2021 12:29:29 PMINFO gateway/mqtt: uplink frame received gateway_id=000080029cc78e2e uplink_id=6a0e3077-2953-4c3d-80a1-ca4c302963ef 12/7/2021 12:29:35 PMINFO gateway/mqtt: uplink frame received gateway_id=000080029cc78e2e uplink_id=f03732a6-1bb6-4efa-9e98-96e09f6ba968 12/7/2021 12:29:35 PMINFO gateway/mqtt: uplink frame received gateway_id=7076ff02acb2ff00 uplink_id=43e775c3-081a-4e4f-98ea-e8947c603e82 12/7/2021 12:29:39 PMINFO backend/gateway: downlink tx acknowledgement received downlink_id=658b19ee-3244-4e90-81d9-6de2d75b1e22 gateway_id=7076ff02acb2ff00 12/7/2021 12:29:39 PMINFO device-session saved ctx_id=658b19ee-3244-4e90-81d9-6de2d75b1e22 dev_addr=e074eba5 dev_eui=848bcdfffe60a2ba 12/7/2021 12:29:39 PMINFO sent downlink meta-data to network-controller ctx_id=658b19ee-3244-4e90-81d9-6de2d75b1e22 12/7/2021 12:29:40 PMINFO gateway/mqtt: uplink frame received gateway_id=7076ff02acb2ff00 uplink_id=af7d1b51-0d6f-4603-a639-d4ab795143fc 12/7/2021 12:29:40 PMINFO gateway/mqtt: uplink frame received gateway_id=000080029cc78e2e uplink_id=e5569413-e429-43aa-8405-61448af54006
Which should not happen in my understanding.
All profiles (gateway, device, service) are pointing to AU915 NS instance.
In this test, the device becomes lost. It asks for join several times (seems to be on both NS) and loose its keys suddenly and need to join again. Once I stop the US915 service, it works normally.
The only populated table on US915 database is the rounting_profile, which points to AS API address.
Shouldn’t the US915 instance just ignore those packets ? In my understanding is almost the same case as one unknown device on gateway range sending packets to it.
Any hint about this infra is really appreciated.