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@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@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@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