ESP8266 Developer Zone

Re: incorrect espconn pointer in callbacks

2015-07-09T12:46:44+08:00

use remote_id and remote_port, that works, it's idiotic, but whatever...

Statistics: Posted by tve — Thu Jul 09, 2015 12:46 pm

Re: incorrect espconn pointer in callbacks

2015-07-09T12:35:34+08:00

I think we may also be able to place context in a field of struct espconn called "reverse". I am thinking that if this is set in the connection callback then it will be passed in to other callbacks in the future. However ... I won't swear to that. There is a hint that this might be what is happening ... but there is no solid confirmation ... that I know off ... at this time.

Statistics: Posted by kolban — Thu Jul 09, 2015 12:35 pm

Re: incorrect espconn pointer in callbacks

2015-06-15T10:25:23+08:00

Hi,

So sorry for the inconvenience.

Please refer to documentation "2C-ESP8266__SDK__Programming Guide" -> 8.Appendix -> 8.1 ESPCONN Programming -> 3. espconn callback

The pointer may be different in different callbacks, please use parameter remote_ip and remote_port instead.

Thanks for your interest in ESP8266 !

Statistics: Posted by ESP_Faye — Mon Jun 15, 2015 10:25 am

incorrect espconn pointer in callbacks

2015-06-14T14:45:17+08:00

For TCP connections the void *arg pointer passed to the espconn_reconnect_callback and the espconn_disconnect_callback functions has the value of the listening/accepting connection instead of the disconnected connection. This makes it difficult to find the connection that has been closed and release resources.

Statistics: Posted by tve — Sun Jun 14, 2015 2:45 pm