I think a recent update broke it

[sborn]

I had this running as a service and it worked flawlessly. Now, the iOS devices are suddenly seeing the IP as the IP of the Raspberry Pi that it is running on. Do you have any thoughts about it?

So server.js is running, sending out packets, and the iOS app is seeing the IP of the server rather than of the UNVR from the packet.

I did notice that the packet changed when I ran client.js, but I updated them.

Here is what I get when I run it manually:
got message from 192.168.10.240:49893 successfully sent 146 bytes got message from 192.168.10.240:49893 got message from 192.168.10.240:50816 got message from 192.168.10.240:59979 successfully sent 146 bytes successfully sent 146 bytes successfully sent 146 bytes got message from 192.168.10.240:49893 successfully sent 146 bytes got message from 192.168.10.240:50816 successfully sent 146 bytes got message from 192.168.10.240:59979 successfully sent 146 bytes got message from 192.168.10.240:59979 got message from 192.168.10.240:49893 got message from 192.168.10.240:50816 successfully sent 146 bytes successfully sent 146 bytes successfully sent 146 bytes

[adams-family]

@sborn Hi, were you able to resolve this issue?

[sborn]

@sborn Hi, were you able to resolve this issue?

I didn't. I think a Ubiquiti update eliminated the need for it, though. Is that not the case?

[adams-family]

@sborn Ubiquity update seems to have eliminated the option to connect to Protect from a different VLAN/VPN completely, according to some posts of other folks :(