Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Thu Jun 16, 2011 21:12 Post subject: Recommended Build - Suggest Change
I am suggesting that the recommended build of 14929 be changed to BS 15962 dated 12/24/10.
I have been running this build on all my equipment (excluding my main router / gateway) since posted with no issues.
It was running on my gateway with no issues but that is the device I upgrade all the time with the new builds. Currently it is running 16994.
15962 is running on two e3000's, two e2000's, one wrt54gs v5 and one gs v7, and one GL all in service.
When I send routers home after repair, they leave with 15962. I get nothing but positive feedback in regards to the operation of the router that went home. _________________ [Moderator Deleted]
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Thu Jun 16, 2011 21:59 Post subject: Re: Recommended Build - Suggest Change
barryware wrote:
I am suggesting that the recommended build of 14929 be changed to BS 15962 dated 12/24/10.
I have been running this build on all my equipment (excluding my main router / gateway) since posted with no issues.
It was running on my gateway with no issues but that is the device I upgrade all the time with the new builds. Currently it is running 16994.
15962 is running on two e3000's, two e2000's, one wrt54gs v5 and one gs v7, and one GL all in service.
When I send routers home after repair, they leave with 15962. I get nothing but positive feedback in regards to the operation of the router that went home.
I concur...I'll update it. The 15692 is one of my fall backs also.
If anyone has any negative comments...I'll take that into consideration as well. I'll wait to update the links until 06/17/11.
redhawk _________________ The only stupid question....is the unasked one.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Thu Jun 16, 2011 23:08 Post subject:
I run VINT on only one router (I have others...but why bother...they are sooooo outdated) The current recommended 15230 can stay. There are almost no advantages of any changes in VINT since then. This stuff is soooo old the dev's are not concentrating on making it better for the old dinosaur routers.
Unless someone can give me a good reason to update past the current VINT recommended 15230 build...it will stay.
redhawk _________________ The only stupid question....is the unasked one.
Hmm, I don't know about this. The build thread looks pretty good but there wasn't much feedback for it and several bugs were introduced in the 15000's. Some that come to mind:
1) NAT Loopback breakage - A well known "feature" which is ridiculous but has workarounds. Recommending an affected build will add many more complaints and waste lots of time for everyone. This is a small evil that I don't mind in a recommend build.
2) PPPoE/VLAN fixes+breakage - 15508 was a good step in fixing the VLAN GUI for k2.6 builds but it also broke PPPoE (no VLAN changes required to trigger bug) until Eko's recent fixes. Some hardware also had problems with VLAN changes reverting on boot. Should a build that breaks PPPoE for k2.6 builds really be recommended, I think absolutely not.
3) VPN GUI changes - Sash made a ton of changes to the VPN GUI's starting in mid 15000's and I'm not sure how well it was in 15962. There wasn't any feedback about it in the build thread.
Because of the PPPoE breakage I would only consider recommending 15962 for k2.4. For k2.6 I think we should either recommend a very recent build (16900+) or wait for them to be tested longer. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Fri Jun 17, 2011 11:57 Post subject:
Point taken phuzi0n....maybe we should wait for a more stable current build before updating the recommended. list. Something after 17081...that's when the Repeater mode issues were fixed too. (broken starting in the 16500's)
redhawk _________________ The only stupid question....is the unasked one.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Fri Jun 17, 2011 13:07 Post subject:
for a non dd-wrt ho, figuring out what to flash is confusing enough without having one build for k24, another for k26.
that said, screw it.. leave it alone.
afaik, everything phuz pointed out is still broke and was broke in the recommended build.
Maybe I have the build date wrong but the new loopback "feature" has been in place for quite a while and discussion is that it will not be fixed by the devs.
vlans.... well you decide.
pppoe... I had no problems with pppoe with 15962 std_usb_nas on my RT. (currently not running the rt though). I would have remembered as that is my wan connection type if I had problems.
I don't care one way or the other.. It was just a suggestion to change / update the recommended build. _________________ [Moderator Deleted]
Last edited by barryware on Fri Jun 17, 2011 15:07; edited 1 time in total
What DD-WRT needs is "channels" -- not speaking of wireless channels, but development channels. Stable, dev. Then this discussion would be moot. When the "recommended" build is almost a year old, I think this is more than a wish-list item.
afaik, everything phuz pointed out is still broke and was broke in the recommended build.
Only the VLAN GUI was broken in 14929 but it was only a minor point. AFAIK only NAT loopback is currently broken; PPPoE, VLAN GUI, and VPN GUI should be okay currently. There might be a problem with PPPoE VLAN tagging for some VDSL ISP's but the one user I helped with this problem was able to workaround it with the VLAN GUI, it's a bit early to tell how much of a problem it is.
barryware wrote:
Maybe I have the build date wrong but the new loopback "feature" has been in place for quite a while and discussion is that it will not be fixed by the devs.
vlans.... well you decide.
pppoe... I had no problems with pppoe with 15962 std_usb_nas on my RT. (currently not running the rt though). I would have remembered as that is my wan connection type if I had problems.
The problem with VLAN's reverting is only a minor point. The GUI was non-functional before, it became semi-functional after 15508, and afaik the problems have been worked out after ~16900.
It may have been hardware specific, but it certainly affected my wrt320n and wrt300n v1.1 (running k2.6 at the time). I don't use PPPoE for my WAN type normally but after many people reported problems I tried changing my WAN type to PPPoE on them and they immediately locked up. This PPPoE problem is partly responsible for spurring this focused test which didn't get much feedback, I expected more cooperation from Guru's:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=137040 _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
