NATing for Office Connectivity

Sample configuration for an office network via CGNAT n/w: 172.16.28.144/29  231.4: RP/0/RSP0/CPU0:EKM-GW.ASR-9K#sh run | inc 172.16.28.144 172.16.28.144/29 202.88.231.3 172.16.28.144/29 202.88.231.3 Configuration: router static address-family ipv4 unicast 172.16.28.144/29 202.88.231.3 vrf ASNET-INunlimit-Chn address-family ipv4 unicast 172.16.28.144/29 202.88.231.3 231.3: RP/0/RSP0/CPU0:ASR9006-ISM# interface BVI1019 ipv4 address 172.16.28.145 255.255.255.248 ipv4 access-group cgnat-office ingress ! Access list: ipv4 access-list cgnat-office 20 permit […]

Continue Reading

Routing for CGNAT via Mettle NAS

Configuration for natted private IPs routed throught Mettle. Here, for NAS 173, 1. routing: Gateway:VRF > core-60 > NAS 2. add private networks in ACL “gpon98” corresponding to the route map “MettleLimited” applied on the Te4/7 interface on core, which is the routing port, is connected to NAS’s WAN. eg: GW: router static address-family ipv4 […]

Continue Reading

CGNAT configuration for Office connections

A common access list for Office connections using private ips for accessing mail, crm etc. is available on 231.3 ipv4 access-list cgnat-office 20 permit ipv4 172.16.26.156 0.0.0.3 any nexthop1 ipv4 202.88.231.111 30 permit ipv4 172.16.0.0 0.0.255.255 host 164.100.80.207 nexthop1 ipv4 202.88.231.111 40 permit ipv4 172.16.0.0 0.0.255.255 host 202.143.96.173 nexthop1 ipv4 202.88.231.111 50 permit ipv4 172.16.0.0 […]

Continue Reading

Routing for CGNAT

Via Inventum/Unify Via Mettle NAS Office connectivity Invnetum As L2 Via Inventum/Unify router static address-family ipv4 unicast vrf INVENTUM-IN-ALL address-family ipv4 unicast 172.17.161.0/24 202.88.231.75 Via Mettle NAS router static address-family ipv4 unicast vrf GPON-IN-All address-family ipv4 unicast 100.127.128.0/21 202.88.231.100 Office connectivity router static address-family ipv4 unicast vrf ASNET-INunlimit-Chn address-family ipv4 unicast 172.16.28.144/29 202.88.231.111 Invnetum As […]

Continue Reading