08-29-2019 06:15 AM
Dear All,
I've the ASA device with the following config and the problem to config the inside traffic to outside traffic communication. Kindly share the solution for this.
Note: The device with bgp config.
ping from firewall to 10.101.174.178 -- result success
ping from laptop (lap ip: 192.168.12.35) to 192.168.12.33 -- result success
ping from laptop (lap ip: 192.168.12.35) to 10.101.174.178 -- result fail
Config:
-----------------------------
interface GigabitEthernet1/1
nameif outside
security-level 0
ip address 10.101.174.177 255.255.255.0
!
interface GigabitEthernet1/2
nameif inside
security-level 100
ip address 192.168.12.33 255.255.255.0
!
router bgp 100
bgp log-neighbor-changes
address-family ipv4 unicast
neighbor 10.101.174.178 remote-as 200
neighbor 10.101.174.178 activate
network 192.168.12.32 mask 255.255.255.0
no auto-summary
no synchronization
exit-address-family
!
route outside 0.0.0.0 0.0.0.0 10.10.101.174.178 1
!
ASA(config)# show nat
Manual NAT Policies (Section 1)
1 (inside) to (outside) source dynamic any-1 nat-obj-10.101.174.178
translate_hits = 0, untranslate_hits = 0
Auto NAT Policies (Section 2)
1 (inside) to (outside) source dynamic inside_nat interface
translate_hits = 0, untranslate_hits = 0
Regards,
Vijay
Solved! Go to Solution.
08-30-2019 01:46 AM
08-29-2019 07:18 AM
08-30-2019 12:11 AM
Hi Sir,
Thanks for the reply.
I've used this "fixup protocol icmp" but still facing the same issue. Kindly suggest me for other way of solution.
Regards,
Vijay
08-30-2019 12:59 AM
08-30-2019 01:46 AM
08-30-2019 02:05 AM
There is no reason to send me a private message.
You sent this:-
========================from laptop===================
[E:\~]$ ping 10.101.174.178
Pinging 10.100.173.178 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.101.174.178:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Why is it pinging a different IP address (10.100.173.178)?
You didn't send the debug I requested. Does the ping even reach the ASA? The debug would confirm that.
Run a packet capture on the ASA and confirm whether the icmp echo is received on the ASA from the laptop. If not then the laptop is not sending the traffic to the ASA in the first place (which is why the output of the packet-tracert confirms the traffic should be "allowed").
08-30-2019 09:35 AM
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