I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44.
Note it also involves routing subnets that belong to others...
I don't know how difficult it would be to add an extra property to a user record, should be a minute of work in a LAMP environment, I guess. Maybe a shortcut would be to add the "advanced user" property and initially set it equal to the value of the "coordinator" property. Then it can start operation quickly and should it turn out that really users require this without being a coordinator then later some kind of UI can be added to allow setting that. (by the users themselves, by coordinators, or by admins, whatever seems best)
Rob
Further to discussions FYI My system gateway gb7cip acts as Gateway for other UK Subnets that are outside 'my own-loaned' 44net addresses. Which has been agreed with the other UK systems, that are active via 'this gateway' and able to reach the rest of the 44net outside the UK. So there is a requirement to still be able to do this.. (Tick or non tick boxes Network Management) paul g4apl
On 11/04/2019 10:09, Rob Janssen wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44.
Maybe there is a need of a shift of the portal paradigm on allocations.
At the moment, users allocate subnets to a gateway. Maybe a switch to allocating a gateway to a subnet would actually solve the problem:
The subnet owner chooses the gateway as he wishes, which can be his own (which is logically the default choice), or another one (and choosing the wrong one will actually only break his own subnet setup leading to a correct choice later on, without affecting anyone).
Marius, YO2LOJ
On 11.04.2019 14:16, Paul wrote:
Further to discussions FYI My system gateway gb7cip acts as Gateway for other UK Subnets that are outside 'my own-loaned' 44net addresses. Which has been agreed with the other UK systems, that are active via 'this gateway' and able to reach the rest of the 44net outside the UK. So there is a requirement to still be able to do this.. (Tick or non tick boxes Network Management) paul g4apl
On 11/04/2019 10:09, Rob Janssen wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Marius et al,
This is a good idea, however I think it'd be good to add an email notification to the gateway owner that a subnet to route was added, what that subnet is, and contact info of who that subnet belongs to so proper coordination can engage. Without such a user could point his route to an existing host who may not know about this to begin with.
I too host routing for others and having their info helps especially where dynamic commercial ips are concerned.
</$0.02> --- Pardon my brevity but I'm on my smartphone. Sent via the axMail-FAX suite by n1uro.
On April 11, 2019 9:57:07 AM Marius Petrescu marius@yo2loj.ro wrote:
Maybe there is a need of a shift of the portal paradigm on allocations.
At the moment, users allocate subnets to a gateway. Maybe a switch to allocating a gateway to a subnet would actually solve the problem:
The subnet owner chooses the gateway as he wishes, which can be his own (which is logically the default choice), or another one (and choosing the wrong one will actually only break his own subnet setup leading to a correct choice later on, without affecting anyone).
Marius, YO2LOJ
On 11.04.2019 14:16, Paul wrote:
Further to discussions FYI My system gateway gb7cip acts as Gateway for other UK Subnets that are outside 'my own-loaned' 44net addresses. Which has been agreed with the other UK systems, that are active via 'this gateway' and able to reach the rest of the 44net outside the UK. So there is a requirement to still be able to do this.. (Tick or non tick boxes Network Management) paul g4apl
On 11/04/2019 10:09, Rob Janssen wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Brian -
Marius Petrescu -
Paul -
Rob Janssen