physicalgraph.device.Protocol.LAN to a different subnet/vlan

Is physicalgraph.device.Protocol.LAN capable of talking to devices on different vlans/subnets?

If my hub and PC are on the same network, communication works just fine, but once they are on different subnets HTTP packets are no longer sent.

Testing the same packets from a different device (record, replay) everything works just fine so I’m fairly certain everything is routed properly.

I can’t say with 100% certainty but I recall reading a post from ST staff to that effect. My own hunch is that the hub treats any network outside of its’ own subnet as external. If it didn’t the hub could theoretically be used as a tool to attack other networks through a simple SmartApp.

Thank you Steve.

This is kind of what I was seeing too, but I didn’t seen anything ‘official’ in the docs or anything.

I may try for a iptables DNAT/SNAT masquerade to forward the specific traffic/port to the other vlan/subnet as a workaround for now.

1 Like

I was going to say, if you know what you’re doing and have a device/router capable of doing it, just NAT it from the ST segment to your destination segment and then reference the NAT instead, that should work.

It worked beautifully!

I <3 my Raspberry Pi! :slight_smile: