Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010) |
![]() |
| log in |
Message boards : Technical News : Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010)
Previous · 1 . . . 3 · 4 · 5 · 6 · 7 · 8 · 9 . . . 15 · Next
| Author | Message |
|---|---|
|
@Ralf Houven | |
| ID: 972350 · | |
|
BarryAZ, | |
| ID: 972351 · | |
|
C:\WINDOWS\system32>pathping 208.68.240.16 boinc2.ssl.berkeley.edu | |
| ID: 972358 · | |
|
Her a pathping from germany Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18]
über maximal 30 Abschnitte:
0 XXX.XXX.XXX.XXX [xxx.xxx.xxx.xxx]
1 xxx.xxx.xxx.xxx
2 XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX]
3 xxx.xxx.xxx.xxx
4 XXX.XXX.XXX.XXX [xxx.xxx.xxx.xxx]
5 bbrt-hb-0-xe-0-1-0.ewe-ip-backbone.de [80.228.109.229]
6 bbrt.ams-0-10ge-6-0-0.ewe-ip-backbone.de [212.6.114.10]
7 ams-ix.he.net [195.69.145.150]
8 10gigabitethernet4-1.core1.nyc4.he.net [216.66.24.153]
9 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
10 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
11 64.71.140.42
12 208.68.243.254
13 boinc2.ssl.berkeley.edu [208.68.240.18]
Berechnung der Statistiken dauert ca. 325 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 XXX.XXX.XXX.XXX [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
1 0ms 1/ 100 = 1% 1/ 100 = 1% xxx.xxx.xxx.xxx
0/ 100 = 0% |
2 9ms 4/ 100 = 4% 4/ 100 = 4% XXX.XXX.XXX.XXX [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% xxx.xxx.xxx.xxx
1/ 100 = 1% |
4 9ms 3/ 100 = 3% 2/ 100 = 2% XXX.XXX.XXX.XXX [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
5 15ms 2/ 100 = 2% 1/ 100 = 1% bbrt-hb-0-xe-0-1-0.ewe-ip-backbone.de [80.228.109.229]
0/ 100 = 0% |
6 25ms 1/ 100 = 1% 0/ 100 = 0% bbrt.ams-0-10ge-6-0-0.ewe-ip-backbone.de [212.6.114.10]
0/ 100 = 0% |
7 --- 100/ 100 =100% 99/ 100 = 99% ams-ix.he.net [195.69.145.150]
0/ 100 = 0% |
8 110ms 1/ 100 = 1% 0/ 100 = 0% 10gigabitethernet4-1.core1.nyc4.he.net [216.66.24.153]
0/ 100 = 0% |
9 190ms 1/ 100 = 1% 0/ 100 = 0% 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
0/ 100 = 0% |
10 191ms 1/ 100 = 1% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
2/ 100 = 2% |
11 194ms 3/ 100 = 3% 0/ 100 = 0% 64.71.140.42
9/ 100 = 9% |
12 196ms 14/ 100 = 14% 2/ 100 = 2% 208.68.243.254
0/ 100 = 0% |
13 194ms 12/ 100 = 12% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.18]
Ablaufverfolgung beendet. Looks ok for me 'til hop 12 and 13. __W__ ____________ _______________________________________________________________________________ | |
| ID: 972359 · | |
|
From The Netherlands: | |
| ID: 972362 · | |
|
Because of the outages last year I made sure that my profile collected 6 days worth of WU to keep working when SETI is down.
C:\Documents and Settings\Seanie>pathping 208.68.240.16 boinc2.ssl.berkeley.edu
Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
0 sean-laptop [192.168.0.21]
1 ipcop.localdomain [192.168.0.1]
2 skyrouter [192.168.1.1]
3 cr1.wmmal.uk.easynet.net [87.87.253.189]
4 ip-87-87-147-1.easynet.co.uk [87.87.147.1]
5 te0-0-0-2.er11.thlon.ov.easynet.net [89.200.135.133]
6 linx.he.net [195.66.224.21]
7 10gigabitethernet2-3.core1.nyc4.he.net [72.52.92.77]
8 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25]
9 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
10 64.71.140.42
11 208.68.243.254
12 boinc2.ssl.berkeley.edu [208.68.240.13]
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 sean-laptop [192.168.0.21]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% ipcop.localdomain [192.168.0.1]
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% skyrouter [192.168.1.1]
0/ 100 = 0% |
3 37ms 0/ 100 = 0% 0/ 100 = 0% cr1.wmmal.uk.easynet.net [87.87.25
3.189]
0/ 100 = 0% |
4 35ms 81/ 100 = 81% 81/ 100 = 81% ip-87-87-147-1.easynet.co.uk [87.8
7.147.1]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% te0-0-0-2.er11.thlon.ov.easynet.ne
t [89.200.135.133]
0/ 100 = 0% |
6 36ms 0/ 100 = 0% 0/ 100 = 0% linx.he.net [195.66.224.21]
0/ 100 = 0% |
7 103ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet2-3.core1.nyc4.he
.net [72.52.92.77]
0/ 100 = 0% |
8 177ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-1.core1.sjc2.he
.net [72.52.92.25]
0/ 100 = 0% |
9 179ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he
.net [72.52.92.69]
0/ 100 = 0% |
10 186ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
8/ 100 = 8% |
11 185ms 9/ 100 = 9% 1/ 100 = 1% 208.68.243.254
0/ 100 = 0% |
12 184ms 8/ 100 = 8% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.24
0.13]
Trace complete.
____________ | |
| ID: 972363 · | |
|
From Russia: | |
| ID: 972364 · | |
|
Please insert the pathping results in [pre]text [/pre]tags. It will be better to read. __W__ ____________ _______________________________________________________________________________ | |
| ID: 972371 · | |
|
Ah. So this is where the network gurus are hanging out, is it? | |
| ID: 972387 · | |
|
results from spain | |
| ID: 972406 · | |
|
Simple failure - immediate backoff/retry: | |
| ID: 972407 · | |
Please insert the pathping results in also edit to connect remove the carige return, make the line continious... ____________ | |
| ID: 972408 · | |
|
From East of England - 40 miles from London. | |
| ID: 972413 · | |
|
Results from Houston area.
Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:
0 Mercury.myhome.westell.com [192.168.5.100]
1 192.168.5.1
2 dslrouter [192.168.1.1]
3 10.33.35.1
4 so-2-1-0-0.DFW01-CORE-RTR1.verizon-gni.net [130.81.36.128]
5 as0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.20.60]
6 0.ge-2-3-0.XL3.DFW7.ALTER.NET [152.63.1.18]
7 TenGigE0-6-2-0.GW4.DFW13.ALTER.NET [152.63.101.17]
8 teliasonera-gw.customer.alter.net [63.65.123.46]
9 las-bb1-link.telia.net [213.248.80.13]
10 sjo-bb1-link.telia.net [80.91.247.171]
11 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
12 64.71.140.42
13 208.68.243.254
14 boinc2.ssl.berkeley.edu [208.68.240.13]
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mercury.myhome.westell.com [192.168.5.100]
0/ 100 = 0%
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.5.1
0/ 100 = 0%
2 1ms 0/ 100 = 0% 0/ 100 = 0% dslrouter [192.168.1.1]
0/ 100 = 0%
3 30ms 1/ 100 = 1% 1/ 100 = 1% 10.33.35.1
0/ 100 = 0%
4 38ms 0/ 100 = 0% 0/ 100 = 0% so-2-1-0-0.DFW01-CORE-RTR1.verizon-gni.net [130.81.36.128]
0/ 100 = 0%
5 31ms 0/ 100 = 0% 0/ 100 = 0% as0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.20.60]
0/ 100 = 0%
6 31ms 1/ 100 = 1% 1/ 100 = 1% 0.ge-2-3-0.XL3.DFW7.ALTER.NET [152.63.1.18]
0/ 100 = 0%
7 31ms 0/ 100 = 0% 0/ 100 = 0% TenGigE0-6-2-0.GW4.DFW13.ALTER.NET [152.63.101.17]
0/ 100 = 0%
8 33ms 0/ 100 = 0% 0/ 100 = 0% teliasonera-gw.customer.alter.net [63.65.123.46]
0/ 100 = 0%
9 78ms 0/ 100 = 0% 0/ 100 = 0% las-bb1-link.telia.net [213.248.80.13]
0/ 100 = 0%
10 79ms 0/ 100 = 0% 0/ 100 = 0% sjo-bb1-link.telia.net [80.91.247.171]
0/ 100 = 0%
11 82ms 0/ 100 = 0% 0/ 100 = 0% hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
0/ 100 = 0%
12 81ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
8/ 100 = 8%
13 83ms 9/ 100 = 9% 1/ 100 = 1% 208.68.243.254
0/ 100 = 0%
14 83ms 8/ 100 = 8% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.13]
Trace complete.
____________ Boinc....Boinc....Boinc....Boinc.... | |
| ID: 972414 · | |
|
Results from New Haven Ct. | |
| ID: 972428 · | |
|
I recently had a problem with an Internet phone provider when calling a specific area code. All other calls were fine. The service rep was more candid than he should have been for sure, but there was an auxiliary provider that was causing the problem. They just did not like handling the traffic. I think Hurricane Electric (the ape rant common denominator), like the aux provider in my case, needs some consultation. | |
| ID: 972430 · | |
|
Here is an pingpath from Dortmund, Germany
Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18]über maximal 30 Abschnitte:
0 ***.***.***.***
1 ***.***.***.***
2 dor002ibr005-xdsl.versatel.de [62.214.64.175]
3 ge-02-01-v551-xdsl.dor002isp005.versatel.de [62.214.33.109]
4 10g-9-1.dor002isp006.versatel.de [62.214.110.133]
5 10g-8-1.fra020isp006.versatel.de [62.214.110.146]
6 de-cix.he.net [80.81.192.172]
7 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
8 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
9 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]
10 10gigabitethernet1-2.core1.chi1.he.net [72.52.92.102]
11 10gigabitethernet3-2.core1.sjc2.he.net [72.52.92.73]
12 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
13 64.71.140.42
14 208.68.243.254
15 boinc2.ssl.berkeley.edu [208.68.240.18]
Berechnung der Statistiken dauert ca. 375 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ***.***.***.***
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% ***.***.***.***
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% dor002ibr005-xdsl.versatel.de [62.214.64.175]
0/ 100 = 0% |
3 16ms 0/ 100 = 0% 0/ 100 = 0% ge-02-01-v551-xdsl.dor002isp005.versatel.de [62.214.33.109]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% 10g-9-1.dor002isp006.versatel.de [62.214.110.133]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% 10g-8-1.fra020isp006.versatel.de [62.214.110.146]
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% de-cix.he.net [80.81.192.172]
0/ 100 = 0% |
7 23ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
0/ 100 = 0% |
8 33ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-3.core1.lon1.he.net [72.52.92.33]
0/ 100 = 0% |
9 98ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92.241]
0/ 100 = 0% |
10 121ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet1-2.core1.chi1.he.net [72.52.92.102]
0/ 100 = 0% |
11 177ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.sjc2.he.net [72.52.92.73]
0/ 100 = 0% |
12 180ms 0/ 100 = 0% 0/ 100 = 0% 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
0/ 100 = 0% |
13 183ms 0/ 100 = 0% 0/ 100 = 0% 64.71.140.42
6/ 100 = 6% |
14 182ms 6/ 100 = 6% 0/ 100 = 0% 208.68.243.254
1/ 100 = 1% |
15 182ms 7/ 100 = 7% 0/ 100 = 0% boinc2.ssl.berkeley.edu [208.68.240.18]
Ablaufverfolgung beendet.
It seems to me that the problems start at 64.71.140.42. Mfg. McHunter ____________ | |
| ID: 972445 · | |
|
Hi Kaylie, | |
| ID: 972456 · | |
Hi Kaylie, Perhaps this would be too mean: Top News: Hurricane Electric Jams SETI Traffic Large Internet trafficker either doesn’t like or can’t handle the enthusiasm for small time, but very popular “Seti At Home” project. It’s been known that some internet traffickers interfere with specific traffic because they don’t like their competitors or just don’t think that the bandwidth is worth the trouble. They can, a simple software patch can jam up packets from or to anywhere. It’s been done before. Maybe the aliens are doing it! In any event, the provider is best to fix the problem before it becomes well known that they cannot transfer such small bursts of data. I was just going to post this on my Website and everywhere else I could think of, but, what does the staff think? (Probably not on a weekend) | |
| ID: 972462 · | |
|
Here is what I get i Finland (for some reason i was able to upload about 30 workunits 1 hour ago ? the ping is still around 275 ms in the last hopes) | |
| ID: 972465 · | |
Message boards : Technical News : Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010)
| Copyright © 2013 University of California |