Object network (whatever you want to call it) if you don't have ASDM and you do it from the CLI, here is the config you will need to do a PAT and the translated address is outside as shown. you would need to change the network 10.1.10.0 to 10.0.0.0. please note that you will need to change the IP to match your network as mine is a little bit different. if you are using ASDM, see the attached step. To get PC1 to browse the internet, you will have to NAT the inside network. You should be able to get a connection between the pc1 and the ASA and vice versa. Now going back to the ASA, you should also make a route to the inside like this: you should add the following command to R1 since i have no config on R1, i would go and assume that you have made a route to the 10.0.0.0 network on R1. Do you think this may be a NAT issue? I did follow a lab where PAT was configured on the ASA using the external IP (192.168.8.250) as a network object, however I was still unable to ping and halted the lab right there to troubleshoot. Just to add additional context, the 192.168.8.X network is the personal home network on which my GNS3 host sits. New flow created with id 4, packet dispatched to next module I am still unable to ping 8.8.8.8 from 10.0.0.100, here is the packet-tracer output as requested:Ĭiscoasa# packet-tracer input inside icmp 10.0.0.100 8 0 8.8.8.8 Okay, you are right in saying the packets are not dropped when doing a packet tracer to 192.168.8.1.

* - candidate default, U - per-user static route, o - ODR I - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP In 192.168.8.250 255.255.255.255 identityĬodes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area Ping from ASA-1 inside interface - UnsuccessfulĬiscoasa# packet-tracer input inside icmp 10.1.0.1 8 0 192.168.8.250 Ping from PC1 to ASA inside interface - Successful Quite simply put, the ASA seems to have no route between two directly connected interfaces (inside & outside). It is worth noting that I am able to ping the inside interface of ASA-1 from both PC1 and R1. When pinging from the firewall I am able to ping outside to 8.8.8.8, however, when pinging from the inside interface, PC1 or R1 I am not able to reach 8.8.8.8. The problem I am having is as follows: I am unable to pass traffic through the firewall from inside to outside with the following Drop-reason: (no-route) No route to host I have a directly connected inside network of 10.1.0.0/24 and an outside network of 192.168.8.0/24. It is fairly straightforward in terms of networks. I have created a lab in GNS3 utilizing the GNS3 VM: I know there are similar posts on these types of issues, however none seem to have assisted me in resolving my issue.

'does gns3 support cisco asa firewalls'