yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
f1bf1560d625de04ad15ae06d78bd54371d2d45d
doc-exports/docs/er/umn/er_01_0121.html
Qin Ying, Fan 4d053b2368 ER UMN 20240805 version 
Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com>
Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
2024-09-02 09:40:01 +00:00

5.6 KiB
Raw Blame History

Why Traffic Can't Be Forwarded from a VPC with a Route Destination of 0.0.0.0/0 to Its Enterprise Router?

Scenarios

Traffic cannot be forwarded from a VPC to the enterprise router that it is attached to if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:
  • An ECS in the VPC has an EIP bound.

    Refer to solution 1.

  • ELB, NAT Gateway, VPC Endpoint and DCS are deployed in the VPC.

    Refer to solution 1 or solution 2.

    When method 2 is used, if a VPC wants to access public network, the traffic from the VPC is forwarded to the enterprise router and then to the public network. For this reason, if a VPC accesses the public network using an EIP, do not use this method.

Solutions

Select a solution based on your actual service scenario.
  • Solution 1: Change the destination (0.0.0.0/0) of the default route to a specific IP address range, for example, 192.168.0.0/16.
  • Solution 2: Add eight routes with specific IP address ranges as the destination to replace the default route (with a destination of 0.0.0.0/0).
    Table 1 Route destinations and next hops

    Destination

    Next Hop

    128.0.0.0/1

    Enterprise router

    64.0.0.0/2

    Enterprise router

    32.0.0.0/3

    Enterprise router

    16.0.0.0/4

    Enterprise router

    8.0.0.0/5

    Enterprise router

    4.0.0.0/6

    Enterprise router

    2.0.0.0/7

    Enterprise router

    1.0.0.0/8

    Enterprise router
Parent topic: FAQ