Hi Henrique, On Mon, Apr 3, 2017 at 11:06 PM henriqsc <[email protected]> wrote:
> Hello > > We are trying to set up our routers to get the configuration from the > controller at boot time but we realised that it was not happening probably > because the wan interface was not ready to communicate to the controller > before the firmware itself starts. We tried to solve that by setting > connect_timeout and increasing it to say 120 seconds which would be > enough time to the wan to be ready. If I got it right openwisp_config would > allow 120 seconds to the wan to be ready but it didn't work that way. For > testing purposes we set a sleep time of 120 seconds at the beginning of > /etc/config/openwisp_config bash script and that sort of worked the way we > expected, we were able to get the configuration after 120 seconds. > That is not needed, openwisp_config tries to connect to the controller automatically and retries after a while if it can't. If the wan interface is not ready, after the specified interval, openwisp_config will retry. See the Debugging section of openwisp-config README <https://github.com/openwisp/openwisp-config#debugging> (and I suggest to the rest of the README if you haven't read it already). Our interval time will be 7200 seconds because we want to preserve link > capacity and also want to avoid applying configurations every 2 minutes so > that this operation does not disrupt the operation of the routers. In this > regardt does openwisp_config applies the configuration even if there is no > changes to the configuration? > No, openwisp-config only downloads a configuration checksum to compare with the configuration checksum of the last configuration applied. It proceed to downoad and apply the full configuration only if detect changes. -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
