Hot answers tagged

6

For NAT to work, you must specify a standard access list to identify the traffic that should be NATted. You reference the access list (source list 1) correctly, but you have not created the access list. Correct NAT config would be: ip nat inside source list 1 interface GigabitEthernet0/0 overload access-list 1 permit 192.168.1.0 0.255.255.255 Your extended ...


2

The vendor (AT&T) who provided the new APNs also provides a managed router on-site where the private traffic arrives. They added a NAT on that device of the udp traffic from the mobile devices to the old public address, and they translate that destination public address to a private address in our network. So our internal network (beyond the managed ...


1

You have a typo in your access-list that was not allowing traffic to enter the VPN tunnel: access-list 100 permit ip 192.168.30.0 0.0.0.255 103.168.10.0 0.0.0.255 access-list 100 permit ip 192.168.30.0 0.0.0.255 103.168.20.0 0.0.0.255 access-list 100 permit ip 192.168.40.0 0.0.0.255 103.168.10.0 0.0.0.255 access-list 100 permit ip 192.168.40.0 0.0.0.255 103....


1

While this is an old question, it may still be relevant in searches - so I'll attempt a general answer. I think you're needlessly complicating things by trying to cascade multiple zones. You define zones by trust level. If two zones have the same level of trust they should really be just one. If you need to route between subnets in the same zone there's no ...


Only top voted, non community-wiki answers of a minimum length are eligible