<?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 Google QUIC Disconnects in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/67967#M39748</link>
    <description>&lt;P&gt;We started getting complaints from users that various Google services were showing intermittent disconnects. I think we've tracked it down to the QUIC protocol not being accurately identified by the PAN firewalls and getting blocked. I see 443/udp traffic from the hosts in question getting dropped as "unidentified-udp" mixed in with the allowed "quic" traffic on the same ports to the same general set of Google servers.&amp;nbsp;Google has been rolling out QUIC for a while now, but we only recently allowed it in the firewall. It's been since then that we've seen the Google issues start.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am considering adding a rule allowing "any" application out on 443/udp as a workaround.&amp;nbsp;Has anyone else seen similar problems? That is, do you allow "quic" out to the Internet, but otherwise would drop 443/udp and see or not see this issue? Did you implement a workaround like this or something else? (BTW, I am not overly concerned about the security implications. PAN firewalls don't understand&amp;nbsp;the QUIC traffic like HTTPS to guess at&amp;nbsp;the Google "applications" inside.)&lt;/P&gt;</description>
    <pubDate>Wed, 11 Nov 2015 21:18:06 GMT</pubDate>
    <dc:creator>cosx</dc:creator>
    <dc:date>2015-11-11T21:18:06Z</dc:date>
    <item>
      <title>Google QUIC Disconnects</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/67967#M39748</link>
      <description>&lt;P&gt;We started getting complaints from users that various Google services were showing intermittent disconnects. I think we've tracked it down to the QUIC protocol not being accurately identified by the PAN firewalls and getting blocked. I see 443/udp traffic from the hosts in question getting dropped as "unidentified-udp" mixed in with the allowed "quic" traffic on the same ports to the same general set of Google servers.&amp;nbsp;Google has been rolling out QUIC for a while now, but we only recently allowed it in the firewall. It's been since then that we've seen the Google issues start.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am considering adding a rule allowing "any" application out on 443/udp as a workaround.&amp;nbsp;Has anyone else seen similar problems? That is, do you allow "quic" out to the Internet, but otherwise would drop 443/udp and see or not see this issue? Did you implement a workaround like this or something else? (BTW, I am not overly concerned about the security implications. PAN firewalls don't understand&amp;nbsp;the QUIC traffic like HTTPS to guess at&amp;nbsp;the Google "applications" inside.)&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2015 21:18:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/67967#M39748</guid>
      <dc:creator>cosx</dc:creator>
      <dc:date>2015-11-11T21:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: Google QUIC Disconnects</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/67973#M39751</link>
      <description>&lt;P&gt;Not sure which version of software and/or dynamic updates you are on, however our PAN does see the quic traffic but we dont see any of the unidentified-udp. We currently are blocking quic but that is mainly because no one has complained about it. We dont use many google apps, maily search and mail for some users.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2015 21:43:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/67973#M39751</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2015-11-11T21:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: Google QUIC Disconnects</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/68077#M39788</link>
      <description>&lt;P&gt;Running 6.1.2 and keep up-to-date with the application-threat updates.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yeah, it all worked fine when we weren't allowing quic. We didn't start seeing problems until we expressly allowed it.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2015 00:51:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-quic-disconnects/m-p/68077#M39788</guid>
      <dc:creator>cosx</dc:creator>
      <dc:date>2015-11-13T00:51:04Z</dc:date>
    </item>
  </channel>
</rss>

