<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SCEP through ASA L2L VPN in VPN</title>
    <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221507#M82201</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;first of all thanks for your response and yes you've tracked my problem correct&lt;/P&gt;&lt;P&gt;I thought about your solution, but I'm not sure that it works because (as far as i remember) for logging and snmp to work you have to configure, that the (remote) syslog / SNMP server is locatet behind the inside interface to make encr. work. &lt;/P&gt;&lt;P&gt;But you don't have an option saying where the trustpoint is located.&lt;/P&gt;&lt;P&gt;I'll of course give it a try in my lab and update everyone on that issuee&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Jun 2013 10:50:06 GMT</pubDate>
    <dc:creator>Michael Dombek</dc:creator>
    <dc:date>2013-06-06T10:50:06Z</dc:date>
    <item>
      <title>SCEP through ASA L2L VPN</title>
      <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221505#M82199</link>
      <description>&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;i’ve just hit an odd problem with an ASA | PKI | VPN Tunnel setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;I tried to connect a remote ASA to a central pki server using SCEP.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;The setup looks like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;ASA-Remote&amp;nbsp; &amp;lt;===L2L-VPN===&amp;gt;&amp;nbsp; ASA-Central --- PKI Server&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;The ASA remote has a trustpoint configured using the ip address of the PKI Server &lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; line-height: normal; padding-left: 30px;"&gt;crypto ca trustpoint pki&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; line-height: normal; padding-left: 60px;"&gt;revocation-check crl&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; line-height: normal; padding-left: 60px;"&gt;&lt;SPAN&gt;enrollment url &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://192.168.191.5:8080/xxxx"&gt;http://192.168.191.5:8080/xxxx&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; line-height: normal; padding-left: 60px;"&gt;serial-number&lt;/P&gt;&lt;P style="margin-bottom: 0.0001pt; line-height: normal; padding-left: 60px;"&gt;crl configure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;Capturing the ASA-Remote outside interface I can se that the ASA-Remote is sending pakets to the PKI-Server &lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;&amp;lt;publicIP-ASA-REMOTE&amp;gt;.15252 &amp;gt; 192.168.191.5.8080&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; line-height: normal;"&gt;This indicates to me that the ASA is not using the VPN Tunnel between ASA-Remote and ASA-Central for this communication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any Ideas how to fix this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers and thanks Michael&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2013 09:55:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221505#M82199</guid>
      <dc:creator>Michael Dombek</dc:creator>
      <dc:date>2013-06-06T09:55:53Z</dc:date>
    </item>
    <item>
      <title>SCEP through ASA L2L VPN</title>
      <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221506#M82200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just commenting with regards getting the ASA to tunnel the connections it generates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your purpose is just to tunnel some traffic from the actual remote ASA device to a server on the other site then I guess you could considering adding the remote ASA public IP address to the crypto ACL. Since it seems that the ASA is just using the source address of the interface behind which the routing table is telling the destination address is found on?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess you would need something like (presuming software levels, ACL names, interface names etc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Remote&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list L2LVPN permit ip host &lt;REMOTE asa="" public="" ip=""&gt; host &lt;SERVER ip=""&gt;&lt;/SERVER&gt;&lt;/REMOTE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Central&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list L2LVPN permit ip host &lt;SERVER ip=""&gt; host &lt;REMOTE asa="" public="" ip=""&gt;&lt;/REMOTE&gt;&lt;/SERVER&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list INSIDE-NAT0 permit ip host &lt;SERVER ip=""&gt; host &lt;REMOTE asa="" public="" ip=""&gt;&lt;/REMOTE&gt;&lt;/SERVER&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (inside) 0 access-list INSIDE-NAT0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would ofcourse make it impossible for the server to be in connection with the remote ASA in any other way than the L2L VPN. Then again I am not sure if that is any problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would imagine this should be possible since SNMP, Syslog sending etc can be done in the same way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 10:21:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221506#M82200</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-06T10:21:15Z</dc:date>
    </item>
    <item>
      <title>SCEP through ASA L2L VPN</title>
      <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221507#M82201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;first of all thanks for your response and yes you've tracked my problem correct&lt;/P&gt;&lt;P&gt;I thought about your solution, but I'm not sure that it works because (as far as i remember) for logging and snmp to work you have to configure, that the (remote) syslog / SNMP server is locatet behind the inside interface to make encr. work. &lt;/P&gt;&lt;P&gt;But you don't have an option saying where the trustpoint is located.&lt;/P&gt;&lt;P&gt;I'll of course give it a try in my lab and update everyone on that issuee&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 10:50:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221507#M82201</guid>
      <dc:creator>Michael Dombek</dc:creator>
      <dc:date>2013-06-06T10:50:06Z</dc:date>
    </item>
    <item>
      <title>SCEP through ASA L2L VPN</title>
      <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221508#M82202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I configured/tested the SNMP and Logging (+L2LVPN) once for someone asking here on the forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will see if I can find the thread from the CSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But in short, I had defined the ASA to use the "outside" interface in both logging and snmp configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 10:59:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221508#M82202</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-06T10:59:52Z</dc:date>
    </item>
    <item>
      <title>Re: SCEP through ASA L2L VPN</title>
      <link>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221509#M82203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good thing we have Google. Faster to find the thread through there&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the thread I mentioned&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/2141385" rel="nofollow"&gt;https://supportforums.cisco.com/thread/2141385&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;EDIT: &lt;/STRONG&gt;Actually it seems that this thread is also linked to another one &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 11:01:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/vpn/scep-through-asa-l2l-vpn/m-p/2221509#M82203</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-06T11:01:07Z</dc:date>
    </item>
  </channel>
</rss>

