<?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 permit ip protocol? in Other Security Subjects</title>
    <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452746#M80652</link>
    <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;basic question!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what i'm passing when i do access-list t2 permit ip any any?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;permiting all tcpip stack?&lt;/P&gt;&lt;P&gt;when i permit tcp i'm not also permiting ip?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where can i read more about these separation of tcp udp ip icmp?&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2019 20:49:52 GMT</pubDate>
    <dc:creator>joaquimlopes</dc:creator>
    <dc:date>2019-03-09T20:49:52Z</dc:date>
    <item>
      <title>permit ip protocol?</title>
      <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452746#M80652</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;basic question!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what i'm passing when i do access-list t2 permit ip any any?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;permiting all tcpip stack?&lt;/P&gt;&lt;P&gt;when i permit tcp i'm not also permiting ip?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where can i read more about these separation of tcp udp ip icmp?&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 20:49:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452746#M80652</guid>
      <dc:creator>joaquimlopes</dc:creator>
      <dc:date>2019-03-09T20:49:52Z</dc:date>
    </item>
    <item>
      <title>Re: permit ip protocol?</title>
      <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452747#M80653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The statement ip will allow ICMP, TCP, and UDP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4 - Transport 	=&amp;gt; TCP, UDP, RTP, SCTP	&lt;/P&gt;&lt;P&gt;3 - Network 	=&amp;gt; IP, ICMP, IPsec, ARP, RIP, BGP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TCP will allow all TCP connection oriented protocols as http, https, ftp, telnet ...&lt;/P&gt;&lt;P&gt;UDP will all connection less protocols as TFTP, DNS ..&lt;/P&gt;&lt;P&gt;ICMP is all the internet messages protocols as echo, echo reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Command reference guide:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_reference_chapter09186a00801727a3.html#wp1067755" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_command_reference_chapter09186a00801727a3.html#wp1067755&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Establishing Connectivity:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172786.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name or number of an IP protocol. It can be one of the keywords icmp, ip, tcp, or udp, or an integer in the range 1 to 254 representing an IP protocol number. To match any Internet protocol, including ICMP, TCP, and UDP, use the keyword ip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take also a look at the OSI Reference model of TCP/IP:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci523729,00.html" target="_blank"&gt;http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci523729,00.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://en.wikipedia.org/wiki/OSI_model" target="_blank"&gt;http://en.wikipedia.org/wiki/OSI_model&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://en.wikipedia.org/wiki/OSI_protocols" target="_blank"&gt;http://en.wikipedia.org/wiki/OSI_protocols&lt;/A&gt;&lt;/P&gt;&lt;P&gt;sincerely&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2005 00:00:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452747#M80653</guid>
      <dc:creator>Patrick Iseli</dc:creator>
      <dc:date>2005-10-26T00:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: permit ip protocol?</title>
      <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452748#M80654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;permit ip means permitting both tcp and udp including all ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the reason being the router/pix will examine layer3 first then layer4, as layer4 is encapsulated in layer3.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2005 00:02:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452748#M80654</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2005-10-26T00:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: permit ip protocol?</title>
      <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452749#M80655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for the reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so, can i permit only for eg: outbound tcp www without any permit ip statements?&lt;/P&gt;&lt;P&gt;or do i have always to use permit ip somewhere and then filter at higher level?&lt;/P&gt;&lt;P&gt;i thought that allowing tcp will allow lower stack level to accomplish the permitted task&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;once again thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2005 10:16:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452749#M80655</guid>
      <dc:creator>joaquimlopes</dc:creator>
      <dc:date>2005-10-26T10:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: permit ip protocol?</title>
      <link>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452750#M80656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, you should never use the ip statement if possible (sometimes for blocking is ok), it is always better to explicit permit the protocols that you want to permit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside permit tcp InsideNetwork InsideSubnetmask any eq www&lt;/P&gt;&lt;P&gt;access-list inside permit tcp InsideNetwork InsideSubnetmask any eq https&lt;/P&gt;&lt;P&gt;access-list inside permit tcp InsideNetwork InsideSubnetmask any range 20 21&lt;/P&gt;&lt;P&gt;access-group inside in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: If you do not limit the protocols on the inside interface then all traffic is allowed to go to any other lower security level interfaces on a PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Security levels by default are:&lt;/P&gt;&lt;P&gt;outside = 0&lt;/P&gt;&lt;P&gt;dmz = 50&lt;/P&gt;&lt;P&gt;inside = 100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sincerely&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2005 12:00:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-security-subjects/permit-ip-protocol/m-p/452750#M80656</guid>
      <dc:creator>Patrick Iseli</dc:creator>
      <dc:date>2005-10-26T12:00:49Z</dc:date>
    </item>
  </channel>
</rss>

