<?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 The reason it is working is in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619065#M197050</link>
    <description>&lt;P&gt;The reason it is working is because when the client connects to the server an entry in the state table is made for that connection and then the packet is sent to the server.&lt;/P&gt;&lt;P&gt;The return packet is not checked against the acl applied inbound on the inside interface because there is an existing entry in the state table so it is allowed.&lt;/P&gt;&lt;P&gt;The acl on your inside interface is applied when a connection is initiated from a device on the inside of the ASA because there isn't an entry already in the state table.&lt;/P&gt;&lt;P&gt;That is how stateful firewalls work, if the initial packet is allowed then the return traffic is allowed without having to allow it explicitly in an acl.&lt;/P&gt;&lt;P&gt;If they didn't then you are correct in what you say, an entry would be needed in your inside acl because there would be no state for the firewall to use.&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2015 22:37:34 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2015-03-27T22:37:34Z</dc:date>
    <item>
      <title>Stateful Firewall and how it functions ?</title>
      <link>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619064#M197049</link>
      <description>&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;Hello Everyone,&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); min-height: 8pt; height: 8pt; background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;I am little bit confused between stateful firewall and how it works. I know that stateful firewall keeps track of the connections initiated by internal network or from the outside network i.e internet.&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); min-height: 8pt; height: 8pt; background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;So does that mean if the connection is initiated b&lt;SPAN style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 10pt; list-style: none; margin: 0px; outline-width: 0px; padding: 0px; background: transparent;"&gt;y outside host from internet to the inside host then we dont need to allow access-list when our internal host will respond to the request to the outside host?&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); min-height: 8pt; height: 8pt; background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;This confusion is because in our network we have a site to site (LAN to LAN) VPN between our main site to one of the branch office. Users from branch offices are accessing VM that are residing on the servers located in our main site. Now our firewall is allowing outside connection from the branch office for the VM to inside server and the crypto map is allowing interesting traffic from the server to the remote users. Also we used nat 0&amp;nbsp; to not to nat the traffic from our server to the branch office. Everything is working fine and the tunnel is UP. However i am not sure why we didnt allow this connection in our access-list on the inside interface of the firewall?&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); min-height: 8pt; height: 8pt; background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 12px; list-style: none; margin-bottom: 0px; outline-width: 0px; padding: 0px; font-family: Arial; line-height: 18px; color: rgb(82, 82, 82); background-image: initial; background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;"&gt;&lt;SPAN style="border: 0px; border-collapse: collapse; border-spacing: 0px; font-size: 10pt; list-style: none; margin: 0px; outline-width: 0px; padding: 0px; background: transparent;"&gt;In my understanding when our server will respond to the request made by outside users this connection should be allowed on the access-list on the inside interface otherwise the packet will be dropped? Why this setup is working without this inside access-list ?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:30:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619064#M197049</guid>
      <dc:creator>Vivek Singh</dc:creator>
      <dc:date>2019-03-12T05:30:22Z</dc:date>
    </item>
    <item>
      <title>The reason it is working is</title>
      <link>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619065#M197050</link>
      <description>&lt;P&gt;The reason it is working is because when the client connects to the server an entry in the state table is made for that connection and then the packet is sent to the server.&lt;/P&gt;&lt;P&gt;The return packet is not checked against the acl applied inbound on the inside interface because there is an existing entry in the state table so it is allowed.&lt;/P&gt;&lt;P&gt;The acl on your inside interface is applied when a connection is initiated from a device on the inside of the ASA because there isn't an entry already in the state table.&lt;/P&gt;&lt;P&gt;That is how stateful firewalls work, if the initial packet is allowed then the return traffic is allowed without having to allow it explicitly in an acl.&lt;/P&gt;&lt;P&gt;If they didn't then you are correct in what you say, an entry would be needed in your inside acl because there would be no state for the firewall to use.&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2015 22:37:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619065#M197050</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-03-27T22:37:34Z</dc:date>
    </item>
    <item>
      <title>Yeah i got your point and</title>
      <link>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619066#M197051</link>
      <description>&lt;P&gt;Yeah i got your point and that cleared my doubt as well. Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2015 12:03:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stateful-firewall-and-how-it-functions/m-p/2619066#M197051</guid>
      <dc:creator>Vivek Singh</dc:creator>
      <dc:date>2015-04-08T12:03:29Z</dc:date>
    </item>
  </channel>
</rss>

