No static IP possible after ESPEasy mega 20180410
Moderators: grovkillen, Stuntteam, TD-er
No static IP possible after ESPEasy mega 20180410
I installed mega-20180410 on a Wemos D1 mini.
This version works excellent without any problems with a static IP number.
Because there are new developments (for example, %sunset% and %sunrise%), I wanted to install one of the latest versions.
I have installed several versions but no version works with a static IP number anymore.
An IP number is always assigned via DHCP, even after an OTA update of version 20180410 to a higher version.
Also, the versions after 20180410 always end up in a Setup loop, making configuration difficult.
Is there a solution for my problem, or maybe I'm doing something wrong?
This version works excellent without any problems with a static IP number.
Because there are new developments (for example, %sunset% and %sunrise%), I wanted to install one of the latest versions.
I have installed several versions but no version works with a static IP number anymore.
An IP number is always assigned via DHCP, even after an OTA update of version 20180410 to a higher version.
Also, the versions after 20180410 always end up in a Setup loop, making configuration difficult.
Is there a solution for my problem, or maybe I'm doing something wrong?
Re: No static IP possible after ESPEasy mega 20180410
Make sure you enter all values (IP, subnet, gateway, DNS).
Previous versions would accept incomplete settings, but the later core versions do not.
Previous versions would accept incomplete settings, but the later core versions do not.
Re: No static IP possible after ESPEasy mega 20180410
Thank you for your quick response.
I think I filled in everything, but I will try again.
I think I filled in everything, but I will try again.
Re: No static IP possible after ESPEasy mega 20180410
After a number of experiments with version: ESP_Easy_mega-20180621_normal_ESP8266_4096.bin,
here the results in a number of printscreen images.
here the results in a number of printscreen images.
- Attachments
-
- result_extern_dns_after_reboot.PNG (14.31 KiB) Viewed 8394 times
Re: No static IP possible after ESPEasy mega 20180410
I'm sorry, something goes wrong with the placement of the print screens
- Attachments
-
- local_dns_config.PNG (13.29 KiB) Viewed 8387 times
-
- result_local_dns_after_reboot.PNG (15.17 KiB) Viewed 8387 times
-
- extern_dns_config.PNG (14.36 KiB) Viewed 8387 times
-
- result_extern_dns_after_reboot.PNG (14.31 KiB) Viewed 8387 times
Re: No static IP possible after ESPEasy mega 20180410
Did you set or change the "Allowed IP range"? (See Client IP Filtering)
If you're suspecting that filter to be causing issues, then disable that filter.
Setting those strange ranges is probably not improving reliability of debugging.
If you didn't set those ranges, then we have another problem at hand.
It looks like you're still getting DHCP-based IP addresses and not the static IP range.
Could you backup your settings, perform a full flash erase, re-flash the latest firmware and first try again with static IP?
If that works, you could try to restore the saved settings.
If you're suspecting that filter to be causing issues, then disable that filter.
Setting those strange ranges is probably not improving reliability of debugging.
If you didn't set those ranges, then we have another problem at hand.
It looks like you're still getting DHCP-based IP addresses and not the static IP range.
Could you backup your settings, perform a full flash erase, re-flash the latest firmware and first try again with static IP?
If that works, you could try to restore the saved settings.
Re: No static IP possible after ESPEasy mega 20180410
With the last 4 print screens I have worked as follows:
The module 'Wemos D1 mini (4Mb)' first completely deleted from 0x000000 up to 0x3FFFFF with the file blank_1Mb.bin
Then implemented a Flash with Firmware mege-20180621.
On the Config page everything filled in as Print Screen 'local_dns_config' with DNS 192.168.1.254, but also tried with Ziggo DNS IP 89.101.251228.
The result can be seen in Print Screen 'result_dns_after_reboot'.
This looks fine, only the IP address is from the DHCP Server. I also now have the correct time of the NTP Server.
Then I used the Config page at ESP DNS with the IP address of Google, IP 8.8.8.8 (see 'extern_dns_config')
The result can be seen in Print Screen 'result_extern-dns-after_reboot'.
Now is error: IP / subnet (subnetmask is DNS)
DNS
Allowed IP Range
Even if I do not fill in Client IP filtering, I get the same result.
Furthermore, no time is available via the NTP Server.
When I first Flash an older version (20180410), which works great, but then upgrade to version 20180621 with OTA, it goes wrong again and I get the result like in print screen 'result_extern_dns_after_reboot'.
I hope that after this explanation it becomes a bit more clear what my problem is with the new version of ESP Easy.
The module 'Wemos D1 mini (4Mb)' first completely deleted from 0x000000 up to 0x3FFFFF with the file blank_1Mb.bin
Then implemented a Flash with Firmware mege-20180621.
On the Config page everything filled in as Print Screen 'local_dns_config' with DNS 192.168.1.254, but also tried with Ziggo DNS IP 89.101.251228.
The result can be seen in Print Screen 'result_dns_after_reboot'.
This looks fine, only the IP address is from the DHCP Server. I also now have the correct time of the NTP Server.
Then I used the Config page at ESP DNS with the IP address of Google, IP 8.8.8.8 (see 'extern_dns_config')
The result can be seen in Print Screen 'result_extern-dns-after_reboot'.
Now is error: IP / subnet (subnetmask is DNS)
DNS
Allowed IP Range
Even if I do not fill in Client IP filtering, I get the same result.
Furthermore, no time is available via the NTP Server.
When I first Flash an older version (20180410), which works great, but then upgrade to version 20180621 with OTA, it goes wrong again and I get the result like in print screen 'result_extern_dns_after_reboot'.
I hope that after this explanation it becomes a bit more clear what my problem is with the new version of ESP Easy.
Re: No static IP possible after ESPEasy mega 20180410
Tested today the latest version of 20180708. The problems I had are still present. After many tests I come to the conclusion that, when using a random DNS Server, my Wemos-D1 mini gets an IP number from the DHCP server of my Router. The NTP server also gives the correct time setting.
However, when I use the Google DNS address 8.8.8.8, the Wemos Module gets the fixed IP address, but there is no connection with the NTP server
However, when I use the Google DNS address 8.8.8.8, the Wemos Module gets the fixed IP address, but there is no connection with the NTP server
Re: No static IP possible after ESPEasy mega 20180410
Problem fixed IP number resolved !!
Today I did some tests performed with the latest version.
After consulting with a 'Colleague and Friend' he came up with the idea to fill in 255.255.255.0 at 'ESP Subnet:' on the Config Page..
In fact, this is the subnet mask of the fixed IP number.
The problem was solved.
Is there a wrong text in the Config Page, or is something wrong with the source code with the relevant variables.
Today I did some tests performed with the latest version.
After consulting with a 'Colleague and Friend' he came up with the idea to fill in 255.255.255.0 at 'ESP Subnet:' on the Config Page..
In fact, this is the subnet mask of the fixed IP number.
The problem was solved.
Is there a wrong text in the Config Page, or is something wrong with the source code with the relevant variables.
Re: No static IP possible after ESPEasy mega 20180410
Can you give an example of two texts contradicting eachother? (with links when possible)
Who is online
Users browsing this forum: Google [Bot] and 1 guest