Hi Don,
First of all, it is enough to add that 44.135.192.160/29 subnet, there is no
need to add the individual hosts.
But your IPs are not ok.
For 44.135.192.160/29, 160 is the network address, and 167 the broadcast
address.
This allows you to use 161 to 166 as valid IPs.
So I would propose:
va7dgp.ampr.org 44.135.192.161
va7tsa.ampr.org 44.135.192.162
bpq.va7dgp.ampr.org 44.135.192.163
bpq.va7tsa.ampr.org 44.135.192.164
and this leaves space for 2 more IPs in that subnet (165 and 166).
The names of the hosts have to be registered via the DNS robot, not the
portal, which has to be solved by your local coordinator, again, no need to
add them individually in the portal.
Marius, YO2LOJ
-----Original Message-----
From: Don Poaps
Sent: Monday, September 14, 2015 18:26
To: AMPRNet working group
Subject: [44net]
va7dgp.ampr.org
(Please trim inclusions from previous messages)
_______________________________________________
Greetings..
I'm running a Windows based BPQ32 BBS. John Wiseman GB8BPQ has made it
possible that we can use the AMPRnet. I have gotten my 44.135.192.160/29
listed in the Encap. What I need is to add four more.
va7dgp.ampr.org 44.135.192.160
Subnet
va7tsa.ampr.org 44.135.192.161
bpq.va7dgp.ampr.org 44.135.192.162
bpq.va7tsa.ampr.org 44.135.192.163
I see a menu to add a Subnet but I don't the capability to add the above.
I've bombarded Luc ve3jpl email. He must be on vacation or away..
I know we are all Hams/Volunteers
73
Don va7dgp
*Don Poaps*
*New Westminster, BC*
*VA7DGP*