Jonathan Fitzgerald
asked on
Having issues with a NAT push from Sonicwall to ASA, had been working before, stopped routing traffic and failing on packet trace on ASA side.
Issues with NAT on Sonicwall to ASA VPN
ASA File - ASA---Clean---03.03.txt
When running packet trace having an issue with ACL going out of the ASA
ASA File - ASA---Clean---03.03.txt
When running packet trace having an issue with ACL going out of the ASA
ASKER
Please see the attached updated config
Remote connection coming from External IP: 172.89.95.101
The connection from Remote LAN: 192.168.15.1/24
ASA Internal Side: 10.0.30.1/24
ASA-Clean03.05.2020.txt
Remote connection coming from External IP: 172.89.95.101
The connection from Remote LAN: 192.168.15.1/24
ASA Internal Side: 10.0.30.1/24
ASA-Clean03.05.2020.txt
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Unfortunately with the obfuscation you have applied, the config is not consistent.
Rather than using asterisks to obfuscate, I would suggest replacing words with a different word, and then for IPv4 public addresses, just use the first three octets of an otherwise unused (in the config) RFC1918 address spacve, so in this case, I would suggest using 172.16.1