11 Apr
2019
11 Apr
'19
8:55 a.m.
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(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net