Sponsored Content
Full Discussion: opening ports
Special Forums Cybersecurity opening ports Post 16660 by dryheat on Tuesday 5th of March 2002 05:02:27 PM
Old 03-05-2002
My app. is listening. I create the socket, do the bind, listen, select, then accept when the select passes to set up the connection. These are stream-type TCP sockets. The code works fine locally, if I have the client and server on the same Windows machine. I haven't compiled the client on the Linux box yet.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Opening files

I am very new to unix. I want to open a file and read one line in at a time. Can anybody help? (3 Replies)
Discussion started by: saarshad001
3 Replies

2. UNIX for Advanced & Expert Users

Opening CDE

I have installed JASS on one of my sun servers. I am now trying to open for CDE. For that I have done these steps: mv /etc/rc2.d/_S71rpc.JASS.* /etc/rc2.d/S71rpc mv /etc/rc2.d/_S99dtlogin.JASS* /etc/rc2.d/S99dtlogin but still no CDE. Any advice on this?? (3 Replies)
Discussion started by: encrypted
3 Replies

3. AIX

Opening ports

Hi guys, I need to open ports on my AIX machine. The only way I know is to use service name to disable or enable ports which are used by the services. I found in /etc/services that the ports are unidentified. Btw, I want to open port number 11576 and 11577. Need help on this one. Thanks! :) (1 Reply)
Discussion started by: raskita
1 Replies

4. UNIX for Dummies Questions & Answers

Opening TCP ports

I'm not sure if this is the right place for this post, but I'd be grateful if somebody could please help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i... (2 Replies)
Discussion started by: thehaapyappy
2 Replies

5. IP Networking

problem opening TCP ports

Please can somebody help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth0 -p tcp --sport 1982 -m state --state NEW,ESTABLISHED -j ACCEPT iptables... (5 Replies)
Discussion started by: thehaapyappy
5 Replies

6. Solaris

Please help with opening a port??

Hello all, I need assistance... I need to open a port # 36677 and have it remain open even after a power cycle. I thought all I needed to do was add it to /etc/services. That was not it... Can someone please tell me how to do this. Thank you. (6 Replies)
Discussion started by: komputersman
6 Replies

7. Solaris

SMC not opening

I am working with Solaris 9.In that I am trying to open SMC(Solaris Management Console) but when I am clicking it,nothing is opening. Can any1 tell me why it is not opening??:confused: (1 Reply)
Discussion started by: smartgupta
1 Replies

8. Cybersecurity

Opening ports 8015/8016 restricted to selected IP addresses

Hello there I'm using a vendor-supplied application on RHEL4 that includes a built-in Tcl webserver. The webserver is working but I cannot access it from any computer other than the host workstation. I suspect that the firewall is blocking ports 8015/8016. I have two questions: 1. How do... (1 Reply)
Discussion started by: craig3201
1 Replies

9. UNIX for Dummies Questions & Answers

Who are all opening my datasets,?

Hi, I need a command/script, who opened my dataset, consider a situation like, if a user has opened the dataset few days back then, that command/script should list his/her id. I don't want audit on my dataset, i need only list of users who are using my dataset. Thank you. (10 Replies)
Discussion started by: subbarao12
10 Replies
LISTEN(2)						      BSD System Calls Manual							 LISTEN(2)

NAME
listen -- listen for connections on a socket LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> int listen(int s, int backlog); DESCRIPTION
To accept connections, a socket is first created with socket(2), a willingness to accept incoming connections and a queue limit for incoming connections are specified with listen(), and then the connections are accepted with accept(2). The listen() system call applies only to sockets of type SOCK_STREAM or SOCK_SEQPACKET. The backlog argument defines the maximum length the queue of pending connections may grow to. The real maximum queue length will be 1.5 times more than the value specified in the backlog argument. A subsequent listen() system call on the listening socket allows the caller to change the maximum queue length using a new backlog argument. If a connection request arrives with the queue full the client may receive an error with an indication of ECONNREFUSED, or, in the case of TCP, the connection will be silently dropped. Current queue lengths of listening sockets can be queried using netstat(1) command. Note that before FreeBSD 4.5 and the introduction of the syncache, the backlog argument also determined the length of the incomplete connec- tion queue, which held TCP sockets in the process of completing TCP's 3-way handshake. These incomplete connections are now held entirely in the syncache, which is unaffected by queue lengths. Inflated backlog values to help handle denial of service attacks are no longer neces- sary. The sysctl(3) MIB variable kern.ipc.soacceptqueue specifies a hard limit on backlog; if a value greater than kern.ipc.soacceptqueue or less than zero is specified, backlog is silently forced to kern.ipc.soacceptqueue. INTERACTION WITH ACCEPT FILTERS
When accept filtering is used on a socket, a second queue will be used to hold sockets that have connected, but have not yet met their accept filtering criteria. Once the criteria has been met, these sockets will be moved over into the completed connection queue to be accept(2)ed. If this secondary queue is full and a new connection comes in, the oldest socket which has not yet met its accept filter criteria will be terminated. This secondary queue, like the primary listen queue, is sized according to the backlog argument. RETURN VALUES
The listen() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The listen() system call will fail if: [EBADF] The argument s is not a valid descriptor. [EDESTADDRREQ] The socket is not bound to a local address, and the protocol does not support listening on an unbound socket. [EINVAL] The socket is already connected, or in the process of being connected. [ENOTSOCK] The argument s is not a socket. [EOPNOTSUPP] The socket is not of a type that supports the operation listen(). SEE ALSO
netstat(1), accept(2), connect(2), socket(2), sysctl(3), sysctl(8), accept_filter(9) HISTORY
The listen() system call appeared in 4.2BSD. The ability to configure the maximum backlog at run-time, and to use a negative backlog to request the maximum allowable value, was introduced in FreeBSD 2.2. The kern.ipc.somaxconn sysctl(3) has been replaced with kern.ipc.soacceptqueue in FreeBSD 10.0 to prevent confusion about its actual functionality. The original sysctl(3) kern.ipc.somaxconn is still available but hidden from a sysctl(3) -a output so that existing applications and scripts continue to work. BSD
July 15, 2014 BSD
All times are GMT -4. The time now is 07:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy