6 Feb
2016
6 Feb
'16
4:52 p.m.
Hey Brian,
Interesting to see that my allocation is messed up though I think I was
given these addresses at two different times. I'll wait to see what Dan
would like to do with my allocation. I'm flexible.
Beyond me, it seems that the various IPs that are listed in your
to-be-deleted.txt are IPs that *aren't* in the portal. Correct? If so,
it seems to me that the proper next steps would be for the various
coordinators to reach out to the various HAMs and see if they want to
retain their allocations. If they do want to keep their allocations, it
then seems the coordinator will need to enter them into the portal for them.
Do I understand all this correctly?
--David
On 02/06/2016 02:33 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages)
_______________________________________________
David,
If you're using the .39 and .41 addresses in addition to the .40 address,
your allocation isn't correct. It probably should be for a small subnet
instead of for a single address. And for the typical /29 subnet, the
.39 address would be in a different subnet than .40 and .41 are.
It looks like there's even more wrong here - 44.4.10.40/29 is allocated
to N6ACK. You shouldn't have been allocated 44.4.10.40/32 at all, or
N6ACK should have been allocated some other subnet. The portal software
is supposed to prevent such overlaps from occuring, so it looks like
we've discovered a bug in the portal.
There's a note in your /32 allocation that it was added by the gateways
conversion script so that makes it a longstanding error that predates
the existence of the portal.
The simplest solution is to get you a proper allocation, like
44.4.10.32/29. I can do that but it would be better if your coordinator
worked with us on this. He is K6DLC Daniel Curry and I'm sure he'd be
happy to help us straighten this out. Your gateway entry will have to
change too, as it's for 44.4.10.40/32.
- Brian
On Sat, Feb 06, 2016 at 01:43:24PM -0800, David Ranch wrote:
So I logged into the portal and I see:
---------------------------------------------------------------------
Network Type Description Actions
44.4.10.40/32 user KI6ZHD Edit | Release
44.4.128.0/22 user KJ6VU Edit | Release
---------------------------------------------------------------------
The top entry is seemingly incomplete as I've been previously granted
and DNS resolution confirms I have (had?):
$ host 44.4.10.39
39.10.4.44.in-addr.arpa domain name pointer ki6zhd-5.ampr.org.
<------- This is what I actively use on RF
$ host 44.4.10.40
40.10.4.44.in-addr.arpa domain name pointer ki6zhd.ampr.org. <-------
for special projects right now
$ host 44.4.10.41
41.10.4.44.in-addr.arpa domain name pointer ki6zhd-dgw.ampr.org.
<--------- This is what I use when the IPIP tunnel is up
Are these missing entries something I missed or something my local
coordinator missed? Depending on your answer here, I imagine this
will be the same reasoning for my other fellow HAMs being on the
"to-be-deleted.txt" list.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net