Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Red Hat 9.0, Windows XP, Windows 98, Windows 2000 pro
purpose doesn't really matter all to much tcp is much better than udp as far as a protocol goes but UDP does have it's purposes where nothing else would do. As far as basic functionality TCP is better because it has error checking built in where as UDP is simple best effort delivery. On transferring a file with UDP you may get it all you may not. You are going to get it all with TCP whatever is on the host computer is what you get everytime.
what Rain said, TCP is what you want for reliable connections, examples include HTTP, FTP, TELNET, SSH. When a computer sends data, the reciever sends back an ACK (acknowledge) and if the there is no ACK recieved after a period of time, the sender re-sends the data. In UDP its just send it and hope it gets there. UDP is used in DHCP, DNS (i think), RIP and other protocols that dont require a reliable connection.
And UDP is the default delivery mechanism for most streaming media
- less overhead involved and less likely to experience "stutter" when playing back as there's no hanging about waiting for acknowledgements
There's no "better" or "worser". TCP is connection oriented, used when you'd like to send data and be sure it was received (mail, ftp, www and many other uses). UDP is connection-less, when you don't want/don't need to know if the data was received (and you don't need/want retransmissions). It may be used for video, VoIP etc.
When you send VoIP, a loss of one piece is not a problem - people will be able to understand each other. The same with video. That's why UDP is used there.
Oh...Forgot one thing. UDP is faster. You don't need to connect. So when I want just to send short data, I prefer UDP.