Hi!

I have to ADSL sites, one works and one does not. They belong to the same operator, Telia Sonera.

The setiathome home page, however, works from both sites!

The setiathome home page isn't on the Hurricane link,

Claggy

Hi!

I have to ADSL sites, one works and one does not. They belong to the same operator, Telia Sonera.

The setiathome home page, however, works from both sites!

The setiathome home page isn't on the Hurricane link,

Claggy

No, I guessed that :-)

My problems erupted just recently. The interesting thing is that my traces are almost identical, with the only difference that one of them stops att the gateway. Maybe all my packets reach the destination? It could be the return path that doesn't work.

/Peter

I hope this get corrected SOON. I have over 40 WUs that have a deadline of 9/1 so this is cutting it close.


I can not Reach any of the servers.
The problem started Aug 8th
Qwest/Centrylink is my ISP
USA Minnesota.

Pinging 208.68.240.13 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 208.68.240.16 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.16:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 208.68.240.18 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.18:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 208.68.240.20 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.68.240.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 1 ms <10 ms <10 ms gateway.maxx5.com [198.36.195.46]
2 213 ms 199 ms 50 ms mpls-dsl-gw53-245.mpls.qwest.net [207.225.140.245]
3 55 ms 36 ms 63 ms mpls-agw1.inet.qwest.net [75.168.229.161]
4 66 ms 33 ms 32 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
5 369 ms 583 ms 411 ms chi-bb1-link.telia.net [213.248.85.29]
6 112 ms 98 ms 112 ms sjo-bb1-link.telia.net [213.248.80.25]
7 679 ms 918 ms 635 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * * Request timed out.
9 * * * Request timed out.

Trace complete.


Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 208 hops:

1 <10 ms <10 ms <10 ms gateway.maxx5.com [198.36.195.46]
2 427 ms 504 ms 34 ms mpls-dsl-gw53-245.mpls.qwest.net [207.225.140.24
5]
3 58 ms 23 ms 63 ms mpls-agw1.inet.qwest.net [75.168.229.161]
4 995 ms 502 ms 529 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
5 233 ms 79 ms 80 ms chi-bb1-link.telia.net [213.248.85.29]
6 313 ms 127 ms 301 ms sjo-bb1-link.telia.net [213.248.80.25]
7 288 ms 315 ms 126 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

Trace complete.

Hello
I have been unable to upload results since August 22, I have +1k units to upload.

1. Are you able to reach ANY of the upload, download, or scheduling servers?
-NO
2. When did you start having this problem?
August 22:nd
3. What is your ISP?
TeliaSonera
4. What is your geographic location?
Södertälje, Sweden

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
TimeOut on all IP

Skickar ping-signal till 208.68.240.13 med 32 byte data:
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.

Ping-statistik för 208.68.240.13:
Paket: Skickade = 4, Mottagna = 0, Förlorade = 4 (100 %)

Skickar ping-signal till 208.68.240.16 med 32 byte data:
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.

Ping-statistik för 208.68.240.16:
Paket: Skickade = 4, Mottagna = 0, Förlorade = 4 (100 %)

Skickar ping-signal till 208.68.240.18 med 32 byte data:
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.

Ping-statistik för 208.68.240.18:
Paket: Skickade = 4, Mottagna = 0, Förlorade = 4 (100 %)

Skickar ping-signal till 208.68.240.20 med 32 byte data:
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.

Ping-statistik för 208.68.240.20:
Paket: Skickade = 4, Mottagna = 0, Förlorade = 4 (100 %)

6. How about traceroutes of the above four addresses?
Fails

C:\Users\Kepan>pathping 208.68.240.13

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.13]
över högst 30 hopp:
0 I7-2600.PeLiMo [192.168.0.103]
1 192.168.0.1
2 s-b2-link.telia.net [80.91.248.199]
3 s-bb1-link.telia.net [213.248.66.5]
4 kbn-bb1-link.telia.net [213.248.65.25]
5 nyk-bb1-link.telia.net [213.248.64.22]
6 sjo-bb1-link.telia.net [80.91.252.153]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C

C:\Users\Kepan>pathping 208.68.240.16

Spårar väg till setiboincdata.ssl.berkeley.edu [208.68.240.16]
över högst 30 hopp:
0 I7-2600.PeLiMo [192.168.0.103]
1 192.168.0.1
2 s-b1-link.telia.net [80.91.247.49]
3 s-bb2-link.telia.net [80.91.246.150]
4 kbn-bb1-link.telia.net [213.155.130.53]
5 nyk-bb2-link.telia.net [80.91.249.29]
6 sjo-bb1-link.telia.net [213.248.80.1]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C
C:\Users\Kepan>pathping 208.68.240.18

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.18]
över högst 30 hopp:
0 I7-2600.PeLiMo [192.168.0.103]
1 192.168.0.1
2 s-b1-link.telia.net [80.91.247.49]
3 s-bb1-link.telia.net [80.91.249.70]
4 kbn-bb1-link.telia.net [80.91.248.45]
5 nyk-bb1-link.telia.net [213.248.64.22]
6 sjo-bb1-link.telia.net [213.155.130.131]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C
C:\Users\Kepan>pathping 208.68.240.20

