search

stfnhmplr / node-red-contrib-homee

access the homee api with node-red
37 stars 8 forks source link

real Homee & virtual Homee in different Subnets #27

Open DomKow2008 opened 2 years ago

DomKow2008 commented 2 years ago

I am wondering if it's possible to connect a virtual Homee to a real Homee if devices are in different Subnets?

Assume the following case for my Network: IOT Network: real Homee (192.178.99.5) Server Network virtual Homee via Docker (192.168.0.100)

I am not able to connect the virtual Homee to my real Homee in this scenario, however I just created a NodeRed instance on a Raspi within same network as real Homee and I am able to connect.

Any ideas or thoughts on that?

hblaschka commented 2 years ago

This is a network level routing issue, not an issue with Stefan´s package. You need to ensure that traffic coming from and to 192.178.99.5 is passed towards 192.168.0.100 and vice versa. This linked article (German, as I assume you are German) might give you an idea (there are limitless ways to do it) on how to do that:

https://www.msxfaq.de/sonst/iot/iot-router.htm

Stefan might input on which traffic is flowing on which ports in which direction, to basically enable you to block all other traffic between the devices/subnets.

DomKow2008 commented 2 years ago

Thanks for the quick reply! I just disabled the firewall between both networks for test purpose, but it's still the same result.

I just tried to capture the network traffic when I try to connect to a virtual Homee, which looks like this: 10:48:35.018699 IP homee-xxxxxx.local.58318 > 192.168.99.255.15263: UDP, length 7

So I am not very experienced with this networking stuff, but I assume the issue is that the ports used are not broadcasted by default to other subnets. Does this makes any sense?