Sponsored Content
Special Forums IP Networking UDP Server/Daemon for receiving & acknowledging data Post 302367886 by allbread on Tuesday 3rd of November 2009 05:12:15 PM
Old 11-03-2009
Thanks - I have the Stevens, "Unix Network Programming Volume I" reference but it is out of date (2nd edition) so I've been looking for source material online.

Any advice as to the best way to implement... even general "direction" suggestions would be much appreciated.?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

3600 tcp/udp, trap-daemon, text relay-answer

3600 tcp/udp, trap-daemon, text relay-answer Does anyone know what this service is responsible for, or how significant it is? Thanks.....James (1 Reply)
Discussion started by: cassj
1 Replies

2. IP Networking

i want a UDP Client receiving program

Hi I want a UDP client receiving program. Here is the scenario. The client has to listen to the UDP server and has to acknowledge back on receiving data from the server. Can anyone help me out. regards, Nirmala (1 Reply)
Discussion started by: Nirmala
1 Replies

3. IP Networking

concurrent udp server

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

4. Programming

problem receiving data from TCP socket

Hi all, I'm writing a socket program which sends a structure from one machine to another. When I run my client first time it runs well, however after the first time I couldn't receive all the data inside the structure (it is like, half of the array is received and the other half is not set). I... (1 Reply)
Discussion started by: SaTYR
1 Replies

5. Programming

Print server via UDP

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

6. UNIX for Dummies Questions & Answers

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... (1 Reply)
Discussion started by: allbread
1 Replies

7. Shell Programming and Scripting

mail is not receiving from the server

Dear All, I am using CentOS release 5.5 (Final).I want to monitoring the system activity through mail.But the <code>mail -s "Subject" user1@domain.com</code> is not working from the server.could you help me the procedure to generate mail from the server. (2 Replies)
Discussion started by: kpoobathi
2 Replies

8. Programming

Sending and Receiving data between Client, HTTP Proxy, and Remote Server

I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply. I'm sending the host a HTTP 1.0 request that is formatted as such: GET / HTTP/1.0 Host: http://www.google.com Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies

9. Programming

Clients - Server ( UDP )

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
UDP(4)							   BSD Kernel Interfaces Manual 						    UDP(4)

NAME
udp -- Internet User Datagram Protocol SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> int socket(AF_INET, SOCK_DGRAM, 0); DESCRIPTION
UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family. UDP sockets are connectionless, and are normally used with the sendto(2) and recvfrom(2) calls, though the connect(2) call may also be used to fix the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used). UDP address formats are identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet address format. Note that the UDP port space is separate from the TCP port space (i.e., a UDP port may not be ``connected'' to a TCP port). In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved ``broadcast address''; this address is network interface dependent. Options at the IP transport level may be used with UDP; see ip(4). ERRORS
A socket operation may fail with one of the following errors returned: [EISCONN] when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the desti- nation address specified and the socket is already connected; [ENOTCONN] when trying to send a datagram, but no destination address is specified, and the socket has not been connected; [ENOBUFS] when the system runs out of memory for an internal data structure; [EADDRINUSE] when an attempt is made to create a socket with a port which has already been allocated; [EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists. MIB VARIABLES
The udp protocol implements a number of variables in the net.inet branch of the sysctl(3) MIB. UDPCTL_CHECKSUM (udp.checksum) Enable udp checksums (enabled by default). UDPCTL_MAXDGRAM (udp.maxdgram) Maximum outgoing UDP datagram size UDPCTL_RECVSPACE (udp.recvspace) Maximum space for incoming UDP datagrams udp.log_in_vain For all udp datagrams, to ports on which there is no socket listening, log the connection attempt (disabled by default). udp.blackhole When a datagram is received on a port where there is no socket listening, do not return an ICMP port unreachable message. (Disabled by default. See blackhole(4).) SEE ALSO
getsockopt(2), recv(2), send(2), socket(2), blackhole(4), inet(4), intro(4), ip(4) HISTORY
The udp protocol appeared in 4.2BSD. BSD
June 5, 1993 BSD
All times are GMT -4. The time now is 01:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy