HE connection problems thread

Message boards : Number crunching : HE connection problems thread
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 14 · 15 · 16 · 17 · 18 · 19 · 20 . . . 25 · Next

AuthorMessage
Phil ZL1PK

Send message
Joined: 5 Feb 00
Posts: 4
Credit: 9,103,236
RAC: 9
New Zealand
Message 1156747 - Posted: 28 Sep 2011, 3:45:05 UTC

I am not sure you need another one but still have no download/upload here.

1. Are you able to reach ANY of the upload, download, or scheduling servers? NO
2. When did you start having this problem? ABOUT 24th
3. What is your ISP? XTRA
4. What is your geographic location? NZ
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20? 100% PACKET LOSS
6. How about traceroutes of the above four addresses? TIMES OUT AT paix.he.net (198.32.176.20
7. Or nslookups of the above four addresses? SAME

Thanks
Phil
ID: 1156747 · Report as offensive
Rodrigo Lobos Aleuy

Send message
Joined: 2 Aug 99
Posts: 3
Credit: 4,658,018
RAC: 0
Chile
Message 1156809 - Posted: 28 Sep 2011, 12:15:58 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?
No

2. When did you start having this problem?
DOn't know, it is still not working, 28 Sep 08:51 AM, local time

3. What is your ISP?
GTD Internet (Chile)

4. What is your geographic location?
Santiago, Chile

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?

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),

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),


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),

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),


6. How about traceroutes of the above four addresses?


Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]over a maximum of 30 hops:
1 7 ms 2 ms 2 ms 192.168.1.1
2 28 ms 32 ms 31 ms 10.9.85.1
3 152 ms 151 ms 146 ms sblx12gw.gtdinternet.com [190.196.63.126]
4 137 ms 110 ms 89 ms cn1.ge1-0-1.sblx12.gtdinternet.com [190.196.125.54]
5 58 ms 65 ms 45 ms ci1.te1-2.v219.cn1.gtdinternet.com [190.196.125.29]
6 128 ms 144 ms 139 ms ci2.te1-1.ci1.gtdinternet.com [201.238.238.26]
7 144 ms 68 ms 55 ms ge13-0-0.santiago2.san.seabone.net [195.22.221.85]
8 181 ms 172 ms 180 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
9 255 ms 278 ms 301 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
10 155 ms 168 ms 181 ms 10gigabitethernet2-2.core1.ash1.he.net [206.223.115.37]
11 247 ms 255 ms 260 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 83 ms 105 ms 144 ms 10.9.85.1
3 42 ms 11 ms 33 ms sblx12gw.gtdinternet.com [190.196.63.126]
4 104 ms 120 ms 154 ms cn1.ge1-0-1.sblx12.gtdinternet.com [190.196.125.54]
5 11 ms 14 ms 9 ms ci1.te1-2.v219.cn1.gtdinternet.com [190.196.125.29]
6 22 ms 23 ms 21 ms ci2.te1-1.ci1.gtdinternet.com [201.238.238.26]
7 79 ms 89 ms 122 ms ge13-0-0.santiago2.san.seabone.net [195.22.221.85]
8 230 ms 156 ms 144 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
9 196 ms 174 ms 183 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
10 298 ms 309 ms 285 ms 10gigabitethernet2-2.core1.ash1.he.net [206.223.115.37]
11 206 ms 209 ms 211 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


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

1 2 ms 2 ms 1 ms 192.168.1.1
2 76 ms 58 ms 30 ms 10.9.85.1
3 26 ms 15 ms 8 ms sblx12gw.gtdinternet.com [190.196.63.126]
4 24 ms 14 ms 47 ms cn1.ge1-0-1.sblx12.gtdinternet.com [190.196.125.54]
5 159 ms 154 ms 166 ms ci1.te1-2.v219.cn1.gtdinternet.com [190.196.125.29]
6 94 ms 112 ms 153 ms ci2.te1-1.ci1.gtdinternet.com [201.238.238.26]
7 153 ms 150 ms 106 ms ge13-0-0.santiago2.san.seabone.net [195.22.221.85]
8 251 ms 286 ms 292 ms te4-4.ashburn2.ash.seabone.net [89.221.40.7]
9 271 ms 273 ms 249 ms te4-4.ashburn2.ash.seabone.net [89.221.40.7]
10 279 ms 215 ms 207 ms 10gigabitethernet2-2.core1.ash1.he.net [206.223.115.37]
11 363 ms 313 ms 305 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.



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

1 3 ms 3 ms 3 ms 192.168.1.1
2 83 ms 105 ms 144 ms 10.9.85.1
3 42 ms 11 ms 33 ms sblx12gw.gtdinternet.com [190.196.63.126]
4 104 ms 120 ms 154 ms cn1.ge1-0-1.sblx12.gtdinternet.com [190.196.125.54]
5 11 ms 14 ms 9 ms ci1.te1-2.v219.cn1.gtdinternet.com [190.196.125.29]
6 22 ms 23 ms 21 ms ci2.te1-1.ci1.gtdinternet.com [201.238.238.26]
7 79 ms 89 ms 122 ms ge13-0-0.santiago2.san.seabone.net [195.22.221.5]
8 230 ms 156 ms 144 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
9 196 ms 174 ms 183 ms te4-3.ashburn2.ash.seabone.net [89.221.40.13]
10 298 ms 309 ms 285 ms 10gigabitethernet2-2.core1.ash1.he.net [206.223.115.37]
11 206 ms 209 ms 211 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.





7. Or nslookups of the above four addresses?

Server: UnKnown
Address: 192.168.1.1
Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20

Server: UnKnown
Address: 192.168.1.1
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

Server: UnKnown
Address: 192.168.1.1
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18

Server: UnKnown
Address: 192.168.1.1
Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20



IMPORTANT!
I succesfully used the
http://www.checker.freeproxy.ru/checker/last_checked_proxies.php
to upload pending WU
ID: 1156809 · Report as offensive
Profile Mad Max
Volunteer tester
Avatar

Send message
Joined: 16 Mar 00
Posts: 475
Credit: 213,231,775
RAC: 407
United States
Message 1156848 - Posted: 28 Sep 2011, 15:06:32 UTC

What I find odd here in Orlando is that my home connection through Earthlink (Isp) uses Bright House hardware is connecting just fine (lots of uploaded WUs). But my dedicated fiber connection at my office through Bright House directly is not connecting. And I believe that all Bright House traffic is directed toward the Tampa area. I did do some pings on the addresses at the house and it came back with mostly replies and a few time outs here and there, and time ranges from the 100’s to very high 900’s. Have not done any traces yet at the house but here is the IP addresses from my office. So a path out there is working just not sure on what that path is yet. My guess is that I don’t think it is a Seti, Berkeley campus, Hurricane Electric problem.

raceRoute to 208.68.240.13 [boinc2.ssl.berkeley.edu]

Hop (ms) (ms) (ms) IP Address Host name
1 3 0 0 206.123.64.154 -
2 0 0 0 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 7 1 0 206.223.118.37 10gigabitethernet3-1.core1.dal1.he.net
4 35 26 26 72.52.92.253 10gigabitethernet1-2.core1.phx1.he.net
5 42 36 37 72.52.92.249 10gigabitethernet2-2.core1.lax1.he.net
6 47 49 49 72.52.92.21 10gigabitethernet1-3.core1.pao1.he.net
7 45 45 45 64.71.140.42 -
8 49 49 49 208.68.243.254 -
9 49 49 49 208.68.240.13 boinc2.ssl.berkeley.edu
Trace complete

TraceRoute to 208.68.240.16 [setiboincdata.ssl.berkeley.edu]

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.154 -
2 0 0 0 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 1 10 1 206.223.118.37 10gigabitethernet3-1.core1.dal1.he.net
4 27 27 26 72.52.92.253 10gigabitethernet1-2.core1.phx1.he.net
5 39 37 37 72.52.92.249 10gigabitethernet2-2.core1.lax1.he.net
6 45 45 45 72.52.92.21 10gigabitethernet1-3.core1.pao1.he.net
7 45 45 45 64.71.140.42 -
8 50 49 49 208.68.243.254 -
9 49 49 49 208.68.240.16 setiboincdata.ssl.berkeley.edu
Trace complete

TraceRoute to 208.68.240.18 [boinc2.ssl.berkeley.edu]

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.154 -
2 0 0 0 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 0 0 0 206.223.118.37 10gigabitethernet3-1.core1.dal1.he.net
4 28 27 26 72.52.92.253 10gigabitethernet1-2.core1.phx1.he.net
5 36 41 36 72.52.92.249 10gigabitethernet2-2.core1.lax1.he.net
6 45 45 45 72.52.92.21 10gigabitethernet1-3.core1.pao1.he.net
7 45 45 46 64.71.140.42 -
8 49 49 49 208.68.243.254 -
9 49 49 49 208.68.240.18 boinc2.ssl.berkeley.edu
Trace complete

TraceRoute to 208.68.240.20 [setiboinc.ssl.berkeley.edu]

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.154 -
2 0 0 0 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 1 9 1 206.223.118.37 10gigabitethernet3-1.core1.dal1.he.net
4 27 37 27 72.52.92.253 10gigabitethernet1-2.core1.phx1.he.net
5 46 36 38 72.52.92.249 10gigabitethernet2-2.core1.lax1.he.net
6 45 45 45 72.52.92.21 10gigabitethernet1-3.core1.pao1.he.net
7 46 45 45 64.71.140.42 -
8 49 49 49 208.68.243.254 -
9 49 49 49 208.68.240.20 setiboinc.ssl.berkeley.edu
Trace complete



IAS - Where Space Is Golden!
ID: 1156848 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 1156852 - Posted: 28 Sep 2011, 15:09:34 UTC - in response to Message 1156848.  

My guess is that I don’t think it is a Seti, Berkeley campus, Hurricane Electric problem.


I believe it has been established that the problem is originating in the offsite router at PAIX that handles the server traffic.


"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 1156852 · Report as offensive
Amauri
Volunteer tester

Send message
Joined: 18 May 08
Posts: 26
Credit: 1,107,140
RAC: 0
Brazil
Message 1156872 - Posted: 28 Sep 2011, 19:18:07 UTC

All traceroutes show that the traffic pass thru or stop at IP 64.71.140.42

64.71.140.42 Whois

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=64.71.140.42?showDetails=true&showARIN=true&ext=netref2
#

UC Berkeley HURRICANE-DC0244-741 (NET-64-71-140-40-1) 64.71.140.40 - 64.71.140.47
Hurricane Electric, Inc. HURRICANE-2 (NET-64-71-128-0-1) 64.71.128.0 - 64.71.191.255
American Registry for Internet Numbers NET64 (NET-64-0-0-0-0) 64.0.0.0 - 64.255.255.255

Hope this can help...
ID: 1156872 · Report as offensive
ruslynr

Send message
Joined: 22 May 99
Posts: 2
Credit: 1,495,947
RAC: 0
New Zealand
Message 1157019 - Posted: 29 Sep 2011, 10:21:38 UTC

Yes Malaria control, Milkyway & Einstein work fine
Last exchange with Seti was Sept 21st.
Event log reports that "Internet access OK - Project servers may be temporaraly down
Paradise.net.nz
New Zealand


29/9/2011 ~23:00 NZDST

tracert 208.68.240.16

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 1 ms <1 ms <1 ms 192.168.99.3
3 * * * Request timed out.
4 8 ms 10 ms 15 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
5 * * * Request timed out.
6 20 ms 19 ms 19 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
7 21 ms 20 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
8 20 ms 20 ms 19 ms 203.167.233.10
9 151 ms 151 ms 154 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.114]
10 177 ms 173 ms 159 ms i-0-5-1-1.paix-core01.bi.reach.com [202.84.143.62]
11 262 ms 726 ms 214 ms i-2-2.paix01.bi.reach.com [202.84.251.58]
12 168 ms 165 ms 170 ms paix.he.net [198.32.176.20]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * ^C




tracert 208.68.240.13

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 2 ms <1 ms <1 ms 192.168.99.3
3 * * * Request timed out.
4 10 ms 16 ms 11 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
5 * * * Request timed out.
6 20 ms 26 ms 23 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
7 19 ms 21 ms 22 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
8 21 ms 20 ms 19 ms 203.167.233.10
9 162 ms 151 ms 151 ms i-0-0-4-0.tlot-core01.bx.reach.com [202.84.142.118]
10 168 ms 169 ms 169 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.140.90]
11 173 ms 169 ms 168 ms i-2-2.paix01.bi.reach.com [202.84.251.58]
12 171 ms 198 ms 181 ms paix.he.net [198.32.176.20]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


tracert 208.68.240.20

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.99.3
3 * * * Request timed out.
4 61 ms 13 ms 12 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
5 * * * Request timed out.
6 19 ms 19 ms 19 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
7 25 ms 19 ms 19 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
8 21 ms 18 ms 21 ms 203.167.233.10
9 151 ms 151 ms 151 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.114]
10 158 ms 159 ms 159 ms i-0-5-1-1.paix-core01.bi.reach.com [202.84.143.62]
11 246 ms 157 ms 157 ms i-3-1.paix01.bi.reach.com [202.84.251.34]
12 172 ms 174 ms 168 ms paix.he.net [198.32.176.20]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * ^C


nslookup
Default Server: UnKnown


> server 203.96.152.4
Default Server: [203.96.152.4]
Address: 203.96.152.4

> 208.68.240.13
Server: [203.96.152.4]
Address: 203.96.152.4

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

>
> 208.68.240.16
Server: [203.96.152.4]
Address: 203.96.152.4

Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

>
> 208.68.240.18
Server: [203.96.152.4]
Address: 203.96.152.4

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18

>
> 208.68.240.20
Server: [203.96.152.4]
Address: 203.96.152.4

Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20
ID: 1157019 · Report as offensive
XLinux
Volunteer tester

Send message
Joined: 18 Oct 02
Posts: 1
Credit: 3,647,819
RAC: 0
Austria
Message 1157067 - Posted: 29 Sep 2011, 12:58:20 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?


Upload and download seem to be negativ. Scheduler?:
29-Sep-2011 14:02:34 [SETI@home] Fetching scheduler list
29-Sep-2011 14:02:37 [SETI@home] Master file download succeeded
29-Sep-2011 14:02:42 [SETI@home] Sending scheduler request: To report completed tasks.
29-Sep-2011 14:02:42 [SETI@home] Reporting 1 completed tasks, not requesting new tasks
29-Sep-2011 14:05:44 [SETI@home] Scheduler request failed: HTTP gateway timeout

Einstein@home and Milkyway@home do work. climateprediction.net seem to have problems too.


2. When did you start having this problem?


First failed upload at 21-Sep-2011 13:24:31 (+0200):
21-Sep-2011 13:24:31 [SETI@home] Temporarily failed upload of 13jl11ac.7740.15200.13.10.105_1_0: HTTP error

Last finished download at 19-Sep-2011 02:36:38 (+0200):
19-Sep-2011 02:36:38 [SETI@home] Finished download of 15jl11ab.9769.5384.10.10.81


3. What is your ISP?


Inode by UPC (Austria)


4. What is your geographic location?


Austria/Central Europe


5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?


--- 208.68.240.13 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99118ms
rtt min/avg/max/mdev = 184.296/185.960/226.078/4.835 ms

--- 208.68.240.16 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99068ms
rtt min/avg/max/mdev = 180.089/182.245/223.407/6.378 ms

--- 208.68.240.18 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99124ms
rtt min/avg/max/mdev = 180.087/181.599/204.819/2.873 ms

--- 208.68.240.20 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99038ms
rtt min/avg/max/mdev = 176.030/177.649/219.515/5.463 ms


6. How about traceroutes of the above four addresses?


tracepath 208.68.240.13
1: UnusMultorum.local (192.168.25.231) 0.068ms pmtu 1500
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.923ms
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.600ms
2: 10.255.147.1 (10.255.147.1) 5.339ms
3: at-vie-xion-pe01-vl-2057.upc.at (84.116.229.13) 102.470ms asymm 11
4: at-vie01a-rd1-vl-2050.aorta.net (84.116.228.193) 107.991ms asymm 11
5: nl-ams05a-rd2-xe-0-1-0.aorta.net (213.46.160.145) 104.559ms asymm 10
6: us-nyc01b-rd1-gi-4-0-0.aorta.net (84.116.130.30) 101.494ms asymm 9
7: us-nyc01b-ri1-ge-0-1-0.aorta.net (213.46.190.178) 103.930ms asymm 8
8: core1.nyc4.he.net (198.32.118.57) 104.699ms
9: 10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197) 176.824ms
10: 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 184.140ms
11: 64.71.140.42 (64.71.140.42) 174.966ms asymm 12
12: 64.71.140.42 (64.71.140.42) 178.089ms pmtu 1476
12: 208.68.243.254 (208.68.243.254) 179.884ms asymm 13
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
^C

tracepath 208.68.240.16
1: UnusMultorum.local (192.168.25.231) 0.060ms pmtu 1500
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.665ms
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.533ms
2: 10.255.147.1 (10.255.147.1) 5.275ms
3: at-vie-xion-pe02-vl-2058.upc.at (84.116.228.209) 100.496ms asymm 11
4: at-vie15a-rd1-vl-2051.aorta.net (84.116.229.1) 100.139ms asymm 11
5: uk-lon01b-rd1-xe-1-0-2.aorta.net (84.116.130.253) 100.173ms asymm 10
6: 84-116-130-141.aorta.net (84.116.130.141) 100.076ms asymm 9
7: us-nyc01b-ri1-xe-3-1-0.aorta.net (213.46.190.94) 99.660ms asymm 8
8: core1.nyc4.he.net (198.32.118.57) 99.700ms
9: 10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197) 172.379ms
10: 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 179.472ms
11: 64.71.140.42 (64.71.140.42) 173.803ms asymm 12
12: 64.71.140.42 (64.71.140.42) 173.869ms pmtu 1476
12: 208.68.243.254 (208.68.243.254) 191.570ms asymm 13
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
^C

tracepath 208.68.240.18
1: UnusMultorum.local (192.168.25.231) 0.060ms pmtu 1500
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.342ms
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.249ms
2: 10.255.147.1 (10.255.147.1) 5.569ms
3: at-vie-xion-pe02-vl-2058.upc.at (84.116.228.209) 101.239ms asymm 11
4: at-vie15a-rd1-vl-2051.aorta.net (84.116.229.1) 120.526ms asymm 11
5: uk-lon01b-rd1-xe-7-1-2.aorta.net (84.116.134.229) 112.920ms asymm 10
6: 84-116-130-149.aorta.net (84.116.130.149) 101.023ms asymm 9
7: us-nyc01b-ri1-ge-0-1-0.aorta.net (213.46.190.178) 99.569ms asymm 8
8: core1.nyc4.he.net (198.32.118.57) 101.688ms
9: 10gigabitethernet10-1.core1.sjc2.he.net (184.105.213.173) 177.479ms
10: 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 179.515ms
11: 64.71.140.42 (64.71.140.42) 174.115ms asymm 12
12: 64.71.140.42 (64.71.140.42) 190.791ms pmtu 1476
12: 208.68.243.254 (208.68.243.254) 178.073ms asymm 13
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
^C

tracepath 208.68.240.20
1: UnusMultorum.local (192.168.25.231) 0.063ms pmtu 1500
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.274ms
1: 81-223-28-101.sdsl-line.inode.at (81.223.28.101) 1.324ms
2: 10.255.147.1 (10.255.147.1) 5.346ms
3: at-vie-xion-pe01-vl-2057.upc.at (84.116.229.13) 101.863ms asymm 11
4: at-vie01a-rd1-vl-2050.aorta.net (84.116.228.193) 104.225ms asymm 11
5: nl-ams05a-rd2-xe-0-0-2.aorta.net (84.116.130.73) 101.649ms asymm 10
6: us-nyc01b-rd1-gi-2-0-0.aorta.net (84.116.130.26) 101.347ms asymm 9
7: us-nyc01b-ri1-xe-3-1-0.aorta.net (213.46.190.94) 103.683ms asymm 8
8: core1.nyc4.he.net (198.32.118.57) 102.314ms
9: 10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197) 171.337ms
10: 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 180.439ms
11: 64.71.140.42 (64.71.140.42) 175.158ms asymm 12
12: 64.71.140.42 (64.71.140.42) 174.903ms pmtu 1476
12: 208.68.243.254 (208.68.243.254) 179.482ms asymm 13
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
^C


7. Or nslookups of the above four addresses?


nslookup 208.68.240.13
Server: 192.168.16.9
Address: 192.168.16.9#53

Non-authoritative answer:
13.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu.

Authoritative answers can be found from:
208.in-addr.arpa nameserver = dill.arin.net.
208.in-addr.arpa nameserver = t.arin.net.
208.in-addr.arpa nameserver = u.arin.net.
208.in-addr.arpa nameserver = v.arin.net.
208.in-addr.arpa nameserver = w.arin.net.
208.in-addr.arpa nameserver = x.arin.net.
208.in-addr.arpa nameserver = y.arin.net.
208.in-addr.arpa nameserver = z.arin.net.
t.arin.net internet address = 199.253.249.63
u.arin.net internet address = 204.61.216.50
u.arin.net has AAAA address 2001:500:14:6050:ad::1
v.arin.net internet address = 63.243.194.2
v.arin.net has AAAA address 2001:5a0:10::2
w.arin.net internet address = 72.52.71.2
w.arin.net has AAAA address 2001:470:1a::2
x.arin.net internet address = 199.71.0.63
x.arin.net has AAAA address 2001:500:31::63
y.arin.net internet address = 192.42.93.32
z.arin.net internet address = 199.212.0.63
z.arin.net has AAAA address 2001:500:13::63
dill.arin.net internet address = 192.35.51.32

nslookup 208.68.240.16
Server: 192.168.16.9
Address: 192.168.16.9#53

Non-authoritative answer:
16.240.68.208.in-addr.arpa name = setiboincdata.ssl.berkeley.edu.

Authoritative answers can be found from:
208.in-addr.arpa nameserver = u.arin.net.
208.in-addr.arpa nameserver = v.arin.net.
208.in-addr.arpa nameserver = w.arin.net.
208.in-addr.arpa nameserver = x.arin.net.
208.in-addr.arpa nameserver = y.arin.net.
208.in-addr.arpa nameserver = z.arin.net.
208.in-addr.arpa nameserver = dill.arin.net.
208.in-addr.arpa nameserver = t.arin.net.
t.arin.net internet address = 199.253.249.63
u.arin.net internet address = 204.61.216.50
u.arin.net has AAAA address 2001:500:14:6050:ad::1
v.arin.net internet address = 63.243.194.2
v.arin.net has AAAA address 2001:5a0:10::2
w.arin.net internet address = 72.52.71.2
w.arin.net has AAAA address 2001:470:1a::2
x.arin.net internet address = 199.71.0.63
x.arin.net has AAAA address 2001:500:31::63
y.arin.net internet address = 192.42.93.32
z.arin.net internet address = 199.212.0.63
z.arin.net has AAAA address 2001:500:13::63
dill.arin.net internet address = 192.35.51.32

nslookup 208.68.240.18
Server: 192.168.16.9
Address: 192.168.16.9#53

Non-authoritative answer:
18.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu.

