raynjamin wrote:Hey everyone,
Super happy with my WRT32X while it works, super sad when I have to restart it several times throughout the day. The beta firmware in question is applicable for botht he WRT3200ACM and the WRT32X, right? And, am I right in saying the only way to get access to it is to pm Lucas from the Linksys team?
Thanks!
Hi Ray,
You are correct. We actually have 2 different releases that we are testing right now.
Benjay wrote:Hey everyone !
I'm having big troubles with my WRT-3200ACM EU version.
My router is rebooting often and the power LED is very low and completely went of after some time. Now its back again but very low compared to the other LEDs.
This happens since a few days...
Also my wifi seems to be very very weak, specialy at the 2.4ghz band. I cant even connect in a room were my old router was able to establish a decent connection with 3 bars and a lot of the times i'm loosing wifi completly. I've tried diffrent settings and channels but it doesn't help at all.
I'm with Firmware Version 1.0.6.181063 but i have also tried other version including factory reset.
This is driving me crazy and i got in serious trouble with my family because it's just no possible to use the internet in a regular base
Do i have a defective unit ? What should i do ?
Hi Ben,
yes yours does sound like a defective unit. If you have poor signal output and dim lights it could either be a bad unit or potentially power supply that is not properly functioning and underpowering your unit. I would contact support to get that one replaced for a new WRT.
Backup your config and do a clear settings reset. Once logged in try adding the site again. If the add key still doesn't work, you can check for a new firmware and apply or revert back to an older version withing the diagnostic page.
Once you are done testing, you can apply your saved config.
All the smart features have disappeared. My home network and internet connectivity is OK but I can't talk to the modem via IP 192.168.1.1 (I have checked that this is actual actual IP address) and can't access the drive connected to the router's USB port.
Can anyone suggest a fix? Of course, without access via 192.168.1.1, I can't check the firmware release or reload/update firmware.
Windows 10
Intel i7
Thanks in advance.
The Modem is provided by the ISP and the EA6300 is your router.
Did you recently have the modem changed?
UPDATE:
I have just checked into the modem via http://192.168.1.1:9999/TMSDeviceDescription.xml which worked. I am currently on V 1.0 firmwar, so I guess I need to load Ver. 1.1.40 (build 176337) first. This however not much help as I still don't know how to load this firmware.
But having got in once by this route, it's not letting me in again.
Thanks for the quick response.
No, The current cable modem (cogeco.ca) has been in place for several years and I have not seen any problems with it - cable, internet or phone.
Disconnect the EA6300's WAN\Internet port from the modem, reboot and then try access it's WebUI.
Thanx Pamela..will play around with settings abit....like I said ..should be able to unplug my ea 6500 and plug this one in and it should work....settings are the same as ea6500.....the ea6500 works great with 7 to eight devices online...not all at the same time mind you but it works good enough....do you have any recommended settings for this router...just wondering....Thanx
P.M sent
Have any of the beta testers noticed if the beta resolves the 5Ghz getting stuck on "Obtaining IP Address" issue?
chadster766 wrote:Have any of the beta testers noticed if the beta resolves the 5Ghz getting stuck on "Obtaining IP Address" issue?
I've been running the newest beta (released on the 9th) since yesterday afternoon. I set DHCP expiry to 30 minutes just in case that was somehow related (seemed many people started seeing issues at 24 hours which is the default), and I've not seen issues yet.
I have a few Windows 10 laptops, on both 2.4 and 5ghz bands, a Chrome cast on 2.4ghz (which is Google's recommendation for it), and a number of iphone/android phone and tablet devices on the 5ghz band. Not at 24 hours yet but this morning my phone at least was working fine, same with my laptop. It actually ran all night without losing the lease on the IP at all.
I'll run some harder tests after work and maybe force a bunch of devices over to 5ghz just for kicks.
Many thanks. That worked and all is working well again.
chadster766 wrote: Have any of the beta testers noticed if the beta resolves the 5Ghz getting stuck on "Obtaining IP Address" issue?
I haven't experienced that issuse since upgrading to beta 1.0.6.186143 
I was doing some reading about updating the standard host file and found a list of 65,000 entries reported as adware, malware, tracking or malicious. So, how do I add this file to my E2500 Router to protect my whole Home Network?
Markd1958 wrote:chadster766 wrote: Have any of the beta testers noticed if the beta resolves the 5Ghz getting stuck on "Obtaining IP Address" issue?I haven't experienced that issuse since upgrading to beta 1.0.6.186143
Could you go to a location where the 5Ghz signal is between -67 to -70 dbm (one bar down from full signal) and switch a few times from the 2.4Ghz to the 5Ghz to see if the "Obtaining IP Address" issue takes place?
Sphexi wrote:
chadster766 wrote:Have any of the beta testers noticed if the beta resolves the 5Ghz getting stuck on "Obtaining IP Address" issue?
I've been running the newest beta (released on the 9th) since yesterday afternoon. I set DHCP expiry to 30 minutes just in case that was somehow related (seemed many people started seeing issues at 24 hours which is the default), and I've not seen issues yet.
I have a few Windows 10 laptops, on both 2.4 and 5ghz bands, a Chrome cast on 2.4ghz (which is Google's recommendation for it), and a number of iphone/android phone and tablet devices on the 5ghz band. Not at 24 hours yet but this morning my phone at least was working fine, same with my laptop. It actually ran all night without losing the lease on the IP at all.
I'll run some harder tests after work and maybe force a bunch of devices over to 5ghz just for kicks.
Could you go to a location where the 5Ghz signal is between -67 to -70 dbm (one bar down from full signal) and switch a few times from the 2.4Ghz to the 5Ghz to see if the "Obtaining IP Address" issue takes place?
Dear Lucas,
Let me check if I understand correct:
1. Tomorrow you will publish a temporary (test) solution or a final stable one?
2. If it's a final stable solution, why a limited public rollout tomorrow and why does it take untill NEXT WEEK OR SO for the update server to push them out?!
Really confusing... Can you please clarify us?!
Are we talking about a stable solution or not?
