<?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 packet size issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/packet-size-issue/m-p/6732#M4933</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Noticed unable to ping packet size above 996 after upgrading to PAN OS 5.&lt;/P&gt;&lt;P&gt;few of our internet apps(cloud) is acting intermittently &lt;/P&gt;&lt;P&gt;Anyone encountering the same issue? &lt;/P&gt;&lt;P&gt;Any advice is appreciated? &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;&amp;gt; ping size 995 source 172.21.194.22 host google.com&lt;/P&gt;&lt;P&gt;PING google.com (74.125.226.14) from 172.21.194.22 : 995(1023) bytes of data.&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=1 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=2 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=3 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=4 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=5 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&amp;gt; ping size 996 source 172.21.194.22 host google.com&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;PING google.com (74.125.226.1) from 172.21.194.22 : 996(1024) bytes of data.&lt;/P&gt;&lt;P&gt;^C&lt;/P&gt;&lt;P&gt;--- google.com ping statistics ---&lt;/P&gt;&lt;P&gt;10 packets transmitted, 0 received, 100% packet loss, time 9014ms&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Mar 2014 09:18:58 GMT</pubDate>
    <dc:creator>ateo</dc:creator>
    <dc:date>2014-03-21T09:18:58Z</dc:date>
    <item>
      <title>packet size issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/packet-size-issue/m-p/6732#M4933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Noticed unable to ping packet size above 996 after upgrading to PAN OS 5.&lt;/P&gt;&lt;P&gt;few of our internet apps(cloud) is acting intermittently &lt;/P&gt;&lt;P&gt;Anyone encountering the same issue? &lt;/P&gt;&lt;P&gt;Any advice is appreciated? &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;&amp;gt; ping size 995 source 172.21.194.22 host google.com&lt;/P&gt;&lt;P&gt;PING google.com (74.125.226.14) from 172.21.194.22 : 995(1023) bytes of data.&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=1 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=2 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=3 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=4 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;72 bytes from lga15s42-in-f14.1e100.net (74.125.226.14): icmp_seq=5 ttl=42 (truncated)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&amp;gt; ping size 996 source 172.21.194.22 host google.com&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;PING google.com (74.125.226.1) from 172.21.194.22 : 996(1024) bytes of data.&lt;/P&gt;&lt;P&gt;^C&lt;/P&gt;&lt;P&gt;--- google.com ping statistics ---&lt;/P&gt;&lt;P&gt;10 packets transmitted, 0 received, 100% packet loss, time 9014ms&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 09:18:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/packet-size-issue/m-p/6732#M4933</guid>
      <dc:creator>ateo</dc:creator>
      <dc:date>2014-03-21T09:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: packet size issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/packet-size-issue/m-p/6733#M4934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ateo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;maybe the mtu-size is to small (default = 1500 byte). you can change the mtu-size if you look at an interface.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="12336" alt="mtu.PNG.png" class="jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/12336_mtu.PNG.png" style="width: 620px; height: 402px;" /&gt;&lt;/P&gt;&lt;P&gt;Keep in mind that every other involved network-device could be a reason for&amp;nbsp; the mtu-size. There are different tools to find the right size if this is the problem.&lt;/P&gt;&lt;P&gt;Regards Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 14:57:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/packet-size-issue/m-p/6733#M4934</guid>
      <dc:creator>kdd</dc:creator>
      <dc:date>2014-03-21T14:57:05Z</dc:date>
    </item>
  </channel>
</rss>

