ESP8266 Developer Zone The Official ESP8266 Forum 2016-08-15T20:19:45+08:00 https://bbs.espressif.com:443/feed.php?f=16&t=2339 2016-08-15T20:19:45+08:00 2016-08-15T20:19:45+08:00 https://bbs.espressif.com:443/viewtopic.php?t=2339&p=8499#p8499 <![CDATA[Re: UDP header]]> AT+CIPDINFO=1

Enables the IP and port for each incomming packet, just what we need.

Thanks.

Statistics: Posted by stokersoft — Mon Aug 15, 2016 8:19 pm

]]> 2016-07-11T10:21:01+08:00 2016-07-11T10:21:01+08:00 https://bbs.espressif.com:443/viewtopic.php?t=2339&p=7891#p7891 <![CDATA[Re: UDP header]]> Command “AT+CIPSTATUS” can get the information of remote IP and port.
Command "AT+CIPSEND=[<link ID>,]<length>[,<remote IP>,<remote port>]" can send UDP data to the target remote IP and port.

Statistics: Posted by Her Mary — Mon Jul 11, 2016 10:21 am

]]> 2016-06-23T17:19:03+08:00 2016-06-23T17:19:03+08:00 https://bbs.espressif.com:443/viewtopic.php?t=2339&p=7483#p7483 <![CDATA[UDP header]]>
I am new to this forum, i hope this is the right place to ask this question.

We use the ESP8266 on a controller board, and control it with AT commands over the uart.

It works as a server on a single UDP port and requests are send to the controller board from Android apps, we can have several apps communicating simultaneously. This works perfectly, and we are very satisfied.

However we have one problem, it seems we cannot fix. Right now each client/app appends its ipaddress and port to the request, we need to do that to be able to tell where to respond. However, if the device is behind a NAT router, this will not work. If we could see the udp header, and thus the ip address and port number for each request, then we could respond back to the correct ip address/port, and NAT will work.

So my question is basically, how do i, with AT commands, get the UDP header of an incoming request to determine the ip address and port to respond back to? I know that if i have only one device communicating, then it will automatically set the ip address and port, but with simultaneous devices communication, we cannot rely on that.

Thank you in advance. If its not possible, what is our next step? Should we build a custom firmware etc?

Regards Jens

Statistics: Posted by stokersoft — Thu Jun 23, 2016 5:19 pm

]]>