Joined: 10 Nov 2018 Posts: 350 Location: South Carolina
Posted: Thu Jul 18, 2019 15:10 Post subject:
Ah-Pin-Kor wrote:
The wrt3200acm and wrt32x are not affected by the partition 2 smaller size problem as they have double the flash size of the wrt1x00 series (256MB vs 128MB).
40352 size for wrt1x00 is the same as the last few builds so no change on the partition 2 problem.
40167 - ok - 37.63MB 39456768
40189 - not ok - 37.88MB 39718912
40260 - not ok - 39718912
40276 - not ok - 39718912
40352 - not ok - 39718912
Ah-Pin-Kor,
In your opinion would you call r40167 a clean and stable version for the 1900?
The wrt3200acm and wrt32x are not affected by the partition 2 smaller size problem as they have double the flash size of the wrt1x00 series (256MB vs 128MB).
40352 size for wrt1x00 is the same as the last few builds so no change on the partition 2 problem.
40167 - ok - 37.63MB 39456768
40189 - not ok - 37.88MB 39718912
40260 - not ok - 39718912
40276 - not ok - 39718912
40352 - not ok - 39718912
Ah-Pin-Kor,
In your opinion would you call r40167 a clean and stable version for the 1900?
I personally didn't try it but read about webui problems in it's build thread. My "ok" status in the table above refers to not having the partition 2 flash problem and not a functional status of the build itself. _________________
Netgear R7800 kongpro 19.07 20190919 || Netgear R7000 36070M kongac (Client Bridge=5GHz, AP=2.4GHz with bridged VAP)
Linksys WRT32X davidc502 OpenWrt || Linksys WRT1200ACv1 Gargoyle 1.11.x
Linksys WRT1900ACSv2 dd-wrt 39956
In my opinion r40167 should be avoided as was already stated on the thread...
I accidently loaded r40167 on my 1900acsv2...It loaded fine on patition2 and then I flashed it to partition1 thinking it would be OK...WRONG! What I got was a gui interface that you could no longer input anything into it...I tried doing the power toggle 3 times to get back to partition2 (tried that about 20 times or more)...Could not get back and since I don't enable SSH/telnet the thing was essentially bricked even though it was still working...But hey it gave me a chance to do the usb to ttl recovery which I had never done before...Found out my cheap prologic clone cable was $hit and ordered a adafruit cable and that worked and I flashed it back to stock and then back to dd...
Like is labeled on the thread I would avoid r40167. _________________ WRT1900ACSv2
Yeah...I had r40009 installed and working for 3 weeks while I was away on my motorcycle trip...Worked without issue for the 3 weeks I was gone...
I'm currently on r40134 which has been working great for me with my VPN and NAS/Media server USB attached drive...
It will be interesting what BS does (if anything) regarding this size dilemma for the 2nd partition on most of the WRT routers (excluding 3200 and 32x).
If the problem remains I will sit on DD-WRT for a good long while then jump ship to Open-WRT but I'd rather stay in the DD camp.
scar1943 wrote:
DaveI wrote:
Like is labeled on the thread I would avoid r40167.
So it sounds like r40134 or r40009 were the last "good" flash's, since NAS quit working on r40048 and r40065.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Thu Jul 18, 2019 22:50 Post subject:
scar1943 wrote:
DaveI wrote:
Like is labeled on the thread I would avoid r40167.
So it sounds like r40134 or r40009 were the last "good" flash's, since NAS quit working on r40048 and r40065.
Totally agree with this procedure. The only thing I can add is make sure that any of later bulky builds are installed on partition 1. Any attempt to put them on partition 2 as would be the case going from Stock to DD-WRT for the first time.
I don't even check which partition is active, just go ahead and issue the command "ubootenv set boot_part 2" before doing the update on my 1200 or 1900's. Doing so has allowed seemless updates recently and the only ason I am running r40009 is GUI loss problem on the most recent builds. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Like is labeled on the thread I would avoid r40167.
So it sounds like r40134 or r40009 were the last "good" flash's, since NAS quit working on r40048 and r40065.
I tried running r40134 but the web GUI came up very slow and I finally kept losing the ability to access the router at all without a reboot. I went back to r40009 and the interface loads instantly and so far no issues. I'll stick to that build.
r40134 has been working fine for me (so far) on my WRT1900acsv2 but as we know everyone's different setup can affect things as well...I'm going to leave it run for several days without rebooting to see if there's a problem with the GUI...So far I haven't had any problem with it for my config. _________________ WRT1900ACSv2
r40134 has been working fine for me (so far) on my WRT1900acsv2 but as we know everyone's different setup can affect things as well...I'm going to leave it run for several days without rebooting to see if there's a problem with the GUI...So far I haven't had any problem with it for my config.
I'd be interested in what you see. I have the 1900acs v1. I'm running a VPN client using policy based routing and putting my roku tv behind it.
I turn the vpn on and off as needed and that's when I noticed the r40134 build wasn't responding. My whole network was still up and could access the internet but I couldn't access the router's gui from multiple devices. I could access it via putty though which made me think it was a gui problem.
I tried clearing nvram but it did the same thing. Returning to r40009 seems to have fixed it.
I have a VPN and I turn it on and off as well sometimes for streaming (As I have marginal bandwidth
12 down/3 up). I haven't had any problems turning mine on and off but I don't use PBR...Mine is a version 2 so maybe there's a difference with that as well version 1 and version 2...I'll post results of no reboot after several days (If I can resist trying any new versions that BS may release in the interim).
ellick wrote:
I'd be interested in what you see. I have the 1900acs v1. I'm running a VPN client using policy based routing and putting my roku tv behind it.
I turn the vpn on and off as needed and that's when I noticed the r40134 build wasn't responding. My whole network was still up and could access the internet but I couldn't access the router's gui from multiple devices. I could access it via putty though which made me think it was a gui problem.
I tried clearing nvram but it did the same thing. Returning to r40009 seems to have fixed it.
Joined: 04 Aug 2012 Posts: 612 Location: behind the screen
Posted: Fri Jul 19, 2019 19:37 Post subject:
ellick wrote:
DaveI wrote:
r40134 has been working fine for me (so far) on my WRT1900acsv2 but as we know everyone's different setup can affect things as well...I'm going to leave it run for several days without rebooting to see if there's a problem with the GUI...So far I haven't had any problem with it for my config.
I'd be interested in what you see. I have the 1900acs v1. I'm running a VPN client using policy based routing and putting my roku tv behind it.
I turn the vpn on and off as needed and that's when I noticed the r40134 build wasn't responding. My whole network was still up and could access the internet but I couldn't access the router's gui from multiple devices. I could access it via putty though which made me think it was a gui problem.
I tried clearing nvram but it did the same thing. Returning to r40009 seems to have fixed it.
Same problem here, after awhile no access to the GUI
r40009 does NOT have that problem _________________ WRT3200ACM openwrt 18.06.5
WRT3200ACM dd-wrt r41791
WRT54GL dd-wrt r21676