TP-Link issues resolved (kind of)

Tue May 19 12:47:35 EDT 2020

Well, the TP-Link is not a network device. It is a Kasa smart wifi power outlet.

I don’t have to use 2 subnets. It was just that I ran out of ethernet ports on my switch. The only port I had available was on my Unifi USG. The USG has 3 ports. one for Wan, 1 for LAN1 and one that can be either a 2nd WAN port or a LAN2 port. LAN1 and LAN2 cannot be on the same subnet. So my LAN2 port was open and I attached it to my MAC and gave it a 192.168.10.0 address.

WRT what Steve Henley stated about multi-home. I am not trying to route across the 2 interfaces by an endpoint. I figured any app on the XTension Mac would do that with out intervention. But it is moot since I only use the 192.168.10.0 interface for my Unifi wifi controller (unrelated to XTension). Everything I need related to XTension is on one subnet (192.168.1.0). And yes, I can do without the second subnet, but still curious why it casques a problem.

So, I am not sure why, if the 192.168.10.0 interface is active, XTension seems to only look at that 192.168.10.0 subnet for the TP-LINK/KASA interface. It seems to not have a problem talking to the Vera which is only on the 192.168.1.0 subnet. I was also having problems with the Philips Hue hub, but not sure if it is related or not. I just stopped using the Hue.

-tom

> On May 19, 2020, at 12:29 PM, Michel Angelo <michel_angelo at me.com> wrote:
> 
> Tom, reading the entire thread, I still fail to understand what you are trying to achieve. 
> 
> It seems to me you use two networks, but it also seems to me you have no reason for doing that. In such a case, if your primary network is enough (the 192.168.0.xxx), just don’t use the other. 
> 
> Again ,wild guess, if your tp-link Is your firewall router and simply lacks an additional physical port on your primary network, add a switch. But I may have misunderstood. 
> 
> -- 
> Michel-angelo
> Envoye de mon mobile
> 
>> Le 19 mai 2020 à 17:39, Steve Henley <steve.henley at shaw.ca> a écrit :
>> 
>> When the Mac is plugged into two different subnets with two different physical interfaces it is multi-homed.
>> 
>> For network activity to travel between the two subnets over the two interfaces from some endpoint on the wireless to the wired (or vice-versa) something on the Mac has to act as a router for that traffic, or the endpoint devices on either subnet need to have the specific IP information to find a path to devices they need to talk to on the other subnet.
>> 
>> James would be the one to answer if XTension can deal with this, but I think I would try to find a different network configuration that allows everything to function on a single network subnet, or a configuration that gets the devices that need to talk to each other on the same subnet.
>> 
>> Just so I am clear, there is a physical Unifi access point, and a separate physical Unifi secure gateway on your network? How many physical ethernet ports do you have on the Unifi AP? Is one of those ports a specific dedicated WAN port? What model of Unifi USG are you using?
>> 
>>> On May 19, 2020, at 8:32 AM, Tom Yarmas <tom at yarmas.com> wrote:
>>> 
>>> I think I have confused things a bit here. I am referring to my TP-Link/Kasa outlets. Not a wireless USB interface.
>>> 
>>> I have the Mac connected via wifi to subnet 192.168.1.0 and it has a static ip address.
>>> 
>>> I also have the same Mac connected via ethernet cable to subnet 192.168.10.0 and it has a static ip address. (this is basically like a DMZ).
>>> 
>>> When both interfaces are enabled, the Kasa outlet (a duplex outlet that has 2 units in XTension) does not respond (but does respond to the Kasa app). This outlet has an IP address on the wifi network (192.168.1.0 subnet).
>>> 
>>> If I disable the ethernet wired IP interface on the Mac, then my Kasa units responds to XTension commands.
>>> 
>>> I use my XTension Mac as a Unifi controller and that is one reason I have the wired connection. I have had trouble with the Unifi AP getting updates via wifi and moved it to a wired connection to resolve that. I could use a wired connection on the same subnet as the wifi (192.168.1.0) I guess. I just ran out of ports and the Unifi USG that I have has an open port, so I used that one (but that USG port has to be on a separate subnet).
>>> 
>>> -tom
>>> 
>>> 
>>>>> On May 19, 2020, at 9:51 AM, Steve Henley <steve.henley at shaw.ca> wrote:
>>>> 
>>>> Tom,
>>>> 
>>>> A few questions to understand your network configuration.
>>>> 
>>>> If the TP-Link is a wireless USB interface, can you give the model of the interface, the version of the TP-Link drivers installed, and the version of Mac OS you are running?
>>>> 
>>>> Are you using DHCP or static addresses on your network, and is the Unifi acting as your DHCP server?
>>>> 
>>>> Is the Unifi the wireless hub that the TP-Link has been connecting to, and would connect to in future, or is there a different wireless hub/router?
>>>> 
>>>>> On May 19, 2020, at 7:00 AM, Tom Yarmas <tom at yarmas.com> wrote:
>>>>> 
>>>>> I finally figured out what is wrong with my TP-Link in XTension (it suddenly stopped working and I could no longer get it to work).
>>>>> 
>>>>> It turns out that I added a wired ethernet connection in addition to my existing wireless connection a while back.This wired connection is on a separate subnet and is used for my Unifi network controller.
>>>>> 
>>>>> If I disable that wired connection, then my TP-Link suddenly works and everything is fine. 
>>>>> 
>>>>> So, I have deduced that I cannot seem to have the XTension Mac on 2 different subnets and expect this to work?
>>>>> 
>>>>> Is there a way to define which network device or subnet the TP-Link interface works on? 
>>>>> 
>>>>> Thanks.
>>>>> 
>>>>> -tom
>>>>> 
>>>>> _______________________________________________
>>>>> XTensionList mailing list
>>>>> XTensionList at machomeautomation.com
>>>>> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
>>>> 
>>>> _______________________________________________
>>>> XTensionList mailing list
>>>> XTensionList at machomeautomation.com
>>>> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
>>>> 
>>> 
>>> _______________________________________________
>>> XTensionList mailing list
>>> XTensionList at machomeautomation.com
>>> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
>> 
>> _______________________________________________
>> XTensionList mailing list
>> XTensionList at machomeautomation.com
>> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist