3x Deco in Access Point mode, constant red light, connection is fine
I have a 3x setup of Deco AC1900 (S1900) configured in access point mode, with each Deco getting an IPv4 from my router (reservations set for each Deco unit, so their IPv4 address is persistent). Running the latest firmware (actually upgraded just 2 days ago, but the problem was occurring with the previous firmware too), have excellent range between the 3 units (Deco app shows 2 out of 3 signal bars on the connection strength between the main Deco and its 2 peers, would love to see how this is refleced in a web GUI byt TP Link is not interedted in building that, so it seems).
So my problem is this: ever so often my main Deco will exhibit a persistent red light and the child Decos a blinking red light. The Deco app shows no alerts and the ever-present and vague "Everything looks good" indication" is there too. Network is apparently working okay (no client has disconneced from wifi and internet connectivity is proven to be working).
What is causing this? What sort of advanced logging can I pull from these devices that can tell me what's wrong?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
Have you set up any firewall or access control settings on the main ISP router? or would there be any third-party firewall programs in the LAN network?
It seems like the online detection of Deco S7 has been blocked by the ISP router.
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
Hi,
nothing is blocked and there's no firewall. It's quite the "dumb" setup really, all 3 Decos are network clients like any other device, although with fixed ipv4 leases, and they just go through the router as gateway.
If this is what you suspect, then what is the deco's process of validating internet access?
- name resolution attempt?
- wget on a specific addrees?
- actual validation against a web site via an API?
- Copy Link
- Report Inappropriate Content
@David-TP hello???
- Copy Link
- Report Inappropriate Content
@TP-Link , HELLO!!!??? Where is your support??
- Copy Link
- Report Inappropriate Content
AFAIK the online detection has been done via a name resolution.
You can set a public DNS on your router (like 1.1.1.1 and 8.8.8.8) and observe the Deco behavior.
- Copy Link
- Report Inappropriate Content
Thanks terziyski. I don't believe it's a DNS problem, my ISP's DNS are way way closer to me (hop-wise) than either 1.1.1.1 or 8.8.8.8 (or their IPv6 equivalents). What debugging information can I pull from the Deco in order to understand and validate if this is really a DNS problem? I don't want to start making changes to a working network before seeing proof that DNS is indeed the problem (and I believe this is a reasonable thought process).
- Copy Link
- Report Inappropriate Content
The problem is that you can't pull any additional debugging information from Deco.
You can check this post related to Deco online status detection.
Apart from that changing your main router's DNSs is not a significant change that you should be concerned about.
I am not sure that DNS change would fix your issue, but at least you can try that and check if there's an improvement.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
need some (oficial) answers here, have an issue with the product and so far struggling to get an official response or resolution. I'm tech savvy enough to go through troubleshooting, so please, support me at the correct level (if you are going to tell me to try to change my DNS, give me a way to prove that as the root cause)
- Copy Link
- Report Inappropriate Content
Awesome support guys, we're 4 months into me reporting this issue and so far no official response... CAN ANYONE FROM TP LINK COMMENT HERE?!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 524
Replies: 10