![]() ![]() ![]() It is used as a gateway for routing your private subnets (i.e., non-routable VLANs) within the GRE tunnel. NOTE: The IP address should not be part of any subnet in your network, nor does it have to be routable in your network. pool tunnel-pool : IP address is allocated from the specified tunnel pool.internal: IP address is allocated from the Remote-Node pool. ![]() NOTE: This address should be a unique, non-routable IP address. This represents the entrance to the tunnel. For more information on creating a routing ACL, see ip access-list route. When you associate a routing ACL to inbound traffic on a managed device terminating a 元 GRE tunnel, that ACL can forward traffic as normal, route traffic to a nexthop router on a nexthop list, or redirect traffic over an 元 GRE tunnel or tunnel group. The tunnel ID used here does not have to match the tunnel ID used in the other managed device.Īuto generates the tunnel endpoint for the specified peer device.Īttach a route ACL to a 元 GRE tunnel interface. You can direct traffic into the tunnel using a static route (by specifying the tunnel as the next hop for a static route) or a session-based ACL. The only Layer-3 GRE modes supported are IPv4 encapsulated in IPv4 and IPv6 encapsulated in IPv6. In Layer-3 GRE tunnels, IPv6 encapsulated in IPv4 and IPv4 encapsulated in IPv6 are not supported. The default is an IPv4 Layer-3 GRE tunnel ( tunnel mode gre ip). This command configures a Layer-2 or Layer-3 GRE tunnel between a managed device and another GRE-capable device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |