10-15-2018
10 More Discussions You Might Find Interesting
1. Programming
Hello,
I actually try to make client-server program.
I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error :
I'm just using this simple code :
and I get the same error if I use :
If someone can help me,
Thanks (2 Replies)
Discussion started by: soshell
2 Replies
2. Shell Programming and Scripting
Hi, I am trying to write 2 simple scripts. One to echo a message into a socket, and the other to read from it. There are many tutorials about, but they're mostly about retrieving web pages through a socket. The code I'm trying is
echo qwerty > /dev/udp/localhost/22 (the first port I found that... (2 Replies)
Discussion started by: zeppelin147
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
4. Programming
Hi all,
On the server side, one socket is used for listening, the others are used for communicating with the client.
My question is: if i want to set option for socket, which socket should be set on?
If either can be set, what's the different?
Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies
5. HP-UX
Hi there,
are there any functions that can get the packets statistics on UNIX ?
thanks. (2 Replies)
Discussion started by: Frank2004
2 Replies
6. Programming
Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct...
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <string.h>
#include... (3 Replies)
Discussion started by: cyler
3 Replies
7. Programming
Dear Experts,
i am compiling my code in suse 4.1 which is compiling fine,
but at runtime it is showing me for socket programming error no 88
as i searched in errno.h it is telling me socket operation on non socket,
what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies
8. Programming
Hello
I try to send DHCP RENEW packets to the network and receive the responses. I broadcast the packet and I can see that it's successfully sent using Wireshark. But I have difficulties receiving the responses.I use packet sockets to catch the packets. I can see that there are responses to my... (0 Replies)
Discussion started by: xyzt
0 Replies
9. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
10. IP Networking
Hello,
Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h.
I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies
CLNP(4) BSD Kernel Interfaces Manual CLNP(4)
NAME
clnp -- Connectionless-Mode Network Protocol
SYNOPSIS
#include <sys/socket.h>
#include <netiso/iso.h>
#include <netiso/clnp.h>
int
socket(AF_ISO, SOCK_RAW, 0);
DESCRIPTION
CLNP is the connectionless-mode network protocol used by the connectionless-mode network service. This protocol is specified in ISO 8473.
It may be accessed through a ``raw socket'' for debugging purposes only. CLNP sockets are connectionless, and are normally used with the
sendto(2) and recvfrom(2) system calls, though the connect(2) call may also be used to fix the destination for future packets (in which case
the read(2) or recv(2) and write(2) or send(2) system calls may be used).
Outgoing packets automatically have a CLNP header prepended to them. Incoming packets received by the user contain the full CLNP header.
The following setsockopt(2) options apply to CLNP:
CLNPOPT_FLAGS Sets the flags which are passed to clnp when sending a datagram. Valid flags are:
CLNP_NO_SEG Do not allow segmentation
CLNP_NO_ER Suppress ER pdus
CLNP_NO_CKSUM Do not generate the CLNP checksum
CLNPOPT_OPTS Sets CLNP options. The options must be formatted exactly as specified by ISO 8473, section 7.5 ``Options Part''. Once an
option has been set, it will be sent on all packets until a different option is set.
CONGESTION EXPERIENCE BIT
Whenever a packet is transmitted, the globally unique quality of service option is added to the packet. The sequencing preferred bit and the
low transit delay bit are set in this option.
If a packet is forwarded containing the globally unique quality of service option, and the interface through which the packet will be trans-
mitted has a queue length greater than congest_threshold, then the congestion experienced bit is set in the quality of service option.
The threshold value stored in congest_threshold may be tuned.
When a packet is received with the globally unique quality of service option present, and the congestion experienced bit is set, then the
transport congestion control function is called.
DIAGNOSTICS
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 destina-
tion address specified and the socket is already connected;
[ENOTCONN] When trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;
[ENOBUFS] When the system runs out of memory for an internal data structure;
[EADDRNOTAVAIL] When an attempt is made to create a socket with a network address for which no network interface exists;
[EHOSTUNREACH] When trying to send a datagram, but no route to the destination address exists.
[EINVAL] When specifying unsupported options.
SEE ALSO
recv(2), send(2), intro(4), iso(4)
BUGS
Packets are sent with the type code of 0x1d (technically an invalid packet type) for lack of a better way to identify raw CLNP packets.
No more than MLEN bytes of options can be specified.
BSD
April 2, 1994 BSD