Spårar väg till setiboinc.ssl.berkeley.edu [208.68.240.20]
över högst 30 hopp:
0 I7-2600.PeLiMo [192.168.0.103]
1 192.168.0.1
2 s-b1-link.telia.net [213.248.77.45]
3 s-bb2-link.telia.net [80.91.254.114]
4 kbn-bb1-link.telia.net [80.91.248.45]
5 nyk-bb2-link.telia.net [80.91.247.119]
6 sjo-bb1-link.telia.net [80.91.252.153]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C

If I look at setiathome.berkeley.edu there is no problem

C:\Users\Kepan>pathping setiathome.berkeley.edu

Spårar väg till setiathome.berkeley.edu [128.32.18.150]
över högst 30 hopp:
0 I7-2600.PeLiMo [192.168.0.103]
1 192.168.0.1
2 s-b1-link.telia.net [80.91.246.230]
3 level3-117311-s-b3.telia.net [213.248.78.110]
4 ae-2-7.bar1.Copenhagen2.Level3.net [4.69.140.202]
5 ae-0-10.bar1.Copenhagen1.Level3.net [4.69.137.153]
6 ae-7-7.ebr1.Dusseldorf1.Level3.net [4.69.142.170]
7 ae-46-46.ebr2.Frankfurt1.Level3.net [4.69.143.170]
8 ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]
9 ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13]
10 ae-47-47.ebr2.Paris1.Level3.net [4.69.143.142]
11 ae-42-42.ebr2.Washington1.Level3.net [4.69.137.54]
12 ae-3-3.ebr1.NewYork2.Level3.net [4.69.132.90]
13 ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]
14 ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
15 ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
16 ae-71-71.csw2.SanJose1.Level3.net [4.69.153.6]
17 ae-21-70.car1.SanJose1.Level3.net [4.69.152.67]
18 CENIC.car1.SanJose1.Level3.net [4.53.16.186]
19 dc-svl-core1--svl-isp1-10ge.cenic.net [137.164.47.133]
20 dc-svl-agg1--svl-core1-10ge.cenic.net [137.164.47.120]
21 dc-ucb--svl-agg1-10ge.cenic.net [137.164.50.19]
22 t1-3.inr-201-sut.Berkeley.EDU [128.32.0.65]
23 g5-1.inr-204-sut.Berkeley.EDU [128.32.255.105]
24 * * *
Statistik för 575 sekunder beräknas...
^C
7. Or nslookups of the above four addresses?

---

@ Brad corson

