Tried an update to daily 80-014217a on an NS M2 XW, reinstalled Tunnel, and it's back on the air ok. I noticed free space for flash = 68K. I don't recall what it might have shown before. iirc, this node went from 3.17RC1 thru a few dailies up to old 176. Not sure where it started as far as Air OS. Could it be related to this https://www.arednmesh.org/content/bad-rocket-m5 ?
Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 5120 5120 0 100% /rom tmpfs 30092 212 29880 1% /tmp /dev/mtdblock5 1216 1148 68 94% /overlay overlayfs:/overlay 1216 1148 68 94% / tmpfs 512 0 512 0% /dev
This node had a habit of not re-establishing the tunnel and OLSR stopping after the slightest outage over the internet (like when the cable co reboots something in the middle of the night), often requiring a hard boot. Maybe related if it's running out of space? Will watch it over the next couple days.
Recovery? Bad flash memory? Replace unit?
Ian
File
Ian, The OpenWrt group increased the 'NOR' flash storage space, showing up as /rom, for the initial image on flash memory. This is what the node reverts back to when holding the reset button (while booted) for ~15 seconds. This increase took away from our local custom configuration settings and add-on package space, showing as the overlay. The overlay keeps a delta of file changes on top of the /rom . It is good that there is enough space to install the tunnel packages :) . This flash is used like a disk drive on a typical computer -- it is long term storage and slower memory generally.
This issue with OLSR and other issues are unrelated. Generally these are due to lack of RAM memory, a different sized chip than 'flash', for the program and linux kernel to run and/or defects/scalability issues with OLSR.
Be sure to only run the nightly builds on a device with 64Mb RAM. We've not gone through to make changes that reduce the usage of RAM yet. 32Mb RAM devices are unstable. The NS M2 XW is a 64Mb RAM device, so you're OK on this device to run the nightly builds.
Joe AE6XE