Monday, January 15, 2018

[Help] - NAT/Routing - Inside network cannot reach Internet in Lab Environment

Hello All,

I am studying for CCNA Security. I have ASAv and Windows Appliance, along with a Router/NAT Cloud and Ethernet Switches(shown in first link).

I am having a problem: The 10.0.0.0/24 and 10.0.1.0/24 Network's, which are in the inside interface on the ASA, cannot reach the internet via the NAT Cloud.

I am able to ping Google from ASA and Windows Appliance can also reach the Internet on a browser. However, the Router/ VPCS are completely unable to reach the Internet.

In fact, the Router cannot even ping the ASA's Outside interface(Gig0/1 - 192.168.122.58). I am not sure why.

I have Routing set up on the Router/ASA. The Router has a default route to the ASA Gig0/0(10.0.0.1). The ASA can ping the Router, the Router can ping 10.0.0.1, not 192.168.122.58).

I actually have a home lab with an ASA and switches. I implemented NAT on my ASA, and Inside network has connectivity. I have only used Switches + ASA. So maybe the problem lies with the Router, maybe it's GNS3 and the NAT Cloud.

There are no access-lists on the ASA or Router. Both Router/ASA have default routes, Router to 10.0.0.1, ASA to NAT Cloud. There are not Zones.

1.) Network Topology - http://ift.tt/2B3mlmM

2.)Ping Results on ASA/Router - http://ift.tt/2DdOb61

EDIT: I have made the same NAT Configurations on the ASA in GNS3 as the ASA in my homelab. I should mention the the ASAv in GNS3 is a 5520, and the ASA at my home lab is a 5506-x. I did both Auto-NAT and Manual-NAT. The configuration is not the problem. But just in case, here is the config. I'll show with ASDM so it may be easier to read. You can see the Windows Appliance has Internet connection since it's being NAT'd with the NAT cloud, not ASA.

http://ift.tt/2DevkYg



No comments:

Post a Comment