16 Apr
2019
16 Apr
'19
9:18 a.m.
Given this, perhaps you could add a note suggesting that one or the list
of blocks should be added when they reregister their gateway, that would
eliminate any confusion... just my two cents.
This better:
—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}
You have the following subnets allocated to you:
{listOfSubnets}
If you add your gateway back, please ensure that you allocate at least one subnet to it,
otherwise this process will remove your gateway again in a week!
Kind Regards,
The AMPRNet Team
—8< SNIP >8—
16 Apr
16 Apr
10:53 a.m.
New subject: RIP problems?
I have added an extra field to the users table on the Portal, initially this has been set
to true if the user is currently a coordinator, otherwise it defaults to false.
I have added a check for anyone adding a gateway with a public IP starting with 44.
If the new flag for the user is false it will not allow the gateway to be added.
If the new flag is true, it will allow the gateway to be added.
If anyone would like this flag setting that is not a coordinator, please ask BK to set it
for you.
Please report any bugs / problems with the changes to me.
Purely for information: the code currently checks for, and does not allow, gateways who’s
endpoint address start with:
0.
10.
127.
169.
254.
192.168.
224.
nor within the range: 172.16.x.x - 172.31.x.x
nor if it is: 255.255.255.255
Regards,
Chris
11:13 a.m.
New subject: RIP problems?
Sweet! Thanks Chris!
Ruben - ON3RVH
On 16 Apr 2019, at 17:56, G1FEF via 44Net
<44net(a)mailman.ampr.org> wrote:
I have added an extra field to the users table on the Portal, initially this has been set
to true if the user is currently a coordinator, otherwise it defaults to false.
I have added a check for anyone adding a gateway with a public IP starting with 44.
If the new flag for the user is false it will not allow the gateway to be added.
If the new flag is true, it will allow the gateway to be added.
If anyone would like this flag setting that is not a coordinator, please ask BK to set it
for you.
Please report any bugs / problems with the changes to me.
Purely for information: the code currently checks for, and does not allow, gateways who’s
endpoint address start with:
0.
10.
127.
169.
254.
192.168.
224.
nor within the range: 172.16.x.x - 172.31.x.x
nor if it is: 255.255.255.255
Regards,
Chris
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2048
days inactive
2048
days old
2 comments
2 participants
participants (2)
-
G1FEF -
Ruben ON3RVH