hello,

we buy bandwith to a US provider, but DC is on mexico, we have updated details on ARIN, also dbs that verify server's location like maxmind are reporting it in mexico.

you can check it at: https://www.maxmind.com/es/home

kind regards

2017-03-17 19:29 GMT-03:00 Anssi Johansson avij@centosproject.org:

17.3.2017, 22.55, Mach Host kirjoitti:

...

Hello,

we setup a new centos mirror and want you to include it on the list

HTTP: http://centos.mexico.machost.co FTP: no RSYNC: no

Sync schedule: Every 2 hrs Bandwidth: 10gbps unmetered Location: Mexico Sponsor: Mach Host Sponsor URL: machost.co IPv4 address to authorize: 204.45.61.61 IPv6 address to authorize: not supported on mexico yet Email contact: info@machost.co Mirroring AltArch : no

Hi, new mirrors in Mexico would be very welcome as it looks like we have only one there at the moment.

However, there seems to be a slight problem with your submission: the server seems to be in U.S. instead of Mexico. If you could haul the server to Mexico and connect it to Mexican fibres that would be great :) Thanks. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

hello,

the ISP is peering locally with mexican isps, only the international traffic goes throught US

kind regards.

2017-03-17 20:09 GMT-03:00 Anssi Johansson avij@centosproject.org:

18.3.2017, 0.48, Mach Host kirjoitti:

...

hello,

we buy bandwith to a US provider, but DC is on mexico, we have updated details on ARIN, also dbs that verify server's location like maxmind are reporting it in mexico.

you can check it at: https://www.maxmind.com/es/home

I'm sorry, but it does not make sense to add a Mexican mirror if all its traffic gets routed through U.S.

You would need to set up peering with Mexican ISPs so that the traffic wouldn't get routed through U.S., otherwise there wouldn't be any advantage to Mexican CentOS users in having a mirror in Mexico.

---

CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

yes, please provide me a mexican host and i will send you the tracert

kind regards.

2017-03-17 21:02 GMT-03:00 Anssi Johansson avij@centosproject.org:

18.3.2017, 1.59, Mach Host kirjoitti:

...

hello,

the ISP is peering locally with mexican isps, only the international traffic goes throught US

Let's get back to this when you can verifiably demonstrate a traceroute from some other Mexican host to centos.mexico.machost.co without the traffic going through U.S. in between. Does this sound fair?

---

CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

hello,

this ip is from SOFTLAYER, softlayer has servers in mexico but is not peering with mexican providers in order to save some money, all traffic going to softlayer is routed thought dallas.

So, please delete all centos mirrors from softlayer as they are not peering in mexico then provide me a true mexican ip so i can perform the tracert.

Here i attach a tracert from my server and from my home in mexico, BOTH are forced to go throught Dallas by $oftlayer

server:

Traza a la dirección 54.3c.39a9.ip4.static.sl-reverse.com [169.57.60.84] sobre un máximo de 30 saltos:

1 1 ms 1 ms 1 ms 204.45.61.254 2 4 ms 4 ms 3 ms 10.152.160.3 3 * * * Tiempo de espera agotado para esta solicitud. 4 5 ms 5 ms 15 ms 10.180.55.4 5 38 ms 32 ms 33 ms 9-1-2.ear3.Dallas1.Level3.net [4.14.130.45] 6 35 ms 33 ms 35 ms ae-2-14.edge5.Dallas3.Level3.net [4.69.143.229] 7 33 ms 40 ms 34 ms ae4-bbr01.eq01.dal03.networklayer.com [4.59.32.38] 8 58 ms 57 ms 57 ms ae0.bbr02.sr03.mex01.networklayer.com [50.97.19.112] 9 58 ms 61 ms 58 ms ae6.dar01.mex01.networklayer.com [50.97.19.109] 10 59 ms 59 ms 58 ms po1.fcr01a.mex01.networklayer.com [169.57.118.131] 11 61 ms 61 ms 57 ms 54.3c.39a9.ip4.static.sl-reverse.com [169.57.60.84]

Traza completa.

4g network:

traceroute to 169.57.60.84 (169.57.60.84), 30 hops max Hop 1: From 10.182.19.114, 107 ms

Hop 2: From 187.196.21.45, 57 ms

Hop 3: From wan-vpn-a04-0810-0408.uninet-ide.com.mx (201.129.22.218), 37 ms

Hop 4: From 10.46.2.2, 47 ms

Hop 5: From 10.46.0.5, 47 ms

Hop 6: From opint-jal-ctg-51-tge0-2-1.uninet.net.mx (187.130.165.90), 41 ms

Hop 7: From bb-la-grand-7-be3.uninet.net.mx (189.246.220.6), 111 ms

Hop 8: From xe-0-7-0-17.r00.lsanca20.us.bb.gin.ntt.net (128.242.179.185), 65 ms

Hop 9: From ae-7.r00.lsanca07.us.bb.gin.ntt.net (129.250.4.42), 101 ms

Hop 10: From ae-2.r23.lsanca07.us.bb.gin.ntt.net (129.250.3.237), 73 ms

Hop 11: From ae-12.r22.snjsca04.us.bb.gin.ntt.net (129.250.4.150), 102 ms

Hop 12: From ae-19.r01.snjsca04.us.bb.gin.ntt.net (129.250.3.27), 85 ms

Hop 13: From ae2.bbr01.eq01.sjc02.networklayer.com (128.241.219.206), 94 ms

Hop 14: From ae5.cbs02.eq01.sjc02.networklayer.com (50.97.17.76), 2532 ms

Hop 15: From ae0.cbs02.cs01.lax01.networklayer.com (50.97.17.86), 88 ms

Hop 16: From ae9.bbr01.cs01.lax01.networklayer.com (50.97.17.67), 87 ms

Hop 17: From ae0.bbr01.sr03.mex01.networklayer.com (50.97.19.114), 145 ms

Hop 18: From ae5.dar01.mex01.networklayer.com (50.97.19.105), 146 ms

Hop 19: From po1.fcr01b.mex01.networklayer.com (169.57.118.135), 156 ms

Hop 20: From 54.3c.39a9.ip4.static.sl-reverse.com (169.57.60.84), 155 ms

Traceroute complete: 20 hops, time: 29693 ms

kind regards

2017-03-17 22:11 GMT-03:00 Anssi Johansson avij@centosproject.org:

18.3.2017, 2.05, Mach Host kirjoitti:

...

yes, please provide me a mexican host and i will send you the tracert

For starters, you could try a traceroute to 169.57.60.84. Please also provide the average ping time from your mirror to that IP address.

---

CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

Anssi is right, I don't see anywhere that they host in mexico.

All other geo IP lookup tools point to Denver US.

Even using maxmind, It tells us ISP and Organization is fdcservers.net

If we look here: https://www.fdcservers.net/network.php

There is no mention of Mexico, but there is mention of Denver, US, where other Geo IP's point to.

If you go directly to 204.45.61.61, it points to http://litehost.co/ Which is located in Chicago, IL, US where traceroute from any location points to.

Their website says "Our Tier 3 datacenter is located in Chicago, IL ensuring 99.9% uptime." Nothing about other locations.

Finally traceroute mentions host-engine, http://host-engine.com/network.htm, Again only mentions of either Chicago and Denver

"Our servers are located in Tier III datacenters on Denver, Miami and Chicago, connected to 1gbps uplink, guaranteeing 99% uptime and the best ping."

I think we can conclude that, the server is actually located in US.

Alex

________________________________ From: CentOS-mirror centos-mirror-bounces@centos.org on behalf of Anssi Johansson avij@centosproject.org Sent: Saturday, March 18, 2017 10:16:52 AM To: centos-mirror@centos.org Subject: Re: [CentOS-mirror] New mirror

18.3.2017, 18.25, Mach Host kirjoitti:

hello,

this ip is from SOFTLAYER, softlayer has servers in mexico but is not peering with mexican providers in order to save some money, all traffic going to softlayer is routed thought dallas.

So, please delete all centos mirrors from softlayer as they are not peering in mexico then provide me a true mexican ip so i can perform the tracert.

Here i attach a tracert from my server and from my home in mexico, BOTH are forced to go throught Dallas by $oftlayer

I'm sorry my example of a Mexican IP address was not good enough for you. That was not a mirror's IP address, but that is probably not relevant. Softlayer does peer with some Mexican providers, but apparently not with the ones you are using. Which Mexican ISPs are you peering with?

But the thing is, I can find tons of examples where traceroute to your server goes through U.S., but none that would show that it would go directly from a host in Mexico to your mirror. In this situation, I believe the burden of proof is on you. Extraordinary claims require extraordinary evidence, as the saying goes.

Please find me an example traceroute which shows true Mexico <-> Mexico connectivity and then I can have a closer look. This would also need to be something that I can verify myself -- examples of such verifiable claims include ISPs' looking glass websites, where I can give an IP address and the website will run a traceroute to the specified address.

I would also like to reiterate that I don't particularly care where the servers itself are located, but where they are exposed to the rest of the Internet. If you route all the mirror's traffic through some VPN to a U.S. IP address, it is a U.S. mirror from our point of view and not a Mexican mirror. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

Hello,

We need that you please change the GBEServers logo with this one:

http://machost.co/images/logo.png

Text: Mach Host - Unmetered Servers Url: http://machost.co

this sponsor is for the donated server 23.237.22.11

thanks

19.3.2017, 22.01, Dewangga Bachrul Alam kirjoitti:

Hello Anssi,

Would you like to share how Cent OS team determine the mirror location by an IP address? Let's pick an example, softlayer has an IP test on Mexico (speedtest.mex01.softlayer.com), but yes, the traffic is through US than directly to Mexico. Possible it's IP Transit, since MIE (Mexico Internet Exchange) have same traceroute details.

[...]

The good news is, I can get result from atlas probe, 10 probes on mexico are active.

Measurements to 204.45.61.61 https://atlas.ripe.net/measurements/7930303/#!probes

Measurements to mie.mx https://atlas.ripe.net/measurements/7930313/#!probes

Any hints from traceroute above? Hope it helps.

Notes: Is there any FAQ from mirror team about choosing mirror location determine by an IP Address? Correct me if I'm wrong.

The short answer is: It depends.

Longer answer: When Massachusetts Institute of Technology submitted their mirror to the list, it was pretty clear that the mirror was actually in Massachusetts. For some other mirrors we may do a quick lookup from one of the GeoIP providers out there, such as MaxMind. If everything matches, good, otherwise we may dig deeper. There are no particular guidelines for us at this stage, because the actions depend on the observed discrepancies. Usually asking for a clarification from the mirror submitter is enough, and we can usually reach a consensus of the mirror's location that way.

I'm unsure how relevant mie.mx is for this discussion, so I'm not commenting on that at this stage. However, while researching for this discussion, I have found that Mexico's ISP are (still) less interconnected than in some other countries. It is very well possible that some Mexican ISPs communicate with each other by passing their packets twice across the U.S. border. Hence my question about which Mexican ISPs centos.mexico.machost.co's host peers with, as that might shed some light on the observed oddities.

Thanks for the Atlas probes, I had entirely forgotten about that. I think it's noteworthy that all those 10 probes from Mexico to 204.45.61.61 ended up getting routed to Denver. This reinforces my view that the mirror does not seem to have a local network presence in Mexico. It looks like it's entirely in U.S., but as Mach Host claims otherwise, I'm listening to their input on this matter.

As for a FAQ, no, this does not come up frequently enough to warrant a FAQ entry. We generally expect mirror admins to know where their servers are, but we check the data they submit to make sure there aren't errors. In this age of "everything's in the cloud and nobody sees physical servers any more", the mirror admins might not even know where their servers are. It happens, but we try to work out the differences.