-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate configuration and data ports #7
Comments
+1 The current setup could be problematic if the bytes meant to be relayed to serial accidentally form a |
I changed the config tcp port - fvpalha/ESP8266-transparent-bridge |
Thanks @fvpalha, I see your pull request and I'll try to test it as soon as I get new modules in sometime in the next week. This is great! |
This commit is full of different changes in addition to second TCP port. @fvpalha could you separate new feature from other changes? The current patch is hard to read read and understand but also can't be simply merged with upstream code. |
Now the data from the serial port and the configuration commands use the same port.
I think it is a good idea to separate this: i.e.
Telnet Port 23 fix for the AT commands.
And also possible for standard/warning/error output.
The os_sprintf data must recieved with an extra serial input at GPIO 2.
AT PORT set the port for the serial data (i.e 10001 as in the XPORT).
Then it would simpler to use also UDP , i.e.
AT PORT NR [TCP|UDP]
And also a client mode: The modul connects to a server or send UDP broadcasts.
The text was updated successfully, but these errors were encountered: