db-schema

Author SHA1 Message Date

Author	SHA1	Message	Date
Rene Krenn	eef8b3b539	TT#148100 support fast allowed_ip lookup for IPv4 and IPv6 rationale: -ipv6 allowed_ip adresses were not yet supported in kamailio -the current ipv4 allowed_ip check has bad performance this change introduces a new UDF to check the UA ip against allowed_ip and man_allowed_ip preferences in a fast and convenient way, ie.: SELECT provisioning.ip_is_allowed( <subscriber_uuid>, <ipv4_or_ipv6_address> ); the check is based on range queries supported by indexes, following the proven approach we already use for roaming/ billing_networks. it requires to transfrom IPnet values of existing data into numerical representation of the network start (network) and end (broadcast) addresses. mariadb does not support arithmetic or bitwise operation for varbinary or numerical values larger than bigint, which is required to calculate network and broadcast adresses. the change therefore provides an own implementation for large integer operations. it works with hex string representations, which fits the existing mariadb "hex()", "unhex()" and "inet6_aton/ntoa()" functions. Change-Id: I9dbaa769252babf168243167c061f035f0f43242 (cherry picked from commit `7c1453e460`)	4 years ago

Rene Krenn

TT#148100 support fast allowed_ip lookup for IPv4 and IPv6

rationale:
-ipv6 allowed_ip adresses were not yet supported in kamailio
-the current ipv4 allowed_ip check has bad performance

this change introduces a new UDF to check the UA ip against
allowed_ip and man_allowed_ip preferences in a fast and
convenient way, ie.:

  SELECT provisioning.ip_is_allowed(
    <subscriber_uuid>,
    <ipv4_or_ipv6_address>
  );

the check is based on range queries supported by indexes,
following the proven approach we already use for roaming/
billing_networks.

it requires to transfrom IPnet values of existing data into
numerical representation of the network start (network) and
end (broadcast) addresses.

mariadb does not support arithmetic or bitwise operation
for varbinary or numerical values larger than bigint, which
is required to calculate network and broadcast adresses.

the change therefore provides an own implementation for
large integer operations. it works with hex string
representations, which fits the existing mariadb "hex()",
"unhex()" and "inet6_aton/ntoa()" functions.

Change-Id: I9dbaa769252babf168243167c061f035f0f43242
(cherry picked from commit 7c1453e460)

1 Commits (mr10.2.1)