<?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: How to block devices from wifi in Nest Wifi</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/How-to-block-devices-from-wifi/m-p/645458#M53763</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/597367"&gt;@Jeffinaz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Controlling something like this on a home network is challenging. Which is to say, for a determined "attacker" who has the network password, it's impossible. Every machine has a unique 48-bit "MAC" address. This is how Google/Nest WiFi identify a particular machine and decide whether it should be blocked or not. However, it's pretty easy for a machine to change what MAC address it uses. This may not be the kind of problem that can be easily solved using technology. But, I will say that I have found operating-system level tools to be a bit more effective. Apple's "Screen Time" and Microsoft's "Family" features, for example, allow some parental control to be enforced on the machine itself rather than attempting to do so at the network level.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Sep 2024 19:33:48 GMT</pubDate>
    <dc:creator>MichaelP</dc:creator>
    <dc:date>2024-09-23T19:33:48Z</dc:date>
    <item>
      <title>How to block devices from wifi</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/How-to-block-devices-from-wifi/m-p/645332#M53754</link>
      <description>&lt;P&gt;My son keeps finding ways to use his pc after i disable his devises via the app. I dont if he is creating a new ip address to go around the block or has a program on his pc that does it. Any thoughts on how to lock him down during scheduled down times?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Sep 2024 20:21:28 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/How-to-block-devices-from-wifi/m-p/645332#M53754</guid>
      <dc:creator>Jeffinaz</dc:creator>
      <dc:date>2024-09-22T20:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to block devices from wifi</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/How-to-block-devices-from-wifi/m-p/645458#M53763</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/597367"&gt;@Jeffinaz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Controlling something like this on a home network is challenging. Which is to say, for a determined "attacker" who has the network password, it's impossible. Every machine has a unique 48-bit "MAC" address. This is how Google/Nest WiFi identify a particular machine and decide whether it should be blocked or not. However, it's pretty easy for a machine to change what MAC address it uses. This may not be the kind of problem that can be easily solved using technology. But, I will say that I have found operating-system level tools to be a bit more effective. Apple's "Screen Time" and Microsoft's "Family" features, for example, allow some parental control to be enforced on the machine itself rather than attempting to do so at the network level.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2024 19:33:48 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/How-to-block-devices-from-wifi/m-p/645458#M53763</guid>
      <dc:creator>MichaelP</dc:creator>
      <dc:date>2024-09-23T19:33:48Z</dc:date>
    </item>
  </channel>
</rss>

