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.