<?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: Standard Ports on Applications in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5089#M3738</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you. &lt;SPAN style="font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;I will implement something along this line whena get a window to test it.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Jan 2013 16:44:49 GMT</pubDate>
    <dc:creator>murphyj</dc:creator>
    <dc:date>2013-01-21T16:44:49Z</dc:date>
    <item>
      <title>Standard Ports on Applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5087#M3736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was wondering if anyone knew away to add a secondary default&lt;BR /&gt;port on an application. For example people in my company access web-browsing on&lt;BR /&gt;port 80 normally but there are a number of site that people have to use that&lt;BR /&gt;are based on port 8080. Is there a way to add more default ports so I do not&lt;BR /&gt;have to create more firewall rules than necessary?&amp;nbsp; Thanks for your time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jan 2013 21:41:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5087#M3736</guid>
      <dc:creator>murphyj</dc:creator>
      <dc:date>2013-01-16T21:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Ports on Applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5088#M3737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"default-application" is hardcoded in the application-db.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can however setup your own service-group which contains both TCP80 and TCP8080.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A problem with that might be if you in the same rule allow (or deny) more than one application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appid: smtp, ssh&lt;/P&gt;&lt;P&gt;service: application-default&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;would mean that smtp would only be allowed on its default-port(s) (TCP25) while ssh would be allowed on its default-port(s) (TCP22).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Compared to if you have:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appid: smtp, ssh&lt;/P&gt;&lt;P&gt;service: test-service (containing TCP25, TCP22)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which would allow SMTP on both TCP25 and TCP22 and SSH on both TCP25 and TCP22.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A workaround for the above is of course to have one rule for smtp and another one for ssh and if you are not happy with application-default manually specify which port(s) should be allowed for each rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think a workaround in your case might be if you create a custom-appid (name it custom-web-browsing or so) which is (in your case) based on "web-browsing" but where you for application-default type both TCP80 and TCP8080.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However im not sure if this custom-app will be detected before or after the built-in appid.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2013 06:24:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5088#M3737</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-01-17T06:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Ports on Applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5089#M3738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you. &lt;SPAN style="font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;I will implement something along this line whena get a window to test it.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2013 16:44:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5089#M3738</guid>
      <dc:creator>murphyj</dc:creator>
      <dc:date>2013-01-21T16:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: Standard Ports on Applications</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5090#M3739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you know if I can copy or reference a predefined appid into a new custom-named one with other default ports? Or do I have to build all custom appids completely from scratch?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2015 13:25:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/standard-ports-on-applications/m-p/5090#M3739</guid>
      <dc:creator>tsvaps001</dc:creator>
      <dc:date>2015-03-27T13:25:16Z</dc:date>
    </item>
  </channel>
</rss>

