Deleted User 298457
Deleted User 298457
Hi guys,
Has anyone any experience of this?
I have a TP Link Archer C80. I added a TP Link AC1900 Mesh hot spot. I'm pretty anal about DHCP reservations as I like to know precisely what is on the network and have my own numbering scheme. I therefore use the admin console all the time. It has been rock solid for months.
Yesterday I added a TP-Link LS1005G 5-Port Gigabit switch. Nothing crazy, I just needed some additional ports. I put into the 5-port switch my Hive and Hue.
I then was able to plug in my Raspberry Pi and run AdGuard. AdGuard for what's worth is running super quick, very responsive and doing its job well. Everything else on the network "seems fine".
I wanted to do a quick reboot of the router and this is where the funny's happened. My WiFi connected but it connected to the mesh directly. The default gateway was the IP of the mesh device. Odd. I switched off the AC1900 and then rebooted the router - phew back to normal. I put this down to an odd side effect but explainable (mesh conflict).
However, the big prevailing issue is that the Archer user interface is now horrendously slow. And features like "connected clients" on the home screen just simply doesn't load.
Notice how Clients is just a blank yellow circle - normally it would say how many are connected.
Is there a way to check if there is something odd going on, on the network itself? I guess I could fire up wireshark? I assume it isn't an odd thing to do - add more TP Link devices!
Any offers of help appreciated.
Has anyone any experience of this?
I have a TP Link Archer C80. I added a TP Link AC1900 Mesh hot spot. I'm pretty anal about DHCP reservations as I like to know precisely what is on the network and have my own numbering scheme. I therefore use the admin console all the time. It has been rock solid for months.
Yesterday I added a TP-Link LS1005G 5-Port Gigabit switch. Nothing crazy, I just needed some additional ports. I put into the 5-port switch my Hive and Hue.
I then was able to plug in my Raspberry Pi and run AdGuard. AdGuard for what's worth is running super quick, very responsive and doing its job well. Everything else on the network "seems fine".
I wanted to do a quick reboot of the router and this is where the funny's happened. My WiFi connected but it connected to the mesh directly. The default gateway was the IP of the mesh device. Odd. I switched off the AC1900 and then rebooted the router - phew back to normal. I put this down to an odd side effect but explainable (mesh conflict).
However, the big prevailing issue is that the Archer user interface is now horrendously slow. And features like "connected clients" on the home screen just simply doesn't load.
Notice how Clients is just a blank yellow circle - normally it would say how many are connected.
Is there a way to check if there is something odd going on, on the network itself? I guess I could fire up wireshark? I assume it isn't an odd thing to do - add more TP Link devices!
Any offers of help appreciated.
ax73 and re405 or something.