<?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: Port ranges on CSS in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294456#M4540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  good catch.  I was obviously out of my mind on that one.  I think I can safely say that I lost my perspective (big picture) on that one.  I was thinking of a load balance algorithm in my mind that doesn't exist in real life.  Too much brainstorming.  Obviously, a content rule will just load balance between services in the same rule.  My sincere appologies to Paul.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Jul 2004 16:01:45 GMT</pubDate>
    <dc:creator>robin.pimentel</dc:creator>
    <dc:date>2004-07-06T16:01:45Z</dc:date>
    <item>
      <title>Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294451#M4535</link>
      <description>&lt;P&gt;Is there an easy way to have a content rule listen on a range of selcted ports rather than all open or just one?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jun 2004 10:14:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294451#M4535</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-06-29T10:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294452#M4536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  I just want to shoot out an idea to you.  I haven't tried this out myself, so my apologies if I'm way off here.  Is there a reason why you couldn't define a service for each port on the same host?  So lets say you wanted http and dns:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service serv1-http&lt;/P&gt;&lt;P&gt;port 80&lt;/P&gt;&lt;P&gt;ip 192.168.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service serv1-dns&lt;/P&gt;&lt;P&gt;port 53  (UDP or TCP depending on DNS function)&lt;/P&gt;&lt;P&gt;ip 192.168.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then add the two services to a single content rule (VIP).  Just an idea.  Let me know what you come up with, since your question was pretty interesting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jun 2004 16:50:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294452#M4536</guid>
      <dc:creator>robin.pimentel</dc:creator>
      <dc:date>2004-06-29T16:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294453#M4537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no solution.&lt;/P&gt;&lt;P&gt;You can have a layer 3 rule that will accept all ports and then use an acl to limit what ports you want to be accessible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Jul 2004 07:14:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294453#M4537</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-07-05T07:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294454#M4538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sorry to say this but your solution is totally wrong.&lt;/P&gt;&lt;P&gt;If you have 2 services defined with a different port and assigned to the same content rule, the CSS will one time nat to port1 and one time to port2.&lt;/P&gt;&lt;P&gt;For example, you get a connection on port 80, the CSS could loadbalance the request to serv1-dns since it is configured under the content rule and the CSS will forward the request to port 53 -&amp;gt; see the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no solution to Paul's request unless we get more info about the end goal so we can find a different approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Jul 2004 07:17:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294454#M4538</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-07-05T07:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294455#M4539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks. I have a feeling that is the way I will have to go to do it. It would be useful to have a range facility for ports though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Jul 2004 07:19:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294455#M4539</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-07-05T07:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294456#M4540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  good catch.  I was obviously out of my mind on that one.  I think I can safely say that I lost my perspective (big picture) on that one.  I was thinking of a load balance algorithm in my mind that doesn't exist in real life.  Too much brainstorming.  Obviously, a content rule will just load balance between services in the same rule.  My sincere appologies to Paul.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jul 2004 16:01:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294456#M4540</guid>
      <dc:creator>robin.pimentel</dc:creator>
      <dc:date>2004-07-06T16:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Port ranges on CSS</title>
      <link>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294457#M4541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No problem - sometimes off the wall stuff works...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jul 2004 18:03:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/port-ranges-on-css/m-p/294457#M4541</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-07-06T18:03:22Z</dc:date>
    </item>
  </channel>
</rss>

