Alan Cox wrote:
>
> > Ever since 2.0.36pre, I've began seeing "Connection reset by peer"
> > errors when I would ssh in to my servers. It evetually got worse
> > to where when I first check my POP3 server, I get it.
> >
> > Can anyone enlighten me?
An important point I forgot to mention (DOH!)....I see this only when bouncing
off an internal router.
Linux Server1
208.225.71.1 eth0...internet
192.168.0.1 eth1
Linux Server2
208.225.71.2 eth0
192.168.0.2 eth1
route -host 208.225.71.1 gw 192.168.0.1
Workstation(s)
192.168.0.0 network
route default gw 192.168.0.2
In the above all workstation requests for 208.225.71.1 (server 1 eth0)
will be bounced off of server 2, since server 2 is their default route.
That is where I see the problem. If a workstation requests
208.225.71.2, all is well. If it requests 208.225.71.1, (and gets bounced)
depending on the services and client OS, initially it will error with
"Connection reset by peer". Subsequent 'bounces' will be fine, unless
the communications are ceased for a few minutes (10? 30?) it will again give
and initial "Connection reset by peer".
Linux 2.0 and 2.2:
SSH, SCP (2 in a row), and POP3 (qpopper).
Solaris 7 x86:
http (Netscape), telnet (SetSockOpt: invalid argument).
I'm sure there are other services I havent't list that it is a problem.
Under Linux Netscape is NOT a problem.
Yes I know idealy it can be set up so the router bounce is not needed.
But is there actually some underlying problem with the Linux code?
(forwarding, firewall, or ipmasq?) From syslog, qpopper's failures
look like this:
May 27 20:20:08 schizo in.qpopper[32335]: @zen-machine.psychosis.com: -ERR Too
few arguments for the auth command.
Could the initial packets data be getting it's head or tail cut off?
--
http://www.linuxrouter.org/ Linux Router Project
Over 750,000 people are now in jail for consensual 'crimes'. 2 million more
are now on parole or probation. 4 million more will be arrested this year.
Would someone please remind how 'free' America is again?
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
