19 Jan
2016
19 Jan
'16
1:38 p.m.
John,
Historically I recall 44.131.4.0/24 was allocated to Notts/Derbys/Leics.
At some point in the 1990s there was a UK re-structure and Notts was
allocated 44.131.56.0/24 - which is the bit I'm the present co-ordinator
for. From a quick look at the list it appears 44.131.4.0 is now
allocated to experimental mesh networks.
There are plenty of addresses in the present allocation free so if you
need more or a bigger slice than a /27 to split up for yourself drop me
a line and I'll allocate you some with pleasure.
73
Nick.
On 19/01/2016 10:17, John Wiseman wrote:
(Please trim inclusions from previous messages)
_______________________________________________
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
-----Original Message-----
From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu]
On Behalf Of Brian Kantor
Sent: 18 January 2016 23:00
To: AMPRNet working group
Subject: Re: [44net] DNS Clearout
(Please trim inclusions from previous messages)
_______________________________________________
On Mon, Jan 18, 2016 at 10:37:04PM -0000, John Wiseman wrote:
Are we saying that ampr.org names and presumably
44 addresses are only
valid
if they have a gateway associated with them?
It's been suggested that I use the portal's networks list instead of the
encap file since there are clearly networks which are not tunneled.
I've had addresses with dns entries allocated
since the early 90's which I
use from time to time for testing on rf networks which don't have an
associated gateway. The chances are that by now the only record of that
allocation is the DNS entries. I guess I could just abandon them and
request
a new allocation, and attach it to a dummy
gateway.
I'm suggesting that as a first cut at clearing up the DNS mess. I
suspect
that your radio-only DNS entries would be sacrificed in such a cleanup
and I don't know offhand how to get around that since their subnets are
not registered in the portal. If there's not too many of them, you could
send me a list and I could add them into the portal as radio-connected.
Does Chris know about them so he won't accidently assign them to someone
else?
The portal has a set of 'connection' tickboxes; this is used to indicate
how the network is connected to the Internet. It really should be a
pulldown menu allowing only one choice but that plea has been rejected.
Even if no box is ticked, the network is registered with the portal and
could be ANDed with the DNS - in other words, we'd use the portal's list
of known networks instead of literally the encap file. That list would
include all of the encap file, plus all the otherwise-connected subnets.
In other words, what I'm suggesting is that if the portal doesn't list
the enclosing subnet of a DNS entry, that DNS entry would go away.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net