Same here :(

Everything is stalled...

Dead in the water...

SNAFU...

8/29/2011 4:25:36 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.191_3 finished
8/29/2011 4:25:37 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.233_2 finished
8/29/2011 4:25:38 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.191_3_0
8/29/2011 4:25:53 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.172_3 finished
8/29/2011 4:25:56 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.178_3 finished
8/29/2011 4:26:12 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.185_3_0: HTTP error
8/29/2011 4:26:12 AM | SETI@home | Backing off 18 min 37 sec on upload of 08mr11ai.22737.8411.5.10.185_3_0
8/29/2011 4:26:55 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.191_3_0: HTTP error
8/29/2011 4:26:55 AM | SETI@home | Backing off 13 min 0 sec on upload of 08mr11ai.22737.8411.5.10.191_3_0
8/29/2011 4:27:32 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.235_2 finished
8/29/2011 4:27:49 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.240_2 finished
8/29/2011 4:36:27 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 4:36:27 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 4:37:43 AM | SETI@home | Scheduler request failed: HTTP service unavailable
8/29/2011 5:12:11 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 5:12:11 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 5:13:28 AM | SETI@home | Scheduler request failed: HTTP service unavailable
8/29/2011 6:51:15 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.239_2_0
8/29/2011 6:51:15 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.184_3_0
8/29/2011 6:52:31 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.239_2_0: HTTP error
8/29/2011 6:52:31 AM | SETI@home | Backing off 35 min 30 sec on upload of 08mr11ai.22737.8411.5.10.239_2_0
8/29/2011 6:52:31 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.184_3_0: HTTP error
8/29/2011 6:52:31 AM | SETI@home | Backing off 39 min 1 sec on upload of 08mr11ai.22737.8411.5.10.184_3_0
8/29/2011 7:07:12 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 7:07:12 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 7:08:28 AM | SETI@home | Scheduler request failed: HTTP service unavailable
8/29/2011 8:19:31 AM | SETI@home | update requested by user
8/29/2011 8:19:32 AM | SETI@home | Sending scheduler request: Requested by user.
8/29/2011 8:19:32 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 8:19:33 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 8:19:33 AM | SETI@home | Project has no tasks available
8/29/2011 8:26:39 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 8:26:39 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 8:26:40 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 8:26:40 AM | SETI@home | Project has no tasks available
8/29/2011 8:47:58 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 8:47:58 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 8:48:02 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 8:48:02 AM | SETI@home | Project has no tasks available
8/29/2011 9:26:34 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 9:26:34 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 9:26:35 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 9:26:35 AM | SETI@home | Project has no tasks available
8/29/2011 9:32:51 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.239_2_0
8/29/2011 9:32:51 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.184_3_0
8/29/2011 9:32:58 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.239_2_0
8/29/2011 9:32:58 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.185_3_0
8/29/2011 9:33:00 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.184_3_0
8/29/2011 9:33:00 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.191_3_0
8/29/2011 9:33:01 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.185_3_0
8/29/2011 9:33:01 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.233_2_0
8/29/2011 9:33:02 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.191_3_0
8/29/2011 9:33:02 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.172_3_0
8/29/2011 9:33:03 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.233_2_0
8/29/2011 9:33:03 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.178_3_0
8/29/2011 9:33:04 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.172_3_0
8/29/2011 9:33:04 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.235_2_0
8/29/2011 9:33:05 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.178_3_0
8/29/2011 9:33:05 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.240_2_0
8/29/2011 9:33:06 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.235_2_0
8/29/2011 9:33:07 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.240_2_0
8/29/2011 9:33:11 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 9:33:11 AM | SETI@home | Reporting 9 completed tasks, requesting new tasks for CPU
8/29/2011 9:33:13 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 9:33:13 AM | SETI@home | Project has no tasks available

"Everything is stalled..." - your log shows exactly the opposite - your connection is OK most of the time.

These messages show that your connection is OK:
8/29/2011 9:33:13 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 9:33:13 AM | SETI@home | Project has no tasks available

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

8/29/2011 4:26:12 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.185_3_0: HTTP error
8/29/2011 4:26:12 AM | SETI@home | Backing off 18 min 37 sec on upload of 08mr11ai.22737.8411.5.10.185_3_0
8/29/2011 4:26:55 AM | SETI@home | Temporarily failed upload of 08mr11ai.22737.8411.5.10.191_3_0: HTTP error
8/29/2011 4:26:55 AM | SETI@home | Backing off 13 min 0 sec on upload of 08mr11ai.22737.8411.5.10.191_3_0
8/29/2011 4:27:32 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.235_2 finished
8/29/2011 4:27:49 AM | SETI@home | Computation for task 08mr11ai.22737.8411.5.10.240_2 finished
8/29/2011 4:36:27 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 4:36:27 AM | SETI@home | Requesting new tasks for CPU
8/29/2011 4:37:43 AM | SETI@home | Scheduler request failed: HTTP service unavailable

Those look like normal issues from the server being busy or such.

8/29/2011 9:33:05 AM | SETI@home | Started upload of 08mr11ai.22737.8411.5.10.240_2_0
8/29/2011 9:33:06 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.235_2_0
8/29/2011 9:33:07 AM | SETI@home | Finished upload of 08mr11ai.22737.8411.5.10.240_2_0
8/29/2011 9:33:11 AM | SETI@home | Sending scheduler request: To fetch work.
8/29/2011 9:33:11 AM | SETI@home | Reporting 9 completed tasks, requesting new tasks for CPU
8/29/2011 9:33:13 AM | SETI@home | Scheduler request completed: got 0 new tasks
8/29/2011 9:33:13 AM | SETI@home | Project has no tasks available

This clearly shows you connecting to the server, but no work was in the feeder when you asked.

The "connection problems" in this thread are really more about not being able to reach any of the servers at all. Such as when the requested tests in the OP are preformed.

From this initial data and some looking it seems there is an issue with a router. Making some users unable to connect due to a routing table getting trashed.

I'm not sure if anyone is looking at that currently. As it was stated they are more focused on trying to prevent data that super noisy from going out.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Still no problems at this place, Zutphen, the Netherlands, ISP=KPNPLANET.
From my laptop:

29-8-2011 0:59:58 | SETI@home | Computation for task 12ap11af.5072.255760.16.10.124.vlar_1 finished
29-8-2011 1:00:00 | SETI@home | Started upload of 12ap11af.5072.255760.16.10.124.vlar_1_0
29-8-2011 1:00:03 | SETI@home | Finished upload of 12ap11af.5072.255760.16.10.124.vlar_1_0
29-8-2011 1:00:50 | SETI@home | Sending scheduler request: To fetch work.
29-8-2011 1:00:50 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU
29-8-2011 1:00:51 | SETI@home | Scheduler request completed: got 0 new tasks
29-8-2011 1:00:51 | SETI@home | Project has no tasks available
29-8-2011 19:13:12 | SETI@home | Sending scheduler request: To fetch work.
29-8-2011 19:13:12 | SETI@home | Requesting new tasks for CPU
29-8-2011 19:13:14 | SETI@home | Scheduler request completed: got 0 new tasks
29-8-2011 19:13:14 | SETI@home | Project has no tasks available

I never experienced such weird or random connection problems!
Atleast not for a long time, sometimes the first attempt fails, but the
second try does work?!
Shoudn't we check our 'own routers', first, then the router at the campus or
has the lab, one too?
And why, am I, not affected by this? Have a 'static' IP adress (IPv4 & IPv6).
And a SIEMENS GigaBit , 4 Port + WLAN, router. Which also handles my (Digital)
teevee (ADSL2+) and 2 phones (VoIP).

---

Forgive me and my generic-speak.

Everything stalled = no longer able to crunch data due to the inability to download (or even upload results on many machines) anything from this establishment.

As I've mentioned before, all my systems are in a lab which basically is set and forget. Before the RAID recently croaked, everything was running fine. I haven't touched anything in weeks. RAC steadily climbing to almost 70K RAC.

Since then...nada...

I see the Cricket graph moving upward, and a some work being split. However, the router issue remains.

I still get 100% packet loss to all four servers, and a traceroute dies just after 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69].

