CG-NAT and NAT (Service 11) [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • 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:faq:cgnat [2024/10/14 12:12] – elena.krasnobryzhen:dpi:faq:cgnat [2025/10/31 09:03] (current) – elena.krasnobryzh
    Line 71: Line 71:
       - Subscribers under blocking (Service 5 + policing) should be placed in a separate NAT Pool to avoid impacting active subscribers. For instance, an iPhone may establish many sessions searching for an active service.   - Subscribers under blocking (Service 5 + policing) should be placed in a separate NAT Pool to avoid impacting active subscribers. For instance, an iPhone may establish many sessions searching for an active service.
       - Create sparse pools and separate clients into different NAT Pools by type: individuals and corporate users.   - Create sparse pools and separate clients into different NAT Pools by type: individuals and corporate users.
    -  - Monitor clients generating high load and work with them. For receiving, processing, and storing NetFlow from DPI, we suggest using the [[en:dpi:dpi_components:qoestor|QoE Store software product for statistics collection]] and the [[en:dpi:dpi_components:dpiui|DPIUI2 graphical interface]]. You can analyze subscriber traffic and conclude that their PC is infected.+  - Monitor clients generating high load and work with them. For receiving, processing, and storing NetFlow from DPI, we suggest using the [[en:dpi:qoe_analytics|QoE Store software product for statistics collection]] and the [[en:dpi:dpi_components:dpiui|DPIUI2 graphical interface]]. You can analyze subscriber traffic and conclude that their PC is infected.
     </accordion-item> </accordion-item>
      
    Line 103: Line 103:
      
     <accordion-item title="6. How to Assign a Specific Address to a Subscriber with NAT 1:1?"> <accordion-item title="6. How to Assign a Specific Address to a Subscriber with NAT 1:1?">
     +<note warning>The method described below is inactive when ''rx_dispatcher=1''</note>
     If a subscriber has only one private address and it is necessary to assign a specific public address to the subscriber, the dependency between the private and public addresses must be considered, which is imposed by the non-blocking address dispatching algorithm in DPI. If a subscriber has only one private address and it is necessary to assign a specific public address to the subscriber, the dependency between the private and public addresses must be considered, which is imposed by the non-blocking address dispatching algorithm in DPI.
      
    Line 132: Line 133:
     <code>fdpi_ctrl load profile --ip 10.0.0.15 --service 11 --profile.json '{ "nat_ip_pool" : "188.99.99.27/32", "nat_type" : 1 }'</code> <code>fdpi_ctrl load profile --ip 10.0.0.15 --service 11 --profile.json '{ "nat_ip_pool" : "188.99.99.27/32", "nat_type" : 1 }'</code>
      
    -<note>Parameter description [[en:dpi:opt_cgnat:cgnat_settings#parameters_and_possible_values|via this link]]</note>+<note>Parameter description [[en:dpi:opt_cgnat:сgnat_settings#parameters_and_possible_values|via this link]]</note>
     </accordion-item> </accordion-item>
      
     <accordion-item title="7. NAT Diagnostics"> <accordion-item title="7. NAT Diagnostics">
    -<note>Parameter description [[en:dpi:opt_cgnat:cgnat_settings#parameters_and_possible_values|via this link]]</note>+<note>Parameter description [[en:dpi:opt_cgnat:сgnat_settings#parameters_and_possible_values|via this link]]</note>
      
     1. The pools in the profile must be of the same size ((The requirement is not relevant if ''rx_dispatcher=1'' or ''rx_dispatcher=2'')).  1. The pools in the profile must be of the same size ((The requirement is not relevant if ''rx_dispatcher=1'' or ''rx_dispatcher=2'')).