[194512] in North American Network Operators' Group
Re: Geolocation of o3b satellite end user terminals
daemon@ATHENA.MIT.EDU (TR Shaw)
Thu May 4 18:30:58 2017
X-Original-To: nanog@nanog.org
From: TR Shaw <tshaw@oitc.com>
In-Reply-To: <CAB69EHjWGLHnqtfqVZU_rr6a41SkXDC7ms0Am0PJbOCv64Hy+w@mail.gmail.com>
Date: Thu, 4 May 2017 18:30:54 -0400
To: Eric Kuhnke <eric.kuhnke@gmail.com>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
My limited experience is that you get the location of the gateway the =
traffic it coming out of. This is very similar to the locations returned =
for Motorola Canopy, Ubiquity and other wireless networks. Similar to =
IP location for cell.
> On May 4, 2017, at 2:33 PM, Eric Kuhnke <eric.kuhnke@gmail.com> wrote:
>=20
> Since today seems like the day for IP geolocation related topics...
>=20
> Does anyone have direct experience with third-party IP geolocation =
services
> and o3b served enterprise/ISP-type high capacity customers?
>=20
> For those who are not familiar with them, o3b satellite terminals can =
be
> located literally anywhere in the world below 45 degrees north or =
south
> latitude, served from a fleet of MEO satellites. Each terminal is a =
twin
> pair of motorized/tracking antennas and associated modems, etc with an
> IP/Ethernet hand off to the customer.
>=20
> Their gateways to the Internet are located in about a dozen places =
around
> the globe and ordinarily go out to the Internet through o3b's own IP
> network.
