Archer C6 Onemesh broken
Archer C6 router (V3.20) with RE220 and RE305 Onemesh extenders.
All firmware checked/updated a few months ago when the system was working fine, recently noticed only one extender was operational couldn't get both going at the same time, found another recent update for router but this hasn't fixed it.
I can get one or the other extender onemesh connected but not both at the same time. Both extenders appear in the DHCP table although the RE220 is picking up some historic name in DHCP but both keep correct names in onemesh pages (when visible).
Likewise the tether app only sees one of the extenders when both plugged in.
I have given the extenders reserved IP addresses and can access them through their IP's but nothing untoward showing up there.
I don't have any entries in the IP/MAC binding tables on the router.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @Add2 ,
What are the hardware and firmware versions of RE220 and RE305 respectively?
What error message will there be if RE220 and RE305 cannot be connected to the router simultaneously? Please take a screenshot and send it here.
- Copy Link
- Report Inappropriate Content
RE220 V2.0 1.0.2 Build 20201022 Rel. 66896
RE305 v3.0 1.1.5 Build 20210416 Rel. 61543
The fault is different than I thought, both of the router's Onemesh menus (Basic -> Network Map -> "Mesh Devices" AND Basic -> "Onemesh") are usually only displaying one Onemesh device at a time. Both extenders are fully operational and clients connected and talking through both. When I say usually, tonight is the only time I have seen it display both extenders since the router firmware upgrade earlier this year. Both extenders have 3-bar signal strength on the router and a solid throughput.
Both extenders now appear in the tether app at the same time even when router is still showing only one.
20 minutes after switching Onemesh on, the router still wasn't displaying both Onemesh devices even though both have been operational very soon after switching on again. Initially it showed the RE220 but it was disconnected and "failed" when I added it, then the RE305 showed as connected and the RE220 disappeared. EDIT: 30 minutes after and both now appear again.
The Tether Lab "Wi-fi Detective" can't see my RE220 even though my phone is working through that extender, it does see the RE305. I guess this might be expected behavior with Onemesh.
There is nothing in the router logs of relevance (only has LED controller INFO messages), extenders don't appear to have their own logs, or at the least I haven't found them.
Just in case it is of any relevance, this is entirely a domestic TP-Link network, with one router, two Onemesh extenders, four Gigabit Powerline adapters and three Gigabit Ethernet switches driving worst case about twenty devices. About fourteen devices are near enough 24/7 on Ethernet and up to about 6 Wireless devices intermittently. It sounds a lot for a non-premium router but I have never seen CPU or Memory report have any concern, the network is very smooth and high speed. Memory is always less than 50% and highest CPU core about 35% (normally less). The router WAN is connected to a IPv4 device in modem mode.
- Copy Link
- Report Inappropriate Content
Hello @Add2 ,
Thanks for getting back to me.
From the information you provided, it's clear that the RE220's status in OneMesh's Mesh Devices list is abnormal, right? In other words, before the Archer C6 update, the RE220 and RE305 were displayed normally and reliably in the Mesh Devices list.
After the Archer C6 firmware update, not only did the RE220 no longer appear reliably in OneMesh's Mesh Devices list, but the Tether app also frequently failed to scan the RE220, is that correct? However, the RE220 network is running stably and clients are connecting normally.
If this abnormal display only occurs on the RE220, would you mind temporarily removing the RE305 and testing whether the OneMesh Device List displays the RE220 status normally and whether the Tether app can detect it normally?
Or, would you mind hard reset the RE220 and add it to the OneMesh Network again?
- Copy Link
- Report Inappropriate Content
It happens either way around, just the RE220 displaying or just the RE305 displaying on the C6 router onemesh lists or app. As I've now confirmed they are both working even when not getting displayed, I assume the fault is on the C6 router and it is being temperamental about listing them even when it is satisfactorily managing them operationally.
I will hard reset all the devices in the next week.
I have spotted something else that may vaguely be related to this problem, I can no longer access the modem through its local IP any longer, I suspect this may be because I switched off all ALG settings apart from IpSec. Could one of the ALG settings be interfering in the onemesh operation?
- Copy Link
- Report Inappropriate Content
Hello @Add2 ,
Thanks for getting back to me.
Did you notice the abnormal display of your range extenders after disabling the ALG function?
It's unclear whether the ALG settings affect OneMesh. Have you reset the entire network? Does the Mesh list display normally now?
- Copy Link
- Report Inappropriate Content
Thanks, originally it didn't display both extenders at the same time for at least weeks and yet now the second one appears within the hour. The problem changed from a permanent problem to a temporary (intermittent?) problem so the results of any tests would not be entirely conclusive. As said, Onemesh is fully operational it is only a display problem.
Unfortunately I updated the firmware roughly at the same time as switching off most of the ALG functions so I can't say which triggered the problem.
I'll try the ALG functions first and see if that improves things. I have noticed something else in that the router no longer bridges through to the modem's control panel which could be an ALG needs switching back on,
I'll play and test when I can, I've had a busy week shuffling paperwork.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 156
Replies: 6
Voters 0
No one has voted for it yet.
