1 Apr
2014
1 Apr
'14
4:56 a.m.
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
Like 44.136.138.0/24 via 114.31.199.1 is in Sydney Australia and the peering is to Vocus
On 1/04/2014, at 10:34 am, Neil Johnson <neil.johnson(a)erudicon.com> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Here is example output...
>
> show ip route 44.0.0.0 longer-prefixes
> Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
> D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> E1 - OSPF external type 1, E2 - OSPF external type 2
> i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
> ia - IS-IS inter area, * - candidate default, U - per-user static route
> o - ODR, P - periodic downloaded static route
>
> Gateway of last resort is 128.223.51.1 to network 0.0.0.0
>
> 44.0.0.0/8 is variably subnetted, 30 subnets, 8 masks
> B 44.12.6.0/24 [20/31] via 129.250.0.11, 2d02h
> B 44.0.0.0/8 [20/0] via 216.218.252.164, 7w0d
> B 44.136.138.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.136.139.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.136.150.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.136.151.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.16.15.0/24 [20/0] via 114.31.199.1, 4w3d
> B 44.136.158.0/24 [20/0] via 114.31.199.1, 1w5d
> B 44.136.224.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.136.227.0/24 [20/0] via 114.31.199.1, 1w4d
> B 44.103.0.0/19 [20/0] via 216.218.252.164, 1w4d
> B 44.68.52.0/24 [20/0] via 216.218.252.164, 4w1d
> B 44.161.252.0/22 [20/0] via 216.218.252.164, 4w4d
> B 44.34.128.0/21 [20/31] via 129.250.0.11, 2d02h
> B 44.140.47.0/24 [20/0] via 217.75.96.60, 7w0d
> B 44.140.0.0/16 [20/0] via 217.75.96.60, 6w1d
> B 44.46.160.0/22 [20/0] via 4.69.184.193, 1w3d
> B 44.139.0.0/16 [20/0] via 4.69.184.193, 1d10h
> B 44.98.254.0/24 [20/0] via 4.69.184.193, 1w3d
> B 44.169.48.0/20 [20/0] via 195.66.232.239, 1d10h
> B 44.144.0.0/16 [20/10] via 89.149.178.10, 4w0d
> B 44.24.240.0/20 [20/0] via 12.0.1.63, 2w4d
> B 44.130.99.0/24 [20/0] via 216.218.252.164, 1w1d
> B 44.135.120.0/24 [20/0] via 216.218.252.164, 7w0d
> B 44.127.128.0/24 [20/0] via 216.218.252.164, 1w6d
> B 44.140.64.0/23 [20/0] via 217.75.96.60, 00:30:13
> B 44.140.66.0/24 [20/0] via 217.75.96.60, 00:30:13
> B 44.74.128.0/24 [20/0] via 216.218.252.164, 2w4d
> B 44.140.79.0/24 [20/0] via 217.75.96.60, 7w0d
> B 44.208.0.0/16 [20/0] via 194.85.40.15, 3d20h
>
> On Mon, Mar 31, 2014 at 4:15 PM, Pete McCormick
> <pete.mccormick(a)gmail.com> wrote:
>> (Please trim inclusions from previous messages)
>> _______________________________________________
>> If you're ever interested in what's being advertised you can always check
a "route view" server. If you google "route view" server you'll
get a big list. I normally use "route-views.optus.net.au" because it's close
to me and a cisco.
>>
>> you can then telnet to it without having to log in:
>> telnet route-views.optus.net.au
>>
>> then when you're in you can issue a "show route" command. For
example:
>>
>> show ip route 44.0.0.0 longer-prefixes
>>
>> This will give you all the 44net's advertised out to the internet.
>>
>> If you're interested in digging into the bgp specifics you can pick a network
and issue this command:
>>
>> show ip bgp 44.140.64.0/23
>>
>> This will give you the AS paths and bgp routes to 44.140.64.0/23 along with some
metrics.
>>
>> Cheers
>>
>> Pete
>> ZL1PCM
>>
>>
>>
>>
>>
>>
>> On 1/04/2014, at 9:58 am, Michael E Fox - N6MEF <n6mef(a)mefox.org> wrote:
>>
>>> (Please trim inclusions from previous messages)
>>> _______________________________________________
>>> Steve,
>>>
>>> Huh? AMPRnet is already routed.
>>>
>>> The entire 44.x space is already reachable from anywhere on the Internet via
>>> the BGP peer router at UCSD. And I understand portions are also announced
>>> via BGP elsewhere (mostly in Europe, as I understand it). So in that
>>> respect, it's no different than any other public address allocation to a
>>> global entity that announces a prefix with BGP at the "home office"
and
>>> (optionally) longer prefixes elsewhere.
>>>
>>> But the entire AMPRnet is not contiguous except by the use of tunnels.
>>> Connectivity within the local "islands" is routed. We happen to
use a
>>> combination of RIP (where needed) and OSPF in our part of the network. And
>>> connectivity between the islands is routed over tunnel interfaces. The
>>> options there are static or RIP. Again, this is not much different than a
>>> corporation that uses VPN tunnels between sites. A tunnel is just another
>>> interface to a router. Tunneling does NOT indicate a lack of routing.
>>>
>>> The 44.x address space allows globally unique addressing within the ham
>>> community. It would be impossible to do that with network 10 since it is
>>> already used for other private address space. There is simply no way to
>>> deal with all of the address overlaps. Surely anyone with even basic IP
>>> routing knowledge can understand this.
>>>
>>> So I don't understand what your concern is. What specific problem are
you
>>> trying to solve? In other words, what is it (specifically) that you
can't
>>> do today with the existing infrastructure?
>>>
>>> Also, what type of services are you running today, and how many of each?
>>>
>>> Michael
>>> N6MEF
>>>
>>>
>>> -----Original Message-----
>>> From: 44net-bounces+n6mef=mefox.org(a)hamradio.ucsd.edu
>>> [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Steve
>>> Wright
>>> Sent: Monday, March 31, 2014 1:05 PM
>>> To: 44net(a)hamradio.ucsd.edu
>>> Subject: [44net] routable or private?
>>>
>>> (Please trim inclusions from previous messages)
>>> _______________________________________________
>>>> If this is, " a hack to backbone a semi-private network on top of
the
>>>> public internet" then why do we need 44/8? Please explain why 10/8
would
>>>> not work just as well?
>>>>
>>>> [....] if it's not going to be routable then why do we need 44/8?
use
>>>> RFC1918 space and give 44/8 back. [...] We could attract many
>>>> into this hobby if we'd simply offer to be the teachers of the IP
>>>> networking craft using standards based methods used by everyone else
>>> across
>>>> the internet.
>>>>
>>>
>>> PRECISELY.
>>>
>>> Can we please make a decision on this and move ahead?
>>>
>>> I'd like to know, one way or the other, because I sure aint interested
in
>>> all this private 44net stuff..
>>>
>>> Is 44net routable or private?
>>>
>>>
>>>
>>> Steve
>>>