<?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 Strange behavior with Communication between sub-interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/strange-behavior-with-communication-between-sub-interfaces/m-p/1251728#M826925</link>
    <description>&lt;P&gt;I have a 5550 with 10 sub-interfaces (vlans) configured on Five physical Interfaces.  Each sub-interface has a different security level based on function.  I've noticed that I only have to write an egress rule for traffic to pass from a lower security level interface to higher security level interface. I would have thought I would need to write rules to allow the traffic in both the out and in directions.  We are not using NAT, all public IP addresses.  Any thoughts on this? Example: if I allow tcp port 3389 out of our production data vlan to our admin vlan I only have to write an ACL that says allow tcp/3389 out of production data. I do not need to write an ACL that allows tcp/3389 into the admin vlan. Is this normal behavior?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 16:14:26 GMT</pubDate>
    <dc:creator>kbrinnehl</dc:creator>
    <dc:date>2019-03-11T16:14:26Z</dc:date>
    <item>
      <title>Strange behavior with Communication between sub-interfaces</title>
      <link>https://community.cisco.com/t5/network-security/strange-behavior-with-communication-between-sub-interfaces/m-p/1251728#M826925</link>
      <description>&lt;P&gt;I have a 5550 with 10 sub-interfaces (vlans) configured on Five physical Interfaces.  Each sub-interface has a different security level based on function.  I've noticed that I only have to write an egress rule for traffic to pass from a lower security level interface to higher security level interface. I would have thought I would need to write rules to allow the traffic in both the out and in directions.  We are not using NAT, all public IP addresses.  Any thoughts on this? Example: if I allow tcp port 3389 out of our production data vlan to our admin vlan I only have to write an ACL that says allow tcp/3389 out of production data. I do not need to write an ACL that allows tcp/3389 into the admin vlan. Is this normal behavior?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:14:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-behavior-with-communication-between-sub-interfaces/m-p/1251728#M826925</guid>
      <dc:creator>kbrinnehl</dc:creator>
      <dc:date>2019-03-11T16:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Strange behavior with Communication between sub-interfaces</title>
      <link>https://community.cisco.com/t5/network-security/strange-behavior-with-communication-between-sub-interfaces/m-p/1251729#M826955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it's normal. It's what makes up the stateful firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://en.wikipedia.org/wiki/Stateful_firewall" target="_blank"&gt;http://en.wikipedia.org/wiki/Stateful_firewall&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Sep 2009 18:39:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-behavior-with-communication-between-sub-interfaces/m-p/1251729#M826955</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-09-10T18:39:57Z</dc:date>
    </item>
  </channel>
</rss>

