RAX80 New Firmware Released 1.0.1.70

This is going to be long getting to the point, but if I'm wrong, I went someone to be able to tell me where, or be able to recreate the steps next time they flash back and have access to telnet, which I would kill for right now to see what's going on in the logs. It's possible to fix the access control/attached devices problem. Maybe.

So I just got this router on Saturday and pretty much hit all the problems, especially attached devices and my regular log showing about thirty entries of nothing but the date Wednesday, Dec 31,1969 18:00:00 at random intervals,. I factory reset, telneted in to clear the NVRAM, installed the original firmware release, and spent the last few days testing to see what was going on and took notes. Today I finally came back to the latest firmware for a bit because I was about ninety percent sure the problem was something was causing an overwrite of the NVRAM in the ac_dev_names variables at different points in the strings except--for some reason--the first six devices listed in ac_dev_names. Not a javascript or json, either, so not something I could correct myself.

I saved and examined the nvram eight times and those first six devices in 0 were the only part that never changed. I also saved multiple versions of update_device_info.log and device_detect.log from /tmp so I could see what was happening between changing the name, it showing up in /tmp/devices.json, and then being populated into /tmp/AttachedDevices. I learned one, someone didn't know how to spell Attached; two, groups is misconfigured in /etc but as it's read only, I couldn't fix the problem with 'guest' ; and three, the process wget-device runs in conjunction with get NTP time every three seconds according to the update_device_info. log, which seemed excessive, with _Agent.isStartChecking:0 running right before wget-device every fifteen seconds. This weirdness with time also appeared in device_detect.log, but it was arps every six seconds with random time travel to January 2016 and September 2018.

Anyway, I decided to try again later when I felt like bringing down my entire network and rebuilding it again, updated the firmware to current, noticed Access Control was screwing with the names again and went to play with the Nighthawk app because my profession is software testing and mobile app testing and this is how I have fun. I filled in all the devices in the app to the correct name and give them random device types and turn remote management on and off, yeah, there's not much to do there When I went back to the main browser interface, though, attached devices were--well, not right, but all the names matched the app even if it thought half my devices were Fire TV 4K Generation 3. Access Control was perfect; all my names were exactly as I had entered them. I went to attached devices, tentatively fixed the device type and model, it all stuck. Access Control stuck. While I was looking at settings in the online gui wondering about witchcraft, I noticed ion the NTP page that Daylight Savings Time was unchecked, which has also kept happening like a lot. I turned it on (again), went to verify some wireless settings, and then went back to Attached to see my devices progressively becoming unknown, and Access Control as well. I recreated all my app steps, no go, then I remembered how weird it was that NTP was running every three seconds during device detection, remembered this thread where someone said their speed was throttling at time sync even after the QoS toggle, and turned off Daylight Savings Time and recreated my steps again in the app.

Roughly three hours and change later (as of now), Access Control and Attached Devices in the online GUI are unchanged from what I entered in the Nighthawk App this last time, except what I've edited in attached devices for model and device type every so often to see if it holds and adding a device in Access Control. So its sticking, at least for three and change hours and counting. Still getting the December 31 1969 entries in the log, though. So this might fail at the four hour mark, but I thought I'd share in case someone else can use this.