On Fri, Dec 29, 2000 at 09:19:52AM +1000, Bob Hepple wrote:
> "Peter T. Breuer" wrote:
> >
> > Sounds like the ssh pipes/socketpairs problem. Are you running over
> > ssh? If so a solution is to recompile ssh.
> >
>
> No, plain ole' rsh. But I get the same result with ssh.
>
> Before I posted I noticed previous similar problems in this list (but
> not with FreeSwan, just plain ppp) some of which were replied with
> "should be fixed in version 1.x.x" or with no response at all - but
> nothing in the FAQ. I thought this must have been an old fixed problem,
> a misconfiguration or a versioning problem hence my post here ...
Because of the piplined nature of the rsync implementation and the
back-and-forth nature of the rsync protocol, rsync stresses many TCP
implementations. No one else has mentioned a problem with FreeSwan, but I
suspect a bug with it. You should at least run "netstat" on both ends and
let us know what the send and receive queues are on both sides of that TCP
connection. In the end it will probably take some intervention from the
FreeSwan implementers; if you can give them a test case that they can use
to reproduce it, it will probably help them.
- Dave Dykstra
