| Author |
Message |
|
|
|
I am also having problems with downloading workunits for SETI, in fact at this very moment. Sometimes triggering a retry helps, sometimes not.
Bernhard
(Mountain View, California) |
|
|
|
|
|
To those who have commented on packet loss....
Please keep an eye on the Cricket graphs.
AP work is not going out right now...nothing left to split. And AP work is a big bandwidth user.
If caches finally get filled to current limits and the bandwidth utilization starts to drop, please test again to see if bandwidth saturation is the sole culprit or if there is something else still causing packet loss.
Meow.
____________
******
"Ask not, what your kitty can do for you. Ask what you can do for your kitty."
As it is kitten, so shall it be done.
|
|
|
|
|
|
I can's believe, it works!!!
WU's for all my computers using a proxy, too.
The first WU's i get at 19.10.2011 22:51:38 CET. |
|
|
|
|
|
OK, folks......
Feathering of the Cricket graph is now occuring.
Something less than total bandwidth saturation.
Could you start to test packet loss and see if it has changed?
Meow.
____________
******
"Ask not, what your kitty can do for you. Ask what you can do for your kitty."
As it is kitten, so shall it be done.
|
|
|
|
|
Could you start to test packet loss and see if it has changed?
Meow.
No lost packets at all:
Ping 208.68.240.20 5/5000/56/1; Start time 10/21/11 15:26:38
ping 208.68.240.20 packet 1 round trip time = 236 ms. successful
ping 208.68.240.20 packet 2 round trip time = 224 ms. successful
ping 208.68.240.20 packet 3 round trip time = 231 ms. successful
ping 208.68.240.20 packet 4 round trip time = 225 ms. successful
ping 208.68.240.20 packet 5 round trip time = 222 ms. successful
5 packets sent; 5 packets received; 0% lost.
Round trip times (ms): Minimum: 222, Maximum: 236, Average: 227
End time 10/21/11 15:26:45
Ping 208.68.240.20 5/5000/56/1; Start time 10/21/11 15:26:48
ping 208.68.240.20 packet 1 round trip time = 224 ms. successful
ping 208.68.240.20 packet 2 round trip time = 225 ms. successful
ping 208.68.240.20 packet 3 round trip time = 223 ms. successful
ping 208.68.240.20 packet 4 round trip time = 227 ms. successful
ping 208.68.240.20 packet 5 round trip time = 223 ms. successful
5 packets sent; 5 packets received; 0% lost.
Round trip times (ms): Minimum: 223, Maximum: 227, Average: 224
End time 10/21/11 15:27:00
Ping 208.68.240.20 5/5000/56/1; Start time 10/21/11 15:27:01
ping 208.68.240.20 packet 1 round trip time = 260 ms. successful
ping 208.68.240.20 packet 2 round trip time = 225 ms. successful
ping 208.68.240.20 packet 3 round trip time = 257 ms. successful
ping 208.68.240.20 packet 4 round trip time = 236 ms. successful
ping 208.68.240.20 packet 5 round trip time = 234 ms. successful
5 packets sent; 5 packets received; 0% lost.
Round trip times (ms): Minimum: 225, Maximum: 260, Average: 242
End time 10/21/11 15:27:18
____________
|
|
|
|
|
|
Ping with less than 1% loss at .13 and .16 (0% at .18 and .20)
Download speed as high as I never had before :-)
All this with NO proxy hassle...
Thanks gentlemen for the effort and the great job done!
BR
Andy
____________
|
|
|
|
|
|
Only one instance of packet loss in 32 tests (4 trace routes and 4 pings to each of the 4 SAH addresses).
Also getting some insane speeds on uploads and downloads.
Things are looking good.
T.A. |
|
|
Jeff CobbVolunteer moderator Project administrator Project developer Project scientist Send message
Joined: 1 Mar 99 Posts: 108 Credit: 40,367 RAC: 0

|
|
Thanks for all of the confirmations that connectivity is looking good! We are also seeing zero packet loss from remote pings. In order to test this, we let astropulse run out of data in order to get bandwidth consumption below the saturation point. New data will be arriving in the astropulse queue in the next couple of hours.
____________
|
|
|
|
|
Thanks for all of the confirmations that connectivity is looking good! We are also seeing zero packet loss from remote pings. In order to test this, we let astropulse run out of data in order to get bandwidth consumption below the saturation point. New data will be arriving in the astropulse queue in the next couple of hours.
Thank you Jeff, I was getting nervous that I wouldn't get any new AP's for my weekend AP party :-)
Makes perfect sense to let the bandwidth hog AP run dry, for you to be able to test the connection.
I have never had any problems with the HE connection during all the time others have complained about no connection, but I'm happy it now seems to be fixed.
____________
/The grumpy old Swede.
"I'm so old, that 98% of all trees in the forest, are younger than I am" |
|
|
|
|
|
Pinged in a loop for 25 minutes approximately.
Ping statistics for 208.68.240.20:
Packets: Sent = 2546, Received = 2546, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 216ms, Maximum = 256ms, Average = 220ms
____________
|
|
|
|
|
Eric and I went to the PAIX today and quadrupled the memory in our router. The router stats indicate that there is now plenty of memory to spare. But we are still seeing evidence of packet loss from various points around the globe.
Is anyone seeing a difference? Thanks!
Thanks.
Yes I'm seeing that one machine that wasn't able to connect now is able to connect.
____________
|
|
|
|
|
|
Hi!
I have question about maybe this problem with traffic. From yesterday all my WU waiting in queue to send out - but all have 16,00 from (about) 24KB, and still trying to resend.
here is screenshot
Regards,
Robert |
|
|
|
|
|
Uploads should go through without problems, but downloads are a whole different issue- it's just the usual network congestion.
Until Seti can get more than 100Mb/s bandwidth, that's the way things will be; lots & lots of retries.
____________
Grant
Darwin NT.
|
|
|