[squeeky]

Hi,

I have a WRT1900ACS v2 and have been running the following Kong build forever...

v3.0-r30880M kongmv (11/14/16)

It is time to move on as I would like to use some new features in the current builds and there are a few issues I am tired of.

Anyway I would like some advice on if I can flash right over this build with the latest (v53469) in the repository? My concern is the age of the firmware (2016) and if I have to do it in steps.

I believe I use "ddwrt-linksys-wrt1900acsv2-webflash.bin"

Any advice appreciated.

Thx

[kernel-panic69]

I would consider flashing 08-27-2023-r53445 first, doing a hard reset, then flashing 09-08-2023-r53469 after setting a password, and configuring from scratch. Reason being that wireless interface names have changed and you wouldn't want a build that old on the other partition IMHO.

[squeeky]

So I followed your advice and was able to upgrade to 53445. Hard reset. Everything looked fine. Changed the default subnet from 192.168.1.1 to 192.168.2.1 to match my old config including DHCP scope. Noticed that DHCP worked on boot but all of a sudden no other device could get an IP. Reboot same issue. Factory default to try again. DHCP stops after a short period of time. Upgraded to a 53469 same problem. Thoughts?

[kernel-panic69]

Are you using static leases? Did you import a previous config? Configuration details would help.

[squeeky]

Since I was going from such an old build (Kong 2016) I took screen shot of all my settings and did a factory default for the upgrade. I only noticed the DHCP issue after I configured the WiFi and my clients could not get an IP. I then did a release and renew on my wired PC (used for setup) and it too could not get an address. I had to manually assign one to access the router again.

[dale_gribble39]

Do a hard reset and try minimal configuration and save/apply (or save/reboot), ensuring you wait 5 minutes between apply and until it breaks. Sounds like a bad hostname in a static lease is killing dnsmasq or keeping it from starting.