<?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: MS Direct Access in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40979#M30119</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According to &lt;A href="http://apps.paloaltonetworks.com/applipedia/" title="http://apps.paloaltonetworks.com/applipedia/"&gt; Application Research Center&lt;/A&gt; the appid should be "ipv6":&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;Description&lt;/P&gt;&lt;P&gt;The technique of encapsulating IPv6 packets within IPv4 so that they can be carried across IPv4 routing infrastructures. While the IPv6 infrastructure is being deployed, the existing IPv4 routing infrastructure can remain functional and can be used to carry IPv6 traffic. Examples of IPv6 tunneling mechanisms are 6in4, 6to4. &lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 6in4 stuff is the "protocol 41" according to &lt;A class="active_link" href="http://en.wikipedia.org/wiki/6in4" title="http://en.wikipedia.org/wiki/6in4"&gt;6in4 - Wikipedia, the free encyclopedia&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally speaking if you have setup a "deny + log" rule in the end of your security policy set you should be able to see in the traffic log how the blocked traffic is being identified as.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Mar 2013 07:49:41 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2013-03-20T07:49:41Z</dc:date>
    <item>
      <title>MS Direct Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40977#M30117</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any one setup MS Direct Access?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a MS consultant stating that all that is needed is to set up a NAT and add a security policy to allow TCP 443 and IP Protocol 41.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the dumb question...&lt;/P&gt;&lt;P&gt;How do you allow IP Protocol 41?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 04:37:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40977#M30117</guid>
      <dc:creator>almay</dc:creator>
      <dc:date>2013-03-20T04:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: MS Direct Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40978#M30118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tryed to find "UAG" or Direct acces on &lt;A href="http://apps.paloaltonetworks.com/applipedia//" title="http://apps.paloaltonetworks.com/applipedia//"&gt; Application Research Center&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But it seems that this apllication doesnt has a their own signature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my opinion you have to make a port redirection (NAT rule) and security rule that will allow _all_ application, and it you will have estabilised session take a look into Monitor &amp;gt; Traffic - you will see how this traffic is categorised by PAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;SLawek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 07:45:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40978#M30118</guid>
      <dc:creator>_slv_</dc:creator>
      <dc:date>2013-03-20T07:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: MS Direct Access</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40979#M30119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According to &lt;A href="http://apps.paloaltonetworks.com/applipedia/" title="http://apps.paloaltonetworks.com/applipedia/"&gt; Application Research Center&lt;/A&gt; the appid should be "ipv6":&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;Description&lt;/P&gt;&lt;P&gt;The technique of encapsulating IPv6 packets within IPv4 so that they can be carried across IPv4 routing infrastructures. While the IPv6 infrastructure is being deployed, the existing IPv4 routing infrastructure can remain functional and can be used to carry IPv6 traffic. Examples of IPv6 tunneling mechanisms are 6in4, 6to4. &lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 6in4 stuff is the "protocol 41" according to &lt;A class="active_link" href="http://en.wikipedia.org/wiki/6in4" title="http://en.wikipedia.org/wiki/6in4"&gt;6in4 - Wikipedia, the free encyclopedia&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally speaking if you have setup a "deny + log" rule in the end of your security policy set you should be able to see in the traffic log how the blocked traffic is being identified as.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 07:49:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ms-direct-access/m-p/40979#M30119</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-03-20T07:49:41Z</dc:date>
    </item>
  </channel>
</rss>

