<?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: Scheduling policies and continuous tcp sessions in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8068#M5949</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wouldnt an enabled "rematch sessions" along with a commit just after the time is changed to disallow skype-calls fix this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so the followup question would be if its possible to schedule "commit force"? &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Feb 2010 16:22:23 GMT</pubDate>
    <dc:creator>rps</dc:creator>
    <dc:date>2010-02-26T16:22:23Z</dc:date>
    <item>
      <title>Scheduling policies and continuous tcp sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8066#M5947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Gentlemen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anybody know how we can configure the policies to block a continuous TCP session when the schedule runs out?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The test we are trying to do is to block a skype discussion during a scheduled time.&lt;/P&gt;&lt;P&gt;During the 'allowed' time, we can launch skype and discuss normally. Good.&lt;/P&gt;&lt;P&gt;During the 'blocked' time, we are not able to connect skype to the web. Also Good.&lt;/P&gt;&lt;P&gt;But a contunious session, that was previously initiated during the permit time is not blocked when the allowed schedule runs out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Olivier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Sep 2009 12:26:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8066#M5947</guid>
      <dc:creator>itbrain</dc:creator>
      <dc:date>2009-09-24T12:26:20Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling policies and continuous tcp sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8067#M5948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Olivier,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the schedule for the policy is only applied at the time of  &lt;/P&gt;&lt;P&gt;session setup. If the schedule says the session can be allowed at the  &lt;/P&gt;&lt;P&gt;time of setup, it is allowed. The system does not have a mechanism to  &lt;/P&gt;&lt;P&gt;go back and kill the sessions midstream when the schedule expires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Sep 2009 17:40:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8067#M5948</guid>
      <dc:creator>mjacobsen</dc:creator>
      <dc:date>2009-09-24T17:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling policies and continuous tcp sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8068#M5949</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wouldnt an enabled "rematch sessions" along with a commit just after the time is changed to disallow skype-calls fix this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so the followup question would be if its possible to schedule "commit force"? &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 16:22:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8068#M5949</guid>
      <dc:creator>rps</dc:creator>
      <dc:date>2010-02-26T16:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduling policies and continuous tcp sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8069#M5950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, if you enable "rematch sessions" and then commit the configuration, the existing Skype sessions would be rematched to policy (and blocked in this case if the schedule dictates that action). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Nick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Mar 2010 23:39:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/scheduling-policies-and-continuous-tcp-sessions/m-p/8069#M5950</guid>
      <dc:creator>ncampagna</dc:creator>
      <dc:date>2010-03-09T23:39:17Z</dc:date>
    </item>
  </channel>
</rss>

