3 Dec
2014
3 Dec
'14
6:22 a.m.
I have a serious problem with the new security policy
which does not
allow
to add a subnet if it is not allocated to you in the portal database.
First it is preventing a single gateway to serve multiple hamradios and
their subnets. This is completely against the spirit of hamradio.
It is also preventing to serve IP addresses which are not registered in
the
portal.ampr.org. (i.e. HAMNET Europe (44.168.x.x for France) are
defined in
hamnetdb.net portal. Some 44.76.x.x addresses are not in the portal too
but
only in the host file)
In the Paris area we are developing a HAMNET network using the French
allocation 44.168.x.y. This network is using wifi equipments in 2.3 and
5.6GHz hamradio band. There is a single gateway (mine) and a lot of
sites/subnet/host and backbones which are not mine of course. I have
currently several subnets to add to my gateway but unfortunately I
cannot.
This is holding the deployment of several sites and applications like
DMR
repeaters connections thru HAMNET and other.
I have thought about this new "feature" and I came up with the following
idea.
1) Add a tag to the gateway registration to make the gateway "open" for
other allocation holders.
2) Change the method how networks are affected to gateways. Instead of
adding the network directly under the gateway settings, the "edit
network" page should contain a dropdown list to add the network to one
of the gateway registered to the account holder or to add the network to
one of the "open" gateways.
3) If a network is added to an open gateway, the gateway admin should
receive an email to accept or deny the attachment of the network to his
gateway. If accepted the network will added to encap.txt with the IP of
the "open" gateway.
4) The admin of an "open" gateway should have the right to remove a
network from his gateway.
This solves the "security" issue where a network could be assigned to
any gateway. The shown changes will rely on the network allocation
holder to willingly choose which gateway a network should be routed to
and the gateway admin (if different from network allocation holder) will
have the right to accept or not the traffic.
Comments welcome.
73
--
Marc, LX1DUC
--
www.laru.lu - Luxembourg Amateur Radio Union
www.emcomm.services - Emergency Communication
www.ham-dmr.lu - DMR Infos for HAMs