<?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 Zone-Based-Firewall: crypto map / tunnel interface / zone ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710007#M557211</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are using a CISCO1921-SEC Router. On the "WAN" side we have 1 public IP Adress assigned by DHCP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the moment we are using the WAN Interface with a crypto-map as endpoint of some IPSec connections. We set up a zone-based-firewall with "WAN" and "LAN" zone. In this setup all IPSec Endpoints are on one Interface - connections to the "LAN" zone can be managed by rulesets. What about connections between IPSec connections and the zone "self".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We like to terminate each IPSec connection in a seperated zone. Is this a good idea ?&lt;/P&gt;&lt;P&gt;How can this be configured ?&lt;/P&gt;&lt;P&gt;Each one on a "tunnel inetface" with "tunnel source ..." binding ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give us a hint ... Thanks !! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nachricht geändert durch NISITNETC&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:24:59 GMT</pubDate>
    <dc:creator>NISITNETC</dc:creator>
    <dc:date>2019-03-11T20:24:59Z</dc:date>
    <item>
      <title>Zone-Based-Firewall: crypto map / tunnel interface / zone ?</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710007#M557211</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are using a CISCO1921-SEC Router. On the "WAN" side we have 1 public IP Adress assigned by DHCP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the moment we are using the WAN Interface with a crypto-map as endpoint of some IPSec connections. We set up a zone-based-firewall with "WAN" and "LAN" zone. In this setup all IPSec Endpoints are on one Interface - connections to the "LAN" zone can be managed by rulesets. What about connections between IPSec connections and the zone "self".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We like to terminate each IPSec connection in a seperated zone. Is this a good idea ?&lt;/P&gt;&lt;P&gt;How can this be configured ?&lt;/P&gt;&lt;P&gt;Each one on a "tunnel inetface" with "tunnel source ..." binding ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give us a hint ... Thanks !! &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nachricht geändert durch NISITNETC&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:24:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710007#M557211</guid>
      <dc:creator>NISITNETC</dc:creator>
      <dc:date>2019-03-11T20:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: Zone-Based-Firewall: crypto map / tunnel interface / zone ?</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710008#M557213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt; push ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2011 12:36:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710008#M557213</guid>
      <dc:creator>NISITNETC</dc:creator>
      <dc:date>2011-04-27T12:36:44Z</dc:date>
    </item>
    <item>
      <title>Re: Zone-Based-Firewall: crypto map / tunnel interface / zone ?</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710009#M557214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When tunnels are terminating on the router, that is the self zone, by default all the traffic is allowed, If you want to restrict access you need to create a self zone and add a zone-pair from WAN to Self.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this link will help you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://inkling/?q=node/1305"&gt;http://inkling/?q=node/1305&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Apr 2011 04:09:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710009#M557214</guid>
      <dc:creator>Syed Usaid K</dc:creator>
      <dc:date>2011-04-28T04:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: Zone-Based-Firewall: crypto map / tunnel interface / zone ?</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710010#M557217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; When tunnels are terminating on the router, that is the self zone,&lt;/P&gt;&lt;P&gt;&amp;gt; by&amp;nbsp; default all the traffic is allowed, If you want to restrict access&lt;/P&gt;&lt;P&gt;&amp;gt; you&amp;nbsp; need to create a self zone and add a zone-pair from WAN to Self.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, I set up the self-zone rules and traffic was allowed to the tunnel-end on the system (self).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But we want to set up rules FROM this tunnel-end to the rest of the system. Something like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TUNNEL1 - LAN&lt;/P&gt;&lt;P&gt;TUNNEL2 - LAN&lt;/P&gt;&lt;P&gt;LAN - TUNNEL1&lt;/P&gt;&lt;P&gt;LAN - TUNNEL2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with the situation having a crypto-map in the WAN Interface with all tunnels.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you give ma an example for this ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hope this link will help you,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;A class="jive-link-external-small active_link" href="http://inkling/?q=node/1305"&gt;http://inkling/?q=node/1305&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry, the link is broken ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Apr 2011 07:23:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710010#M557217</guid>
      <dc:creator>NISITNETC</dc:creator>
      <dc:date>2011-04-28T07:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: Zone-Based-Firewall: crypto map / tunnel interface / zone ?</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710011#M557218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;push ... &lt;SPAN __jive_emoticon_name="confused" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/confused.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 May 2011 19:38:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-crypto-map-tunnel-interface-zone/m-p/1710011#M557218</guid>
      <dc:creator>NISITNETC</dc:creator>
      <dc:date>2011-05-06T19:38:20Z</dc:date>
    </item>
  </channel>
</rss>

