Proxy Servers : Where you can find one to help you connect
Any comms news is here: No news folks! Hey that's good news! May 2008.
| Background (as at 19 Apr 2005). | Proxy Server Information | |||
| Well Level3 is the same story as FT to be be honest. No
need to re-tell it just substitute the name below and all will be clear. I have quickly put this page together just to summarise the impact of the France Telecom - Cogent de-peering problems. I do this because the thread is hard to read and to get the information you need to help you is difficult. There are problems for some European users. In France, Holland and Belgium users have problems connecting to the seti data severs. This is because there is now no reliable route through because FT and Cogent had an argument as it is understood. I asked SetiOne (fellow Boincer) to translate the problem into French also so this may help you if you are struggling with English. "Pour les francophones qui rencontrent des problèmes d'envoi
de leur WU (tout type de projet BOINC) il s'agit en fait d'un problème chez Wanadoo
et les filiales de FT (France Telecom) dont les IP sont bloquées par un intermédiaire
US du nom de "Cogent", pourquoi ça l'histoire ne le dit pas." I have been diagnosing the problem for people for some days now and many are affected. The problem manifests itself as BOINC cannot connect to a scheduler - no response. You can test to see if you are affected by running tracert from a command line prompt. tracert setiboinc.ssl.berkeley.edu (for windows users) or traceroute setiboinc.ssl.berkeley.edu (for Unix users) If you fail to see the IP address 66.28.250.125 in the last line - then you are affected. If you see this IP address but still cannot connect then your problem may be different to this one and you should seek help at the seti forum. For those who have the problem you can use a proxy to try and overcome it. Thanks to all who have helped identify and get the work arounds needed. Much appreciated!
|
May 2008: These are known to be working. We cannot accept any responsibility for these servers as we act as a mere collation point. Thanks to the good work of SetiOne
and Thierry Van Driessche the following may help (both seti boincers):
67.99.5.202 PORT : 80 Also You can find a proxy (free proxy) here : aliveproxy.com or here free-proxy-servers.com Also out latest attempts to provide reliable proxies These are the Boinc network buddy providers in the scheme. Also some background You will find Boinc Community Proxy Information here - Background to the Buddy scheme. If you are unsure how to add the proxy information then try Paul's FAQ here. If you are still having problems then come to the forums here and ask. |
|||
| Users have made use of these proxies with success and this may help you too. If you have further problems then please post in the seti thread - http://setiweb.ssl.berkeley.edu/forum_thread.php?id=13867 |
You can find Paul Buck's excellent documentation for BONIC here. Its worth book marking! |
|||
| Update 21 April 2005: Other non FT users may be affected too: Iridian posted news he found in Germany as follows: "Tiscali hat Cogent in Europe depeer'ed, will heissen
sämtliche Peerings mit Cogent/Gatel beendet, nur noch das in den USA steht. Der Grund
ist das ruinöse Dumpingverhalten von Cogent auf dem europäischen Markt. I asked fellow Boincer and Team Member Mad Matt to translate this:
Tiscali de-peered Cogent in Europe, that means they terminated all peerings with
Cogent/Gatel, except for the USA. It is because of the ruinous dumping strategy
of Cogent at the European market.
Some carriers de-peered Cogent in the meantime, some
partially, some fully. Among others, KPN, Tiscali, Teleglobe, Telia etc.
Teleglobe even decided to filter all packets to Cogent, that means you cannot
reach Cogent from Teleglobe and vice versa.
If Cogent goes on like this, it will soon be over (hopefully).
Regards and gl Ian aka (Tigher) |
||||