Ronen:
I do not know of a tool that can truly traceroute a tunnel encapsulated
frame.
When I do testing, I check the route to the to the tunnel endpoint (non 44
address) and when it uses the default router to uscd, I check to see that it
gets to mirroshades.
Assi
I don't know how practical it would be to to try and monitor the dns
server queries to help id which entries are used vs unused. But it
might be something to consider sooner than later as you'd want to let
this run for quite some time to build some statistics.
Just throwing the idea out there.
>As for figuring out what is unused or not, there isn't any good way of
>determining that.
Neil,
Does your script count the BGP'd address space as gateways, or will it
kick back GATENOTFOUND for those too?
You can get those here:
http://thyme.rand.apnic.net/current/data-add-ARIN | grep " 44\."
> Re: [44net] Verifying the identities of IP coordinators
> From:
> Don Fanning <don(a)00100100.net>
> Date:
> 01/13/2016 05:56 PM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> On Wed, Jan 13, 2016 at 6:25 AM, Brian Kantor<Brian(a)ucsd.edu> wrote:
>
> I just thought of another possibility. We could ask that the regional
> coordinators do an audit of their IP spaces in conjunction with the
> above suggestions as they're likely to have closer relationships with
> the end user or be more familiar with the record keeping of their
> countries amateur radio licensing. Then we can check off that IP
> space as "claimed" or "reclaim" it back into the pool.
>
I have made an effort to do that. I tried to contact all hams that are in the current
allocation for the Netherlands, and asked them if they want to maintain their allocation.
As a result, some have replied they no longer want to use it, and I have deleted those
allocations. The ones that confirmed their allocation I put on a list with a datestamp.
But the vast majority of the hams could not be reached. I have no uptodate contact
info and even the old contact info is difficult to access (it is a folder in my mail program
that stores all original requests starting in 2002, I don't even have those for the addresses
requested before 2002).
I also regularly delete the allocations for hams that no longer appear in the official
callsign listing for the Netherlands. (I have done this every year, but recently I have done
it weekly because starting from this year there is a fee for keeping an amateur callsign
and lots of inactive hams have removed their registration as a result)
I only keep the registrations in a hostsfile and use a script to send the updates to the
mail robot. As an afterthought, I should have kept a file with more info like date of
registration and contact address for each entry, but it would require a filtering system
so this information does not end up in the publicly visible file.
I like to keep everything in a textfile as opposed to some database with a web form
frontend, because it allows me to browse through the file to see where a new allocation
is to be put, something lacking from many address allocation systems including
the amprnet portal.
Rob
> Subject:
> Re: [44net] DNS Clearout
> From:
> "John Wiseman" <john.wiseman(a)cantab.net>
> Date:
> 01/19/2016 04:17 PM
>
> To:
> "'AMPRNet working group'" <44net(a)hamradio.ucsd.edu>
>
>
> Thanks, Brian,
>
> I've just checked on the portal, and it seems I'm too late - they have
> already been allocated to someone else. (44.131.4.18-21). So they won't get
> removed by the clearout, but I'll need to replace them anyway. But it
> highlights a problem with your suggested approach - It won't pick up unused
> names which are in address ranges that have been reallocated. And glancing
> though the uk dns records I suspect that applies to a lot of entries.
>
> But I can't think of a better solution, and I guess an incomplete clearout
> is better than none!
>
> 73,
> John
Note that your entries are registered in the ampr.org DNS, but the portal apparently
does not respect that. This is one of the problems with the way the DNS part of the
portal works: there is no way to see what is already in use before allocating something new.
But nothing has been done about that yet, and the issue is open for many years.
Rob
> Subject:
> Re: [44net] DNS (was: Nevada IP Assignments)
> From:
> Neil Johnson <neil.johnson(a)erudicon.com>
> Date:
> 01/19/2016 02:10 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> The initial script is done:
>
> " 44.225.65.22 ","GATENOTFOUND"
> " 44.50.192.22 "," 108.160.233.78"
> " 44.225.66.220 ","GATENOTFOUND"
> " 44.225.65.220 ","GATENOTFOUND"
> " 44.225.64.220 ","GATENOTFOUND"
> " 44.225.66.221 ","GATENOTFOUND"
> " 44.225.64.221 ","GATENOTFOUND"
> " 44.225.66.222 ","GATENOTFOUND"
> " 44.225.64.222 ","GATENOTFOUND"
> " 44.225.66.23 ","GATENOTFOUND"
> " 44.225.65.23 ","GATENOTFOUND"
> " 44.50.192.23 "," 108.160.233.78"
> " 44.225.66.24 ","GATENOTFOUND"
>
> and so on
>
> Of the 36059 address records 30176 don't have a gateway associated with
> them. Seems kind of a large amount. I'll do some more sanity checking.
This is going to fail big time!!
That 44.225 network is probably the most active net-44 network in the world, but it is
not gatewayed to internet. People will not like it when you try to delete that!!
Also, again the proposal is made to transfer things to the portal. I do not consider the
portal ready for production use for this, and I question if it ever will be. Changes to
functionality and replies to questions are so far between that I don't think the maintainer
has enough resources to keep this project moving. Note I don't want to blame him for
this in any way, but I don't think we should become more dependent on it than we are.
Rob
Last year I tried to attack the task of cleaning up the DNS. Brian at one
point did an AND against the gateway subnets with the DNS and it produced
~19k A records - hundreds of times what is valid or even being used.
So as a curiosity exercise, I wrote some script to import the DNS into
MySQL. The result was 16653 unique callsigns in the DNS and 2211
aliased/bad call signs as of June 2015.
I then imported the FCC amateur database and compared it to US (A,K,N,W)
callsigns - that produced 3742 unique US callsigns matching the DNS. Out
of those, 1373 callsigns matched an expired, canceled or terminated
license. This doesn't take into account all the vanity call signs for the
1x2/2x2/2x1/1x3 callsigns which may be attributed to another operator.
While we can get good grips on the US callsigns, as soon as it crosses an
international border, it goes to pot as every country has their own
licensing structure. Many do not have online databases. So that's what
we're faced with.
Ideas welcome as to how we can validate the DNS tables.
Hi All,
I have been looking at my allocations and would like to weed out
the dead wood.
What is the easiest way to do this ?
Regards ..... Peter ZL2BAU
