Message boards :
Number crunching :
HE connection problems thread
Message board moderation
Previous · 1 . . . 21 · 22 · 23 · 24 · 25 · Next
Author | Message |
---|---|
Terror Australis Send message Joined: 14 Feb 04 Posts: 1817 Credit: 262,693,308 RAC: 44 |
I can now connect direct for the first time in about 2 months. The direct connection seems to be as reliable and speedy as going through a proxy. However pings and trace routes still show up to 50% packet loss over the last couple of hops, mainly between 192.32.176.20 and 64.71.140.42 and between 64.71.140.42 and 208.68.243.254. This applies to all four SAH IP's This loss is consistant, 75% 0f all ping attempts show at least a 25% loss In other words, we're back to where we were in June. T.A. |
Belthazor Send message Joined: 6 Apr 00 Posts: 219 Credit: 10,373,795 RAC: 13 |
I've seen different results in just one minute - all packets might been lose and all next packets might been successfully reached S@H: Ping 208.68.240.20 5/5000/56/1; Start time 10/20/11 12:33:56 ping 208.68.240.20 packet 1 round trip time = 257 ms. successful ping 208.68.240.20 packet 2 failed, retcode = 11010 (Timed Out) ping 208.68.240.20 packet 3 failed, retcode = 11010 (Timed Out) ping 208.68.240.20 packet 4 failed, retcode = 11010 (Timed Out) ping 208.68.240.20 packet 5 failed, retcode = 11010 (Timed Out) 5 packets sent; 1 packets received; 80% lost. Round trip times (ms): Minimum: 257, Maximum: 257, Average: 257 End time 10/20/11 12:34:20 Ping 208.68.240.20 5/5000/56/1; Start time 10/20/11 12:34:31 ping 208.68.240.20 packet 1 round trip time = 269 ms. successful ping 208.68.240.20 packet 2 round trip time = 259 ms. successful ping 208.68.240.20 packet 3 round trip time = 315 ms. successful ping 208.68.240.20 packet 4 round trip time = 273 ms. successful ping 208.68.240.20 packet 5 round trip time = 258 ms. successful 5 packets sent; 5 packets received; 0% lost. Round trip times (ms): Minimum: 258, Maximum: 315, Average: 274 End time 10/20/11 12:34:39 Ping 208.68.240.20 5/5000/56/1; Start time 10/20/11 12:34:45 ping 208.68.240.20 packet 1 round trip time = 347 ms. successful ping 208.68.240.20 packet 2 failed, retcode = 11010 (Timed Out) ping 208.68.240.20 packet 3 round trip time = 259 ms. successful ping 208.68.240.20 packet 4 round trip time = 258 ms. successful ping 208.68.240.20 packet 5 round trip time = 258 ms. successful 5 packets sent; 4 packets received; 20% lost. Round trip times (ms): Minimum: 258, Maximum: 347, Average: 280 End time 10/20/11 12:34:56 Trace 208.68.240.20; Start time 10/20/11 12:29:55 Tracing route to 208.68.240.20 50 bytes from 208.68.240.20: time=258 ms Hop Avg Diff Address 1 1 1 192.168.1.1 my.router 2 10 9 91.76.160.1 ppp91-76-160-1.pppoe.mtu-net.ru 3 * * Timed out 4 12 2 212.188.1.113 a197-crs-1-be1-53.msk.stream-internet.net 5 57 46 195.34.59.49 m9-crs-1-be4.msk.stream-internet.net 6 71 -19 195.34.53.126 bor-crs-1-be1.spb.stream-internet.net 7 142 52 195.34.53.102 anc-cr01-be3.ff.stream-internet.net 8 115 8 80.81.192.172 20gigabitethernet4-3.core1.fra1.he.net 9 199 46 72.52.92.89 10gigabitethernet1-2.core1.par1.he.net 10 157 -38 184.105.213.90 10gigabitethernet1-1.core1.par2.he.net 11 159 38 184.105.213.93 10gigabitethernet7-1.core1.ash1.he.net 12 278 111 184.105.213.177 10gigabitethernet7-4.core1.pao1.he.net 13 222 -30 64.71.140.42 14 * * Timed out 15 281 14 208.68.240.20 setiboinc.ssl.berkeley.edu End time 10/20/11 12:30:41 host reached |
Bernd Noessler Send message Joined: 15 Nov 09 Posts: 99 Credit: 52,635,434 RAC: 0 |
I can ping the router and the seti servers. In both cases the packet loss is 18 %. |
RRipley Send message Joined: 18 Apr 01 Posts: 880 Credit: 23,005,843 RAC: 0 |
All my connection problems went away. Sometimes downloads must restart due to connection resets. since 29-Jun-2004: |
Rept-Tile Send message Joined: 18 Oct 03 Posts: 20 Credit: 28,144,831 RAC: 0 |
All my connection problems went away. Same here, in Russia. I wasn't able to download any WUs for almost about last month. Today all my hosts got the full workload. |
Mad Fritz Send message Joined: 20 Jul 01 Posts: 87 Credit: 11,334,904 RAC: 0 |
Me again :-) Ups are ok, but downloads aren't really working. Pings and traceroutes show lost packets (~25%) / sometimes connection time outs. |
Salvis Cerins Send message Joined: 12 Dec 05 Posts: 5 Credit: 2,675,954 RAC: 0 |
Never had any problems with S@H connectivity, except when there was DDoS attack. MPE nets via Baltcom IP transit in Latvia:
Lattelecom FTH connection in Latvia:
|
David S Send message Joined: 4 Oct 99 Posts: 18352 Credit: 27,761,924 RAC: 12 |
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. Well, that explains the down-spike on the Cricket graph. Having just read this, I haven't done any traceroutes yet, but I know two of my machines have made contact since you did this. FWIW, A: I wasn't having problems before; and B: on Tuesday I switched from AT&T dsl to AT&T U-Verse for my internet. (Although it's coming into the house on the same phone line, I set up a new account for the U-Verse, and I would assume it's running through a different router/server on their end.) David David Sitting on my butt while others boldly go, Waiting for a message from a small furry creature from Alpha Centauri. |
Paris Send message Joined: 20 May 99 Posts: 110 Credit: 1,012,250 RAC: 0 |
I have had to use a proxy since Oct 5 but now the fix seems to have worked for me - the proxy is no longer needed. Thanks guys. Plus SETI Classic = 21,082 WUs |
Wild6-NJ Send message Joined: 4 Aug 99 Posts: 43 Credit: 100,336,791 RAC: 140 |
After 3 weeks of needing a proxy, all is now well in NJ without one. [:o) |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Me again :-) Just remember that download issues are also caused right now by the bandwidth being saturated (see the Cricket graphs). But it does appear that packet loss may still be an issue. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
As others have started things seem to have returned to normal for my connects at work. Pings & hops look "normal" with varying amount of loss between 10-33%. Which might just be from the servers getting saturated. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Rept-Tile Send message Joined: 18 Oct 03 Posts: 20 Credit: 28,144,831 RAC: 0 |
Which might just be from the servers getting saturated. Yeah, I suppose we probably can face to some cascade effect on servers due to sudden load increasing. From all of us who were forced to idle last weeks. Let's see. |
Fred J. Verster Send message Joined: 21 Apr 04 Posts: 3252 Credit: 31,903,643 RAC: 0 |
I'm glad it's solved, that is the connection problems, so everyone can get work. Bandwidth will probably always show saturation, at some times. Keeping about a million host, 'satisfied', isn't easy since almost every regular poster on the Number Crunching Forum, has a doubled, tripled, or tenfolded, their RAC or output. ;^) While the MB WUs, have doubled their resolution, IIRC It's a MILESTONE of it's own. |
Brkovip Send message Joined: 18 May 99 Posts: 274 Credit: 144,414,367 RAC: 0 |
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. Jeff/Eric, I am finally able to get through without a proxy. That is great! |
Bernhard Kohlhaas Send message Joined: 24 May 99 Posts: 1 Credit: 163,930 RAC: 0 |
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) |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
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. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
CpointAce Send message Joined: 26 Nov 10 Posts: 3 Credit: 1,872,594 RAC: 38 |
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. |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
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. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Belthazor Send message Joined: 6 Apr 00 Posts: 219 Credit: 10,373,795 RAC: 13 |
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 |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.