o2 leaving INEX on Jan 14th

kazoo106

The only way these people will understand this decision is if people start getting rid of those little USB Devices for providers who peer within the country !

Rattlehead_ie

WTF?

Dude you shouldn't be posting that here!!!!
I presume you think that cause they are doing what they are doing that o2 are now not peering within Ireland and with someone else?!
If this is what you are saying then you are incorrect and o2 will still be peering with most of the other providers here in Ireland

johnciall

kazoo106 wrote: »

The only way these people will understand this decision is if people start getting rid of those little USB Devices for providers who peer within the country !

Am i the only one who has no idea what your trying to say?

kazoo106

So how exactly do they propose doing that - is there some other neutral exchange I don't know about ?

Rattlehead_ie

No but I would presume like many other operators in this country that they have out-sourced their network and the trafficing of that network to another provider say for eg BT Ireland.

SO what you will see is all data traffic for O2 Ireland will traverse INEX via BTs x-connect, but this is only a good educated guess

kazoo106

My point is - If someone now on o2 from Jan 14th, wants to check their eircom.net mails the packets will go out of the country and back in - irish websites will become slower for o2 customers.
This is an Anal decision on o2's behalf - they were one of the better Midband providers and I shall be canceling my contract from Jan 25th

Rattlehead_ie

Kazoo did you even read what I typed.
If you are not willing to read what ppl post I don't see the point in starting a discussion especially when you are being extremely critical of something that you do not have 100% of the facts for.

As I stated if they have chosen another operator like BT Ireland or someone else who peers in Ireland via INEX as their provider then the "packets" wont be going anywhere outside of Ireland for Irish websites.

kazoo106

Answering an earlier one sorry - I'm not sure if BT would be too happy about that - o2's main peer is currently tiscalli - the only peering with BT is through INEX to my knowledge, and it would be very strange for them to be taking transit from a non Tier1 supplier such as BT - Eircom - Imagine - UPC etc
But I suppose the traceroutes will tell !

Sponge Bob

Maybe they will leave O2 UK to handle their peering in Ireland.

Maybe they only went into the INEX for DVB-H peering when they were into DVB-H for all of 6 months a few years back and which is now a dead duck to my mind, maybe they will pick it up OTA instead ...on the roof ......and rerender it.

Who knows. If they cock up email checking they are a dead duck customer wise and they know it.

Jumpy

What does it matter? The pings are woeful as it is, removing peering (that is if they are planning to do this at all) will be all but unnoticable on a midband device.

jor el

kazoo106 wrote: »

they were one of the better Midband providers

And yet you didn't post this in the Midband forum. They haven't been one of the better providers since their decision to start censoring Internet access, many months ago.

daffy_duc

They're still going through INEX, but it looks like BT/Esat are carrying the traffic on their behalf.

Proof (From Irish Broadband):
1 <Internal Network> 0.613 ms 0.889 ms 1.180 ms
2 <Office Connection> 4.922 ms 5.205 ms 5.531 ms
3 DN07-ae1-232-ibis-dc-1.irishbroadband.ie (87.192.233.237) 5.955 ms 6.117 ms 6.258 ms
4 89.127.197.161 (89.127.197.161) 6.715 ms 6.514 ms 6.838 ms
5 ge0-1.br001.cwt.esat.net (193.242.111.17) 7.049 ms 7.187 ms 7.330 ms
6 vlan2.rt001.cwt.esat.net (193.95.129.3) 8.316 ms 5.583 ms 4.496 ms
7 vlan52.sw502.cwt.esat.net (193.95.130.146) 4.716 ms 5.438 ms 5.578 ms
8 ge5-2.sw532.cwt.esat.net (193.95.137.35) 5.793 ms 5.936 ms 6.077 ms
9 193.120.235.218 (193.120.235.218) 7.353 ms 7.514 ms 7.653 ms
10 russell-sbif1.portal.o2.ie (62.40.32.27) 7.874 ms 8.210 ms 8.376 ms


I still don't understand what your initial rant was about, but next time, double check your info before jumping to conclusions?

JHMEG

daffy_duc wrote: »

They're still going through INEX, but it looks like BT/Esat are carrying the traffic on their behalf.
I still don't understand what your initial rant was about, but next time, double check your info before jumping to conclusions?

All that proves is that as of the 5th of Jan 62.40.32.27 is connected to the Esat network, which is probably for historical reasons. This does not prove that O2 ISP traffic is, or will be, going through the INEX. You tested from another ISP.

Additionally:
1. russell-sbif1.portal.o2.ie does not resolve.
2. Connections to 62.40.32.27 do not work.
3. Traceroutes to the above now terminate at 193.120.235.218, an Esat IP address.

daffy_duc

JHMEG wrote: »

All that proves is that as of the 5th of Jan 62.40.32.27 is connected to the Esat network, which is probably for historical reasons.

Lets just say I know more than I'm saying, and that it will probably stay this way after the 14th too.

JHMEG wrote: »

This does not prove that O2 ISP traffic is, or will be, going through the INEX. You tested from another ISP.

Ofcourse I tested from another ISP. Another Irish ISP. Thats the whole point of INEX. To carry traffic between Irish ISP's without sending the traffic via International peering or transit.

JHMEG wrote: »

Additionally:
1. russell-sbif1.portal.o2.ie does not resolve.

It doesn't need to. Just because its a valid PTR, doesn't mean theres a matching A record. There should be, but its not safe to assume that there is.

JHMEG wrote: »

2. Connections to 62.40.32.27 do not work.

Because its a router. How safe is a router if the entire world is allowed to connect to it?

JHMEG wrote: »

3. Traceroutes to the above now terminate at 193.120.235.218, an Esat IP address.

Right, because its a router. And packets will pass through that router to get to the endpoint.
Run a traceroute to www.o2.ie and see for yourself.