Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for cross-subnet communication? #20

Open
mattgphoto opened this issue Mar 30, 2019 · 0 comments · May be fixed by #21
Open

Allow for cross-subnet communication? #20

mattgphoto opened this issue Mar 30, 2019 · 0 comments · May be fixed by #21

Comments

@mattgphoto
Copy link

Hey there! I know it's been a while since you touched this app, but I'd really like to use it and now that I've put my Bulbs on their own LAN subnet (My home LAN is x.x.10.x and now the 'IoT LAN' as I call it is on x.x.20.x), I can see when MaxLIFX tries to discover bulbs it reaches out to broadcast, it seems:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:44:11.816078 IP 192.168.10.50.65289 > 192.168.10.255.56700: UDP, length 36
15:44:36.793388 IP 192.168.10.50.57182 > 192.168.10.255.56700: UDP, length 36
15:46:48.609113 IP 192.168.10.50.64130 > 192.168.10.255.56700: UDP, length 36
15:48:02.345216 IP 192.168.10.50.64174 > 192.168.10.255.56700: UDP, length 36
15:48:20.358130 IP 192.168.10.50.54793 > 192.168.10.255.56700: UDP, length 36
15:48:40.004710 IP 192.168.10.50.63145 > 192.168.10.255.56700: UDP, length 36
15:49:12.999449 IP 192.168.10.50.63162 > 192.168.10.255.56700: UDP, length 36
15:49:19.851017 IP 192.168.10.50.62279 > 192.168.10.255.56700: UDP, length 36

But nothing is received on the LAN2 side. I've allowed all traffic between the two subnets on port 56700 (And I can verify that traffic does flow on LAN2 to the LIFX Cloud, it appears:

15:54:45.895369 IP 104.198.46.246.56700 > 192.168.20.118.53027: Flags [.], ack 5176, win 65392, length 0
15:54:45.902500 IP 104.198.46.246.56700 > 192.168.20.108.56509: Flags [.], ack 7282, win 65392, length 0
15:54:45.902677 IP 104.198.46.246.56700 > 192.168.20.114.64825: Flags [.], ack 6724, win 65392, length 0
15:54:45.905052 IP 192.168.20.111.21709 > 104.198.46.246.56700: Flags [P.], seq 4600:4717, ack 4134, win 1460, length 117
15:54:45.906731 IP 192.168.20.115.56700 > 192.168.20.255.56700: UDP, length 88
15:54:45.908168 IP 192.168.20.116.56700 > 192.168.20.255.56700: UDP, length 88
15:54:45.909430 IP 104.198.46.246.56700 > 192.168.20.146.60080: Flags [.], ack 6542, win 65392, length 0
15:54:45.938087 IP 192.168.20.110.31600 > 104.198.46.246.56700: Flags [P.], seq 4296:4413, ack 3817, win 1460, length 117
15:54:45.953788 IP 192.168.20.115.20937 > 104.198.46.246.56700: Flags [P.], seq 4599:4716, ack 4135, win 1460, length 117

I'm using a pfsense firewall, if that helps at all. I'm wondering how to finagle this on my side if it's not something that MaxLIFX can do. Please let me know if you have any ideas! Thank you!

@tidusjar tidusjar linked a pull request Mar 30, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant