Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

Can't contact bridge after router gives it new DHCP IP #96

Open
cliffspencer opened this issue Jul 25, 2015 · 0 comments
Open

Can't contact bridge after router gives it new DHCP IP #96

cliffspencer opened this issue Jul 25, 2015 · 0 comments

Comments

@cliffspencer
Copy link

My new DSL router is handing out a different dynamic IP to the bridge each time the router reboots (contrary to the previous behavior) and there appears to be no way to assign a consistent DHCP address to a device. This means that the SDK can no longer establish a connection to the bridge. Currently this forces me to pushlink each time the router reboots. Thanks Verizon. Is there any alternative to this? Is there some way that when I call enableLocalConnection the bridge can be discovered?
Thanks,

Cliff

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant