[bdNOG] Proof of a Geolocation of an IP address

Thu Dec 11 05:47:40 BDT 2014

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

to add to this discussion, two easy ways

a) get the transit provider to give you the point to point IP address,
and have them set the rdns that indicates both the location and your
company name. this will even show up on the graphical traceroute tools
and geoloc stuffs properly.

b) join an IX like LINX or LONAP in London. Lonap is not very expensive.

- -gaurab

On 12/10/14, 8:41 PM, Muhammad Moinur Rahman wrote:
> Hi,
> 
> Thanks to Paul and Pappu Vai for the ideas. Hopefully I will try to
> join the RING soon. As requesting a RIPE Atlas didn't yet bring me
> a good result.
> 
> The catch with the problem is competency of clients. Right now I
> am trying to teach someone why outgoing BGP advertisement controls
> your incoming traffic and vice versa. Let's see.
> 
> BR, Moin
> 
> On Wed, Dec 10, 2014 at 7:00 AM, Paul S. <contact at winterei.se 
> <mailto:contact at winterei.se>> wrote:
> 
> I too highly recommend getting membership into NLNOG's ring. Job's 
> really helpful as well :)
> 
> 
> On 12/10/2014 ?? 09:14, Fakrul Alam wrote:
>> Ya i agree with Mr Paul. If you are in RING network 
>> (https://ring.nlnog.net/) or if you have any Ripe Atlas Probe,
>> you can do it quite easily.
>> 
>> / Pappu
>> 
>> Sent from my iPhone
>> 
>> On Dec 10, 2014, at 5:24 AM, Paul S. <contact at winterei.se 
>> <mailto:contact at winterei.se>> wrote:
>> 
>>> Hi,
>>> 
>>> Assuming a proper signed NDA is in place, just send the client
>>> a copy of your signed contract with whoever provides colocation
>>> for your London pop?
>>> 
>>> Assuming you're actually there to peer at LINX or the like,
>>> even better if you can try a trace from a London peer's network
>>> to one of your router interfaces, and have it end up within
>>> <5ms.
>>> 
>>> The last one would require the client to actually be competent 
>>> (and the reverse paths be configured through the same link) 
>>> though, so the former is safer and preferable (verifiable by 
>>> lawyers, even!)
>>> 
>>> On 12/10/2014 ?? 04:17, Muhammad Moinur Rahman wrote:
>>>> None of the web based traceroute result provider read geoloc
>>>> or DNS PTR. I have checked most of the scripts and those read
>>>> the country Information and more importantly always read the 
>>>> aggregated prefixes, unfortunately the information of which
>>>> is not easily changeable by anyone except IRR hostmaster. :(
>>>> 
>>>> 
>>>> On Wed, Dec 10, 2014 at 1:13 AM, Aniruddha Barua 
>>>> <aniruddha.barua at colbd.com
>>>> <mailto:aniruddha.barua at colbd.com>> wrote:
>>>> 
>>>> Dear Moin bhai,
>>>> 
>>>> Where do you want to show the location/geolocation info of 
>>>> your London router IP address? In DNS PTR records or in whois
>>>> records? I am not sure if 'geoloc' attribute in 'inetnum'
>>>> object record for your London IP block in APNIC whois db will
>>>> show your desired output but you might give it a try.
>>>> 
>>>> Regards,
>>>> 
>>>> Aniruddha Barua. Email: aniruddha.barua at colbd.com 
>>>> <mailto:aniruddha.barua at colbd.com>, cto at colbd.com 
>>>> <mailto:cto at colbd.com>
>>>> 
>>>> On Dec 10, 2014, at 12:22AM, Muhammad Moinur Rahman 
>>>> <5u623l20 at gmail.com <mailto:5u623l20 at gmail.com>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> We have a router in London. We have IP blocks assigned on the
>>>> interfaces; assigned by APNIC. Loopback IP is also assigned
>>>> from the same /24 block. The catch is our our ASN and IP
>>>> address is registered for a company in Singapore.
>>>> 
>>>> Now the point is how can we prove to a client that: 1. We
>>>> have a router in London 2. The traceroute report showing the
>>>> IP address is assigned in our London-Dhaka Router
>>>> interfaces. 3. I can use APNIC assigned IP address in my
>>>> London router. And various traceroute reports from various 
>>>> sites who uses reverse whois lookup from APNIC will always
>>>> show my IP address as Singapore.
>>>> 
>>>> TIA.
>>>> 
>>>> BR, Moin
>>>> 
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> 
nog mailing list
>>>> nog at bdnog.org <mailto:nog at bdnog.org> 
>>>> http://mailman.bdnog.org/mailman/listinfo/nog
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________ nog mailing
>>>> list nog at bdnog.org <mailto:nog at bdnog.org> 
>>>> http://mailman.bdnog.org/mailman/listinfo/nog
>>> 
>>> _______________________________________________ nog mailing
>>> list nog at bdnog.org <mailto:nog at bdnog.org> 
>>> http://mailman.bdnog.org/mailman/listinfo/nog
> 
> 
> _______________________________________________ nog mailing list 
> nog at bdnog.org <mailto:nog at bdnog.org> 
> http://mailman.bdnog.org/mailman/listinfo/nog
> 
> 
> 
> 
> _______________________________________________ nog mailing list 
> nog at bdnog.org http://mailman.bdnog.org/mailman/listinfo/nog
> 

- -- 

http://www.gaurab.org.np/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iEYEARECAAYFAlSI25wACgkQSo7fU26F3X2dDwCg5/etGXQaxvbHuyZI2anmkhgb
2eIAnjfslJI0Hvoa9qe9jWrdGURNDfwU
=cKJj
-----END PGP SIGNATURE-----