This almost has to be a corrupted routing table. I'm completely out of work, and some of the results waiting to upload are expiring.

---

And why, am I, not affected by this?

Most are not affected - if Most computers/IPs were affected then I think we can't see >90 Mbps usage of the line in the times when there were/are plenty of tasks to get:
http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw;view=octets

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I think there may be another way of looking at this. If you compare the daily results for ALL of S@H users over a period of time, http://stats.free-dc.org/stats.php?page=proj&proj=sah, it would appear that a significant percentage of machines are off line, perhaps 30%. So, while Cricket shows lots of traffic, my guess is that in reality the people who are connecting, are downloading and uploading faster and that the 30% who are, at present, off line, really only demonstrate that the pipe isn't big enough to not max out. Remember, there has been lots of downtime the last 10 days, lots of people saying they out of work and trying to rebuild a 6-10 day supply. It's like that Sam Adam's tap on Friday evening, not quite up to the demand and not, I think, indicative that the number of machines locked out is minimal.

---

Hi!

Looks like something happened.
I've been forced to use proxies since August 22nd, using 3 ISPs.

One works now direct, while other needs proxy (and I do not know yet for third)

My guess: as memory on router is low, after restart it fills up
routing tables. Lucky ones are in, others are out.
Thus, after any reboot of router situation is different, depending on
who managed to get in. Quite likely, we need one user to connect in
proper time to have route inside.

73
Iztok

Hi!

Looks like something happened.
I've been forced to use proxies since August 22nd, using 3 ISPs.

One works now direct, while other needs proxy (and I do not know yet for third)

My guess: as memory on router is low, after restart it fills up
routing tables. Lucky ones are in, others are out.
Thus, after any reboot of router situation is different, depending on
who managed to get in. Quite likely, we need one user to connect in
proper time to have route inside.

73
Iztok

I had thought about setting up a secure proxy on one of my phones at home for my work machines to connect through. However I decided to bring in my flash drive to work & sneaker net it to get all of the work turned in. Around 20 machines fit on a 4GB flash drive with room to spare.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I have been unable to upload results or download new work for over a week. Reading some of the posts here leaves me totally confused. Is SETI up for some people but down for others? Has management given any update on what's wrong and some sort of estimate on when things may get fixed? Is management communicating at all?

Can someone please summarize what, if anything, is known?

---

I have been unable to upload results or download new work for over a week. Reading some of the posts here leaves me totally confused. Is SETI up for some people but down for others? Has management given any update on what's wrong and some sort of estimate on when things may get fixed? Is management communicating at all?

Can someone please summarize what, if anything, is known?

Summary: One of the routers that S@H uses is going bonkers. Leaving groups of users unable to connect.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Well, after a week, I'm connecting from work, and got 2 new tasks. Won't know about home till I get off in 9.5 hours, but something must have been kicked.

---

Looks like someone kicked the router. I finally installed Hotspot Shield, and it let me upload the expiring workunits before they died.

About an hour ago I killed the proxy, and discovered I can not ping all four servers with only minor packet loss...first time in a week.

So perhaps when the rush is over I can actually get new work.

Bill

---

Hi everybody,

works now for me (apart from no tasks available).
Any chance to let us know what has been done/changed?

Anyway - many thanks from Switzerland!

(I hope that not just the group of users unable to connect is shifted)

Andy

---