- Thu Apr 09, 2015 11:58 pm
#14056
did you every find an answer?
- Sat Apr 11, 2015 1:39 am
#14157
That's mostly a problem with the fact that the code tries to do a DNS lookup on every hostname it gets, so it will bork when you feed it a bare IP address. I have some code to fix this, haven't come around to committing it anywhere yet though.
Do you have any idea why I'm seeing this behavior? I guess what I'm asking is if there is some difference between the IoT demo and httpd stacks that might prevent ESP8266 from connecting to an IP address directly?
The IoT http server seems mostly made for quick single-use AJAX calls, so I'm not surprised.
rith87 wrote:@sprite_tm: I have some strange observations when working with your stack from http://git.spritesserver.nl/espeink.git/.
That's mostly a problem with the fact that the code tries to do a DNS lookup on every hostname it gets, so it will bork when you feed it a bare IP address. I have some code to fix this, haven't come around to committing it anywhere yet though.
Do you have any idea why I'm seeing this behavior? I guess what I'm asking is if there is some difference between the IoT demo and httpd stacks that might prevent ESP8266 from connecting to an IP address directly?
PS: The 192.168.4.1 hosted on the IoT demo example can be accessed from my Ubuntu machine; but the one hosted on the httpd stack can only be accessed from my non-Linux devices.
The IoT http server seems mostly made for quick single-use AJAX calls, so I'm not surprised.
