Clayton Fiske wrote:
On Wed, Feb 05, 2003 at 11:00:24AM +1100, Carl Brewer wrote:
When I run some larger rsyncs from the outside
to the inside box I see this :
Read from remote host foo.bar: Connection timed out
rsync: connection unexpectedly closed (465051 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
rsync: connection unexpectedly closed (465051 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
I don't think this is an MTU issue, although I don't really know
enough about it to be sure. We're clamping the DSL link
(RP pppoe). The rsyncs are using ssh, and have worked
previously when we had a RH ip-drains firewall in place, but
no redirect (the firewall was also the rsync host). Now we've
got a proper seperate firewall I need to get it working again :)
FWIW, I have seen this several times, and each time it was in fact
an MTU issue. You may not have seen it when running rsync from the
firewall previously because it could have been using the pppoe
interface as its source and therefore adopting the smaller MTU from
the start.
Might I suggest my MSS Initiative as a good reading resource?
http://home.earthlink.net/~jaymzh666/mss/
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://home.earthlink.net/~jaymzh666/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
