[163183] in North American Network Operators' Group
RE: Geoip lookup
daemon@ATHENA.MIT.EDU (Paul Kelly :: Blacknight)
Fri May 24 03:28:02 2013
From: "Paul Kelly :: Blacknight" <paul@blacknight.com>
To: 'Owen DeLong' <owen@delong.com>, "'bmanning@vacation.karoshi.com'"
<bmanning@vacation.karoshi.com>
Date: Fri, 24 May 2013 07:27:47 +0000
In-Reply-To: <20130524065755.9BCF25A4010@merlin.blacknight.ie>
Cc: 'North American Network Operators Group' <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> >
> > Just because I have operations in one region does not preclude me
> from having operations
> > in other regions. YMMV of course.
> >
> > /bill
>=20
> That was exactly my point, Bill... If you have operations in RIPE and ARI=
N
> regions, it is entirely possible for you to obtain addresses from RIPE or=
ARIN
> and use them in both locations, or, obtain addresses from both RIPE and
> ARIN and use them in their respective regions, or mix and match in just a=
bout
> any imaginable way. Thus, IP addresses don't reside in regions, either. T=
hey
> are merely issued somewhat regionally.
>=20
In theory Maxmind is quite accurate. From 1 x /20 that we own we tag differ=
ent space with the country: flag in the RIPE db. Maxmind picks this up afte=
r approx 30 days and says it's in Country X vrs country Y.
e.g.
$ geoiplookup 81.17.247.64
GeoIP Country Edition: US, United States
$ geoiplookup 81.17.247.1=20
GeoIP Country Edition: IE, Ireland
Obviously the RIPE db structure makes this simple. As for other RIRs it's n=
ot as easy. Like someone else said, it's going to be an 80% solution and it=
s really down to good administration from a network operator point of view.=
i.e. if you route some of your RIPE space in ARIN territory you should spe=
cify the country. There's numerous reasons for this but it's just good prac=
tice IMO.
Pk
