CGNAT. Network Address Translation for IPv4 [Документация 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

    Next revision    		Previous revision
    en:dpi:dpi_brief:test_cases:nat [2024/12/19 14:29] – created elena.krasnobryzhen:dpi:dpi_brief:test_cases:nat [2025/05/26 14:45] (current) – [3. Creating a reverse route (GUI)] elena.krasnobryzh
    Line 18: Line 18:
     </note> </note>
      
    -{{ :dpi:dpi_brief:test_cases:nat_img9.png?nolink&700 |}}+{{ :en:dpi:dpi_brief:test_cases:nat_img9.png?nolink&700 |}}
      
     Let’s start testing. The actions can be performed both via the graphical interface of the SSG and through the CLI. The choice of method is up to the client; both methods are presented in the instructions. Let’s start testing. The actions can be performed both via the graphical interface of the SSG and through the CLI. The choice of method is up to the client; both methods are presented in the instructions.
    Line 74: Line 74:
     Consider a situation where a point-to-point network 10.0.1.0/30 is configured between the routers with the SSG, the router's interface on the subscriber side (R1) has the IP 10.0.1.2, and the router's interface after the SSG (R2) has the IP 10.0.1.1 (see the diagram). Consider a situation where a point-to-point network 10.0.1.0/30 is configured between the routers with the SSG, the router's interface on the subscriber side (R1) has the IP 10.0.1.2, and the router's interface after the SSG (R2) has the IP 10.0.1.1 (see the diagram).
      
    -{{ :dpi:dpi_brief:test_cases:nat_img10.png?nolink&700 |}}+{{ :en:dpi:dpi_brief:test_cases:nat_img10.png?nolink&700 |}}
      
     On router R2, it will be necessary to configure the route to the NAT pool. For Cisco-like CLI, the configuration will look like this: On router R2, it will be necessary to configure the route to the NAT pool. For Cisco-like CLI, the configuration will look like this:
    Line 128: Line 128:
     In the same section “DPI/Services”, CGNAT tab.\\ In the same section “DPI/Services”, CGNAT tab.\\
     In the right column "Subscribers", add a subscriber, select the "Unbound" type, enter the subscriber’s IP, select service 11 “CGNAT” or “NAT 1:1”, check the box "Yes" to enable, select the profile, click "Apply" and "Save".\\ {{:en:dpi:dpi_brief:test_cases:nat_img4.png?nolink&500|}} In the right column "Subscribers", add a subscriber, select the "Unbound" type, enter the subscriber’s IP, select service 11 “CGNAT” or “NAT 1:1”, check the box "Yes" to enable, select the profile, click "Apply" and "Save".\\ {{:en:dpi:dpi_brief:test_cases:nat_img4.png?nolink&500|}}
    - 
     ====3. Creating a reverse route (GUI)==== ====3. Creating a reverse route (GUI)====
     To route reverse traffic to the NAT pool towards the subscribers, it will be necessary to create a route to the NAT pool on the router after the SSG and make this route known to the other routers in the network. The process is the same as in Test 1. The steps and commands do not change. To route reverse traffic to the NAT pool towards the subscribers, it will be necessary to create a route to the NAT pool on the router after the SSG and make this route known to the other routers in the network. The process is the same as in Test 1. The steps and commands do not change.
    - 
     ====4. Checking traffic flow and interface orientation (GUI)==== ====4. Checking traffic flow and interface orientation (GUI)====
     In the GUI, navigate to DPI > Statistics > NAT Statistics\\ {{:en:dpi:dpi_brief:test_cases:nat_img5.png?nolink&800|}}\\ In the GUI, navigate to DPI > Statistics > NAT Statistics\\ {{:en:dpi:dpi_brief:test_cases:nat_img5.png?nolink&800|}}\\