10 More Discussions You Might Find Interesting
1. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
2. Solaris
I'd like to use SPARC Solaris10 to 'wake up' an old PC on same LAN.
what is the simplest way of doing it? (preferably without installing new software)
thanks. (14 Replies)
Discussion started by: orange47
14 Replies
3. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
4. IP Networking
Hi!
I'm writing an application (using BSD sockets on a Linux host) which communicates over TCP/IP with an embedded device. This embedded device has an old and real slow integrated circuit (Epson S1S6000) which handles all of the TCP/IP communication for it.
Problem is, this circuit (S1S6000)... (7 Replies)
Discussion started by: olle
7 Replies
5. Shell Programming and Scripting
I have multiple processes running the same program on my linux machine. For each process I want to be able to use a unique (available) TCP port. I have thought of using netstat to check which ports are available for use however, the time-window between checking and selecting might expose some race... (1 Reply)
Discussion started by: timmylita
1 Replies
6. IP Networking
Hello,
I'm having an issue with TCP sockets.
When the TCP connection is terminated on one end, TCP packet with RST flag set is being sent to the sender. All the packets sent so far were carrying the DSCP 'AF21' set by me. But packet with RST flag is carrying DSCP '0'.
Is this expected or... (0 Replies)
Discussion started by: Solace
0 Replies
7. UNIX for Dummies Questions & Answers
Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies
8. Shell Programming and Scripting
can u tell me from where do i get
TCP/IP Source code plz. (2 Replies)
Discussion started by: pradeep83rawat
2 Replies
9. UNIX for Dummies Questions & Answers
hi,
i am using Sun Solaris 8 (Sparc). Currently there is a SNMP agent running on port 161.
How should I change it to port 8001?
which file to modify and restart is necessary?
pls teach me the information.
thanks (8 Replies)
Discussion started by: champion
8 Replies
10. IP Networking
I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message,
Exec format error cannot bind a name to the port.
As far as I know the port is not being used by another client.
How... (1 Reply)
Discussion started by: lopez
1 Replies
TCP(4) BSD Kernel Interfaces Manual TCP(4)
NAME
tcp -- Internet Transmission Control Protocol
SYNOPSIS
#include <sys/socket.h>
#include <netinet/in.h>
int
socket(AF_INET, SOCK_STREAM, 0);
DESCRIPTION
The TCP protocol provides reliable, flow-controlled, two-way transmission of data. It is a byte-stream protocol used to support the
SOCK_STREAM abstraction. TCP uses the standard Internet address format and, in addition, provides a per-host collection of ``port
addresses''. Thus, each address is composed of an Internet address specifying the host and network, with a specific TCP port on the host
identifying the peer entity.
Sockets utilizing the tcp protocol are either ``active'' or ``passive''. Active sockets initiate connections to passive sockets. By default
TCP sockets are created active; to create a passive socket the listen(2) system call must be used after binding the socket with the bind(2)
system call. Only passive sockets may use the accept(2) call to accept incoming connections. Only active sockets may use the connect(2)
call to initiate connections.
Passive sockets may ``underspecify'' their location to match incoming connection requests from multiple networks. This technique, termed
``wildcard addressing'', allows a single server to provide service to clients on multiple networks. To create a socket which listens on all
networks, the Internet address INADDR_ANY must be bound. The TCP port may still be specified at this time; if the port is not specified the
system will assign one. Once a connection has been established the socket's address is fixed by the peer entity's location. The address
assigned the socket is the address associated with the network interface through which packets are being transmitted and received. Normally
this address corresponds to the peer entity's network.
TCP supports one socket option which is set with setsockopt(2) and tested with getsockopt(2). Under most circumstances, TCP sends data when
it is presented; when outstanding data has not yet been acknowledged, it gathers small amounts of output to be sent in a single packet once
an acknowledgement is received. For a small number of clients, such as window systems that send a stream of mouse events which receive no
replies, this packetization may cause significant delays. Therefore, TCP provides a boolean option, TCP_NODELAY (from <netinet/tcp.h>, to
defeat this algorithm. The option level for the setsockopt call is the protocol number for TCP, available from getprotobyname(3).
Options at the IP transport level may be used with TCP; see ip(4). Incoming connection requests that are source-routed are noted, and the
reverse source route is used in responding.
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;
[ENOBUFS] when the system runs out of memory for an internal data structure;
[ETIMEDOUT] when a connection was dropped due to excessive retransmissions;
[ECONNRESET] when the remote peer forces the connection to be closed;
[ECONNREFUSED] when the remote peer actively refuses connection establishment (usually because no process is listening to the port);
[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.
SEE ALSO
getsockopt(2), socket(2), intro(4), inet(4), ip(4)
HISTORY
The tcp protocol stack appeared in 4.2BSD.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution