What is the final outcome of the discussion? Will any changes be made to the Portal to validate user input for default users? Will there be a change in functionality w.r.t. having gateways with external address within AMPRnet? Will incomplete gateway entries be deleted?
I hope we can have some outcome of the bad situation and following discussion, instead of leaving everything as it is.
Rob
I am happy to implement BK’s suggestion to limit the setting up of gateway endpoints that fall within the 44/8 range to co-ordinators.
I am also happy to go through and remove any currently empty/incomplete gateways. Perhaps I could also setup a cronjob that purge such entries on a regular basis, e.g. any that are over a week old with no subnets?
I can implement the above fairly quickly if that is what is wanted?
Regards, Chris
On 15 Apr 2019, at 18:02, Rob Janssen pe1chl@amsat.org wrote:
What is the final outcome of the discussion? Will any changes be made to the Portal to validate user input for default users? Will there be a change in functionality w.r.t. having gateways with external address within AMPRnet? Will incomplete gateway entries be deleted?
I hope we can have some outcome of the bad situation and following discussion, instead of leaving everything as it is.
Rob _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I have written a cronjob script that will run once each week around 2am (UK time) on a Monday.
It will search the database for all gateway entries that have no associated subnets and that have not been updated for at least one week. Any gateways matching this criteria will be deleted from the database and an email sent to the owner. The email will contain the following text:
—8< SNIP >8--- Hello {givenName},
This is a system generated email from the AMPRNet Portal.
This is a courtesy notice to advise you that your gateway entry has been removed.
Your gateway was removed by an automated process that looks for gateways that have had no attached subnets for at least one week.
Your gateway has met this criteria and has thus been removed.
It is important that the Portal data is kept up to date and accurate. If you still want to run a gateway, please feel free to add your gateway back to the Portal.
Your gateway's details were: Title: {gwTitle} IP: {gwIP} Host: {gwHost} Notes: {gwNotes}
Kind Regards, The AMPRNet Team —8< SNIP >8---
Everyone happy with this? Any comments?
Thanks, Chris
On 15 Apr 2019, at 18:22, G1FEF via 44Net 44net@mailman.ampr.org wrote:
I am happy to implement BK’s suggestion to limit the setting up of gateway endpoints that fall within the 44/8 range to co-ordinators.
I am also happy to go through and remove any currently empty/incomplete gateways. Perhaps I could also setup a cronjob that purge such entries on a regular basis, e.g. any that are over a week old with no subnets?
I can implement the above fairly quickly if that is what is wanted?
Regards, Chris
Chris,
Thank you, I think that will be quite helpful. - Brian
On Tue, Apr 16, 2019 at 02:11:18PM +0100, G1FEF via 44Net wrote:
I have written a cronjob script that will run once each week around 2am (UK time) on a Monday.
It will search the database for all gateway entries that have no associated subnets and that have not been updated for at least one week. Any gateways matching this criteria will be deleted from the database and an email sent to the owner. The email will contain the following text:
—8< SNIP >8--- Hello {givenName},
This is a system generated email from the AMPRNet Portal.
This is a courtesy notice to advise you that your gateway entry has been removed.
Your gateway was removed by an automated process that looks for gateways that have had no attached subnets for at least one week.
Your gateway has met this criteria and has thus been removed.
It is important that the Portal data is kept up to date and accurate. If you still want to run a gateway, please feel free to add your gateway back to the Portal.
Your gateway's details were: Title: {gwTitle} IP: {gwIP} Host: {gwHost} Notes: {gwNotes}
Kind Regards, The AMPRNet Team —8< SNIP >8---
Everyone happy with this? Any comments?
Thanks, Chris
Chris;
On Tue, 2019-04-16 at 14:11 +0100, G1FEF via 44Net wrote:
I have written a cronjob script that will run once each week around 2am (UK time) on a Monday.
It will search the database for all gateway entries that have no associated subnets and that have not been updated for at least one week. Any gateways matching this criteria will be deleted from the database and an email sent to the owner. The email will contain the following text:
Great job!
This is a system generated email from the AMPRNet Portal.
[snip]
I'd also try to include the block they registered and hint that they should attach their block to their gateway. I don't think folks would add a gateway if they haven't been approved for a block.
Your gateway's details were: Title: {gwTitle} IP: {gwIP} Host: {gwHost} Notes: {gwNotes}
-> Your block: {44.x.x.x/yy}
Everyone happy with this? Any comments?
Just my suggestion. Not crucial but it may help those who have never registered a gateway before.
Hi Brian,
On 16 Apr 2019, at 14:45, Brian n1uro@n1uro.ampr.org wrote:
I'd also try to include the block they registered and hint that they should attach their block to their gateway. I don't think folks would add a gateway if they haven't been approved for a block.
Your gateway's details were: Title: {gwTitle} IP: {gwIP} Host: {gwHost} Notes: {gwNotes}
-> Your block: {44.x.x.x/yy}
A lot of users have more than one block allocated, so it would have to be a list of blocks. Also, just adding their list of blocks without further explanation might be misleading - it could be read that they have been deleted as well as the gateway.
If folk think this data would be useful then I think additional words would be required to ensure there is no confusion?
Regards, Chris
-
Brian -
Brian Kantor -
G1FEF -
Rob Janssen