EAP610-Outdoor wireless stopped working after 2 weeks
I have an EAP610-Outdoor AP and it was working perfectly for a couple of weeks, then one day the wireless stopped functioning. Everything else about the AP seems fine. The web interface works, it gets an IP through DHCP, SSH works, SNMP works, the LED works, but there's no detectable wireless activity and client devices can no longer see the SSID on either frequency band, even when they're right next to the AP.
I've tried:
- Updating to the latest firmware.
- Rebooting.
- Power cycling.
- Factory reset from both the web interface and physical reset button.
- Using the default TP-Link SSIDs after a factory reset.
- Entering SSID manually on client devices.
- Using different client devices, including PCs and mobile phones.
- Moving client to within a few feet of the AP.
- Changing wireless frequencies/bandwidths/modes/power.
- Different WPA security settings.
- Toggling SSID broadcast.
- Confirming that the scheduler is disabled.
- Using a shorter Ethernet cable between the AP and PoE injector.
Nothing seems to work. The clients all act as if the AP doesn't exist, even though they all worked perfectly for the first two weeks.
The only notable event that has happened recently is that we had a lot of rain, but the AP is under an awning and doesn't get wet unless there's a strong gust of wind, so I don't see why that would've affected it. There wasn't any lightning, but either way, the AP does have a grounding wire attached.
On the Radio Traffic stats, the RX counters are all zero. The only counters that change are TX Packets and TX Bytes, which tick up every few seconds. I also see the wireless interfaces listed with the "ifconfig" command through SSH, and their RX/TX stats agree with the web interface.
Is there anything else I can try or is it just defective hardware suffering from an early failure?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Fae,
I've done that dozens of time already. Even tried configuring it standalone and same results. I've tried downgrading it to 1.0.6 and later 1.0.3 to no avail.
I was just wondering, with all the incidents that you received about EAP610-Outdoor after a firmware upgrade which you recommend via Omada, do we still really have to open a ticket? Should this be an engineering concern with an open show stopper bug? And also why in Omada you still recommend upgrading the default firmware to version 1.1.3 know that when you do this it will brick the unit?
Come on TP Link people you can do better than this.
- Copy Link
- Report Inappropriate Content
@Garrett07 I agree with you. Plus they should put on hold the recommendation to upgrade the 610 in Omada.
- Copy Link
- Report Inappropriate Content
@MP64 i think your AP is murdered by the lightning
- Copy Link
- Report Inappropriate Content
Kasalamatan wrote
@MP64 i think your AP is murdered by the lightning
I beg to disagree. I lost the wireless right after i upgraded the firmware from version 1.0.4 (which I cannot find on any download servers of TP Link) to version 1.1.3. If you have read this thread i'm not the only one who experienced it. I have another device of same model still running on firmware 1.0.4 situated nearby and still working perfectly.
- Copy Link
- Report Inappropriate Content
My EAP610-Outdoor is experiencing the same problem. It was hooked up via mesh and stopped working last night, I am using 1.1.3 firmware but upgraded to this I believe a few weeks back. I brought the unit inside and and hooked to Ethernet, forgot the unit and readopted in the web ui and but still can't see the wireless on either band.
I noticed there is a EAP650-Outdoor out now, anyone know if this one is more reliable?
Update:
I contacted tech support via chat, and they determined my device was defective. Since I was inside the warranty period, they replaced the unit. The tech on the other side of the chat was knowledgeable and friendly. The whole process took about 3 weeks to complete from start to finish but I can report the new device is working properly. Side note: the 610-Outdoor unit generally runs warm to the touch. When my device stopped broadcasting the SSID, the green light was still on, but the device was cool to touch. Something to look for when troubleshooting.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 7476
Replies: 25