<div>
It doesn't look like your encryption domain access lists are an exact inverse match.
</div>


It doesn't look like your encryption domain access lists are an exact inverse match.

<div>
<div class="content wysiwyg-content">
Team,<br />
<br />
we have established a tunnel between ASA 5515-X 8.6(1) version to 8.2 version ASA 5510 firewall.<br />
<br />
<br />
Issue is Traffic is not passsing and packets are not encrypting from ASA 5515-X side<br />
<br />
<br />
Pls see the attachements of &nbsp;the sanitised configurtion &nbsp;and Phase-2 tunnel status of ASA 5515-X side firewall <br />
<br />
<br />
Pls treat this is an urgent and very important and reply asap as you people might have 24*7 support<br />
<br />
<br />
<br />
<br />
Regards<br />
Ramu<br />
<a href="https://filedb.experts-exchange.com/incoming/2013/07_w28/664922/Santised-s2s-confguraiton.txt" target="_blank" class="file-inline" title="ASA 5515-X S2S configuraiton (1 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Santised-s2s-confguraiton.txt</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2013/07_w28/664926/Error-Phase2.TXT" target="_blank" class="file-inline" title="phase-2 status (1 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Error-Phase2.TXT</a>
</div>
</div>


Error-Phase2.TXT

Santised-s2s-confguraiton.txt

Team,

we have established a tunnel between ASA 5515-X 8.6(1) version to 8.2 version ASA 5510 firewall.


Issue is Traffic is not passsing and packets are not encrypting from ASA 5515-X side


Pls see the attachements of  the sanitised configurtion  and Phase-2 tunnel status of ASA 5515-X side firewall 


Pls treat this is an urgent and very important and reply asap as you people might have 24*7 support




Regards
Ramu

Cisco site-site tunnnel issue

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

Internet Protocol Security (IPsec) is a protocol suite for secure Internet Protocol (IP) communications by authenticating and encrypting each IP packet of a communication session. IPsec includes protocols for establishing mutual authentication between agents at the beginning of the session and negotiation of cryptographic keys to be used during the session. IPsec can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host). IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite.