Refer to the OpenWrt documentation: Failsafe mode, factory reset, and recovery mode <https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset> .
F. On Fri, 12 Jul 2024 at 09:30, Piviul <[email protected]> wrote: > Hi all, I have installed openwisp and changed some parameters in a > openwisp template relative to the wireless configuration. When they are > deployed to the router I've got these logs: > > Fri Jul 12 12:59:26 2024 daemon.info openwisp: Local configuration > outdated > Fri Jul 12 12:59:26 2024 daemon.info openwisp: Downloading configuration > from controller... > Fri Jul 12 12:59:26 2024 daemon.info openwisp: Configuration downloaded, > now applying it... > Fri Jul 12 12:59:28 2024 daemon.info openwisp: Service network has been > reloaded via procd/ubus > Fri Jul 12 12:59:28 2024 daemon.info openwisp: Service system has been > reloaded via procd/ubus > Fri Jul 12 12:59:28 2024 daemon.info openwisp: Service wireless has been > reloaded via procd/ubus > Fri Jul 12 12:59:30 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 > names > Fri Jul 12 12:59:30 2024 daemon.info dnsmasq[1]: read > /tmp/hosts/dhcp.dnsmasq1 - 0 names > Fri Jul 12 12:59:33 2024 daemon.info openwisp: Testing configuration... > Fri Jul 12 12:59:33 2024 daemon.info openwisp: Configuration test > succeeded > Fri Jul 12 12:59:33 2024 daemon.info openwisp: Configuration applied > successfully > Fri Jul 12 12:59:33 2024 kern.info kernel: [14951.527763] device wlan0 > left promiscuous mode > Fri Jul 12 12:59:33 2024 kern.info kernel: [14951.532411] br-lan: port > 3(wlan0) entered disabled state > Fri Jul 12 12:59:34 2024 daemon.notice netifd: lan (7004): udhcpc: > received SIGTERM > Fri Jul 12 12:59:34 2024 daemon.notice netifd: lan (7004): udhcpc: > unicasting a release of 192.168.64.70 to 192.168.64.2 > Fri Jul 12 12:59:34 2024 daemon.notice netifd: lan (7004): udhcpc: > sending release > Fri Jul 12 12:59:34 2024 daemon.notice netifd: lan (7004): udhcpc: > entering released state > Fri Jul 12 12:59:35 2024 daemon.notice netifd: lan (7004): Command > failed: ubus call network.interface notify_proto { "action": 0, > "link-up": false, "keep": false, "interface": "lan" } (Permission denied) > Fri Jul 12 12:59:35 2024 daemon.notice netifd: Interface 'lan' is now down > > So the openwrt device lan is down now and I can't reach the device any > more. In this cases I have to reset with the device button or there is > some other way getting control on it? > > Piviul > > -- > 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]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/55d5e249-1912-4f3f-aa08-947e1adb950d%40gmail.com > . > -- 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]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6LkcWGVRk%2BP9a18herjD%2BgS8dQLSzKM0GZx%3DLk4gea3Fg%40mail.gmail.com.
