<?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 Re: stateful feature in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/stateful-feature/m-p/904947#M974663</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;A standard access-list on a router is not stateful whereas a firewall like the pix does keep state ie. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when a conversation between a two machines is setup with a firewall in between the traffic path the firewall keeps track of not just the IP address/port number but also the TCP flags that are used in the packet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if i initiate a connection to a server using telnet my intial packet has &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source IP address: 192.168.5.1 (my client) &lt;/P&gt;&lt;P&gt;source port: 23467 ( random generated port) &lt;/P&gt;&lt;P&gt;destination IP address: 172.16.10.1 (telnet server) &lt;/P&gt;&lt;P&gt;destination port: 23 ( telnet port ) &lt;/P&gt;&lt;P&gt;TCP Flag: SYN &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The firewall will enter this into it's state table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when the server responds &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;source IP address: 172.16.10.1 &lt;/P&gt;&lt;P&gt;source port: 23 &lt;/P&gt;&lt;P&gt;destination IP address: 192.168.5.1 &lt;/P&gt;&lt;P&gt;destination port: 23467 &lt;/P&gt;&lt;P&gt;TCP Flags SYN/ACK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The firewall receives this packet, checks it's state table and realises this is a return packet to the initial packet sent out by the client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if the above packet from the server was sent to the client, but the client had not actually sent a packet first the firewall would drop the packet because it has no entry in it's state table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An router access-list does not keep state of the connection in the same way. It merely checks the packet against it's access-list and permits or denies it but it has no concept of "return" traffic or a packet being part of an ongoing communication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Sep 2007 12:20:29 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2007-09-21T12:20:29Z</dc:date>
    <item>
      <title>stateful feature</title>
      <link>https://community.cisco.com/t5/network-security/stateful-feature/m-p/904946#M974661</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  What is a stateful feature in PIX firewall ? What is the difference between router access-list and pix access-list ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:14:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stateful-feature/m-p/904946#M974661</guid>
      <dc:creator>mohanraj1</dc:creator>
      <dc:date>2019-03-11T11:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: stateful feature</title>
      <link>https://community.cisco.com/t5/network-security/stateful-feature/m-p/904947#M974663</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;A standard access-list on a router is not stateful whereas a firewall like the pix does keep state ie. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when a conversation between a two machines is setup with a firewall in between the traffic path the firewall keeps track of not just the IP address/port number but also the TCP flags that are used in the packet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if i initiate a connection to a server using telnet my intial packet has &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source IP address: 192.168.5.1 (my client) &lt;/P&gt;&lt;P&gt;source port: 23467 ( random generated port) &lt;/P&gt;&lt;P&gt;destination IP address: 172.16.10.1 (telnet server) &lt;/P&gt;&lt;P&gt;destination port: 23 ( telnet port ) &lt;/P&gt;&lt;P&gt;TCP Flag: SYN &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The firewall will enter this into it's state table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when the server responds &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;source IP address: 172.16.10.1 &lt;/P&gt;&lt;P&gt;source port: 23 &lt;/P&gt;&lt;P&gt;destination IP address: 192.168.5.1 &lt;/P&gt;&lt;P&gt;destination port: 23467 &lt;/P&gt;&lt;P&gt;TCP Flags SYN/ACK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The firewall receives this packet, checks it's state table and realises this is a return packet to the initial packet sent out by the client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if the above packet from the server was sent to the client, but the client had not actually sent a packet first the firewall would drop the packet because it has no entry in it's state table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An router access-list does not keep state of the connection in the same way. It merely checks the packet against it's access-list and permits or denies it but it has no concept of "return" traffic or a packet being part of an ongoing communication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 12:20:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stateful-feature/m-p/904947#M974663</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-09-21T12:20:29Z</dc:date>
    </item>
  </channel>
</rss>

