09-02-2009
UDP is connectionless, so there's no way to tell whether it gets through except the normal response from the server. By connectionless, I mean that each UDP data packet is sent individually and separately, like tossed paper airplanes
There's no setup phase like TCP, you just send and it either works or not.
10 More Discussions You Might Find Interesting
1. IP Networking
Just like concurrent tcp server, anyone know how to design the concurrent udp server with the thread? it's best to give some basic examples,thanks (0 Replies)
Discussion started by: Frank2004
0 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
3. UNIX for Advanced & Expert Users
HI
I want to create a UDP concurrent server
can any one give the code for UDP concurrent server (8 Replies)
Discussion started by: chanikya
8 Replies
4. Programming
Hello,
I would like to ask you for a help. I need to program in C print server which is based on connectionless protocol UDP. The problem is that I am not experienced in programming network applications, I can help myself with some other answered questions on this forum about network apps in C,... (1 Reply)
Discussion started by: samciz
1 Replies
5. UNIX for Dummies Questions & Answers
So I am attempting to implement a UDP server on an older Solaris 9 box; the server will be handling packets at a rate of about 12/sec and will be constructing acknowledgment messages on the fly.
I've found snippets of sample code here and there on the net... should I be writing this from scratch... (1 Reply)
Discussion started by: allbread
1 Replies
6. Programming
Hi,
I have a situation where i need to communicate a linux client with a windows server, I am using a UDP socket communication channel. I am able to send packets from my linux clients to the windows server but unable to receive any data packet from the server. Do i need to make any setting in... (0 Replies)
Discussion started by: John20
0 Replies
7. Programming
I want to send packets through single socket() but using two different port numbers in UDP. Anybody give some idea on this.
Thanks in advance.:) (2 Replies)
Discussion started by: naresh046
2 Replies
8. IP Networking
Hifriends
I have a doubt .
how to create a multi-chat server using UDP which can run on MAC systems..
Thank u in advance (3 Replies)
Discussion started by: babbu25
3 Replies
9. Shell Programming and Scripting
We have open port UDP port 31011, how to verify if port were working or traffic were receive. (2 Replies)
Discussion started by: avtalan
2 Replies
10. Programming
Hello,
I have a question: I want to create a n client to one server connection. This is the client-server algorithm.
Enybody help to make the changes? (0 Replies)
Discussion started by: MaHmur
0 Replies
LEARN ABOUT SUNOS
in.echod
in.echod(1M) System Administration Commands in.echod(1M)
NAME
in.echod - UDP or TCP echo protocol service daemon
SYNOPSIS
in.echod
FMRI
svc:/internet/echo:default
DESCRIPTION
FMRI stands for Fault Management Resource Identifier. It is used to identify resources managed by the Fault Manager. See fmd(1M) and
smf(5).
The in.echod service provides the server-side of the echo protocol. This protocol is used for debugging and bandwidth measurement and is
available on both TCP and UDP transports, through port 7.
The in.echod service is an inetd(1M) smf(5) delegated service. The in.echod detects which transport is requested by examining the socket it
is passed by the inetd daemon.
TCP-based service
Once a connection is established, the in.echod echoes any data received from the client back to the client. The server echoes data
until the client program terminates the connection.
UDP-based service
The in.echod listens for UDP datagrams. When a datagram is received, the server creates a UDP datagram containing the data it received
and sends it to the client.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNW |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
inetd(1M), attributes(5), smf(5)
RFC 862
SunOS 5.10 23 Aug 2004 in.echod(1M)