Authoritative answers can be found from:
208.in-addr.arpa nameserver = w.arin.net.
208.in-addr.arpa nameserver = x.arin.net.
208.in-addr.arpa nameserver = y.arin.net.
208.in-addr.arpa nameserver = z.arin.net.
208.in-addr.arpa nameserver = dill.arin.net.
208.in-addr.arpa nameserver = t.arin.net.
208.in-addr.arpa nameserver = u.arin.net.
208.in-addr.arpa nameserver = v.arin.net.
t.arin.net internet address = 199.253.249.63
u.arin.net internet address = 204.61.216.50
u.arin.net has AAAA address 2001:500:14:6050:ad::1
v.arin.net internet address = 63.243.194.2
v.arin.net has AAAA address 2001:5a0:10::2
w.arin.net internet address = 72.52.71.2
w.arin.net has AAAA address 2001:470:1a::2
x.arin.net internet address = 199.71.0.63
x.arin.net has AAAA address 2001:500:31::63
y.arin.net internet address = 192.42.93.32
z.arin.net internet address = 199.212.0.63
z.arin.net has AAAA address 2001:500:13::63
dill.arin.net internet address = 192.35.51.32

nslookup 208.68.240.20
Server: 192.168.16.9
Address: 192.168.16.9#53

Non-authoritative answer:
20.240.68.208.in-addr.arpa name = setiboinc.ssl.berkeley.edu.

Authoritative answers can be found from:
208.in-addr.arpa nameserver = y.arin.net.
208.in-addr.arpa nameserver = z.arin.net.
208.in-addr.arpa nameserver = dill.arin.net.
208.in-addr.arpa nameserver = t.arin.net.
208.in-addr.arpa nameserver = u.arin.net.
208.in-addr.arpa nameserver = v.arin.net.
208.in-addr.arpa nameserver = w.arin.net.
208.in-addr.arpa nameserver = x.arin.net.
t.arin.net internet address = 199.253.249.63
u.arin.net internet address = 204.61.216.50
u.arin.net has AAAA address 2001:500:14:6050:ad::1
v.arin.net internet address = 63.243.194.2
v.arin.net has AAAA address 2001:5a0:10::2
w.arin.net internet address = 72.52.71.2
w.arin.net has AAAA address 2001:470:1a::2
x.arin.net internet address = 199.71.0.63
x.arin.net has AAAA address 2001:500:31::63
y.arin.net internet address = 192.42.93.32
z.arin.net internet address = 199.212.0.63
z.arin.net has AAAA address 2001:500:13::63
dill.arin.net internet address = 192.35.51.32

ID: 1157067 · Report as offensive
Pascal Meeuws

Send message
Joined: 25 Nov 09
Posts: 5
Credit: 1,380,836
RAC: 0
Netherlands
Message 1157088 - Posted: 29 Sep 2011, 14:59:28 UTC

Well.. all communications with the seti@ahome servers are failing again.

Traceroutes are the same for all four given servers

5 20gigabitethernet1-3.core1.ams1.he.net (195.69.145.150) 20.433 ms 20.639 ms 23.824 ms
6 10gigabitethernet2-1.core1.par2.he.net (184.105.213.102) 30.768 ms 33.302 ms 30.985 ms
7 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 109.527 ms 110.573 ms 114.922 ms
8 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 184.362 ms 181.987 ms 179.034 ms
9 * * *
10 * * *

According to the BOINC log, it started at on 22 September 00:00:00 CET
22-Sep-2010 00:00:00 [---] Resuming network activity
22-Sep-2010 00:00:01 [SETI@home] Started upload of ap_06my10ad_B4_P1_00216_20100918_05743.wu_1_0
22-Sep-2010 00:00:04 [---] Project communication failed: attempting access to reference site

Regards,

Pascal
It's 100% certain. There is no intelligent life in this universe.
ID: 1157088 · Report as offensive
Profile Donald L. Johnson
Avatar

Send message
Joined: 5 Aug 02
Posts: 8240
Credit: 14,654,533
RAC: 20
United States
Message 1157139 - Posted: 29 Sep 2011, 17:23:51 UTC
Last modified: 29 Sep 2011, 17:26:38 UTC

Folks, the problem is KNOWN to be a flakey router (208.68.243.254) at the Hurricane Electric interconnect in Palo Alto, California. S@H staff is working with HE to get it either fixed or replaced, but until that happens, SOME folks' access to the S@H upload/download pipe will be blocked, and it may not always be the same ones.

There is a work-around - see the Proxy thread.
Donald
Infernal Optimist / Submariner, retired
ID: 1157139 · Report as offensive
Profile Gary Charpentier Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 25 Dec 00
Posts: 30608
Credit: 53,134,872
RAC: 32
United States
Message 1157145 - Posted: 29 Sep 2011, 17:44:22 UTC - in response to Message 1157139.  

Folks, the problem is KNOWN to be a flakey router (208.68.243.254) at the Hurricane Electric interconnect in Palo Alto, California. S@H staff is working with HE to get it either fixed or replaced, but until that happens, SOME folks' access to the S@H upload/download pipe will be blocked, and it may not always be the same ones.

There is a work-around - see the Proxy thread.

Almost correct. The router does not belong to either Hurricane Electric or to Seti. It belongs to a third party who has graciously donated its use to Seti and is also paying the rent to have that router in the PAIX co-location facility. I don't know if that box carries any traffic other than for Seti, but it could. This makes the politics of getting it fixed or replaced a bit interesting. As things stand now this third party is in control. I'm sure if someone stepped up to the plate and offered to purchase a enterprise class router and pay the monthly rent at PAIX the staff would be very happy.

Oh, the task of the router is to take HE traffic for Seti and re-route it onto Cal-Ren to head to a link to the Campus. There is another router on Campus that splits the traffic back so the SETI traffic goes up the 100mbs fiber to the SSL and Campus traffic goes into their net. This isn't something a home LAN router can do.

ID: 1157145 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1157158 - Posted: 29 Sep 2011, 18:04:11 UTC - in response to Message 1157145.  

Folks, the problem is KNOWN to be a flakey router (208.68.243.254) at the Hurricane Electric interconnect in Palo Alto, California. S@H staff is working with HE to get it either fixed or replaced, but until that happens, SOME folks' access to the S@H upload/download pipe will be blocked, and it may not always be the same ones.

There is a work-around - see the Proxy thread.

Almost correct. The router does not belong to either Hurricane Electric or to Seti. It belongs to a third party who has graciously donated its use to Seti and is also paying the rent to have that router in the PAIX co-location facility. I don't know if that box carries any traffic other than for Seti, but it could. This makes the politics of getting it fixed or replaced a bit interesting. As things stand now this third party is in control. I'm sure if someone stepped up to the plate and offered to purchase a enterprise class router and pay the monthly rent at PAIX the staff would be very happy.

Oh, the task of the router is to take HE traffic for Seti and re-route it onto Cal-Ren to head to a link to the Campus. There is another router on Campus that splits the traffic back so the SETI traffic goes up the 100mbs fiber to the SSL and Campus traffic goes into their net. This isn't something a home LAN router can do.

To add to what Gary said: Matt told us that the router at the Berkeley end of that complicated link is a Cisco 7600 series (MLK Day 2008) - that's at least five figures in anybody's currency. It actually lives at the top of the fiber link, in the J-rack in SETI's server closet (or did when the February 2008 photo album was taken).

We don't know exactly what model number the PAIX router is, but it'll have to be a compatible Cisco running IOS, and any replacement would probably be on the scale of the lab's 7600.
ID: 1157158 · Report as offensive
Profile Donald L. Johnson
Avatar

Send message
Joined: 5 Aug 02
Posts: 8240
Credit: 14,654,533
RAC: 20
United States
Message 1157216 - Posted: 29 Sep 2011, 20:26:56 UTC
Last modified: 29 Sep 2011, 20:32:03 UTC

Gary and Richard, thank you for the clarifications and additional information.
I knew there was more to it than that, I just wanted to get it posted so folks would know the problem is being worked, and maybe stop posting their huge traceroute and ping results.

Again, thanks for chiming in.
Donald
Infernal Optimist / Submariner, retired
ID: 1157216 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65709
Credit: 55,293,173
RAC: 49
United States
Message 1157332 - Posted: 30 Sep 2011, 2:58:13 UTC - in response to Message 1157158.  

Folks, the problem is KNOWN to be a flakey router (208.68.243.254) at the Hurricane Electric interconnect in Palo Alto, California. S@H staff is working with HE to get it either fixed or replaced, but until that happens, SOME folks' access to the S@H upload/download pipe will be blocked, and it may not always be the same ones.

There is a work-around - see the Proxy thread.

Almost correct. The router does not belong to either Hurricane Electric or to Seti. It belongs to a third party who has graciously donated its use to Seti and is also paying the rent to have that router in the PAIX co-location facility. I don't know if that box carries any traffic other than for Seti, but it could. This makes the politics of getting it fixed or replaced a bit interesting. As things stand now this third party is in control. I'm sure if someone stepped up to the plate and offered to purchase a enterprise class router and pay the monthly rent at PAIX the staff would be very happy.

Oh, the task of the router is to take HE traffic for Seti and re-route it onto Cal-Ren to head to a link to the Campus. There is another router on Campus that splits the traffic back so the SETI traffic goes up the 100mbs fiber to the SSL and Campus traffic goes into their net. This isn't something a home LAN router can do.

To add to what Gary said: Matt told us that the router at the Berkeley end of that complicated link is a Cisco 7600 series (MLK Day 2008) - that's at least five figures in anybody's currency. It actually lives at the top of the fiber link, in the J-rack in SETI's server closet (or did when the February 2008 photo album was taken).

We don't know exactly what model number the PAIX router is, but it'll have to be a compatible Cisco running IOS, and any replacement would probably be on the scale of the lab's 7600.

Yep, that is no home router, I did a search of Cisco 7600 series routers and depending on the model, the price varies, a lot.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 1157332 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1157354 - Posted: 30 Sep 2011, 4:15:30 UTC - in response to Message 1157332.  

Folks, the problem is KNOWN to be a flakey router (208.68.243.254) at the Hurricane Electric interconnect in Palo Alto, California. S@H staff is working with HE to get it either fixed or replaced, but until that happens, SOME folks' access to the S@H upload/download pipe will be blocked, and it may not always be the same ones.

There is a work-around - see the Proxy thread.

Almost correct. The router does not belong to either Hurricane Electric or to Seti. It belongs to a third party who has graciously donated its use to Seti and is also paying the rent to have that router in the PAIX co-location facility. I don't know if that box carries any traffic other than for Seti, but it could. This makes the politics of getting it fixed or replaced a bit interesting. As things stand now this third party is in control. I'm sure if someone stepped up to the plate and offered to purchase a enterprise class router and pay the monthly rent at PAIX the staff would be very happy.

Oh, the task of the router is to take HE traffic for Seti and re-route it onto Cal-Ren to head to a link to the Campus. There is another router on Campus that splits the traffic back so the SETI traffic goes up the 100mbs fiber to the SSL and Campus traffic goes into their net. This isn't something a home LAN router can do.

To add to what Gary said: Matt told us that the router at the Berkeley end of that complicated link is a Cisco 7600 series (MLK Day 2008) - that's at least five figures in anybody's currency. It actually lives at the top of the fiber link, in the J-rack in SETI's server closet (or did when the February 2008 photo album was taken).

We don't know exactly what model number the PAIX router is, but it'll have to be a compatible Cisco running IOS, and any replacement would probably be on the scale of the lab's 7600.

Yep, that is no home router, I did a search of Cisco 7600 series routers and depending on the model, the price varies, a lot.

Any of the 7600 or 4300 series would be massive overkill if all that is being moved is a single GB line to the science lab. At work I am using a Cisco 4503 with a 48 ports of 1gb and 12 ports of 10Gb for an entire test lab.
If it is a dedicated device for the HE line then it would probably be a Cisco 1900 or something similar.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1157354 · Report as offensive
Profile RRipley
Volunteer tester

Send message
Joined: 18 Apr 01
Posts: 880
Credit: 23,005,843
RAC: 0
Germany
Message 1157388 - Posted: 30 Sep 2011, 7:59:09 UTC
Last modified: 30 Sep 2011, 8:01:20 UTC

From today 30 Sep 2011 5:192 UTC all of my venues can talk to S@H again! Sent over 100 WUs this early morning from the last venue (Provider is British Telecom in Germany).
since 29-Jun-2004:
ID: 1157388 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1157390 - Posted: 30 Sep 2011, 8:25:14 UTC - in response to Message 1157354.  

To add to what Gary said: Matt told us that the router at the Berkeley end of that complicated link is a Cisco 7600 series (MLK Day 2008) - that's at least five figures in anybody's currency. It actually lives at the top of the fiber link, in the J-rack in SETI's server closet (or did when the February 2008 photo album was taken).

We don't know exactly what model number the PAIX router is, but it'll have to be a compatible Cisco running IOS, and any replacement would probably be on the scale of the lab's 7600.

Yep, that is no home router, I did a search of Cisco 7600 series routers and depending on the model, the price varies, a lot.

Any of the 7600 or 4300 series would be massive overkill if all that is being moved is a single GB line to the science lab. At work I am using a Cisco 4503 with a 48 ports of 1gb and 12 ports of 10Gb for an entire test lab.
If it is a dedicated device for the HE line then it would probably be a Cisco 1900 or something similar.

I'd be very surprised. Before the lab upgraded to the 7600 series, they were using a 2811 - and eventually found that it was restricting the bandwidth to 61 Mb/sec. It isn't the port speed which matters, it's the CPU power (yes, a CPU in a router) to handle the encryption/decryption for the VPN tunnel. See message 698445.

The same search led me to some data on the PAIX router - apparently it's a 7301 - message 700589.
ID: 1157390 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1157395 - Posted: 30 Sep 2011, 9:17:30 UTC

I'm getting some weird stuff from the router today:

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

1 <1 ms <1 ms <1 ms my.router [192.168.173.1]
2 18 ms 18 ms 19 ms esr9.manchester6.broadband.bt.net [217.47.158.140]
3 18 ms 19 ms 18 ms 217.47.158.125
4 19 ms 18 ms 18 ms 10gigabitethernet6-3.core1.ash1.he.net [213.1.69.18]
5 17 ms 18 ms 18 ms 10gigabitethernet6-3.core1.ash1.he.net [217.32.27.234]
6 19 ms 19 ms 18 ms 10gigabitethernet6-3.core1.ash1.he.net [217.32.27.54]
7 18 ms 18 ms 17 ms 10gigabitethernet6-3.core1.ash1.he.net [217.32.27.182]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 111 ms 114 ms 111 ms 10gigabitethernet6-3.core1.ash1.he.net [72.52.92.137]
13 192 ms 184 ms 190 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
14 * * * Request timed out.
15 215 ms 186 ms 191 ms 208.68.243.254
16 221 ms 221 ms 211 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

Five different IP addresses for the 6-3 router? That feels like problems within the global HE network, not just something limited to 'our' router.

In and among, I've had a few successful contacts with SETI (upload/report/new work/download) this morning, but most attempts have failed.
ID: 1157395 · Report as offensive
Highlander
Avatar

Send message
Joined: 5 Oct 99
Posts: 167
Credit: 37,987,668
RAC: 16
Germany
Message 1157397 - Posted: 30 Sep 2011, 9:33:06 UTC

According to Cricket-Graph, the link is completely down at the moment; and beside that, i wasn't able to connect the last few hours. k, in times like this no special problem at all, but tried a traceroute and it stopped right 2 hops still @ my ISP. Seems as the .13 .16 .18 .20 IPs are not routable at all (at the moment).
- Performance is not a simple linear function of the number of CPUs you throw at the problem. -
ID: 1157397 · Report as offensive
Profile Fred J. Verster
Volunteer tester
Avatar

Send message
Joined: 21 Apr 04
Posts: 3252
Credit: 31,903,643
RAC: 0
Netherlands
Message 1157407 - Posted: 30 Sep 2011, 11:01:11 UTC - in response to Message 1157397.  
Last modified: 30 Sep 2011, 11:03:58 UTC

I stopped checking and tracing routes, since 'nothing has come out of it' and the
problem apparently, still excist.

It (always) takes some time to get "through", but still works, I also do not
interveine by manually operating BOINC, because it is a BOINC task, to get this right.
But it is a mainly NetWork/MODEM-ROUTER(s) and ICT, problem!

I'm too lazy and busy, (do have a live, too) to "baby-sit" BOINC.
Only exception is "Bêta Testing/Tuning, OpenCL for MB and
AstroPulse.

ID: 1157407 · Report as offensive
Profile Fred J. Verster
Volunteer tester
Avatar

Send message
Joined: 21 Apr 04
Posts: 3252
Credit: 31,903,643
RAC: 0
Netherlands
Message 1157425 - Posted: 30 Sep 2011, 12:48:32 UTC - in response to Message 1157407.  
Last modified: 30 Sep 2011, 13:21:53 UTC

Last connection attempts from my LT (WLAN; b/g/n; 54Mbit/sec.)
29-9-2011 16:55:44 | SETI@home | Started upload of 14jl11aa.6496.127397.5.10.62_1_0
29-9-2011 16:55:49 | SETI@home | Finished upload of 14jl11aa.6496.127397.5.10.62_1_0
29-9-2011 16:55:50 | SETI@home | Started upload of 14jl11aa.6496.127397.5.10.65_1_0
29-9-2011 16:55:50 | SETI@home | Sending scheduler request: To report completed tasks.
29-9-2011 16:55:50 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU
29-9-2011 16:55:53 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 16:55:53 | SETI@home | Project has no tasks available
29-9-2011 16:55:54 | SETI@home | Finished upload of 14jl11aa.6496.127397.5.10.65_1_0
29-9-2011 17:00:56 | SETI@home | Sending scheduler request: To report completed tasks.
29-9-2011 17:00:56 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU
29-9-2011 17:00:59 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 17:00:59 | SETI@home | Project has no tasks available
29-9-2011 17:13:11 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 17:13:11 | SETI@home | Requesting new tasks for CPU
29-9-2011 17:13:13 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 17:41:34 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 17:41:34 | SETI@home | Requesting new tasks for CPU
29-9-2011 17:41:36 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 17:41:36 | SETI@home | Project has no tasks available
29-9-2011 18:39:13 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 18:39:13 | SETI@home | Requesting new tasks for CPU
29-9-2011 18:39:15 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 18:39:15 | SETI@home | Project has no tasks available
29-9-2011 19:38:53 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 19:38:53 | SETI@home | Requesting new tasks for CPU
29-9-2011 19:38:55 | SETI@home | Scheduler request completed: got 0 new tasks
29-9-2011 19:38:55 | SETI@home | Project has no tasks available [/b]
29-9-2011 22:53:37 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 22:53:37 | SETI@home | Requesting new tasks for CPU
29-9-2011 22:53:59 | SETI@home | Scheduler request failed: Couldn't connect to server
29-9-2011 22:54:15 | | Project communication failed: attempting access to reference site
29-9-2011 22:54:18 | | Internet access OK - project servers may be temporarily down.
29-9-2011 22:55:05 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 22:55:05 | SETI@home | Requesting new tasks for CPU
29-9-2011 22:55:28 | SETI@home | Scheduler request failed: Couldn't connect to server
29-9-2011 22:55:42 | | Project communication failed: attempting access to reference site
29-9-2011 22:55:43 | | Internet access OK - project servers may be temporarily down.
29-9-2011 22:58:40 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 22:58:40 | SETI@home | Requesting new tasks for CPU
29-9-2011 22:59:02 | SETI@home | Scheduler request failed: Couldn't connect to server
29-9-2011 22:59:18 | | Project communication failed: attempting access to reference site
29-9-2011 22:59:19 | | Internet access OK - project servers may be temporarily down.
29-9-2011 23:05:06 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 23:05:06 | SETI@home | Requesting new tasks for CPU
29-9-2011 23:05:28 | SETI@home | Scheduler request failed: Couldn't connect to server
29-9-2011 23:05:41 | | Project communication failed: attempting access to reference site
29-9-2011 23:05:43 | | Internet access OK - project servers may be temporarily down.
29-9-2011 23:19:12 | SETI@home | Sending scheduler request: To fetch work.
29-9-2011 23:19:12 | SETI@home | Requesting new tasks for CPU
29-9-2011 23:19:16 | SETI@home | Scheduler request completed: got 2 new tasks
29-9-2011 23:19:18 | SETI@home | Started download of 21jn11ac.8041.20113.5.10.2
29-9-2011 23:19:18 | SETI@home | Started download of 21jn11ac.8047.20113.6.10.54
29-9-2011 23:19:24 | SETI@home | Finished download of 21jn11ac.8041.20113.5.10.2
29-9-2011 23:19:24 | SETI@home | Finished download of 21jn11ac.8047.20113.6.10.54
[/b]

When no connection is made, f.i. Internet access OK - project servers may be temporarily down. It shows, every 4 -5 minutes, trying to connect again, should a similar or another 'back off' mechanism,
double the 'waiting-time', at each unsuccessful work-fetch, IMO!

BOINC 6.12.34; x86; OS is WIN XP x86 and NO Manual Intervention,
was made.
I'll check my other rigs and their behavior.
Maybe a "Completely
Difference Approach
" , regarding SETI@home (+Bêta?), is necessary!

Since Europe is already 'awake', when Berkeley still enjoys their sleep, etc. , so if
ASIA, then RUSIA, followed by EUROPE, Great Brittanny and the U.S.of America,
can ONLY be "reached, during a time-frame of 6 hours". (Or 'vice-versa')!

You already can set your NetWorkConnection in BOINCs preferences, or WEB-Based (Account) Settings, but doubt, maybe tuesday as exception, that anyone has or is using "Active Network Limitations", as a permanent NetWorkSetting, to only connect in your "Day Time", in your Country.

(Since 18 months, I've got a new MODEM/ROUTER, which also runs an 'embedded' version of *NIX and can not be accessed(SIEMENS Gigaset SX551, 4 port + WLAN(ADSL), also providing Digital Telly*(ADSL2+) and 2 Phone lines(VOIP)).
(I 'hacked', my 'old MODEM/ROUTER', to adjust the packet-size and UP- and Down-Load speed, which was available from, one of the thousands of Forums, involving improving a PC and it's NetWork Capabillities)!

*Set-Top Box, fed by the SX551 EtherNet Cabel, just like any PC.
This Digital Triple-Tuner, one to view, one to Record and ~400 RADIO stations, needs 2 x =>12Mbit, to function properly and that's not even Full HD!

The 3 biggest Cities, on the West-Coast, already have WLAN HotSpots/DiGiTenna(TV) and >100MBIT fiber, but a 1 Gbit connection, now costs, depending of you are a (Z.Z.P er) Self Employed 1 Man Bussiness a >1 Business, or just a 'consumer', about €300 to €650,00 a month!!!


My ISP (Planet Technologies; KPN-Planet) offers a +100Mbit DSL, so same UP--
and Down_Load speed, for €77,50, a month, higher speeds are geting very expensive and not needed for 'normal' WEB/Telly?Phone, servicess.
ID: 1157425 · Report as offensive
Previous · 1 . . . 14 · 15 · 16 · 17 · 18 · 19 · 20 . . . 25 · Next

Message boards : Number crunching : HE connection problems thread


 
©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.