Bram Schoenmakers wrote:
If you can write (and compress if short of disk space) the dump
locally and
try an scp to your remote host as Nikos is suggesting, that will narrow
down the problem a bit. Any other large file will do: doesn't have to be a
dump.
As I wrote in my initial mail:
======
* Downloading the very same big file over SCP causes problems too, below some
SCP debug output. The connection drops quickly after it gained a reasonable
download speed.
Sorry, didn't pick up the thread until late in the day. If this is the
case, gzip over bzip2 is not likely to be the answer, nor is any SSH
keepalive option (though they'd be easy to try *just in case*).
Other than Nikos' PMTU suggestions I don't have much to offer.
You could try another ethernet card if you have one to see if that
makes any difference;
or you can do some creative monitoring with tcpdump to see what
traffic is being sent (try to exclude the actual ssh transfer);
can you try the scp with *no* firewall in place; this is straw clutching.
Presumably *some* data does actually arrive at the other end?
--Alex
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
