The up-to-date list that specify IP addresses that belong to each autonomous system is loaded on software update from RIPE DB. The global list of these links is in the file /etc/dpi/asnum.bin.

One may need to modify this list occasionally - to improve NetFlow reports and for use in other services.

The list of changes is prepared in text format. Each record is placed in a new line:

CIDR AS_number
CIDR AS_number
...

Here CIDR specifies the IP addresses range that belongs to the specified system.

This file is converted into the internal format by as2bin utility. It is placed to /etc/dpi/aslocal.bin. DPI picks up the changes from the latest file. The IP addresses' ranges are added to the global list. In case some changes overlap with the global list, the local ranges override existing ones.

cat aslocal.txt|as2bin /etc/dpi/aslocal.bin
service fastdpi reload

Loading the modifications does not require DPI restart (only reload).

To add local addresses to the operator's autonomous system in order to improve NetFlow reports:

vi aslocal.txt
10.0.0.0/8 64511
172.16.0.0/12 64511
192.168.0.0/16 64511
cat aslocal.txt|as2bin /etc/dpi/aslocal.bin
service fastdpi reload

Here 64511 is the operator's autonomous system number.

To apply specific policies to operator's addresses 10.0.0.1 and 10.0.0.2:

vi aslocal.txt
10.0.0.1/32 64512
10.0.0.2/32 64512
cat aslocal.txt|as2bin /etc/dpi/aslocal.bin
service fastdpi reload

In order to avoid overlap of the new autonomous systems' numbers with existing ones, we advise to use the reserved numbers for new systems:

 
64496..64511 are reserved for use in documentation and examples
64512..65534 are reserved for private purposes

There is no analog to aslocal.bin for IPv6, as there is no way to merge these structures like in IPv4 case. It is necessary to add subnets to the general list:

1. convert to text

   bin2as /etc/dpi/asnum6.bin > list.txt

2. add your subnets to text of list.txt
3. merge back

   cat list.txt | as2bin6 /etc/dpi/asnum6.bin