On Fri, 5 Jan 2001, Rogier Wolff wrote:
>Date: Fri, 5 Jan 2001 01:08:49 +0100 (MET)
>From: Rogier Wolff <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Content-Type: text/plain; charset=US-ASCII
>Subject: Network oddity
>
>
>Hi all,
>
>I have a server,
Interesting,
yesterday I have TCP problems with my three independent systems.
They all acts as simple firewalls with MASQ. Yesterday they all
suddenly stopped responding to ssh TCP connections to IP on eth1
(internal net) but they continued to work on IP attached to eth0
and lo. The problem
Interesting,
yesterday I have TCP problems with my three independent systems.
They all acts as simple firewalls with MASQ. Yesterday they all
suddenly stopped responding to ssh TCP connections to IP on eth1
(internal net) but they continued to work on IP attached to eth0
and lo. The problem
On Fri, 5 Jan 2001, Rogier Wolff wrote:
Date: Fri, 5 Jan 2001 01:08:49 +0100 (MET)
From: Rogier Wolff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII
Subject: Network oddity
Hi all,
I have a server, and it reports ("netstat -a")
tcp
Hi all,
I have a server, and it reports ("netstat -a")
tcp0 0 server:sshclient:1022 SYN_RECV
This sounds normal right?
However there are 79 of these lines in the netstat output. Not normal!
A TCP connection is identified by the 12 bytes source IP, dest IP,
source port,
5 matches
Mail list logo
