Just have them login once a year and reup their registration.. Like they
make you do for repeater coordination.. Allow a 90 day grace period and then
lock it for 30 days if still no contact they obviously have abandon it.. or
will return when they realize it is down.. Time frames I suggest are just
that.
That way no notice, no email reminders, no bother to the system or anyone..
They must login or get booted... Not trying to be mean.. but lets say ham A
has died.. The portal may never know this... Lets say they changed email, no
email reminder will ever reach them.. Let's say they lost interest, even an
email or post card could simply get ignored..
If it's simple and the system can send an email to the Last Known Good email
at say 11 Months... Fine.. Or make it a rolling 12 months from last login to
the portal.. But no need to make it any more than simple..
Let's keep its K.I.S.S
73
Sorry working late and bored.. lol
-----Original Message-----
From: 44net-bounces+n9lya=blueriver.net(a)hamradio.ucsd.edu
[mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of
lleachii(a)aol.com
Sent: Tuesday, March 12, 2013 4:37 PM
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] Portal registrations
(Please trim inclusions from previous messages)
_______________________________________________
Bill, WA7NWP,
I'm not sure this is best suggestion for many reasons:
- There was a discussion a few weeks back where it was determined that all
stations do not necessarily run telnet (while having others test
connectivity to my station, some were attempting to telnet to me). For
example, my station is not a TNOS/JNOS based router, and therefore does not
provide Converse (the telnet-based service we're referring to) by default.
Under that guideline, my allocation would be purged.
- We also determined that, while all stations should make their IP addresses
ping-able, that was not necessarily the case (either by intent or error).
- For various reasons, AMPRNet allocations may not necessarily be online or
available through AMPR
- A Station does not necessarily have to download the encap to have a
working allocation (one could manually add static routes from the portal
list or use RIP44, for example)
- It would be impossible to use the download guideline for those using the
RIP44 routing protocol, as it is multicast; and doesn't know what stations
are receiving it or using it
We have to be mindful that all stations may not be identically configured,
use the same Operating Systems, routing protocols nor system configurations
to accomplish connectivity to AMPRNet.
73,
Lynwood
KB3VWG
On 03/12/2013 03:00 PM, 44net-request(a)hamradio.ucsd.edu wrote:
> Automate it for now and the future... If a client doesn't
> ping/poke/telnet/download or whatever within 30days/3months/whatever -
> purge the entry. You know - just like DHCP but at a higher level..
> :)
>
> Bill, WA7NWP
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44nethttp://www.ampr.org/donate.html
I've lost track of the status of the portal functionality.
We have a block of addresses allocated to our county network (44.4.50.0/28).
I also have two addresses allocated for my personal machines (44.4.2.152,
44.4.2.153)
But when I log into the portal I see no active records.
At some point will the existing records appear in the portal when I log in?
Thanks
N6MEF
I don't understand how I can allocate anything out of 44.135.0.0/16
Since I still can allocate host out of Ampr host robot at UCSD. You need a guide for this website
----- Reply message -----
From: "Brian Kantor" <Brian(a)ucsd.edu>
To: "AMPRNet working group" <44net(a)hamradio.ucsd.edu>
Subject: [44net] Portal registrations
Date: Mon, Mar 11, 2013 13:20
(Please trim inclusions from previous messages)
_______________________________________________
It's especially important for the area coordinators to get themselves
registered as such with the portal. I think that in a few months we'll
just have to consider any regions with no registered coordinator as
abandoned by their former coordinators.
Similarly with gateways: at some time in the future gateways which aren't
registered with the portal will have to be dropped from the encap file.
People with existing allocations should make sure that their own allocation
is registered with the portal, if necessary by going through the portal
allocation process. If you do this, be sure to include a note that it's
a re-registration of an existing allocation.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44nethttp://www.ampr.org/donate.html
Hi All,
FYI - There was a bug in the code that emailed out the encap file to anyone that had the "only when changed" option set, resulting in the encap file not being emailed at all to them.
The bug has now been identified and fixed, so if anyone wants to receive an emailed copy of the encap file only when anything has changed, please login to the portal and click on: "Gateways" -> "Options" and alter the "Frequency" to "Only when changed".
If you do not wish to receive an email copy of the encap file, please ensure that the "Email" field on this same page is blank.
Thanks,
Chris
Following requests from co-ordinators, I have added some additional functionality to the portal.
If you are a country or regional co-ordinator you now have an extra menu link "IP Allocations" from where you can view / edit all the subnets you have allocated.
73
Chris - G1FEF
Here are "all" the IANA assigned numbers, if we're gonna get technical :)
"Private-Use" being really the important ones.
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-specia…
Tim Osburn
www.osburn.com
206.812.6214
W7RSZ
On Fri, 1 Mar 2013, Jann Traschewski wrote:
> Date: Fri, 01 Mar 2013 22:41:34 +0100
> From: Jann Traschewski <jann(a)gmx.de>
> Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
> To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
> Subject: Re: [44net] encap.txt
>
> (Please trim inclusions from previous messages)
> _______________________________________________
>> For now I have block most of the bogons plus 44/8 thusly:
>>
>> /^(0.|10.|44.|127.|169.154.|192.168.|224.)/
>
> Isn't it 169.254. ?
>
>> When I have more time I will create a more elegant table based filter, so we
>> can allow/deny subnets.
>
> Maybe it is worth to put 172.16.|172.17.|...|172.31. into the list (if
> it will not "break" the line :D)
>
> 73,
> Jann
>
>
> --
> Jann Traschewski, Lenbachstr. 6, D-90489 Nuernberg, Germany
> Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de
> Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
> http://www.ampr.org/donate.html
>
The portal has all the visible text in a separate language file, so can very easily be translated into other languages, but I need some willing volunteers!
So, if anyone is willing to create and maintain alternative languages for the portal, please could they drop me an email. I know a couple of people did mention this in the past, but if you could get in touch again, I am now ready to deploy the language files.
Thanks,
Chris
KK6CND [Chris Foreman],
Please resubmit your allocation request to the AMPR portal. I forgot
to allocate a proper IP address to your previous request.
--
Geoff Joy - ke6qh -
AmprNet IP Address Coordinator for San Bernardino & Riverside Counties.
geoff(a)windomeister.com
