UDP?
Opened this issue · 4 comments
Some comments/questions :
Does this have the ability to UDP listen, I cant seem to make that work ? Almost all protocols I could use this module for are UDP based, many require the ability to socket listen on multiple ports.
The command line arguments for access point credentials need to be quoted. The essid may contain any chartacters you like, same for password - so it is entirely possible for spaces to be in either.
It is a promising start, but the TCP listener should cought out the number of bytes for the payload it is about to output. The original firmware is pretty poor but the +IPD message has the correct idea.
Well, listen has 'tcp' hardcoded at the moment. It's on my TODO list.
As for credentials - it's a known limitation, since microrl has no support for escaping spaces right now. It's on my TODO list as well.
Listen command right now is "VERY" limited and broken, mostly since Espressif's API has no freaking way to actually stop listening on a port.
I dont mind if it does not stop. The problem I have with the current firmware 0018000902 is that it randomly stops listening to UDP sockets, also large volumes of short UDP packets cause the module to reset ! Bit crappy so far, I am desperate to make it work as a customer has soldered 200 of these down .... ho hum ....
PS In udplisten change "webserver_" names to something more general like "socket_" as listening should be generic, but I guess you know that :-) Looks like a good start, I prefer your command line but it closer to what I am used to. Remember the output needs to parsed by another CPU, +IPD,N,X: Bla was not a great syntax but it was at least easy to parse, be carful not to filter or reform anything coming from sockets, as this would break binary protocols :-)