You are here

Issue with Nightly Build on PicoStation M2 - Settings Not Committing

3 posts / 0 new
Last post
ve2wyd
ve2wyd's picture
Issue with Nightly Build on PicoStation M2 - Settings Not Committing

Hi everyone!

I recently flashed a couple of PicoStation M2 units with the latest nightly build firmware:
aredn-20240920-6d259c7-ath79-tiny-ubnt_picostation-m-squashfs-factory.bin

The flashing process completed successfully, and I switched to DHCP. Upon the first boot, I got assigned 192.168.1.10 via DHCP, so I connected to 192.168.1.1 as expected. I was prompted to set a node name and password. I entered VE2WYD-QTH for the node name and dummypass/dummypass for the password. After saving and rebooting, I expected to receive an IP in the 10.71.210.185/29 range, but instead, I keep getting 192.168.1.10.

Moreover, each time I reconnect, it repeatedly asks me to set the node name and password, as if the settings aren’t being committed.

The only way I’ve been able to successfully use the nightly build is by first installing the stable version aredn-3.24.6.0-ath79-tiny-ubnt_picostation-m-squashfs-factory.bin, setting it up, and then upgrading to the nightly build using the aredn-20240920-6d259c7-ath79-tiny-ubnt_picostation-m-squashfs-sysupgrade.bin through the node's GUI.

Has anyone else experienced this issue with the nightly build, or does anyone know a solution?

Thanks in advance!
Bruno (VE2WYD)

K7EOK
Picostation M2 is listed as
Picostation M2 is listed as untested and sunset.  I don't understand why you would put a nightly on it.  Just revert to the last stable firmware you were able to run on it and consider upgrading to a newer device with more memory ... if you can.   Ed
 
ve2wyd
ve2wyd's picture
PicoStation M2
Well I know its legacy HW, I just happens to have over 30 picos laying around with antenna.  Wanted to try out the new UI...
They work well as a AP, 8MB is indeed really low.

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer