> just tried JAP here from France
> no luck but the proxies work
>
>
> over on NANOG they are quite hard on Cogent saying they have a few
> bottomless pits
> 1 for our traffic
> 2 of money


I gave up on NANOG quite a while ago. It was full of bitter people that couldn't do something right if their lives depended on it.

---

> I gave up on NANOG quite a while ago. It was full of bitter people that
> couldn't do something right if their lives depended on it.

Quite true, but like any group there are a few exceptions.

You can glean some information from NANOG with a little bit of effort.

---

What is NANOG?

---

> What is NANOG?

The North American Network Operator's Group -- it's an informal forum for (in theory) the people that run the largest backbones.

I'm not sure that everyone there actually does run a backbone, and as Hammy suggests many list members have egos that are more expansive than their networks.

Still, they see things and do things on a daily basis that those of us farther down the food chain never see. If you can apply a robust bulls*** filter it is a good source of information about the Internet in general.

... and how some people keep it running with duct tape and chewing gum.

---

I just gotta say this....

Is it just me, or is the name of one of the participants, OpenTransit, somehow ironic.

---

There are many a nomenclature faux pas in computing - The irony is not lost.

---

So....the French Operators Group might be called FOG. Hmmmm....sounds just right for France Telecom given this situation; Je ne vois rien!

---

> So....the French Operators Group might be called FOG. Hmmmm....sounds just
> right for France Telecom given this situation; Je ne vois rien!
>

FR(N)OG -> http://www.frnog.org/

---

hi,
here is a french tracrt from near Paris (with FranceTelecom as provider)

C:\>tracert setiboinc.ssl.berkeley.edu (04/19/2005 18:00 UTC)

Détermination de l'itinéraire vers setiboincdata.ssl.berkeley.edu [66.28.250.125] avec un maximum de 30 sauts :

1 144 ms 55 ms 56 ms 193.253.171.219
2 57 ms 56 ms 55 ms 10.224.33.5
3 93 ms 55 ms 54 ms pos12-.nraub103.Aubervilliers.francetelecom.net
[193.252.159.29]
4 56 ms 58 ms 54 ms pos3-0.nrsta104.Paris.francetelecom.net [193.252.103.97]
5 56 ms 51 ms 52 ms 193.252.98.2
6 217 ms 139 ms 179 ms P2-0.OAKCR2.Oakhill.opentransit.net [193.251.242.98]
7 136 ms 137 ms 137 ms P1-0.ASHCR1.Ashburn.opentransit.net [193.251.243.89]
8 137 ms 171 ms 137 ms sl-st21-ash-15-3.sprintlink.net [144.223.246.21]
9 135 ms 137 ms * p16-0-1-1.r21.asbnva01.us.bb.verio.net [129.250.9.53]
10 139 ms 134 ms 137 ms p16-2-0-0.r81.asbnva01.us.bb.verio.net [129.250.2.131]
11 * * * Délai d'attente de la demande dépassé.
12 * * * Délai d'attente de la demande dépassé.
13 * * * Délai d'attente de la demande dépassé.
14 * * * Délai d'attente de la demande dépassé.
15 * * * Délai d'attente de la demande dépassé.
16 * * * Délai d'attente de la demande dépassé.
17 * * * Délai d'attente de la demande dépassé.
18 * * * Délai d'attente de la demande dépassé.
19 * * * Délai d'attente de la demande dépassé.
20 * * * Délai d'attente de la demande dépassé.
21 * * * Délai d'attente de la demande dépassé.
22 * * * Délai d'attente de la demande dépassé.
23 * * * Délai d'attente de la demande dépassé.
24 * * * Délai d'attente de la demande dépassé.
25 * * * Délai d'attente de la demande dépassé.
26 * * * Délai d'attente de la demande dépassé.
27 * * * Délai d'attente de la demande dépassé.
28 * * * Délai d'attente de la demande dépassé.
29 * * * Délai d'attente de la demande dépassé.
30 * * * Délai d'attente de la demande dépassé.

Itinéraire déterminé. > > > hi all
> > > > PING www.climateprediction.net (137.108.64.33): 56 data bytes
> > > > --- www.climateprediction.net ping statistics ---
> > > > 5 packets transmitted‰'k¹>õ¥•Ëòv1›È6؆ved, 100% packet
> loss
> > > > any idee for this ?
> > > > thx
> > > Hi
> > > You are in France?
> > > You may be affected by the problem. Do a tracert
> > setiboic.ssl.berkeley.edu and
> > > post the results and we can see then.
> >
> > hi tiger: yep i m her in france !
> >
> > Target Name: www.climateprediction.net
> > IP: 137.108.64.33
> > Date/Time: 19/04/2005 13:39:30
> >
> > 1 * * * * * * * * [-]
> > 2 * * * * * * * * [-]
> > 3 57 ms 57 ms 54 ms 57 ms 53 ms 57 ms 56 ms 58 ms
> > [193.253.171.66]
> > 4 54 ms 51 ms 50 ms 54 ms 54 ms 53 ms 51 ms 52 ms
> > [10.224.28.18]
> > 5 59 ms 59 ms 59 ms 60 ms 60 ms 59 ms 57 ms 61 ms
> > pos12-3.nrsta304.Paris.francetelecom.net [193.252.103.158]
> > 6 66 ms 60 ms 57 ms 61 ms 60 ms 57 ms 61 ms 59 ms
> > [193.251.126.50]
> > 7 60 ms 58 ms 59 ms 59 ms 58 ms 60 ms 56 ms 60 ms
> > P9-0.PASCR1.Pastourelle.opentransit.net [193.251.129.61]
> > 8 60 ms 60 ms 60 ms 58 ms 159 ms 59 ms 58 ms 59 ms
> > Level3.GW.opentransit.net [193.251.240.214]
> > 9 60 ms 62 ms 59 ms 66 ms 138 ms 59 ms 63 ms 77 ms
> > ae-0-17.mp1.Paris1.Level3.net [212.73.240.97]
> > 10 69 ms 69 ms 66 ms 77 ms 123 ms 68 ms 69 ms 68 ms
> > ae-1-0.bbr1.London2.Level3.net [212.187.128.46]
> > 11 132 ms 67 ms 69 ms 69 ms 101 ms 66 ms 68 ms 69 ms
> > ge-3-0-0.gar1.London2.Level3.net [4.68.124.62]
> > 12 66 ms 66 ms 65 ms 68 ms 78 ms 65 ms 63 ms 67 ms
> > [195.50.116.202]
> > 13 69 ms 66 ms 66 ms 69 ms 66 ms 68 ms 67 ms 68 ms
> > po2-0.lond-scr4.ja.net [146.97.35.221]
> > 14 76 ms 64 ms 66 ms 67 ms 67 ms 66 ms 66 ms 67 ms
> > gi0-1.lond-bar4.ja.net [146.97.35.210]
> >
> >
> > ????? IP: 137.108.64.33
> >
> > wath u can see ?
> >
> Hi. My guess would be that the router for that university is down or their
> link to Internet is down. I cant tracert it either....get as far London only.
> Wait while and see what happens.
>

---

Hi Pat-SC. Yes that tracert says you are affected by the networking problem. You need to search down this thread for a proxy you can use so that you can connect. Bon chance!

---

Technical News ____ April 19, 2005 - 18:00 UTC

April 19, 2005 - 18:00 UTC



Recently, many participants in Europe stopped being able to contact the SETI@home servers. This was the result of ISP OpenTransit (France Telecom) de-peering the ISP Cogent. De-peering means the refusal to exchange Internet traffic. Our data server is on the Cogent network, so participants connected to the Internet via OpenTransit were cut off.

The network experts on the Berkeley campus contacted Cogent about this. Cogent resports that France Telecon made a unilateral decision to de-peer. They are trying to reach an understanding with France Telecom with the goal of reinstating the connection.

There is a very helpful message board thread with suggestions on how to use proxies to work around this problem in the short run.

You can view this thread here _


Copied from here:

http://setiweb.ssl.berkeley.edu/tech_news.php







My very best wishes ........ and kindness to all ..........

friendly and respectful
byron ... [/url]_ International _ Earth _ Flag

[url=http://www.planetary.org/html/society/tributes/index.html ] Carl Sagan is my hero , may his _ Humanity _ his Passion _ and his Eloquence _ Live forever[/url]

> Hi Pat-SC. Yes that tracert says you are affected by the networking problem.
> You need to search down this thread for a proxy you can use so that you can
> connect. Bon chance!
>

Thank you Tigher, I finally find some proxies addresses later in the messages flow, adresses which work correctly with S@H. I'm not very easy whith the use of messages board to find quickly THE solution ...

Merci également à SetiOne.

Good night & bonne nuit

---

> > > > Well you can add another area to the misfortune. I am in
> French
> > Guyana,
> > > South
> > > > America. We come in to the US on the Americas II line. I get
> the
> > trace
> > > > routes and ping ok for SETI, but the server systems do not
> respond
> > and
> > > have
> > > > not since Thursday the 14th. It is the same thing for Pirate
> and
> > LHC,
> > > but
> > > > Einstein and climat are working.
> > > >
> > > Hi GOC. Sounds like a different problem. Post your tracert info here
> so
> > we can
> > > see. Thanks
> > >
> >
> > I'm seem to have the same problem but in the land down under -
> >
> > Tracing route to setiboincdata.ssl.berkeley.edu [66.28.250.125]
> > over a maximum of 30 hops:
> >
> > 1 1 ms 1 ms 1 ms 192.168.1.254
> > 2 2232 ms 966 ms 2713 ms nexthop.qld.iinet.net.au [203.55.228.88]
> > 3 1931 ms 1989 ms 2617 ms Gi1-0-0-17.bne-pipe-bdr1.chime.net.au
> > [203.55.228.188]
> > 4 1490 ms 1061 ms 358 ms
> GigabitEthernet2-1.cha23.Brisbane.telstra.net
> > [139.130.130.37]
> > 5 953 ms 2148 ms 1891 ms
> > GigabitEthernet5-0.cha-core4.Brisbane.telstra.net [203.50.44.9]
> > 6 2161 ms 3286 ms * Pos4-0.chw-core2.Sydney.telstra.net
> > [203.50.6.225]
> > 7 * 1681 ms 2264 ms InterfaceA.oxf-core1.Sydney.telstra.net
> > [203.50.6.2]
> > 8 1493 ms 3172 ms 1182 ms
> > GigabitEthernet6-0.syd-core04.Sydney.net.reach.com [203.50.13.34]
> > 9 1927 ms 1886 ms 1351 ms i-5-0.syd-core02.net.reach.com
> [202.84.144.249]
> > 10 2244 ms 2732 ms 2150 ms i-4-0.syd-core01.net.reach.com
> [202.84.221.89]
> > 11 3274 ms 1396 ms 3430 ms i-12-2.wil-core01.net.reach.com
> > [202.84.144.25]
> > 12 1431 ms * * i-3-2.wil03.net.reach.com
> [202.84.251.170]
> > 13 1879 ms 2331 ms 3034 ms unassign.net.reach.com [134.159.63.66]
> > 14 1662 ms 3095 ms 1557 ms p15-0.core01.lax01.atlas.cogentco.com
> > [154.54.2.213]
> > 15 1412 ms 3148 ms * p14-0.core01.sjc01.atlas.cogentco.com
> > [66.28.4.74]
> > 16 1759 ms 3610 ms 3115 ms p4-0.core01.sfo01.atlas.cogentco.com
> > [66.28.4.93]
> > 17 1518 ms 3460 ms 2057 ms
> g0-1.na01.b003123-1.sfo01.atlas.cogentco.com
> > [66.28.6.2]
> > 18 3909 ms * * UC-Berkeley.demarc.cogentco.com
> [66.250.4.74]
> > 19 3114 ms 3658 ms 2452 ms 66.28.250.125
> >
> > Trace complete.
> >
> > Is this the same? I'm still trying to understand Traceroute and the
> > unassign.net.reach.com is a trigger for me ??
> >
> > Any help ??
> >
> > Thanx's
> >
> > James
> >
> >
> >
> >
> >
> James Hi.
> I see you are reaching the Boinc data server from that trace route. But you
> have very long times between hops. This may be network congestion rather than
> any problem being routed to UC. So I think your problem is different but
> nevertheless a problem. It may just go away when things get quieter. Where you
> see a ** that can mean a router is dropping packets and thats where the
> problem may lie. It may be badly configured or just overworked or faulty. But
> you do eventually get through albeit slowly. Just hang and see if it resolves
> itself. Cheers and G'day!
>
My problem, I have been told is that the time between jumps is 160-200 and that in the asbnva01.us.bb.verio.net groups there is so much bottlenecked information that it considers it garbage and trashes it.
By adding in the appropriate proxy settings and piggybacking the data gets through ok, only setback is if the other operators start scaning and clearing out unwanted traffic, it will be necessary to modif the proxy often.

---

Hi again GOC
I think your problems might be closer to home than US mainland. You see the 2232 ms 966 ms 2713 ms in the second line? Thats your PC/modem waiting 2.2 secs .9 secs and 2.7 secs for a response from your own ISP I think. If you have these dealys so early in the route then as you get pings deeper into the network they will always be reflecting these poor early starts. If the problem does not go away then I would talk to your ISP. Where you see * * this means a router is dropping packets as I said before but they may well be timing out because of poor performance closer to home. You must be north of Brisbane I guess...what are the telecoms links like in more Northern Queensland? Are they known to be good normally? Let us know what happens.

---

Hi all. I put a short web page together to get the proxy information together in one place instead of way down the thread. Users who have this connection problem or think they have should go to Help Information to find out what to do.

---

> Hi all. I put a short web page together to get the proxy information together
> in one place instead of way down the thread. Users who have this connection
> problem or think they have should go to <a> href="http://www.iantighe.com/boincers.htm"> Help Information[/url] to find out
> what to do.
>

Well done, Ian, thanks!

By co-incidence, I just opened this thread to suggest just this:
"Wouldn't it be a good idea if someone how understands this stuff could gather the wheat from the chaff and put it together for those who don't"

It's been done, thanks again.

BTW, you asked in another thread (I think), Yes, South West London...

---

If you seek information about network connection problems in France, Belgium and Holland please Go here.

Hey hi there. Yeah I guessed it was pc.....dont live in London myself but worked there 11 years until recently. Learned to navigate/travel using two things. 1) oh yes its over SW1 or E8 or N8... and 2) how far is Wimbledon..or Ilford etc.....err about 50 minutes...yes but how far....dunno....just 50 minutes. hehe that's London! And thanks for the thanks on the web page. I have offered to the Seti team too to add to their news story after speaking with David A about the problems by email. Hope they do....the thread is awful to try and find anything. Hampshire and ex SW Trains user btw. C U later.

---

> If you seek information about network connection problems in France, Belgium
> and Holland please Go
> here.
>
Excellent Ian ;-))

---

********************
<img src="http://www.boincstats.com/signature/user_132726.gif" border="0">

just found this in a German Online Magazine CT

France Telecom kappt Verbindungen zum Konkurrenten Cogent


France Telecom cuts connections to the competitor Cogent

sorry only in German, if you need a translation try

http://world.altavista.com/

Greetings from Germany NRW
Ulli S@h Berkeley's Staff Friends Club m7 ©

From sic transit gloria orbis to sick transit going loopy! So much for the internet...

---