This repository has been archived by the owner on Feb 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 95
In AP, DNS server always redirects to 192.168.4.1 no mater what APStaticIP is set to. #58
Labels
bug
Something isn't working
Comments
Hi @yiancar Thanks a lot for your smart eyes which spot the puzzling-to-me captive-portal issue. I've tested the fix and will release a new version within today with your contribution noted. Waiting for more of your bug spotting. 👍 Best Regards, |
The preliminary test for you to enjoy 👍
|
Hi @yiancar The new ESP_WiFiManager releases v1.6.1 has just been published, with the note about your contribution in Contributions and Thanks Cheers, Releases v1.6.1
|
khoih-prog
added a commit
to khoih-prog/ESPAsync_WiFiManager
that referenced
this issue
Apr 26, 2021
### Releases v1.7.1 1. Fix captive-portal bug if Config Portal AP address is not default 192.168.4.1. Check [In AP, DNS server always redirects to 192.168.4.1 no mater what APStaticIP is set to. #58](khoih-prog/ESP_WiFiManager#58) 2. Fix MultiWiFi bug.
Cheers thank you for the quick reply! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
My understanding is that the intention of the code is to auto direct the user connected to the config portal once connected. Currently due to a misconfiguration in the DNS server if
APStaticIP
is set the user has to enter the IP ofAPStaticIP
to the browser.This is because the DNS server is configured with
WiFi.softAPIP()
before softAP itself has been given the value ofAPStaticIP
.Esentially the DNS entry always redirects to 192.168.4.1.
Steps to Reproduce
Use the ESP32_FSWebServer_DRD sketch.
Connect to AP.
Config page only appears when 192.168.100.1 is used in the browser.
Proposed solution
DNS Setup
ESP_WiFiManager/src/ESP_WiFiManager-Impl.h
Line 364 in 27f8867
ESP_WiFiManager/src/ESP_WiFiManager-Impl.h
Line 424 in 27f8867
Either move DNS setup after the AP configuration or put another checker at DNS setup to check if
APStaticIP
is set.The text was updated successfully, but these errors were encountered: