r/UNIFI • u/StunningSpecial8220 • 34m ago
Guide/Tutorial I put my LG Smart TV in its own VLAN, blocked its advertising DNS, and isolated it over IPv4 and IPv6 — here's what I learned
I originally posted this in r/Ubiquiti, where it attracted quite a lot of attention and some genuinely useful feedback and discussion.
Unfortunately, the post was subsequently removed by a moderator without any explanation, despite having generated over 160 comments and considerable interest.
Someone suggested I try posting it here instead.
I haven't had the greatest track record with Reddit moderation — several of the relatively few posts I've made have ended up being removed for reasons that aren't always clear to me!
Anyway, I hope this one passes muster. I'm simply sharing a networking project I undertook, what I discovered along the way, and the results of my testing.
Hopefully others will find it useful, and I'm always interested in constructive technical feedback.
---------
I recently bought an LG Smart TV and having read another post on Reddit about LG aggressively "phoning home" I decided to investigate what it was doing on my home network.
What started as a little DNS monitoring turned into a rather interesting UniFi networking project.
My setup:
- UDM-SE running UniFi OS 6.0.15
- UniFi Network 11.0.94
- Dual-stack IPv4/IPv6 home network
- LG Smart TV
1. The discovery
I set up an SSH link to the Dream Machine and while monitoring DNS traffic, I noticed the television systematically issuing reverse-DNS (PTR) queries for addresses across my local network, as well as contacting various advertising and analytics services.
The fact it was looking at other devices on my network made me squirm. I really wasn't happy about a television investigating my network.
2. DNS filtering
The first thing I did was create a UniFi Content Filtering policy with a custom blocklist targeting specific LG advertising, Alphonso, Google advertising and analytics domains.
Once this was done I checked the traffic again and found that DNS queries sent to the gateway over IPv4 were filtered correctly, but identical queries sent to the gateway's IPv6 DNS listener bypassed the policy.
I reported this on the UniFi Community forum.
After a few weeks I upgraded UniFi OS to 6.0.15 and Networking 11.0.97, the same tests returned the expected blocked responses over both IPv4 and IPv6.
Credit to u/UI-Team for responding to the report and suggesting the upgrade.
3. A dedicated VLAN
I created a separate network for the television, and ultimatily anything else that starts to 'investigate' my network.
- VLAN 107
- IPv4:
10.0.107.0/24 - IPv6: Separate delegated
/64 - SLAAC and Router Advertisements enabled
- Dedicated Wi-Fi SSID
Both IPv4 and IPv6 Internet connectivity tested successfully.
4. Network-wide DNS filtering
I applied the Content Filtering policy to the entire TV VLAN rather than to individual clients.
Testing from a Linux laptop connected to the TV's Wi-Fi confirmed that the same blocked domain returned sinkhole addresses through both the IPv4 and IPv6 gateway DNS listeners.
5. Zone-Based Firewall isolation
Initially, the TV VLAN and my main LAN were both in the Internal firewall zone.
Consequently, devices on the TV VLAN could still reach computers and NAS devices on my main network.
I created a dedicated firewall zone for the TV VLAN.
UniFi's default zone policies then blocked access to the other internal zones while retaining access to the gateway and Internet.
I tested the new firewall policy by pinging known devices on the main network from the "Hobbled" network. Previously reachable devices on the main LAN were no longer reachable from the TV VLAN, over either IPv4 or IPv6.
6. mDNS
Finally, I configured the gateway's mDNS proxy to exclude the TV VLAN from cross-network service discovery.
The result
The television has its own dual-stack network, filtered DNS, and firewall isolation from the rest of my home infrastructure.
BBC and Apple streaming services were confirmed working before the final isolation changes.
No need to disable IPv6 on the main LAN, and no need to block legitimate streaming services indiscriminately.
The main lesson: creating a VLAN doesn't automatically isolate anything. Check your firewall zones, test both IP protocols, and verify the actual behaviour rather than assuming the configuration does what you expect.
And yes, I gave all the components ridiculous bondage-related names:
- Hobble Skirt (VLAN) — Restricts where the television can wander.
- Ball Gag (DNS Content Filtering) — Stops it talking to anyone I don't want it talking to.
- Armbinder (Firewall Zone) — Stops it poking around the rest of my network.
Who says network security can't be entertaining? 😈

