In the middle of my tests with Basic Station with CUPS , I found another problem when I was trying to change the Packet Forward configuration by web console with TTNV3 to AWS IoT Core LoRaWAN:
- I finish the Basic Station configuration with an “apply & save”, and everything seems to be fine, but it is not true.
- When I did a reboot, the Packet Forward configuration back to web console and by syslog messages I saw that the gateway back to Packet Forward mode instead of Basic Station.
- The strange behavior is that when by web console a change the configuration again to Basic Station, the AWS configuration that I did, it came back, I did again “apply & save”, the Basic Station operation mode back. The problem is that if I reboot the gateway, I will lose again the Basic Station configuration.
It seems to me like a Web console bug and the Basic Station is being saved as the “current operation mode”, but it still there in “some place”.
I attached two screenshots below.
Could you help me?
Regards,
Cláudio


. Lessons learned only one configuration source 