ESP8266 Community Forum

- Sun Jan 18, 2015 8:27 am #7608 Hello Zeroday and everybody!

Has this bug #26 - net.server.listen does not closes after server closed - had any attention? https://github.com/nodemcu/nodemcu-firmware/issues/26

Is there anything I (or others) can do to help with resolving it?

It would be great to be able to run a web-server together with a dns-server for example, to provide a captive portal. However, currently we would need to reboot after each close() because otherwise (according to ThomasW here: http://www.esp8266.com/posting.php?mode=reply&f=24&t=1285#pr7590) we would get our old callbacks being used instead of any new ones?

- Sun Jan 18, 2015 8:48 am #7610

Hello Zeroday and everybody!

Has this bug #26 - net.server.listen does not closes after server closed - had any attention? https://github.com/nodemcu/nodemcu-firmware/issues/26

Is there anything I (or others) can do to help with resolving it?

It would be great to be able to run a web-server together with a dns-server for example, to provide a captive portal. However, currently we would need to reboot after each close() because otherwise (according to ThomasW here: http://www.esp8266.com/posting.php?mode=reply&f=24&t=1285#pr7590) we would get our old callbacks being used instead of any new ones?

You slightly misunderstood my post (wasn't clear enough maybe): After closing a server and creating a new one, the callbacks used are correct but the module still listens on the old port (and uses the callbacks from the newly created server)

Thomas

- Sun Jan 18, 2015 8:58 am #7613 Yes I did misunderstand you, sorry about that!

Thanks for the clarification - I've edited the issue to reflect this.