1 Apr
2014
1 Apr
'14
5:24 a.m.
My mistake. Marc’s correct.
you’d need to trace route to get the last gateway, then put that in a geolocation search
Pete
On 1/04/2014, at 11:11 am, Marc, LX1DUC <lx1duc(a)laru.lu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 31/03/2014 23:56, Pete McCormick wrote:
Thats right. So all of these 44/8 networks have
organised themselves a BGP peering to the internet.
If you have a look at the “via xxx.xxx.xxx.xxx” part of the list below and put it into a
geolocation service you can see where they are. e.g.
http://www.ip2location.com/demo
the via IP address is the next-hop as seen from that looking glass
server/router. It is not the Router ID of the originating router.
Your Example shows:
B 44.161.252.0/22 [20/0] via 216.218.252.164, 4w4d
route-views.optus.net.au shows:
B 44.161.252.0/22 [20/1] via 203.13.132.53, 1w3d
route-server.he.net shows:
*>i44.161.252.0/22 37.49.236.136 20 100 0 51405 60391 i
As a matter of fact I know that 44.161.252.0/22 is not originated from
any of these IP addresses.
73 de Marc
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net