11-08-2021 01:53 AM
Hello,
I am student and I need help with firewall connection.
I can ping to 192.168.10.2 but I can not ping 192.168.10.1
How can I configure firewall to connect it with different subnet?
Thank you for help.
Regards B.
11-08-2021 02:24 AM
It is just a guess as you don't provide any config:
The ASA needs a route to any remote destination. If you have a default rout to the internet (on the left) and no other route, the ASA does not know that the 192.168.100.0 network is on the right. Add a static route for that network pointing to the next hop 192.168.10.2 and it could start working.
11-08-2021 08:43 AM
I do not understand.
11-08-2021 03:55 AM
Hello,
post the zipped Packet Tracer project (.pkt) file...
11-08-2021 08:45 AM
11-10-2021 12:21 AM
Hello
See attached revised PT file,
It seems in packet tracer network translation(NAT) doesn’t work, so i changed your static routing to accommodate connectivity from host to r2,
Lastly applied an access-list for external echo-reply to be allowed through firewall
11-28-2021 09:37 AM
Hello,
Thank you for working connection, but I do not understand what did you change and where.
I will be very grateful for explanations.
I want to understand this, not just have a working solution.
Regards
Bogumił
11-28-2021 10:00 AM
Hello,
the easiest way to resolve this is probably to change the default inside route to a more specific route:
--> no route inside 0.0.0.0 0.0.0.0 192.168.10.2 1
--> route inside 192.168.100.0 255.255.255.0 192.168.10.2
11-28-2021 01:23 PM
Hello,
It not helps. Ping does not cross firewall. I get message: Destination host unreachable.
I do not how to solve the problem.
Regards
Bogumił
11-28-2021 01:31 PM
Hello,
your original question was:
--> I can ping to 192.168.10.2 but I can not ping 192.168.10.1
From which source IP address can you not ping 192.168.10.1 ?
11-28-2021 01:39 PM
Ping from PC0 reach IP 192.168.10.1
I do not know why but from other side of firewall (IP 192.168.1.2 and the rest) returns: Destination host unreachable.
11-29-2021 01:17 AM
Hello
As stated I changed the static routing you had to allow host to rtr communication and allowed ICMP echo (ping reply) to enter the ASA fw.
By default ASA firewalls (like majority of all firewall) block traffic originating from a low security interface ( such as a wan/public interface) to enter the FW unless you allow it through so any ping originating from within your network (behind the firewall) to a wan host will be allowed however its return ping reply(echo reply will be blocked
You can allow this traffic by either enabling icmp inspection via its global inspection policy or use an access-list.
11-29-2021 01:41 AM
Hello,
I am the beginner. I do not understand. I do not know what rtr communication is.
I need explanation step by step. In which devices what command you wrote?
Without this information I am not able recreate your solution.
Regards
Bogumił
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide