Chris, Thanks for the work.
In the portal gateway network allocations, I think a free typing instead of the lis twill be more useful. It'll allow to add allocations which were not classified as tunnel at the time of the creation and more important i twill allow the group multiple allocated subnets in a single one for gateways which are handling multiple allocations. This will reduce the size of the routing table.
73 de Remi F6CNB
Hi Remi,
Thanks for the work.
You are welcome :-)
In the portal gateway network allocations, I think a free typing instead of the lis twill be more useful. It'll allow to add allocations which were not classified as tunnel at the time of the creation and more important i twill allow the group multiple allocated subnets in a single one for gateways which are handling multiple allocations. This will reduce the size of the routing table.
Do you mean to add a 44.x.x.x network to a gateway? If so, it used to be a free text filed, but people were adding networks that were not allocated, I think as a shortcut - rather than getting a network allocated then adding it to a gateway, they were just adding it unallocated which resulted in the database being inaccurate.
So now you have to select from a drop down box of allocated networks that have their connection type set to tunnel, this ensures the database accurately reflects the actual situation with regards to the gateways.
Thanks, Chris