So, Ive left this thing plugged in…I see a lot of traffic from AWS cloud servers and nothing alarming. Strange that it has this much traffic but not making contact to kasa.
However…Right at 5 days (120:0:0) the KP125 decided to become its own DHCP server and assign itself a class C IP of 192.168.0.1. The network its on has no class C IP’s (192-223) anywhere at all. The firewall/ DHCP server has the entire class C range blocked. At (120:10:0) it re-grabbed the 10.50.17.39 IP.
I assume that @andy router is at 192.168.0.1 where my house … I did change my netgear’s LAN to 192.168.1.1 and I see that @kevin1 is also on a 192.168.1.x. Guessing most people here are using a 10.x.x.x.
Im not sure why kasa has this thing doing rouge routing right at 5 days and Im not sure why using they would use the most common dhcp IP, then Im not sure why that doesn’t cause more havoc on andy’s network than ours, it actually probably is for 10 mins… But I assume that must be crashing the LAN hub between LAN sense and LAN kasa while testing LAN communications. I tried to ssh into the KP125 but it wouldn’t let me in. I thought that all kasa and tp-link plugs all had an open local API… just would be interested in view the json file at this point.