I have a network server running with the default network id of 000000. It has a device which is already joined and sending data. I wanted to update the network id on this network server so that I can utilise the network id filtering option on the gateway.
My understanding was that if I change the network id, then the devices need to be rejoined so that they can send data again. But when I updated the network id and restarted the network server, the device continued to send data without any interruption. Is this how it is supposed to work?
I came across this behavior and confirmed with @brocaar that it is intentional. The network server only uses the NetID at join time, it is not used for validation after the fact. This allows you to, for example, migrate devices live without rejoin from a network server with one NetID to another network server with a different NetID.
I’m reopening this thread since I need some clarification on a NetID migration.
I’d like to do the same thing @Zakir_Hussain wanted to so, so change the NetID to filter just my devices on my gateways (RAK WizGate 7268CV2).
As per what’s written in the thread, if I just change the NetID, the already present sessions would continue to be active and thus the device would send uplinks without any problem.
Next thing I’d like to filter the traffic from the gateways to Chirpstack to the only uplinks from my NetID. So if I add the NetID on the gateways, what would happen? Are the uplinks from the already connected devices (with DevAddr with the old NetID) going to be discarded or are they going to be kept since they have already working sessions?