I just loaded your new 21395 k26 build on all my routers that had the old 22200 build.
But I wonder why you didn't base your updated build on your latest k26 build (22200)? There were a couple of builds between the two too if I remember correctly.
Are we missing something in the new 21395 build that we had in the old 22200 build?
Stability is the main thing tho, my routers with the old 22200 build were rock stable with literally no downtime.
I was curious about this as well, as most people seem to be running his 22200, at least for the e3000 crowd (unless they are on a 3.x load). _________________ Linksys E3000 v1 - r27506, K3.x
I just loaded your new 21395 k26 build on all my routers that had the old 22200 build.
But I wonder why you didn't base your updated build on your latest k26 build (22200)? There were a couple of builds between the two too if I remember correctly.
Are we missing something in the new 21395 build that we had in the old 22200 build?
Stability is the main thing tho, my routers with the old 22200 build were rock stable with literally no downtime.
They only contained minor fixes, e.g. one release had some proftpd update, the other a samba fix.
If you notice something and know it has been fixed in trunk, I can backport some more little fixes. I have another VM , but don't know what release it is as I named it trunk, but it is dated to around the same time we were at ~22000 _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
I just loaded your new 21395 k26 build on all my routers that had the old 22200 build.
But I wonder why you didn't base your updated build on your latest k26 build (22200)? There were a couple of builds between the two too if I remember correctly.
Are we missing something in the new 21395 build that we had in the old 22200 build?
Stability is the main thing tho, my routers with the old 22200 build were rock stable with literally no downtime.
They only contained minor fixes, e.g. one release had some proftpd update, the other a samba fix.
If you notice something and know it has been fixed in trunk, I can backport some more little fixes. I have another VM , but don't know what release it is as I named it trunk, but it is dated to around the same time we were at ~22000
Thanks again. Do you remember what the Samba fix were? I'm using samba extensively from most of my routers as I have a setup where they login to a NAS and executes several scripts.
Everything seems to work just as well with the new build but I'm still curious what was the Samba fix.
I don't went anything to break on what I consider to be one of the best dd-wrt builds ever!
I just loaded your new 21395 k26 build on all my routers that had the old 22200 build.
But I wonder why you didn't base your updated build on your latest k26 build (22200)? There were a couple of builds between the two too if I remember correctly.
Are we missing something in the new 21395 build that we had in the old 22200 build?
Stability is the main thing tho, my routers with the old 22200 build were rock stable with literally no downtime.
They only contained minor fixes, e.g. one release had some proftpd update, the other a samba fix.
If you notice something and know it has been fixed in trunk, I can backport some more little fixes. I have another VM , but don't know what release it is as I named it trunk, but it is dated to around the same time we were at ~22000
Thanks again. Do you remember what the Samba fix were? I'm using samba extensively from most of my routers as I have a setup where they login to a NAS and executes several scripts.
Everything seems to work just as well with the new build but I'm still curious what was the Samba fix.
I don't went anything to break on what I consider to be one of the best dd-wrt builds ever!
It was a problem with the user/share setup.
Between 21395 and 22200 there were not a whole lot of commits for any broadcom units and a lot of the fixes enhancements in later revisions for K26 units came from my fixes, which are already in these builds. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
OK checked all my backups and found a 22000 release.
That is good news. Although your recent build seems to work fine I feel better if it would be based on something that has been proven rock stable for a year
Thank you Kong! Yes, if you could do a build off of 22000, I've also been running that on a wrt610nv2 without any issues and it would be great to stick with it.
I was able to pull an OpenVPN binary from an older build I had lying around that was compiled with OpenSSL 0.9.81 just as a stop-gap, but it was causing 100% CPU spike when OpenVPN was configured in TCP mode (which some of my clients need). So I'm thankful you were able to release a patched build so I can get them set back up.
22000+ would be fine, but it had a bug that it could not mount hard disk partitions, due to a wrong version of diskinfo. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
kong
I have a request, trying my luck because this is probably a hard one: USB did not work on the Asus RT-N66U with those older k26 builds. Would you by any chance be able to fix that in your refreshed build?
That should be fixed in k3 builds, are you able to backport the fix?
That would be perfect, I really would like to run Optware on a coupe of Asus RT-N66U routers. I believe those are currently the fastest routers that will run the k26 builds, but unfortunately USB is broken on those routers.
Okay, so analyzing the remote access to my https gui on my WNDR4000 running VPN KongMod 22200, it shows that it's immune to Heartbleed.
Since this build is susceptible to Heartbleed, I assumed access to my https gui would be subject as well. However, it appears not... at lease according to COMODO