Configuring autonomous systems [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:dpi:dpi_options:opt_statistics:statistics_asn:start [2020/02/05 17:30] – ↷ Page moved from en:dpi:dpi_options:base_functionality:opt_statistics:statistics_asn:start to en:dpi:dpi_options:opt_statistics:statistics_asn:start lexx26en:dpi:dpi_options:opt_statistics:statistics_asn:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
-====== 4 Configuring autonomous systems ====== 
-{{indexmenu_n>4}} 
-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.** 
  
-<note warning>Please do not modify it to preserve its update method.</note> 
- 
-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: 
- 
-<code> 
-CIDR AS_number 
-CIDR AS_number 
-... 
-</code> 
- 
-Here CIDR specifies the IP addresses range that belongs to the specified system. 
- 
-<note important>In order to check whether the IP belongs to autonomous system the DPI uses classical DIR24 algorithm with limited number of /24 networks that can be splited into smaller subnets (/25..../32). There can be no more than 8192 such subnets.</note> 
- 
-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. 
- 
-<code> 
-cat aslocal.txt|as2bin /etc/dpi/aslocal.bin 
-service fastdpi reload 
-</code> 
- 
-Loading the modifications does not require DPI restart (only reload). 
- 
-<note important>In case of crossing the global list by IP the local settings will replace the existing entries in it.</note> 
- 
-====== Examples for IPv4 ====== 
- 
-To add local addresses to the operator's autonomous system in order to improve NetFlow reports: 
- 
-<code> 
-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 
-</code> 
- 
-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: 
- 
-<code> 
-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 
-</code> 
- 
-In order to avoid overlap of the new autonomous systems' numbers with existing ones, we advise to use the reserved numbers for new systems: 
-<code>  
-64496..64511 are reserved for use in documentation and examples 
-64512..65534 are reserved for private purposes 
-</code> 
- 
-====== Examples for Ipv6 ====== 
- 
-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: 
- 
-  - convert to text 
-<code>bin2as /etc/dpi/asnum6.bin > list.txt</code> 
-  - add your subnets to text of list.txt 
-  - merge back 
-<code>cat list.txt | as2bin6 /etc/dpi/asnum6.bin</code>