Joined: 08 May 2018 Posts: 14224 Location: Texas, USA
Posted: Mon Feb 10, 2020 16:35 Post subject: New Build 42335: 02-10-2020-r42335
WARNING:DO NOT flash this experimental test build unless you know the risks and recovery methods. Report here to provide important info for developers and users. Always state your hardware model & version, mode (e.g. Repeater) and SPECIFIC build (e.g. netgear-r7000-webflash). Avoid discussions and create a new thread for specific problems or questions as this thread is not for support, and posts may be deleted or moved.
Important: if reporting any issues, provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.)
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template example to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
Router/Version: Dlink DIR-882 A1
Firmware: DD-WRT v3.0-r42335
Kernel Version: Linux DIR-882 4.14.170 #184 SMP Thu Feb 6 15:16:17 +04 2020 mips DD-WRT
Previous: r42132
Reset: No
Mode: 2.4GHz AP / 5GHz WDS AP
Uptime 1h
Status: Working, will edit post if something comes up.
did anyone else has tried this build on Dlink DIR-882 A1? any issues? is it safe to move to this from 03-27-2019-r39296 build?
If I do decide to upgrade, I know I have to factory reset it in a process, but can I later import a backup file from r39296? If not is there another method to migrate settings. I have a massive amount of configurations there and redoing it manually will take hours. I wish there was a build-aware tool on PC side that will parse a backup file and allow migration between builds or even platforms to make it clean.
did anyone else has tried this build on Dlink DIR-882 A1? any issues? is it safe to move to this from 03-27-2019-r39296 build?
If I do decide to upgrade, I know I have to factory reset it in a process, but can I later import a backup file from r39296? If not is there another method to migrate settings. I have a massive amount of configurations there and redoing it manually will take hours. I wish there was a build-aware tool on PC side that will parse a backup file and allow migration between builds or even platforms to make it clean.
OMG You're really still on this old release from March last year? Just a joke, don't judge me
The main reason why you have to do a reset to factory default at the point of upgrading to this actual firmware release is, the nvram settings from the old kernel v3 are presumably incompatible and could be result in a bricked device. So it's NOT recommended to do so. The same thing happens when you try to upload your old backup configuration file (-> your old nvram settings) into the new kernel v4.14.
I actual run the latest release r42335 without any big issues. There were much more problems with your old last release with kernel v3 r39296 you're still on.
Once you have configured everything again from ground, you can upgrade future releases without resetting again to factory default, as far as the kernel jump to a higher release isn't soooo high of course
OMG You're really still on this old release from March last year? Just a joke, don't judge me
The main reason why you have to do a reset to factory default at the point of upgrading to this actual firmware release is, the nvram settings from the old kernel v3 are presumably incompatible and could be result in a bricked device. So it's NOT recommended to do so. The same thing happens when you try to upload your old backup configuration file (-> your old nvram settings) into the new kernel v4.14.
I actual run the latest release r42335 without any big issues. There were much more problems with your old last release with kernel v3 r39296 you're still on.
Once you have configured everything again from ground, you can upgrade future releases without resetting again to factory default, as far as the kernel jump to a higher release isn't soooo high of course
It's good you have posted this because I think there's more than a fair few of us that didn't know about the reset. Now that I know to do the reset I'll give it a try at the weekend provided you, and a few others, confirm there's no issues with r42335.
Finally took the plunge and upgraded to 42335 from 39296 on my DIR-882-A1. So far, so good. A couple of minor issues that are probably known about: The Wifi LEDs still aren't working, not a deal breaker obviously, but it would be nicer to see them flickering away reassuringly. And second:
Does anyone know why some devices are showing as LEGACY in the client info list? Is this affecting performance or is it by design for the new kernel? Sorry if this has been answered previously. Again though, things seem to be fine, been up 24hrs now without issue, there has been upto 12 devices connected at the sametime, although the router is only really used as an AP.[/img]
Finally took the plunge and upgraded to 42335 from 39296 on my DIR-882-A1. So far, so good. A couple of minor issues that are probably known about: The Wifi LEDs still aren't working, not a deal breaker obviously, but it would be nicer to see them flickering away reassuringly. And second:
Does anyone know why some devices are showing as LEGACY in the client info list? Is this affecting performance or is it by design for the new kernel? Sorry if this has been answered previously. Again though, things seem to be fine, been up 24hrs now without issue, there has been upto 12 devices connected at the sametime, although the router is only really used as an AP.[/img]
Same issue I had with my 54g devices.
Eventually they started disconnecting every 30 seconds.
After almost 15 day uptime, the webgui can no longer be accessed. SSH works fine though, and top states load avg 4.96 4.93 4.92 2/65 5701. Throughput is also fine since im able to cap my 100/100 mbit line via wifi.