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
WRT1900ACS V2
Web flash via chrome from build 40134.
Initially appeared stable, but quickly developed serious issues for me.
Flashed with QoS off. On Chrome new QoSs showed as 'undefined' but via Firefox showed all options. Turned QoS back on in Firefox and switched to Cake from Pie.
After around 30 minutes I lost connectivity to internet and thought I was unable to connect to router at all, even by cable, but managed to restore connection, then switched boot partition to revert to 40134.
Question . I am wondering whether a factory reset might fix this and whether the settings being carried over from the older build are causing these issues?
I've been running this build on my WRT1900ACS V2 for about 14 hours now with no such problem but I do not use the QOS as I've found it did not do anything to reduce bufferbloat on my setup and only resulted in consumption of bandwidth...Also sometimes a reboot of both the router and the Gateway device after an upgrade (In my case a Ubiquiti CPE) will avoid the loss of connectivity...At least that's the case for my setup. Flashing with Chrome has also been found to be problematic in the past for some. I did an upgrade from the previous build using the web-flash file.
ttowling wrote:
WRT1900ACS V2
Web flash via chrome from build 40134.
Initially appeared stable, but quickly developed serious issues for me.
Flashed with QoS off. On Chrome new QoSs showed as 'undefined' but via Firefox showed all options. Turned QoS back on in Firefox and switched to Cake from Pie.
After around 30 minutes I lost connectivity to internet and thought I was unable to connect to router at all, even by cable, but managed to restore connection, then switched boot partition to revert to 40134.
Question . I am wondering whether a factory reset might fix this and whether the settings being carried over from the older build are causing these issues?
Upgraded WRT1200AC v1 from r41117 to r41134 using Waterfox 56.2.14 (64 bit) running on Linux Mint 19.1 OS.
Successful update and reboot. No reset, nothing disabled prior to update, uptime about 30 mins, wired/wireless connected, vpn up immediately. No drops wired/wireless or OpenVPN. New data added to syslog that I don't recall seeing before.
Kernel Version Linux 4.9.194 #1313 SMP Wed Sep 25 04:35:31 CEST 2019 armv7l
Sep 26 07:52:36 Steve daemon.notice openvpn[1655]: OpenVPN 2.4.7 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Sep 25 2019
Sep 26 07:52:36 Steve daemon.notice openvpn[1655]: library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.09
I have a similar problem on 2 wrt3200acm routers configured as WDS Stations. The link to the WDS AP via 5 GHz seems to be stable. I still have admin access to all of the routers from a wired connection though. And the 2 GHz radio seems to die even though the status page says it's up. 2 GHz clients that were attached drop off. Rebooting the WDS Station routers restores service. I tried a factory restore on one of the routers and manually reconfigured it but the problem persists.
ttowling wrote:
WRT1900ACS V2
Web flash via chrome from build 40134.
Initially appeared stable, but quickly developed serious issues for me.
Flashed with QoS off. On Chrome new QoSs showed as 'undefined' but via Firefox showed all options. Turned QoS back on in Firefox and switched to Cake from Pie.
After around 30 minutes I lost connectivity to internet and thought I was unable to connect to router at all, even by cable, but managed to restore connection, then switched boot partition to revert to 40134.
Question . I am wondering whether a factory reset might fix this and whether the settings being carried over from the older build are causing these issues?
Could you show the warning message from syslog page for the administrator information please? (http://192.168.1.1/Syslog.asp)
I fear to upgrade about WRT1900ACS V2. It is unstable.
Thanks
ttowling wrote:
WRT1900ACS V2
Web flash via chrome from build 40134.
Initially appeared stable, but quickly developed serious issues for me.
Flashed with QoS off. On Chrome new QoSs showed as 'undefined' but via Firefox showed all options. Turned QoS back on in Firefox and switched to Cake from Pie.
After around 30 minutes I lost connectivity to internet and thought I was unable to connect to router at all, even by cable, but managed to restore connection, then switched boot partition to revert to 40134.
Question . I am wondering whether a factory reset might fix this and whether the settings being carried over from the older build are causing these issues?
I am a dd-wrt user.
I think my message may make your inconvenience.
I recommend all of us (including me) report the operation of our routers.
If we report the dd-wrt build (Normal Operation or Abnormal Status)
Please also highlight the warning message from System Logs. The situations may make Programmer debug easily for the next build.
I am a dd-wrt user.
I think my message may make your inconvenience.
I recommend all of us (including me) report the operation of our routers.
If we report the dd-wrt build (Normal Operation or Abnormal Status)
Please also highlight the warning message from System Logs. The situations may make Programmer debug easily for the next build.
Posted: Fri Sep 27, 2019 4:13 Post subject: WRT1900ACSV2 (T_T)
On my last post, I also mention that WRT1900ACSV2 DD-WRT Build is unstable since November 2017. The CPU Temperature is too high to 83.2C. It causes the CPU unstable. I know your case because I also this issues in 2017 Build but if you use VNC to remote the desktop or laptop. It can remote but you cannot browse the internet. After that, You will discover that is a DNS issues from the DD-WRT. AC(S)V2 means slow.
The wifi signal also cause by CPU High Temperature.
If you test, you will find changing Clone WAN MAC from MAC Address Clone, we must change vendor Mac Address. If not, the ISP will not provide a new Dynamic IP Address or no update.
The other issues are that DDNS Issues (http://192.168.1.1/DDNS.asp)does not work every reboot.
The reboot router button and schedule router processes are a little different. It is different with other type of routers. The reboot router button does not work the apply setting when you update some configurations. Schedule reboot will work since 2017.
We need to cut off the power and restart the router. After that it will work.
ttowling wrote:
M wrote:
Dear All
I am a dd-wrt user.
I think my message may make your inconvenience.
I recommend all of us (including me) report the operation of our routers.
If we report the dd-wrt build (Normal Operation or Abnormal Status)
Please also highlight the warning message from System Logs. The situations may make Programmer debug easily for the next build.
I recommend you downgrade the build to 2016 or 2017 version
ttowling wrote:
M wrote:
Dear All
I am a dd-wrt user.
I think my message may make your inconvenience.
I recommend all of us (including me) report the operation of our routers.
If we report the dd-wrt build (Normal Operation or Abnormal Status)
Please also highlight the warning message from System Logs. The situations may make Programmer debug easily for the next build.