<?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 hello , in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071225#M136278</link>
    <description>&lt;P&gt;hello ,&lt;/P&gt;
&lt;P&gt;thank you for reply &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;have you a doc step by step ( first setup and configuration of asa) &amp;nbsp;and Firepower ?&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2017 07:31:39 GMT</pubDate>
    <dc:creator>mmarouan</dc:creator>
    <dc:date>2017-04-26T07:31:39Z</dc:date>
    <item>
      <title>InterVlan ASA</title>
      <link>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071223#M136274</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;I am new to SA I want to set up an ASA 5525 on a local network in there are VLANs (Vlan print vlan server vlan client vlan wifi Vlan DMZ )&lt;BR /&gt;I want how I can configure it and communicate the print and server vlan and client to each other&lt;BR /&gt;And for the DMZ it must be consulted in public and internally by vlan server and client&lt;/P&gt;
&lt;P&gt;My architecture its :&lt;/P&gt;
&lt;P&gt;for the internal vlan (they have the same physical interface " subinterfaces"):&lt;BR /&gt;Vlan 2 server (172.16.1.0/24) &lt;BR /&gt;Vlan 3 desktop (172.16.2.0/24)&lt;BR /&gt;Vlan 4 printer (172.16.3.0/24)&lt;BR /&gt;Vlan 2,3,4 some secrity level&lt;/P&gt;
&lt;P&gt;and &lt;BR /&gt;Vlan 5 DMZ (172.16.4.0/24)&lt;BR /&gt;For the vlan DMZ it has a unique physical interface. I have an application web server in the zone DMZ which must communicate with a server in the vlan 2 for the replication MSSQL&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;thanks in advance&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 09:15:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071223#M136274</guid>
      <dc:creator>mmarouan</dc:creator>
      <dc:date>2019-03-12T09:15:11Z</dc:date>
    </item>
    <item>
      <title>You should be able to set up</title>
      <link>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071224#M136276</link>
      <description>&lt;P&gt;You should be able to set up 1 physical interface and break it into sub-interfaces for your internal networks. A good example of this is given here:&lt;/P&gt;
&lt;P&gt;http://www.petenetlive.com/KB/Article/0001085&lt;/P&gt;
&lt;P&gt;The DMZ can be a standalone interface as there is only 1 VLAN behind it.&lt;/P&gt;
&lt;P&gt;Once they are broken up into sub-interfaces, each acts as its own interface with a security level and ip address etc. You can create ACL's to allow traffic from lower security level interfaces to higher ones. traffic from a Higher to lower security level should be allowed without the need to add ACL's.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2017 11:36:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071224#M136276</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2017-04-24T11:36:12Z</dc:date>
    </item>
    <item>
      <title>hello ,</title>
      <link>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071225#M136278</link>
      <description>&lt;P&gt;hello ,&lt;/P&gt;
&lt;P&gt;thank you for reply &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;have you a doc step by step ( first setup and configuration of asa) &amp;nbsp;and Firepower ?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2017 07:31:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intervlan-asa/m-p/3071225#M136278</guid>
      <dc:creator>mmarouan</dc:creator>
      <dc:date>2017-04-26T07:31:39Z</dc:date>
    </item>
  </channel>
</rss>

