<?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 Denials in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zone-based-firewall-denials/m-p/1487608#M633170</link>
    <description>&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;I am having trouble with Sun Unix NFS and NIS between two servers, one that is outside the firewall (192.168.20.1) and the NFS/NIS server (192.168.10.1) that is inside.&amp;nbsp; Even though I have NFS selected as an allowed protocol, it appears that we get frequent denials from the inside zone to the outside zone between these two servers an high port numbers.&amp;nbsp; So rather than fight this, I added a rule as follows using SDM.&amp;nbsp; My question is... Is this the proper way to specify a zone based rule where I want to allow ALL protocols?&amp;nbsp; SDM says if you do not specifically ADD a protocol, it allows ALL protocols; however, if you look further below at my syslog, it is obvious this this is not working.&amp;nbsp; I have also noticed that the cause of this is due to a Stray Segment with ip ident 0.&amp;nbsp; Can anyone tell me if this is due to my rule or what could cause a "stray segment" if that is the cause?&amp;nbsp; Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;-------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;class-map type inspect match-all cls-sum-gc3_server_in_out&lt;BR /&gt;&lt;/STRONG&gt; match access-group name acl-gc3_server_in_out&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;policy-map type inspect pm-inspect-in-out&lt;BR /&gt;&lt;/STRONG&gt; class type inspect cls-sum-gc3_in_out&lt;BR /&gt;&amp;nbsp; inspect pm-increase_tcp_idle_timeout&lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG style="font-family: courier new,courier; "&gt; class type inspect cls-sum-gc3_server_in_out&lt;BR /&gt;&amp;nbsp; inspect&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; class class-default&lt;BR /&gt;&amp;nbsp; drop&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;zone-pair security zp-in-out source GC3-zone destination ULA-Corp-zone&lt;/STRONG&gt;&lt;BR /&gt; service-policy type &lt;STRONG&gt;inspect pm-inspect-in-out&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;ip access-list extended acl-gc3_server_in_out&lt;/STRONG&gt;&lt;BR /&gt; remark SDM_ACL Category=128&lt;BR /&gt; permit ip host 192.168.10.1 192.168.0.0 0.0.255.255&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; "&gt;-------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;syslog denial examples&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Jul 21 13:22:40 silrt0g1 19060: Jul 21 13:22:39.547: %FW-6-DROP_PKT: Dropping tcp session 192.168.10.1:908 192.168.20.1:61395&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 13:37:25 silrt0g1 19061: Jul 21 13:37:24.551: %FW-6-DROP_PKT: Dropping tcp session 192.168.10.1:908 192.168.20.1:61505&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 13:43:19 silrt0g1 19064: Jul 21 13:43:18.330: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61515 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 14:20:59 silrt0g1 19075: Jul 21 14:20:58.692: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61742 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 14:25:44 silrt0g1 19076: Jul 21 14:25:43.470: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61770 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:14:25 GMT</pubDate>
    <dc:creator>sdniel</dc:creator>
    <dc:date>2019-03-11T18:14:25Z</dc:date>
    <item>
      <title>Zone Based Firewall Denials</title>
      <link>https://community.cisco.com/t5/network-security/zone-based-firewall-denials/m-p/1487608#M633170</link>
      <description>&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;I am having trouble with Sun Unix NFS and NIS between two servers, one that is outside the firewall (192.168.20.1) and the NFS/NIS server (192.168.10.1) that is inside.&amp;nbsp; Even though I have NFS selected as an allowed protocol, it appears that we get frequent denials from the inside zone to the outside zone between these two servers an high port numbers.&amp;nbsp; So rather than fight this, I added a rule as follows using SDM.&amp;nbsp; My question is... Is this the proper way to specify a zone based rule where I want to allow ALL protocols?&amp;nbsp; SDM says if you do not specifically ADD a protocol, it allows ALL protocols; however, if you look further below at my syslog, it is obvious this this is not working.&amp;nbsp; I have also noticed that the cause of this is due to a Stray Segment with ip ident 0.&amp;nbsp; Can anyone tell me if this is due to my rule or what could cause a "stray segment" if that is the cause?&amp;nbsp; Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;-------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;class-map type inspect match-all cls-sum-gc3_server_in_out&lt;BR /&gt;&lt;/STRONG&gt; match access-group name acl-gc3_server_in_out&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;policy-map type inspect pm-inspect-in-out&lt;BR /&gt;&lt;/STRONG&gt; class type inspect cls-sum-gc3_in_out&lt;BR /&gt;&amp;nbsp; inspect pm-increase_tcp_idle_timeout&lt;BR /&gt;&lt;/SPAN&gt;&lt;STRONG style="font-family: courier new,courier; "&gt; class type inspect cls-sum-gc3_server_in_out&lt;BR /&gt;&amp;nbsp; inspect&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; class class-default&lt;BR /&gt;&amp;nbsp; drop&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;zone-pair security zp-in-out source GC3-zone destination ULA-Corp-zone&lt;/STRONG&gt;&lt;BR /&gt; service-policy type &lt;STRONG&gt;inspect pm-inspect-in-out&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;ip access-list extended acl-gc3_server_in_out&lt;/STRONG&gt;&lt;BR /&gt; remark SDM_ACL Category=128&lt;BR /&gt; permit ip host 192.168.10.1 192.168.0.0 0.0.255.255&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; "&gt;-------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;STRONG&gt;syslog denial examples&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Jul 21 13:22:40 silrt0g1 19060: Jul 21 13:22:39.547: %FW-6-DROP_PKT: Dropping tcp session 192.168.10.1:908 192.168.20.1:61395&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 13:37:25 silrt0g1 19061: Jul 21 13:37:24.551: %FW-6-DROP_PKT: Dropping tcp session 192.168.10.1:908 192.168.20.1:61505&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 13:43:19 silrt0g1 19064: Jul 21 13:43:18.330: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61515 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 14:20:59 silrt0g1 19075: Jul 21 14:20:58.692: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61742 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;Jul 21 14:25:44 silrt0g1 19076: Jul 21 14:25:43.470: %FW-6-DROP_PKT: Dropping tcp session 192.168.20.1:61770 192.168.10.1:908&amp;nbsp; due to&amp;nbsp; Stray Segment with ip ident 0&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zone-based-firewall-denials/m-p/1487608#M633170</guid>
      <dc:creator>sdniel</dc:creator>
      <dc:date>2019-03-11T18:14:25Z</dc:date>
    </item>
  </channel>
</rss>

