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"?
Thanks!
Last edited by Scott; 03-01-2010 at 08:04 PM..
Reason: Added code tags
Hi. I would like to be able to deny IP address for too many failed login attemps (either from ssh, sftp, ftp, etc). The system I wish this to work on is an AIX 5.1 system. I'm new to AIX but I'm a linux user. There is a program for linux called fail2ban which reads from the log files and see if... (1 Reply)
Hi,
I have created the below ftp script to put files over to our capacity server, the check at the end works if ftp fails to run however if the script cannot login or the transfer itself failed there is no warnings.
Does anyone know the syntax to trap the erorr codes or to put a check within... (3 Replies)
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)
I wrote a very simple script to calculate the DB connection from an appserver and check the total netstat connection to a particular DB exceed 25 then it will send mail
netstat -a 2> /dev/null | awk '/.*ESTAB/{print $5}' | cut -d. -f1 | uniq -c | awk '{if ($1 > 25)print $2," exceed ",$1;}'
... (1 Reply)
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)
Hey all I'm having a big problem here. Someone is attempting an SSH to a destination host on which an account resides and locking the account. I'm trying to determine who is performing the SSH attempts from my host. For instance they're logged in as their standard account but then (I'm assuming)... (13 Replies)
Hello
netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server?
1366888371 data packet headers correctly predicted
1195906 connection requests
5227320 connection accepts
5992919... (6 Replies)
The purpose of this thread is for everyone to follow the same methodology so we can create a future table, for the benefit of all, that shows how many failed login attempts (hacking) per day per server (and per minute) are happening.
This is not a thread on writing scripts or creating... (10 Replies)
Discussion started by: Neo
10 Replies
LEARN ABOUT OSF1
slattach
slattach(8) System Manager's Manual slattach(8)NAME
slattach - Attaches a serial line to a network interface
SYNOPSIS
/usr/sbin/slattach [{+|-} {c|e|i}] ttyname [baudrate]
DESCRIPTION
The slattach command assigns a tty line to a network interface, allowing terminal devices to communicate across a network. The ttyname
argument is the name of any valid tty device in /dev. This can be either the full path name (for example, /dev/tty01) or the name in /dev
(for example, tty01). The optional baudrate argument is used to set the speed of the connection. The default speed is 9600 baud.
The tty line is attached to the first available network interface (sl0, sl1, already be configured with the local and remote addresses of
each end of the SLIP connection (see ifconfig(8)).
Only a person with superuser authority can attach a network interface.
To detach the interface, use the ifconfig interface_id down command after terminating the slattach process. interface_id is the name that
is shown by the netstat command.
FLAGS
Enables (+) or disables (- TCP header compression. Enables (+) or disables (- automatic TCP header compression. If enabled and the remote
system is using TCP header compression, TCP header compression is automatically enabled on the local system. If both local and remote sys-
tems have enabled this flag, TCP header compression is not used. One system must force the use of TCP header compression. Enables (+) or
disables (- ICMP traffic suppression. If enabled, ICMP traffic (like that generated by ping(8)) is not allowed to pass over the SLIP con-
nection.
When the system is booted, all flags are initially disabled. Once a flag is enabled, it remains enabled until the system is rebooted or
until another slattach command is issued with the flag disabled.
NOTES
The slattach command requires the Serial Line Internet Protocol (SLIP), which the kernel must support. If making a SLIP connection to
another Tru64 UNIX system, both systems must run slattach. If making a SLIP connection to a system not running the Tru64 UNIX operating
system, the other system must support the SLIP protocol.
EXAMPLES
To attach a tty device to a network interface, enter: /usr/sbin/slattach /dev/tty01 4800 This command attaches tty01 to a network interface
to be used by the Serial Line Internet Protocol (SLIP). The connection speed is 4800 baud.
To attach a tty device to a network interface at 19200 bits per second (bps), with TCP header compression enabled and ICMP traffic suppres-
sion disabled, enter: /usr/sbin/slattach +c -i /dev/tty01 19200
FILES
Specifies the command path Contains the slattach process ID
RELATED INFORMATION
Commands: netstat(1), ifconfig(8)
Specifications: SLIP is described in RFC1055. TCP header compression is described in RFC1144. delim off
slattach(8)