Firmware Version
DD-WRT v3.0-r40784 std (08/25/19)
Kernel Version
Linux 4.9.190-rc1 #1245 SMP Sun Aug 25 04:08:25 CEST 2019 armv7l _________________ WRT1900ACSv2
Last edited by DaveI on Sun Aug 25, 2019 19:04; edited 2 times in total
Upgraded WRT1200AC v1 from r40723 to r40784 using Waterfox 56.2.13 (64 bit) running on Linux Mint 19.1 OS.
Ran command "ubootenv set boot_part 2" before update. Successful update and reboot. Usual OpenVPN yellows in syslog. No reset,no issues. Uptime about 45 minutes
r40723 running so well for me I hesitated to update to r40784
Kernel Version Linux 4.9.190-rc1 #1245 SMP Sun Aug 25 04:08:25 CEST 2019 armv7l
Aug 25 08:12:34 router daemon.notice openvpn[1733]: OpenVPN 2.4.7 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 25 2019
Aug 25 08:12:34 router daemon.notice openvpn[1733]: library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.09
Edit: Randomly dropped VPN connection a few times over the past 24 hours, reverted to r40723 The drops were the only issue I've had but not getting that with r40723
Last edited by Monza on Mon Aug 26, 2019 12:06; edited 1 time in total
OpenVPN CLIENT works fine (nordvpn server)
5GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
2.4GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
NAS via USB Samba also working fine
Try to Upgrade WRT1900ACS v2 from r40723 to r40784. Download FW File. Updrade runns o.k.! After Upgrade the Router shows still the Version r40723! Second try, same. So what is the problem? Is the file r40784 wrong on FTP Server or what can i do?
Try to Upgrade WRT1900ACS v2 from r40723 to r40784. Download FW File. Updrade runns o.k.! After Upgrade the Router shows still the Version r40723! Second try, same. So what is the problem? Is the file r40784 wrong on FTP Server or what can i do?
Did it fail to update because you were trying to flash it to the smaller partition?
So i not understand... till version Firmware: DD-WRT v3.0-r40723 std (08/21/19) i do everytime the same. Upload new FW file and ready. And now the partition is too small? in frist post he write he is upgrade to first partition on 1900acs v2. So what is the solution to make the new upgrades?
Last edited by marcox on Mon Aug 26, 2019 14:31; edited 1 time in total
go to admin,commands and run this
ubootenv set boot_part 2
then flash to the current firmware
then from now on every time before you flash your going to want to run
ubootenv set boot_part 2
First then flash
the newer firmwares are to big for partition 2 _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Ran "ubootenv set boot_part 2" command to get back to build r40009 on the second partition then successfully upgraded to r40784.
OpenVPN still fails to start when enabled and pressing save then pressing apply. I checked in Status/openvpn and the vpn was not running. I have to press apply a second time to get it to run.
Build r40009 is still the last build I haven't had bugs. The best thing (for me) about the new builds is the addition of Cake to the list of QoS disciplines. I used it in openwrt and it works much better for me.
i understand but last question:
"i suggest going to firmware 40009 flash that twice"
how to do i install the firmware 40009 flash twice?
O.k. fist is normal, but the second i need the command first?
..............
i assume your on partion two already with the current firmware, if its questionable if partition two is valid
ubootenv set boot_part 1 then flash 40009 that would put 40009 on partition 2, then from there you could flash the new one to partition 1
in the end you want to end up with a good firmware on partition 2 so if you run into trouble down the line with a bad flash it has something valid on partition 2 so you can recover is the whole point of it.
ubootenv get boot_part will tell you what partition you are currently on.
output would be:
a_pEnv->crc = b2121afb
crc32 = b2121afb
1
means you on partition 1 now.... if it says 2 then your currently on 2....
the point of the command
ubootenv set boot_part 2
is to fool the router into thinking you are on partition 2 during a flash so it writes to partition 1
ubootenv set boot_part 1
would then ofcourse make the flash write to partion 2
so if you have any doubt what so ever on if you have a good flash on partition two i mentioned 40009 build because i know it fits on partition 2 and it is also a pretty stable solid build.
Newer Builds are bigger then partition 2 allows
good luck and enjoy. _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.