9 More Discussions You Might Find Interesting
1. AIX
Hi.
I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ?
Tks (2 Replies)
Discussion started by: stephnane
2 Replies
2. IP Networking
The following thread is closed: 133552-howto-linux-multihomed-dns-client (Sorry I am not allowed to post URLs)
Therefore I write this append in an own thread.
The HOWTO in the referenced thread helped me a lot and I only want to append how to make reverse lookup working for a local zone:
... (0 Replies)
Discussion started by: scheruga
0 Replies
3. UNIX for Advanced & Expert Users
Hey everyone. We're in the process of deploying a number of servers. They're HP DL360 G6's. OS is RHEL 5.4
They've got two on board NIC's, as well as an additional dual port network card, giving us a total of 4 NIC's. Eth0 and Eth2 are bonded together using the bonding module, and the resulting... (2 Replies)
Discussion started by: msarro
2 Replies
4. IP Networking
The Linux resolver queries all nameservers in the order they are listed in /etc/resolver.conf.
If a nameserver times out, it advances on to the following nameserver.
But, if a nameserver returns "not found" (NXDOMAIN) it stops.
This behaviour is problematic when you need to resolve names from... (0 Replies)
Discussion started by: colemar
0 Replies
5. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
6. IP Networking
Hello this is my first post at this forum.
Apologize for my lack of network understanding
but Im posting to learn.
I have a problem reaching default gateway 10.18.110.1
If I use my laptop I can ping 10.18.110.1 but with our red hat multihomed server the gateway does not respond to ping.
cat... (11 Replies)
Discussion started by: vettec3
11 Replies
7. HP-UX
As user root and with some users I can use ssh to connect to remote hosts. But with a specific user I can't use ssh client because:
$ ssh
OpenSSL version mismatch. Built against 90807f, you have 90703f
Is it a $PATH problem or what?
HP-UX version is 11.11. (2 Replies)
Discussion started by: untamed
2 Replies
8. IP Networking
I'm not sure it that's the right term for what I'm asking about, but it's the best I could come up with. Here is my situation...
I'm setting up a network using OpenVPN. The clients I'm setting up will need to be able to access their own DNS servers (to resolve internal names at their location)... (4 Replies)
Discussion started by: deckard
4 Replies
9. UNIX for Dummies Questions & Answers
How can I use ssh client with proxy support?
If possible: with proxy chain support. :) (2 Replies)
Discussion started by: zylwyz
2 Replies
LEARN ABOUT OPENDARWIN
tcp
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