11-04-2009
UDP server on Solaris 9
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 or is there some kind of service (a couple people have mentioned inetd) that I should be basing this on?
Point me in the right direction... please?
Thanks!
9 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. Programming
Hi,
Am very new to socket programming.
When we use UDP sockets to communicate between two processess,
will both the client/server socket be able to send/recv ?
meaning can sendto()/ recvfrom() be used on both server and client?
It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 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
Hi,
My network dep. telles me that they have opened the FW but my application still can not get through to other server. If it was TCP I could simply test it myself with "telnet", but how can I check it when the connection is UDP?
Tnx (1 Reply)
Discussion started by: mehrdad68
1 Replies
6. IP Networking
Hello !
I seem to have the same problem as in https://www.unix.com/ip-networking/91203-inaddr_any-opposite.html#post302262417
But I can't find a solution.
I have a UDP server socket bound to 0.0.0.0. The server hosts the addresses IP1, IP2 and IP3. I get an incoming request to IP1. I use... (1 Reply)
Discussion started by: steinwej
1 Replies
7. 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
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. 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.chargend
in.chargend(1M) System Administration Commands in.chargend(1M)
NAME
in.chargend - UDP or TCP character generator service daemon
SYNOPSIS
in.chargend
FMRI
svc:/internet/chargen: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.chargend service provides the server-side of the character-generator protocol. This protocol is used for debugging and bandwidth
measurement and is available on both TCP and UDP transports, through port 19.
The in.chargend service is an inetd(1M) smf(5) delegated service. The in.chargend 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.chargend generates a stream of data. Any data received is discarded. The server generates data
until the client program terminates the connection. Note that the data flow is limited by TCP flow control mechanisms.
UDP-based service
The in.chargend listens for UDP datagrams. When a datagram is received, the server generates a UDP datagram in response containing a
random number of ASCII characters (ranging from 0 to 512 characters). Any received data is ignored.
The in.chargend data consists of a pattern of 72 character lines containing the printable, 7-bit ASCII characters. Each line is terminated
with a carriage return and a line feed character.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcnsu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
inetd(1M), attributes(5), smf(5)
RFC 864
SunOS 5.10 23 Aug 2004 in.chargend(1M)