As many of you know, when we set up the portal and moved the gateways maintenance to it, we imported the legacy gateways file which included a significant number of dormant or abandoned gateway entries.
Since then we've requested that people operating gateways "take possession" of them by registering their active gateways.
I believe the time has come to flush all the gateway entries which have not been registered -- clearly by now if they're not registered they must be abandoned.
So I propose that we use the month of August to get the last of the active gateways registered with the portal, and after the last day of the month we remove all unregistered gateways from the gateways files. What will remain are the gateways that are still active and being operated by somebody. This should make the tunnels routing table a bit smaller.
Comments? - Brian
On Wed, 2013-07-31 at 18:54 -0700, Brian Kantor spake:
Comments?
Can we insure that we all have access to the regions we're resonsible for before this occurs? If we cut a gateway by mistake and we don't have access to all our regional subnets, coordinators may not be able to take the proper actions to fix it.
I suggest that you publish a list of whatever you plan to delete. Then give people a small but reasonable amount of time to review the list. It may help to avoid any accidental removals of gateways of those of us who are active.
M
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Wednesday, July 31, 2013 6:54 PM To: 44net@hamradio.ucsd.edu Subject: [44net] gateways sunset
(Please trim inclusions from previous messages) _______________________________________________ As many of you know, when we set up the portal and moved the gateways maintenance to it, we imported the legacy gateways file which included a significant number of dormant or abandoned gateway entries.
Since then we've requested that people operating gateways "take possession" of them by registering their active gateways.
I believe the time has come to flush all the gateway entries which have not been registered -- clearly by now if they're not registered they must be abandoned.
So I propose that we use the month of August to get the last of the active gateways registered with the portal, and after the last day of the month we remove all unregistered gateways from the gateways files. What will remain are the gateways that are still active and being operated by somebody. This should make the tunnels routing table a bit smaller.
Comments? - Brian
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
I'm all for it -- but we need some additional functionality.
1. Ability to edit allocations. 2. Ability to delete allocations
In other words CRUD (Create. Read, Update, and Delete) for Addresses and DNS. It would also be great if we could delegate DNS updates to subnet operators.
------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 http://k7ve.org/blog http://twitter.com/#!/john_hays http://www.facebook.com/john.d.hays
On Wed, Jul 31, 2013 at 6:54 PM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ As many of you know, when we set up the portal and moved the gateways maintenance to it, we imported the legacy gateways file which included a significant number of dormant or abandoned gateway entries.
Since then we've requested that people operating gateways "take possession" of them by registering their active gateways.
I believe the time has come to flush all the gateway entries which have not been registered -- clearly by now if they're not registered they must be abandoned.
So I propose that we use the month of August to get the last of the active gateways registered with the portal, and after the last day of the month we remove all unregistered gateways from the gateways files. What will remain are the gateways that are still active and being operated by somebody. This should make the tunnels routing table a bit smaller.
Comments? - Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
Brian et al,
We need to be careful as we already have errors in the current file.
I am the coordinator for NJ but according to the list you are the coordinator.
Could this be because I have never successfully navigated the portal?
Mark NI2O On Jul 31, 2013 9:54 PM, "Brian Kantor" Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ As many of you know, when we set up the portal and moved the gateways maintenance to it, we imported the legacy gateways file which included a significant number of dormant or abandoned gateway entries.
Since then we've requested that people operating gateways "take possession" of them by registering their active gateways.
I believe the time has come to flush all the gateway entries which have not been registered -- clearly by now if they're not registered they must be abandoned.
So I propose that we use the month of August to get the last of the active gateways registered with the portal, and after the last day of the month we remove all unregistered gateways from the gateways files. What will remain are the gateways that are still active and being operated by somebody. This should make the tunnels routing table a bit smaller.
Comments? - Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
On Thu, Aug 01, 2013 at 05:15:10PM -0400, Mark Phillips wrote:
We need to be careful as we already have errors in the current file. I am the coordinator for NJ but according to the list you are the coordinator. Could this be because I have never successfully navigated the portal?
You're in the portal's user list ok.
I know that Chris is a little behind on getting coordinator updates into the portal, and this is causing confusion. I hope he has time to work on this soon.
I don't think the gateways list has suffered as a result. If any gateway operator has attempted to claim his entry but not yet been able to do so we'll have to defer the cleanup.
There are 254 subnets listed as being gatewayed, but 186 of them appear to be abandoned, so I'd like to get that sorted. - Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/08/2013 23:28, Brian Kantor wrote:
I know that Chris is a little behind on getting coordinator updates into the portal, and this is causing confusion. I hope he has time to work on this soon.
I would so much happier if the portal would be fixed sometime, I keep having issues with the portal.
Allocation requests for LX are notified by email to the lx-ampr (LX Coordinator account) user, but the requests remain invisible to the lx-ampr user in the portal.
DNS request for LX area are neither notified nor visible to user lx-ampr.
Eventually Chris wants to release the source code, so we could assist in completing the portal. If the code would be available on GitHub (as an example) YLs and OMs could provide patches, which Chris could choose to integrate or not...
Again, those are just my thoughts.
73 de Marc, LX1DUC