Sponsored Content
Full Discussion: Create a TCP/IP Connection
Top Forums Shell Programming and Scripting Create a TCP/IP Connection Post 302194107 by era on Monday 12th of May 2008 08:35:09 AM
Old 05-12-2008
The perlipc manual page basically has the stuff you need, although you might need to read up on the background info if you don't understand it on the first read; it really assumes you are familiar with basic socket programming. It all seems quite mysterious until you learn to ignore most of the lingo (-: But try the very simplest examples there; they should suffice for your needs.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

TCP/IP Connection getting slower...

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower. What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies

2. UNIX for Dummies Questions & Answers

How to check the TCP/UDP port of a connection

Hi, Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in? Regards, Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies

3. UNIX for Advanced & Expert Users

about TCP connection

Hi Experts, need help about release or refresh TCP Connection: i have the sample like below : application log connection: 0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00 0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies

4. Programming

close existing tcp connection in C

Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies

5. Solaris

How to kill the TCP ESTABLISHED connection in netstat

Hello, Actually there are some bugs in application which does not close the TCP connection to other server though CORBA. We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies

6. UNIX for Dummies Questions & Answers

TCP failed connection attempts from netstat -s

Dear experts, I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers. How can I pin point what connection failed and what are the ports involved? Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"? ... (2 Replies)
Discussion started by: cache51
2 Replies

7. IP Networking

false tcp connection

Why this happens? How to solve this? $netstat -na |grep 9325 tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds. ... (1 Reply)
Discussion started by: johnbach
1 Replies

8. Solaris

many tcp connection in close-wait

Hi, I use solaris Unix . I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740 root@XX # netstat -an | grep CLOSE_WAIT | wc -l 285 root@XX # netstat -an | grep CLOSE_WAIT 10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies

9. Programming

TCP connection check

Hi. I am writing client - server application using TCP sockets. I need some very basic functionality, namely: how to check if another "participant" of the connection is still present? I want to handle situations, when client is gone, or server breaks down, etc. (25 Replies)
Discussion started by: Shang
25 Replies

10. UNIX for Dummies Questions & Answers

Tcp connection to Linux server fails

I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
IP(3)							     Library Functions Manual							     IP(3)

NAME
ip - TCP, UDP, IL network protocols over IP SYNOPSIS
bind -a #Itcp /net bind -a #Iudp /net bind -a #Iil /net /net/tcp/clone /net/tcp/n /net/tcp/n/data /net/tcp/n/ctl /net/tcp/n/local /net/tcp/n/remote /net/tcp/n/status /net/tcp/n/listen ... DESCRIPTION
The IP device provides the interface for several protocols that run over IP on an Ethernet. TCP and UDP provide the standard Internet pro- tocols for reliable stream and unreliable datagram communication. IL provides a reliable datagram service for communication between Plan 9 machines. IL is the protocol of choice for most Plan 9 services. Each of the protocols is served by the IP device, which represents each connection by a set of device files. The top level directory of each protocol contains a clone file and subdirectories numbered from zero to the number of connections configured for this protocol. Opening the clone file reserves a connection. The file descriptor returned from the open(2) will point to the control file, ctl, of the newly allocated connection. Reading the ctl file returns a text string representing the number of the connection. Connections may be used either to listen for incoming calls or to initiate calls to other machines. A connection is controlled by writing text strings to the associated ctl file. After a connection has been established data may be read from and written to the data file. For the datagram services, IL and UDP, a read of less than the length of a datagram will cause the entire datagram to be consumed. Each write to the data file will send a single datagram on the network. The TCP protocol provides a stream connection that does not preserve read/write boundaries. Prior to sending data, remote and local addresses must be set for the connection. For outgoing calls the local port number will be allo- cated randomly if none is set. Addresses are set by writing control messages to the ctl file of the connection. The connection is not established until the data file is opened. For IL and TCP the process will block until the remote host has acknowledged the connection. UDP opens always succeed. The following control messages are supported: connect ipaddress!port[!r] Set the remote IP address and port number for the connection. If the r flag is supplied and no local address has been specified the system will allocate a restricted port number (less than 1024) for the connection to allow communication with Unix machines' login and exec services. disconnect (UDP only) Clear the remote address of a UDP connection. announce X X is a decimal port number or Set the local port number to X and accept calls to X. If X is accept calls for any port that no process has explicitly announced. The local IP address cannot be set. Announce fails if the connection is already announced or connnected. bind X X is a decimal port number or Set the local port number to X. This exists to support library emulation of BSD sockets and is not otherwise used. backlog n (IL and TCP only) Set the maximum number of pending requests for a given service to n. By default n is set to five. If more than n connections are pending, further requests for a service will be rejected. Port numbers must be in the range 1 to 32767. If a local port has not been announced prior to a connect a local port number will be allo- cated automatically. Local ports are allocated from 5000 up. Several files report the status of a connection. The remote and local files contain the IP address and port number for the remote and local side of the connection. The status file contains protocol-dependent information to help debug network connections. A process may accept incoming connections by calling open on the listen file. The open will block until a new connection request arrives. Then open will return an open file descriptor which points to the control file of the newly accepted connection. This procedure will accept all calls for the given protocol. SEE ALSO
listen(8), dial(2), ndb(6) SOURCE
/sys/src/9/port/devip.c /sys/src/9/port/stil.c /sys/src/9/port/stip.c /sys/src/9/port/tcp*.c IP(3)
All times are GMT -4. The time now is 03:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy