Posted: Mon Feb 04, 2019 8:34 Post subject: Help with WRT32X
Hi guys,
I've installed DD-WRT about 4 months ago on my WRT32X and i think it was on the main partition.
It was a terrible experience the WIFI was completely unstable, some devices coudln't connect at all (iPhone, Airport Express) some were roaming constantly between 2.4GHZ and 5GHZ.
I reverted to stock by booting the other partition and now i have 2 partition : 1 with original VENOM and one with DD-WRT.
My question is : is there a stable fixed build of DD-WRT, if not - is it risky to stay like this ? can i restore to default VENOM fw on both partitions like when the device was new ?
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Mon Feb 04, 2019 12:02 Post subject: Re: Help with WRT32X
bruce_wein wrote:
Hi guys,
I've installed DD-WRT about 4 months ago on my WRT32X and i think it was on the main partition.
It was a terrible experience the WIFI was completely unstable, some devices coudln't connect at all (iPhone, Airport Express) some were roaming constantly between 2.4GHZ and 5GHZ.
I reverted to stock by booting the other partition and now i have 2 partition : 1 with original VENOM and one with DD-WRT.
My question is : is there a stable fixed build of DD-WRT, if not - is it risky to stay like this ? can i restore to default VENOM fw on both partitions like when the device was new ?
Thanks !
Any of the 2019 builds work perfectly on the WRT32X _________________ Linksys WRT32X v1 - r45677
Linksys WRT1900AC v1 - r45677
TP-Link Archer C9 v1 - r45677
Firmware: ftp://ftp.dd-wrt.com/betas/2021/
Posted: Tue Feb 05, 2019 9:43 Post subject: Re: Help with WRT32X
Yemble wrote:
bruce_wein wrote:
Hi guys,
I've installed DD-WRT about 4 months ago on my WRT32X and i think it was on the main partition.
It was a terrible experience the WIFI was completely unstable, some devices coudln't connect at all (iPhone, Airport Express) some were roaming constantly between 2.4GHZ and 5GHZ.
I reverted to stock by booting the other partition and now i have 2 partition : 1 with original VENOM and one with DD-WRT.
My question is : is there a stable fixed build of DD-WRT, if not - is it risky to stay like this ? can i restore to default VENOM fw on both partitions like when the device was new ?
Thanks !
Any of the 2019 builds work perfectly on the WRT32X
The WIFI issues for apple devices have been finally fixed ?
I'll definitely try the new build !
How do I switch to the other partition with initial DD-WRT installation now ?
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Tue Feb 05, 2019 12:20 Post subject: Re: Help with WRT32X
bruce_wein wrote:
Yemble wrote:
bruce_wein wrote:
Hi guys,
I've installed DD-WRT about 4 months ago on my WRT32X and i think it was on the main partition.
It was a terrible experience the WIFI was completely unstable, some devices coudln't connect at all (iPhone, Airport Express) some were roaming constantly between 2.4GHZ and 5GHZ.
I reverted to stock by booting the other partition and now i have 2 partition : 1 with original VENOM and one with DD-WRT.
My question is : is there a stable fixed build of DD-WRT, if not - is it risky to stay like this ? can i restore to default VENOM fw on both partitions like when the device was new ?
Thanks !
Any of the 2019 builds work perfectly on the WRT32X
The WIFI issues for apple devices have been finally fixed ?
I'll definitely try the new build !
How do I switch to the other partition with initial DD-WRT installation now ?
I don't have ANY Apple devices!
I always use Webflash from the DD-WRT GUI, which flashes to the "other" partition. If you want to mess about switching partitions manually, then you are on your own! _________________ Linksys WRT32X v1 - r45677
Linksys WRT1900AC v1 - r45677
TP-Link Archer C9 v1 - r45677
Firmware: ftp://ftp.dd-wrt.com/betas/2021/
Posted: Tue Feb 05, 2019 12:45 Post subject: Re: Help with WRT32X
Yemble wrote:
bruce_wein wrote:
Yemble wrote:
bruce_wein wrote:
Hi guys,
I've installed DD-WRT about 4 months ago on my WRT32X and i think it was on the main partition.
It was a terrible experience the WIFI was completely unstable, some devices coudln't connect at all (iPhone, Airport Express) some were roaming constantly between 2.4GHZ and 5GHZ.
I reverted to stock by booting the other partition and now i have 2 partition : 1 with original VENOM and one with DD-WRT.
My question is : is there a stable fixed build of DD-WRT, if not - is it risky to stay like this ? can i restore to default VENOM fw on both partitions like when the device was new ?
Thanks !
Any of the 2019 builds work perfectly on the WRT32X
The WIFI issues for apple devices have been finally fixed ?
I'll definitely try the new build !
How do I switch to the other partition with initial DD-WRT installation now ?
I don't have ANY Apple devices!
I always use Webflash from the DD-WRT GUI, which flashes to the "other" partition. If you want to mess about switching partitions manually, then you are on your own!
Is there a way to revert to stock VENOM fw through DD-WRT web gui ? I only did this to be able to get back to stock if there is something wrong ... If this issue was already resolved i would be more then happy
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Tue Feb 05, 2019 13:21 Post subject: Re: Help with WRT32X
bruce_wein wrote:
Is there a way to revert to stock VENOM fw through DD-WRT web gui ? I only did this to be able to get back to stock if there is something wrong ... If this issue was already resolved i would be more then happy
But why would you want to revert to Venom? As long as you have one stable DD-WRT image installed, you can use the other partition to experiment with the "next" DD-WRT image. If you don't like it you can just boot to the previous image via the triple power toggle method.
You only need one working partition!
The only credible exception to this, is if you plan to install some other firmware, such as LEDE, but if that is the case, you should have really have bought a WRT3200ACM rather than a WRT32X, since the ACM has a one-step DD-WRT installation process from stock, rather than two-step. _________________ Linksys WRT32X v1 - r45677
Linksys WRT1900AC v1 - r45677
TP-Link Archer C9 v1 - r45677
Firmware: ftp://ftp.dd-wrt.com/betas/2021/
Posted: Tue Feb 05, 2019 16:21 Post subject: Re: Help with WRT32X
Yemble wrote:
bruce_wein wrote:
Is there a way to revert to stock VENOM fw through DD-WRT web gui ? I only did this to be able to get back to stock if there is something wrong ... If this issue was already resolved i would be more then happy
But why would you want to revert to Venom? As long as you have one stable DD-WRT image installed, you can use the other partition to experiment with the "next" DD-WRT image. If you don't like it you can just boot to the previous image via the triple power toggle method.
You only need one working partition!
The only credible exception to this, is if you plan to install some other firmware, such as LEDE, but if that is the case, you should have really have bought a WRT3200ACM rather than a WRT32X, since the ACM has a one-step DD-WRT installation process from stock, rather than two-step.
The only reason I want the ability to come back to VENOM is if the Apple wifi issue still happens after the upgrade, that's all. Otherwise DD-WRT is pure gold.
If anyone could confirm that apple wifi issues are gone on the new fw - that would be awesome !
I don't own any Apple devices (Other than old Ipods)...
But here's some recent entries in the bug tracker regarding Apple products support...See Kong's response from 10 days ago...
I don't own any Apple devices (Other than old Ipods)...
But here's some recent entries in the bug tracker regarding Apple products support...See Kong's response from 10 days ago...
Too bad Kong let's his disliking of Apple in general cloud his judgement in regards fixing this marvelous FW for the greater good.
I thought this Apple VS Android horseshit is long gone.
I was wrong.
Pity ...
Apple make the best phones, the best tablets, the best TV streamers and probably the best laptops.
They are pricey, but so is driving a Mercedes and people still do it.
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Tue Feb 12, 2019 12:10 Post subject:
bruce_wein wrote:
Yemble wrote:
bruce_wein wrote:
Apple make the best phones, the best tablets, the best TV streamers and probably the best laptops.
ROFL... well that's your "unbiased" opinion
Why didn't you buy an AirPort?
Price, lack of features like in DD-WRT
I did not say they make best routers ...
Priceless
Anyway, back to your original question...
Why not boot back to the Linksys partition via the treble power toggle method and then re-install the latest DD-WRT image in exactly the same way that you installed it four months ago (you obviously found a working method). Then you can try out your Apple devices for yourself.
What have you got to lose, as the treble power toggle can always be used to boot the alternative partition? _________________ Linksys WRT32X v1 - r45677
Linksys WRT1900AC v1 - r45677
TP-Link Archer C9 v1 - r45677
Firmware: ftp://ftp.dd-wrt.com/betas/2021/
How did you retain the original/stock firmware on the opposite/alternate partition? From my point of view there are two possibilities for your situation.
You flashed the small image from the Linksys web interface ( FW_WRT32X_1.0.666_DDWRT.img ) and did not continue to upgrade to the full size image from the DD-WRT web interface with ddwrt-linksys-wrt32x-webflash.bin (as this would have overwritten the remaining stock firmware on the opposite partition).
Or
You continued and have upgraded to the full size image from the DD-WRT web interface -after- going through command line via Telnet/SSH to identify the current partition in use and then switching to the alternate -without rebooting- (2 simple commands, then web flash). This would have overwritten/upgraded the existing DD-WRT partition and kept your opposite partition intact. You can use this procedure again to upgrade to the current build for testing.
Here is the Telnet/SSH instructions quoted from the two main stickies linked below.
"
1. Use the ubootenv get boot_part command to learn the current Partition in use.
2. Use the ubootenv set boot_part (1 or 2 – the opposite number returned in Step 1) command.
3. DO NOT REBOOT
4. In DD-WRT GUI – Administration Tab – Firmware Upgrade Sub Tab: Upload the new ’dd-wrt webflash.bin’ file for your Router & Hardware Version. MAKE SURE THAT NO RESET IS SELECTED.
5. After Firmware Upgrade is finished the Router will automatically reboot.
*You should now have the new DD-WRT upgrade on the current Partition and OEM Firmware will still be intact on opposite partition.
"
There are reasons to have stock firmware available.
1.) You are running into any sort of problem that isn't solved by a reset, reconfiguration, upgrading or downgrading DD-WRT. For example there are longstanding mwlwifi driver issues with some Apple products, some Intel Wi-Fi adapter chipsets and Internet of Things or anything with ESP8266.
2.) You want to avoid Telnet/SSH use as much as possible with the ability to easily try other firmware(s) such as stock Linksys or OpenWRT (Davidc502 LEDE Snapshots for example).
As for the Apple situation with Kong, not sure what's going on there. The best solution is to get involved and provide as much information as possible so the problem can be identified and solved. A good example of this is what is currently happening in the ESP8266 issue thread for the mwlwifi driver.
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Tue Feb 12, 2019 13:05 Post subject:
blkt wrote:
1.) You are running into any sort of problem that isn't solved by a reset, reconfiguration, upgrading or downgrading DD-WRT. For example there are longstanding mwlwifi driver issues with some Apple products, some Intel Wi-Fi adapter chipsets and Internet of Things or anything with ESP8266.
The issues with IoT/ESP devices can, potentially, be resolved by making use of the third radio (ath2). It comes with a number of caveats and will rob you of the 2.4GHz radio on ath1... but it is possible!
Unfortunately that solution is not practical to most because of the limited range that third radio has. Enabling Radio2/ath2 has side effects (one of which you mentioned).
It's a different chip (88W8887) outside of the main chipset (2x 88W8964) and it doesn't use the mwlwifi driver as an access point. It is meant for DFS Radar Detection (Dynamic Frequency Selection) and receive only in conjunction with Radio0/ath0 (5Ghz, 802.11a/n/ac). Radio1/ath1 is 2.4Ghz, 802.11b/g/n.
I don't want to get off topic here, just providing reasons to have a stock firmware available as an easy fallback and pointing out the need for real data and feedback.
Last edited by blkt on Tue Feb 12, 2019 14:24; edited 1 time in total
