<?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: Unable to pair controller to Chrome Desktop over WiFi in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-pair-controller-to-Chrome-Desktop-over-WiFi/m-p/40276#M2318</link>
    <description>&lt;P&gt;... Figured out the issue... As as lazy security measure, the external IP address of the controller must match the device...&lt;/P&gt;&lt;P&gt;That gets fun when the computer has IPv6 support and the WiFi doesn't... or when the Carrier assigns hotspots a different IP... etc&lt;/P&gt;&lt;P&gt;I simply checked the box under IPv6 "only use this connection for resources on it's network" to disable it's default route. I could also figure out how to route the WiFi's IPv6 to the external IPv6, but that seems more trouble than it's worth.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Nov 2020 22:39:35 GMT</pubDate>
    <dc:creator>CountChocula</dc:creator>
    <dc:date>2020-11-19T22:39:35Z</dc:date>
    <item>
      <title>Unable to pair controller to Chrome Desktop over WiFi</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-pair-controller-to-Chrome-Desktop-over-WiFi/m-p/40107#M2316</link>
      <description>&lt;P&gt;The following works&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Controller over USB to Desktop&lt;/LI&gt;&lt;LI&gt;Controller over WiFi to Chromebook&lt;/LI&gt;&lt;LI&gt;Controller over WiFi to Raspberry Pi&lt;/LI&gt;&lt;LI&gt;Controller over WiFi to Phone&lt;/LI&gt;&lt;LI&gt;Chrome tab streaming to Chromecast Ultra&lt;/LI&gt;&lt;LI&gt;Chrome tab streaming to Chromecast Audio&lt;/LI&gt;&lt;LI&gt;Ping from Desktop to Stadia&lt;/LI&gt;&lt;LI&gt;Ping from Raspberry Pi on WiFi to Desktop&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The following does not work:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Controller over WiFi to Desktop Chrome 87&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Debugging:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;New profile, Incognito, Chrome Beta, turned on Avahi Reflection, tried manually entering Stadia-00e4 to my hosts file.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Dumps: (flagship is the desktop)&lt;/P&gt;&lt;P&gt;1&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;BR /&gt;11:31:52.062122 ARP, Request who-has Stadia-00e4 tell flagship, length 46&lt;BR /&gt;11:31:52.745802 ARP, Request who-has Google-Home tell 192.168.0.135, length 28&lt;BR /&gt;11:31:52.822899 IP 192.168.0.135.mdns &amp;gt; 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR googlerpc-3._googlerpc._tcp.local., (Cache flush) TXT "cd=09D07F047CA21672D6C79C5800ABBC9B", (Cache flush) SRV 850a4ae0-5586-e520-84dc-ad1739358e63-1.local.:8012 0 0, (Cache flush) A 192.168.0.135 (182)&lt;BR /&gt;11:31:52.823751 IP 192.168.0.135.mdns &amp;gt; 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR Google-Nest-Mini-850a4ae05586e52084dcad1739358e63-1._googlecast._tcp.local., (Cache flush) TXT "id=850a4ae05586e52084dcad1739358e63" "cd=09D07F047CA21672D6C79C5800ABBC9B" "rm=55B6718CCB5EE90E" "ve=05" "md=Google Nest Mini" "ic=/setup/icon.png" "fn=Tequila Shot" "ca=198660" "st=0" "bs=FA8FCA811E61" "nf=1" "rs=", (Cache flush) SRV 850a4ae0-5586-e520-84dc-ad1739358e63-1.local.:8009 0 0, (Cache flush) A 192.168.0.135 (380)&lt;BR /&gt;11:31:52.823926 IP 192.168.0.135.mdns &amp;gt; 224.0.0.251.mdns: 0*- [0q] 4/0/0 PTR 850a4ae0-5586-e520-84dc-ad1739358e63-1._googlezone._tcp.local., (Cache flush) TXT "id=09D07F047CA21672D6C79C5800ABBC9B" "bf9db8e9-58db-4a7c-9c7e-627fb4aaaa3f=0|Purple Power" "__common_time__=0|0", (Cache flush) SRV 850a4ae0-5586-e520-84dc-ad1739358e63-1.local.:10001 610 3, (Cache flush) A 192.168.0.135 (282)&lt;BR /&gt;11:31:53.058559 ARP, Request who-has Stadia-00e4 tell flagship, length 46&lt;BR /&gt;1:32:15.087370 IP Chromecast-Audio.mdns &amp;gt; 224.0.0.251.mdns: 0*- [0q] 1/0/3 PTR 2a3be080-ff41-2833-5bbf-270cd08cbf7f-1._googlezone._tcp.local. (331)&lt;BR /&gt;11:32:15.093370 ARP, Request who-has Stadia-00e4 tell Stadia-00e4, length 28&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2020 18:15:00 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-pair-controller-to-Chrome-Desktop-over-WiFi/m-p/40107#M2316</guid>
      <dc:creator>CountChocula</dc:creator>
      <dc:date>2020-11-19T18:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to pair controller to Chrome Desktop over WiFi</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-pair-controller-to-Chrome-Desktop-over-WiFi/m-p/40276#M2318</link>
      <description>&lt;P&gt;... Figured out the issue... As as lazy security measure, the external IP address of the controller must match the device...&lt;/P&gt;&lt;P&gt;That gets fun when the computer has IPv6 support and the WiFi doesn't... or when the Carrier assigns hotspots a different IP... etc&lt;/P&gt;&lt;P&gt;I simply checked the box under IPv6 "only use this connection for resources on it's network" to disable it's default route. I could also figure out how to route the WiFi's IPv6 to the external IPv6, but that seems more trouble than it's worth.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2020 22:39:35 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Unable-to-pair-controller-to-Chrome-Desktop-over-WiFi/m-p/40276#M2318</guid>
      <dc:creator>CountChocula</dc:creator>
      <dc:date>2020-11-19T22:39:35Z</dc:date>
    </item>
  </channel>
</rss>

