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 survived reboot. Then it suddenly ceased and
I can't trigger it again.
Kernels was 2.2.13, 2.2.16 and 2.2.17 and the systems was
completely unrelated.
Kind of woodoo or what ...
devik
> Oh, this situation seems to continue: it sends a syn-ack and then the
> client replies with a reset. This goes on and on. I'm going to make
> the client disappear, and hope that this makes the number of these
> connections go away.
>
> Kernel is 2.2.13. That was "fresh" when the system was booted. Yes,
> that's over 14 months ago.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 07 2001 - 21:00:21 EST