- Wed Mar 13, 2019 4:57 pm
I may also want to do this for another method but not for answering DNS requests but for spoofing a redirect on as though it was on one of the various device connectivy check urls. But it's the same basic issue.
The old method was to redirect everything to the softAP ip address and then answer the various connectivy check urls (such as google's generate_204) with a 30* redirect. (I've seen people use multiple 300 response codes in examples). This used to work, but doesn't any longer.
One suggestion I saw was that if the netmask of the connected network appears to include the address returned by DNS, it may try to use a different (non TCP/http) method to check if the connection is active. Thus the suggestion was to respond to the DNSServer request with an IP address 'not' on your access point's netmask range so it wouldn't try the alternate method. This still doesn't generate the pop-up so I wanted to try it by actually answering the generate_204 address on the other network address, but I don't know how to get the esp8266 web server to answer the requests on the second IP address.