OmniGuard nsite.tech
← All articles
· 3 min read

Your smart TV is on the same network as your work laptop

Home networks are flat by default: every device can reach every other device. What that means, and how to isolate a machine without cutting it off.

networkinghardeningiot

A typical home network has no internal boundaries. The router hands out addresses, and every device on it can reach every other device directly. Your laptop, your phone, your TV, the doorbell camera, a games console, whatever guests connected last month.

The router's firewall faces outward. Inside, it is one open room.

Why it matters

Most consumer IoT devices are poorly maintained, run outdated software, and never receive another update after shipping. They are the realistic entry point.

Once something has a foothold on any device, a flat network means it can:

  • scan every other device for open services
  • reach management interfaces on machines that assume "only the local network can see this"
  • attempt credential attacks against file shares and remote desktop
  • poison name resolution to intercept traffic

The devices you worry about least are the ones most likely to be the way in.

The straightforward fix: a separate network

If your router supports a guest network or VLANs, put untrusted devices on it. Most guest networks isolate clients from the main network by design, which is precisely what you want.

This is the cleanest answer and costs nothing. The reason people skip it is that some smart-home devices need to talk to a phone app on the main network — worth testing rather than assuming, because many work fine through the cloud.

Isolating a single machine

Where you cannot change the network, you can lock down one machine: block local traffic while keeping the internet, the router and DNS working.

The principle is simple. Block the private address ranges, with exceptions for:

  • your default gateway
  • your DNS servers
  • your own addresses

The trap is the shape of the rule. As covered previously, Windows Firewall evaluates Block rules before Allow rules, so you cannot block a whole range and then allow the gateway back — the block wins and you lose your route.

The exceptions must be absent from the blocked address list. Compute the range minus the exceptions and block only the remainder.

Do not block yourself

Before applying anything, enumerate what must stay reachable:

Get-NetIPConfiguration | Select-Object InterfaceAlias, IPv4Address, IPv4DefaultGateway
Get-DnsClientServerAddress -AddressFamily IPv4 | Select-Object InterfaceAlias, ServerAddresses

Your own addresses matter too — including link-local 169.254.x ones — because a rule that blocks the range containing your own interface can break local services in confusing ways.

Then test from the machine itself: ping the gateway, resolve a name, fetch a page, and confirm a different local device is genuinely unreachable. If all four behave as intended, the rules are right. If DNS broke, they are not.

Remember that networks move

An isolation rule set computed today encodes today's gateway. Join a different network, start WSL or Docker, or renew a lease onto a different subnet, and the new gateway may fall inside your blocked range — at which point the machine silently loses its route, because of a security feature.

Anything that blocks by address needs to be reconciled when the network changes. That is the difference between a rule set that protects you and one that strands you in a coffee shop.

Know the way back

Write the revert command down before you apply anything:

Remove-NetFirewallRule -DisplayName 'YourIsolationRule*'

OmniGuard's LAN lockdown does this reconciliation automatically: it recomputes the intended block set when the network changes and rewrites the rules, so joining a new network cannot leave you blocking your own gateway.

OmniGuard puts this on autopilot — threats, network, Bluetooth and hardening in one console.
Download OmniGuard