On Friday, April 7, 2017 at 10:35:36 AM UTC+2, Federico Capoano wrote: > > On Thursday, April 6, 2017 at 7:07:43 PM UTC+2, henriqsc wrote: >> >> Great. Many thanks. >> >> It applied the configuration without actualy testing it I guess because >> the device where I'm testing it is behind a DHCP modem and I lose >> connection to the controller after I set pppoe. Is that the expected >> behaviour when test_config is not set? >> >>> >>> > Yes, if you disable test_config and supply a problematic configuration > that causes the device inability to reach the controller, you will lose the > device and you will have to restore it in other ways, either by connecting > directly to it with an ethernet cable, but sometimes you may need to go as > far as to put it in failsafe. > > OpenWISP 2 is basically an automation tool. Before you start automating a > process, you should first ensure this process works as expected. So try to > always test your configurations before automating them with openwisp. > > And another suggestion: leaving the test_config option disabled is not a good idea for production use.
I disable that flag in very rare cases and only for debugging purposes. -- 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.
