Mesh TCP connection not working
Mesh TCP connection not working
Postby gailu » Tue Nov 17, 2015 7:09 pm
Hi Experts,
We have followed mesh example provided by espressif on GitHub but we are not able to make TCP connection to our server on internet either from Root node or from child node connected to root node. Though child nodes are successfully joining mesh.
Mesh status is showing MESH_ONLINE_AVAIL and espconn_mesh_connect()/espconn_mesh_sent() both returns 0 (i.e. no error) still no connection is established with server.
My question in this regard is related to a log printed by mesh library, Hope someone can explain the below prints from mesh library.
We observe following log when mesh_success callback is called
con_cb IP:115.29.202.58 rp = 8000, lp = 48470
I would like to know where this IP (115.29.202.58 ) is obtained/printed from? My router is assigning IP to root node in 192.168.0 subnet. To my surprise 115.29.202.58 is public IP of iot.espressif.cn (Checked with nslookup).
Question) I have not tried to contact iot.espressif.cn/115.29.202.58 anywhere in my code, why mesh library is printing this IP and for what purpose it is trying to contact iot.espressif.cn/115.29.202.58?
Question) Is it not possible to use mesh library without iot.espressif.cn/115.29.202.58? I mean does it have any dependency on iot.espressif.cn/115.29.202.58?
Best Regards
We have followed mesh example provided by espressif on GitHub but we are not able to make TCP connection to our server on internet either from Root node or from child node connected to root node. Though child nodes are successfully joining mesh.
Mesh status is showing MESH_ONLINE_AVAIL and espconn_mesh_connect()/espconn_mesh_sent() both returns 0 (i.e. no error) still no connection is established with server.
My question in this regard is related to a log printed by mesh library, Hope someone can explain the below prints from mesh library.
We observe following log when mesh_success callback is called
con_cb IP:115.29.202.58 rp = 8000, lp = 48470
I would like to know where this IP (115.29.202.58 ) is obtained/printed from? My router is assigning IP to root node in 192.168.0 subnet. To my surprise 115.29.202.58 is public IP of iot.espressif.cn (Checked with nslookup).
Question) I have not tried to contact iot.espressif.cn/115.29.202.58 anywhere in my code, why mesh library is printing this IP and for what purpose it is trying to contact iot.espressif.cn/115.29.202.58?
Question) Is it not possible to use mesh library without iot.espressif.cn/115.29.202.58? I mean does it have any dependency on iot.espressif.cn/115.29.202.58?
Best Regards
Re: Mesh TCP connection not working
Postby gailu » Fri Nov 20, 2015 2:12 am
Can Someone from Espressif at least confirm if libmesh.a library is only designed to work with espressif servers so that we decide not to waste further time on this?
Re: Mesh TCP connection not working
Postby ESP_Faye » Fri Nov 20, 2015 9:53 am
Hi,
Sorry that mesh can only work with Espressif Cloud now.
But your advice is very valuable, we will add this new feature to support user's server in the future.
Thanks for your interest in ESP8266 !
Sorry that mesh can only work with Espressif Cloud now.
But your advice is very valuable, we will add this new feature to support user's server in the future.
Thanks for your interest in ESP8266 !
Re: Mesh TCP connection not working
Postby ESP_Alen » Fri Mar 04, 2016 11:18 am
gailu wrote:Hi Experts,
We have followed mesh example provided by espressif on GitHub but we are not able to make TCP connection to our server on internet either from Root node or from child node connected to root node. Though child nodes are successfully joining mesh.
Mesh status is showing MESH_ONLINE_AVAIL and espconn_mesh_connect()/espconn_mesh_sent() both returns 0 (i.e. no error) still no connection is established with server.
My question in this regard is related to a log printed by mesh library, Hope someone can explain the below prints from mesh library.
We observe following log when mesh_success callback is called
con_cb IP:115.29.202.58 rp = 8000, lp = 48470
I would like to know where this IP (115.29.202.58 ) is obtained/printed from? My router is assigning IP to root node in 192.168.0 subnet. To my surprise 115.29.202.58 is public IP of iot.espressif.cn (Checked with nslookup).
Question) I have not tried to contact iot.espressif.cn/115.29.202.58 anywhere in my code, why mesh library is printing this IP and for what purpose it is trying to contact iot.espressif.cn/115.29.202.58?
Question) Is it not possible to use mesh library without iot.espressif.cn/115.29.202.58? I mean does it have any dependency on iot.espressif.cn/115.29.202.58?
Best Regards
Hi,Gailu,
Now, sep-mesh supports local server, you can use API(epsconn_mesh_server_init) to set your local mesh server for mesh nodes.
We have released the mesh demo on github, please clone the current code from github.
https://github.com/espressif/ESP8266_MESH_DEMO
we also released the document about mesh APIs, please get document from the following link.
https://github.com/espressif/ESP8266_ME ... r/document
I'm R&D of sep-mesh, any problem about mesh, please feel free to sent mail to me (xiaoyuezhen@espressif.com).
I'll reply you as soon as possible.
Who is online
Users browsing this forum: No registered users and 15 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.