04-19-2011
I am trying to set TCP_MD5SIG option. I am trying this on an application running on the Linux kernel 2.5.25 which has support for this option. When my application is configured via the console to set an MD5 password for a peer, it is set on the listen socket. This is as per the usage of this option on Linux.
But in another task, the same socket is polled continuously for incoming connection requests via select(), accept(). So, is it correct to do so?
10 More Discussions You Might Find Interesting
1. IP Networking
Hello there
The socket option IP_OPTIONS returns an integer value,
supposed to be the contents of the IP header.
Could you please help me out to interpret those values.
ThankYou. (1 Reply)
Discussion started by: hufs375
1 Replies
2. Programming
Hi there, a newbie as far as compiling c.
I have a problem, I've ported a fairly simple perl socket program over to c.
I compiled it as follows
cc simplesocket.c -lsocket -lnsl
compiles great, no errors.
When I launch it from the command line, it works great!!!!
However, if I... (5 Replies)
Discussion started by: googling2000
5 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I'm writing a kernel module and part of it involves controlling IPCs between processes. My problem is when a process tries to connect to a Unix domain socket, the only identifying information of the socket it supplies (that I can see, anyway) is the special pathname of the socket. From... (0 Replies)
Discussion started by: blank87
0 Replies
4. 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
5. 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
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. Solaris
Hi everyone,
Question for gurus:
Is there a way for us to determine the options used by a socket?
I basically want to know if SO_KEEPALIVE is enabled on a socket to know if the tcp_keepalive_abort_interval parameter will be used by that connection.
Was I clear enough? :confused:
... (0 Replies)
Discussion started by: plmachiavel
0 Replies
9. Red Hat
Is there a Linux tunable to reduce the amount of time a socket waits before considering the remote side dead?
Its the same senario when you try to telnet to a dead machine, telnet sits and waits for ~30seconds, before the socket timer expires and cancels the request. (5 Replies)
Discussion started by: mrmurdock
5 Replies
10. Shell Programming and Scripting
Hi,
bash-3.2$ uname -a
Linux mymac 2.6.18-409.el5 #1 SMP Fri Feb 12 06:37:28 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
bash-3.2$ telnet 10.12.228.40 13900
Trying 10.12.228.40...
telnet: connect to address 10.12.228.40: Connection refused
bash-3.2$ telnet 10.12.228.40 23900
Trying... (2 Replies)
Discussion started by: mohtashims
2 Replies
LISTEN(2) Linux Programmer's Manual LISTEN(2)
NAME
listen - listen for connections on a socket
SYNOPSIS
#include <sys/types.h> /* See NOTES */
#include <sys/socket.h>
int listen(int sockfd, int backlog);
DESCRIPTION
listen() marks the socket referred to by sockfd as a passive socket, that is, as a socket that will be used to accept incoming connection
requests using accept(2).
The sockfd argument is a file descriptor that refers to a socket of type SOCK_STREAM or SOCK_SEQPACKET.
The backlog argument defines the maximum length to which the queue of pending connections for sockfd may grow. If a connection request
arrives when the queue is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports
retransmission, the request may be ignored so that a later reattempt at connection succeeds.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EADDRINUSE
Another socket is already listening on the same port.
EBADF The argument sockfd is not a valid descriptor.
ENOTSOCK
The argument sockfd is not a socket.
EOPNOTSUPP
The socket is not of a type that supports the listen() operation.
CONFORMING TO
4.4BSD, POSIX.1-2001. The listen() function call first appeared in 4.2BSD.
NOTES
To accept connections, the following steps are performed:
1. A socket is created with socket(2).
2. The socket is bound to a local address using bind(2), so that other sockets may be connect(2)ed to it.
3. A willingness to accept incoming connections and a queue limit for incoming connections are specified with listen().
4. Connections are accepted with accept(2).
POSIX.1-2001 does not require the inclusion of <sys/types.h>, and this header file is not required on Linux. However, some historical
(BSD) implementations required this header file, and portable applications are probably wise to include it.
The behavior of the backlog argument on TCP sockets changed with Linux 2.2. Now it specifies the queue length for completely established
sockets waiting to be accepted, instead of the number of incomplete connection requests. The maximum length of the queue for incomplete
sockets can be set using /proc/sys/net/ipv4/tcp_max_syn_backlog. When syncookies are enabled there is no logical maximum length and this
setting is ignored. See tcp(7) for more information.
If the backlog argument is greater than the value in /proc/sys/net/core/somaxconn, then it is silently truncated to that value; the default
value in this file is 128. In kernels before 2.4.25, this limit was a hard coded value, SOMAXCONN, with the value 128.
EXAMPLE
See bind(2).
SEE ALSO
accept(2), bind(2), connect(2), socket(2), socket(7)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-11-20 LISTEN(2)