jimbarstow Posted June 29, 2015 Posted June 29, 2015 When I hooked up my ISY, it got its IP address from my ISP, NOT my router. In spite of not having a local DNS, I can get to the ISY by name, "http://isy.universal-devices.com/99i/".I need to do this for another server that will be talking to the ISY but can't figure out how they did it. In my research, none of the solutions fit the environment that I'm running in. (Apple Airport Extreme in bridge mode to my ISP DHCP server.) Any idea how the ISY does this?
Teken Posted June 29, 2015 Posted June 29, 2015 If ISP modem / router has been bridged this prevents a double NAT situation. Bridging a modem / router also allows you to install a more powerful router with more features. People also do this to extend their WiFi network to provide more coverage. The DNS based on your reply, is being handled by the ISP Modem / router.
Michel Kohanim Posted June 29, 2015 Posted June 29, 2015 Hi jimbarstow, The http://isy.universal-devices.comURL is NOT the IP address of your ISY. The only thing it does is to bring up the Admin Console that searches your LOCAL network for ISY. ISY in no way shape or form accessible remotely (on the Internet) UNLESS:1. You create port forwarding rules in your router 2. Use a portal solution such as MobiLinc With kind regards, Michel
jimbarstow Posted June 29, 2015 Author Posted June 29, 2015 (edited) Hi jimbarstow, The http://isy.universal-devices.comURL is NOT the IP address of your ISY. The only thing it does is to bring up the Admin Console that searches your LOCAL network for ISY. ISY in no way shape or form accessible remotely (on the Internet) UNLESS: 1. You create port forwarding rules in your router 2. Use a portal solution such as MobiLinc With kind regards, Michel In poking around I noticed that the actual name is "isy994-ems". So what is "isy.universal-devices.com"? And by what process does it get translated into the correct ip address? It can't be pushed out the the ISP's DNS so where is that name resolution occurring? I'd like to know because I'm gathering information from a bunch of sensors hooked up to arduino micro controllers. I'd like to be able to push/pull data between the ISY and the arduinos but I can't have any hard-coded IP addresses. I have almost everything working independently and am stuck on the IP address issue. I'm hoping the answer is something I missed, such as we use "xyz" protocol. So far I've investigated local DNS servers (nope), IP reservations on the router (nope), routing tables (don't think so), etc. Edited June 29, 2015 by jimbarstow
Michel Kohanim Posted June 29, 2015 Posted June 29, 2015 Hi jimbarstow, ISY994-EMS is the DHCP name for ISY and the associated local IP address. Again, I have to stress that you can NOT get to ISY using isy.universal-devices.com. That URL is only for downloading the applet/application and that's it. Nothing goes through isy.universal-devices.com . With kind regards, Michel
jimbarstow Posted June 30, 2015 Author Posted June 30, 2015 (edited) Hi jimbarstow, ISY994-EMS is the DHCP name for ISY and the associated local IP address. Again, I have to stress that you can NOT get to ISY using isy.universal-devices.com. That URL is only for downloading the applet/application and that's it. Nothing goes through isy.universal-devices.com . With kind regards, Michel Understood. I'll run an experiment tonight to see if the arduino network interface can handle a name (isy994-ems NOT isy.universal-devices.com) instead of a raw ip address to set variables via your REST interface. Edited June 30, 2015 by jimbarstow
Michel Kohanim Posted June 30, 2015 Posted June 30, 2015 Hi jimbarstow, ISY994-EMS is a DHCP offer name and might not be resolved to an IP address. With kind regards, Michel
Recommended Posts