- Mon Sep 18, 2017 2:31 pm
#70090
gdsports wrote:the latest diagram indicates it connects using static IP for http server then connects using DHCP for http client. If the http client cannot connect to the Internet when using static IP, the gateway or subnet parameters are wrong.
@gdsports,
For both scenarios I had configured static IPs for all ESP8266 devices, each one having its sufix shifted by '1' ( e.g 192.168.n.i+[1...10] ). The router is configured so that assigns low IPs for each incomming DHCP connection. By the way, the router is dedicated for that, so there is no risk of another application intrude on this network.
I was able to connect each ESP8266 either to the remote server, as well to the local clients with their static IPs, therefore I'm not sure if I got exactly what you meant. On this case, should I keep the Gateway configuration, but by using "correct" values ?
I'm using the following configuration:
Code: Select allIPAddress subnet (255,255,255,0) ;
IPAddress net (192,168, 1, 211) ; // varies from 211 up to 220
IPAddress gateway (192,168, 1 ,0) ;
/// IPAddress dns (8,8, 8 ,8) ;
rudy wrote:I think you want to do is to stop the client on the ESPs.
@rudy,
Regardless from this step, the main issue is at some layer bellow of the communication stack, in the IP settings. In fact, once solving the gateway issue, I will run client and server one at a time, at least on the initial stage of the project.
"part of the world that you live in, you are the part that you're giving" - Renaissance