07-19-2015 03:28 AM - edited 03-08-2019 01:01 AM
Unlike TCP connections, why can Telnet NOT be used to verify UDP connections?
Why does the below command fail to show as connected even if there is a connection?
C:\Users\ABC>telnet 10.0.0.1 169
Solved! Go to Solution.
07-19-2015 04:25 AM
Hi,
Telnet can't verify UDP connections simply because Telnet was only designed to use TCP as its underlying transport layer.
Take a read of the RFC 854, Telnet Protocol Specification that states:
A TELNET connection is a Transmission Control Protocol (TCP) connection used to transmit data with interspersed TELNET control information.
Regards
07-19-2015 04:27 AM
Perhaps there is something in your question that I am not understanding. But it seems straightforward to me that telnet was designed as a communications protocol using TCP as its transport layer. There is no provision in the protocol design for using UDP as the transport for telnet.
HTH
Rick
07-19-2015 04:25 AM
Hi,
Telnet can't verify UDP connections simply because Telnet was only designed to use TCP as its underlying transport layer.
Take a read of the RFC 854, Telnet Protocol Specification that states:
A TELNET connection is a Transmission Control Protocol (TCP) connection used to transmit data with interspersed TELNET control information.
Regards
07-19-2015 04:27 AM
Perhaps there is something in your question that I am not understanding. But it seems straightforward to me that telnet was designed as a communications protocol using TCP as its transport layer. There is no provision in the protocol design for using UDP as the transport for telnet.
HTH
Rick
07-19-2015 05:41 AM
You can use the tool Netcat (there are also Windows-versions available) to connect to UDP-servers. But a problem remains, the server needs some input that is understood. And that has to be simulated by you.
This input can also be generated by tools like Scapy, but that needs quite some learning to use it.
07-20-2015 06:11 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Also understand TCP and UDP are two different protocols with different rules of usage. The reason telnet often works with other non-telnet ports, is because TCP shares a common connection setup (the 3 way handshake). Beyond that, some other TCP protocols will take text commands, so if you know what they are, you can also interact with such non-telnet protocols using telnet.
UDP, though, does not have a common setup, if fact, the protocol doesn't support the concept of having a session. The latter, if needed, is provided by the application using UDP.
07-20-2015 09:05 AM
Thanks for the insight.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide