bobbyda wrote: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?
Hi Bobby,
Tomorrow we are hoping for a final build. A normal rollout with automatic updates takes 3-4 days as we open the posting up to about 20-25% of the population per day until we reach full deployment.
At the same time though for people that want it right away we will take the approach of also posting it here on the forums so people can ask questions and share their feedback. Hope this helps.
Best Regards,
Lucas
01-11-201811:36 AM - edited
Hi All,
Update for the day. The product swap program is being halted. The only option available at the moment will be a BETA for both the 32x and ACM.
As of now our plan is to do a limited public rollout of the Final firmware tomorrow. I will be creating a new thread with those details so we can put this one to rest hopefully at 110 pages or so. When that one goes live you will have the option to manually go ahead and download the new firmware, or wait for the update server to push them out over hte course of the next week or so.
Lucas
Can you please make sure you post the link to the new thread in this one so we make sure we can find it? I want to make sure I get the new beta firmware. Thanks.
Steve
Is anything being done on this? I've only owned Linksys routers and consider myself a fan. Thought i'd support them in diving into the gaming world by buying one... Part of me wanted a TPlink ac5400 but got this instead.... You would think linksys would be getting on this or posting in this forum to let us know they are actually caring about their customers...... Am I going to have to take this back?
HOW does this even happen to a big company like linksys, HOW does this kind of bug slip through the cracks BEFORE being released to the public????
PLEASE fix this or at least update us on the issue before I return this.
What other routers have prioritization and similar speed?
chadster766 wrote:
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?
I tried what you asked with my tablet, phones, Macbook, and Ipads and had no issue, they all connected fine going form 2.4 to 5g on my wireless.
Hope this helps!
Currently Linksys EA6500 V2 isn't even listed under "KRACK Advisory - Date: 1/8/18" (NO ETA).
It's totally unacceptable! #FAIL
Please Linksys (Belkin) support your costumers with a proper Firmware to mitigate KRACK WP2 ASAP.
Regards,
Markd1958 wrote:chadster766 wrote:
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?
I tried what you asked with my tablet, phones, Macbook, and Ipads and had no issue, they all connected fine going form 2.4 to 5g on my wireless.
Hope this helps!
That is good news!
Are any devices you tested Android?
aprilthemoo wrote:
I have no idea why they are being so cagey about rolling out this firmware considering the current ones are broken. It makes no sense whatsoever. I'd see the point if the current firmware actually worked...
Truly bizarre.
As a software developer, I think I can give you some level of insight. Consider this. They can do lab testing all day without knowing what these devices are going through in the field. Who knows if there's some bug in the new version that bricks 50% of the devices due to an unforseen circumstance. Maybe it accidentally wipes the flash memory. Maybe the Marvell firmware causes some hardware loop to burn the wifi chip. Who knows? Which would you rather do. Risk having to replace half of your customer bases devcies (granted they have done this for a few of us,) or replace half of a group of 20 testers devices, who volunteered knowing full well the software was untested?
chadster766 wrote:
Are any devices you tested Android?
One was a Samsung Tab A, the rest were apple and HP.
Hope this helps, Mark
Markd1958 wrote:chadster766 wrote:
Are any devices you tested Android?
One was a Samsung Tab A, the rest were apple and HP.
Hope this helps, Mark
Thanks I hope more confirmations come in like yours 
I as well
chadster766
I sent you a PM
Thats correct. I've tried different configurations of the antenna's, I.E - all 3 pointed straight upwards, all 3 pointed at 90 degrees down the hall, left antenna slightly left, right antenna slight right, middle up/down, etc....
I still seem to have speed issues.
Now I do have some understanding of WiFi, and do realize that being beside glass isn't optimal, but I've also have a table directly below the window, and have placed the router on the table also - same results.
Birraque wrote:Currently Linksys EA6500 V2 isn't even listed under "KRACK Advisory - Date: 1/8/18" (NO ETA).
It's totally unacceptable! #FAIL
Please Linksys (Belkin) support your costumers with a proper Firmware to mitigate KRACK WP2 ASAP.
Regards,
Birraque if it is not in the list the unit is either not impacted or has reached EOS (End of Support).
Regards,
Lucas
tldr; port forwarding 3389 on EA9500 - still can't establish Remote Desktop Connection through router
Hi All,
My WRT160 got old and started needing reset once a day, so I went out and got an EA9500.
I made sure to screenshot the important pages on the old router in order to configure the new router like the old one.
This network has a Static IP Windows 7 machine that hosts a Remote Desktop Service on port 3389, which was working with the WRT and is no longer working with the EA9500.
I have configured the EA9500 to port forward 3389 and verified the port is open using http://www.canyouseeme.org/
I have gone through the various Windows firewall configuration pages to no success, (in theory these have not changed) and went so far as to entirely disable windows firewall and still can not connect using the public IP.
If I have access to the local network I can use the local IP to remotely login successfully.
I used wireshark to grab a few packets from the successful local login, and the unsuccessful remote one. The unsuccessful capture filtered for port 3389 only shows three packets, a SYN (into server), SYN-ACK(out of server), and an ACK(into server). The remote client then hangs for a while and puts up an error message. The successful connect capture has some similar packets, and then a lot of tcp traffic which I'm assuming is the application data. (as remote desktop is actually working).
Is it possible there is some kind of authentication/protocol or other behavior that might have changed between the WRT and EA that are stopping this connection from working? I know the port forward is working as I can see the two incoming packets that should be starting the connection.
I've considered changing the port number for testing, but have read somewhere the Mac client used by the remote people can only use the 3389 port.
Has anyone out there run into this or have any insight?
Thanks,
-Ian
Hello,
Could someone send me the MD5 from the file: FW_WRT3200ACM_1.0.6.186143_release.img, my dowload presented problems and I wanted to confirm the size and the MD5 to pofder know if I can install or not.
thankful
Has reached EOS (End of Support) with less than 1 year purchased?
How could it not be impacted by KRACK?
Regards,
Specs on the router and connection.
Currenlty running Firmware 1.0.6.181063
The thermostate is running on the 2.4 band and have it set with the following settings.
Broadcast SSID: Yes
Channel: Auto
Secuirty mode: WPA2 Personal
Wi-Fi mode: 802.11gn
Channel width: 20 MHz Only