Domotz agent not detecting network clients

[System_Error_Message 2]

I have domotz installed on a raspberry pi 2 that is part of 2 networks (it has 2 ip addresses). I noticed that domotz only detects the gateway which is my ISP and not my other network or any other clients. My setup is very unconventional and not something you will find at homes. Every device on my network is part of 2 networks, one for internet (my ISP gives DHCP,handles NAT and such) and 1 for internal communication.

[Giancarlo 33]

This is quite a particular configuration.

At the moment the Domotz Agent scans one single network (C Class), which is the one related to the default gateway. Therefore, if you want the Domotz Agent scanning the clients network (the one for internal communication, you mention), you should set as default gateway on that Raspberry one gateway on your internal network. However, you should make sure that the Raspberry can go out on the internet as well, in order to communicate with Domotz backend/cloud.

Note that the possibility to allow the user to select a different subnet to scan is something we have in our roadmap. But realistically it's not something that might happen before Q1 2016. I invite you to follow this post as well, were other users also require such feature:

 

Edited November 4, 2015 by Giancarlo

[System_Error_Message 2]

Im not doing any sort of layer 2 segmentation. It is done in layer 3. My internal network also consists of VPN clients too. My router only does layer 2 filtering to prevent leaking from my network to the other users of my ISP and also to protect against any hack attempts.

There are 2 gateways for the network however the ISP one is the default gateway because my ISP blocks NAT so it is not possible to set my router as the default gateway for internet access.

 

My asus wifi router that is only used as an access point is able to detect wired devices even though they arent communicating through it. It only shows the mac address of it though instead of the IP address since it has only 1 IP address which is part of my internal network. So wired devices connected to my switch show up on my asus wifi router since it is connected to the same switch.

Edited November 4, 2015 by System_Error_Message

[Jjason 1]

+1 for being able to select more than just one IPv4 /24. While this is common for basic home networks, more folks are adding guest subnets, DMZ subnets, and so on. 

 

Thoughts based on experience: 

1. Use the IP subnets from the interface(s) as the default range(s).

2. Have a settings box that allows the user to add/change/delete IP subnets to their heart's content.

3. Same logic applies to IPv4 and IPv6. 

 

Hope this is useful!

Jason

[System_Error_Message 2]

I think the most important bit is that the agent isnt detecting any of my network clients. Even though i have 2 networks clients are part of both networks at the same time but nothing comes up on the agent, only the gateway.