IoT garage door opener maker disables customer’s service after bad review

Re:IoT garage door opener maker disables customer’s service ... by daurnimator on Tuesday April 04, 2017 @09:40PM (#14038964)

Why do they require a static IP? They should be using DNS. It should be simple for any internet connected device to run dynamic DNS.

[ Parent | on HN ]

Re:IoT garage door opener maker disables customer’s service ... by cookiecaper on Tuesday April 04, 2017 @10:19PM (#14039134)

Assuming a NAT and restrictive firewall like those included in most consumer routers, DNS gets you the public IP address, but it doesn't get you a port to the client (though one may be better advised to use STUN or ICE). You'd need to punch a hole dynamically with UPnP, require the user to punch the hole manually, or introduce a relay server using something like TURN.

[ Parent | on HN ]

Re:IoT garage door opener maker disables customer’s service ... by daurnimator on Wednesday April 05, 2017 @03:36AM (#14040435)

That's assuming you want external access.

Often the user just needs to find the device on their own internal network: in which case a DNS entry of myserialnumber.myIoT.com returning 192.168.1.104 is fine.

Or if you need need to initiate communication from outside the local network: establish a tunnel (in same style as e.g. ngrok).

[ Parent | on HN ]