I'm continuing to have serious connection problems with
satellite ISP (starband) that I blame on the extra latency of the sat communications. I can download files
fine, but uploading is about a 50/50 dice roll. I also have my boxes sharing a dial up modem. I've run boinc
5.4.11 and the newer betas with the same result. I'm on W2K OS boxes, but linux (Suse 10.1 and betas) has the same result. I'm running Rosetta@home. I can upload over the dialup no problem, and then when the manager gets connected to download I can switch back the IP address on that box and finish very quickly using the sat modem, but establishing the connection and request via sat is usually met with all the wide variety of errors from 'can't write to hard disk' to
505, 504 or whatever you can think of errors. If I establish the request via dialup - no problem then as I say I can switch the downloading in the middle of the session to my sat IP and finish very quickly.

The *only* exception to this is when the downloaded Rosetta WU's contain a .txt file. Then the sat download barfs, and I can only finish by switching back that boxes IP to talk to the dialup modem settings!!

In other words, it will download all the .gz files very fast over the sat modem,
but for some reason it will halt on the .txt files and I can only finish by switching that boxes connection back to the dialup modem connection.
I use freeproxy to do that and share both sat and dialup modems with all boxes on my local lan.


How bizarre is that?

I hope this can help someone figure out what is broken
with the BOINC networking.

I can run folding@home all day long over sat modem without these problems.

/mike

---

I'm continuing to have serious connection problems with
satellite ISP (starband) that I blame on the extra latency of the sat communications. I can download files
fine, but uploading is about a 50/50 dice roll. I also have my boxes sharing a dial up modem. I've run boinc
5.4.11 and the newer betas with the same result.

How long latencies do you see?

I've had similar problems in the 4.something times when I couldn't do a trickle report (that's CPDN) for my life if I was using GPRS modem as connection device. Things went smooth if I used 3G. The round-trip time is quite long with GPRS (600+ milliseconds) while it's acceptable with 3G (150-200 milliseconds).
The error message was different though, it said something about server not replying which clearly indicated long latency problem.

---

Metod ...

I'm continuing to have serious connection problems with
satellite ISP (starband) that I blame on the extra latency of the sat communications. I can download files
fine, but uploading is about a 50/50 dice roll. I also have my boxes sharing a dial up modem. I've run boinc
5.4.11 and the newer betas with the same result.

How long latencies do you see?

I'll have to test with ping and then I'll let you know. It kind of has its
ups and downs and I don't know if it's the Starband ISP sat service or other
factors.


I've had similar problems in the 4.something times when I couldn't do a trickle report (that's CPDN) for my life if I was using GPRS modem as connection device. Things went smooth if I used 3G. The round-trip time is quite long with GPRS (600+ milliseconds) while it's acceptable with 3G (150-200 milliseconds).
The error message was different though, it said something about server not replying which clearly indicated long latency problem.

Yeah, I think it's strange that I can download large .gz files fine over the
sat connection but a very small .txt file won't download over sat, I have to
switch to dial up connection for the proxy to finish. I find that strange,
but I'm not a TCP/IP wiz either.

/mike

---