Every number in the piece comes from one person's capture of one network, so treat the results as an illustration of what's possible. They aren't benchmarks.
Why DNS logs aren't enough
The author runs a Proxmox home lab, a Synology NAS and a two-node Technitium DNS cluster. He points out that DNS logs show what a device asks for, not what it does next. His fix was port mirroring, which Cisco calls SPAN. The switch copies every frame from one port to another, so a PC on the second port can watch the traffic without sitting in its path.
His switch is a Zyxel XGS1210-12, a roughly $120 web-managed model. He mirrored the link to his router onto the port feeding his desktop. Anything crossing between his wired gear and the router was copied to Wireshark.
He did two runs:
- First run (161 seconds): A single MacBook Time Machine backup to the Proxmox node produced 1.32 GB of capture. That made the run useless for his purpose.
- Second run (1,799 seconds): This produced 1,028,250 frames and 943 MB. A pre-capture ARP sweep found 42 IP addresses and 38 unique MAC addresses on the LAN.
The capture-machine caveat
The author's desktop was both the capture machine and an active network client, which skewed the data. Much of what the PC sent appeared twice. The first copy was the PC's own, and the second was the switch's mirrored copy about 30 microseconds later. Most broadcasts doubled up too.
He used Wireshark's editcap to strip duplicates. It removed 174,736 copies but missed the PC's own outgoing packets.
His explanation is checksum offloading. Wireshark's documentation says Wireshark captures packets before they are sent to the network adapter, so it sees outgoing packets before the NIC has calculated the final checksum. The mirrored copy carries the finished checksum, so the two never match. The Wireshark documentation backs the general mechanism. It doesn't verify his exact duplicate count.
The practical fix is a dedicated capture machine that isn't doing anything else. One older networking blog goes further and recommends using a span port on a switch to mirror traffic to a dedicated capture PC rather than disabling offload on the adapter. If you capture on the same PC anyway, Wireshark's wiki notes that new installations of Wireshark 1.2 and above disable IP, TCP, and UDP checksum validation by default. Those red "bad checksum" lines are therefore usually cosmetic.
An idle Windows PC was the loudest device
The author expected the TV to top the chart. Instead, his untouched desktop made about 2,000 DNS lookups for 309 domains in half an hour. It had a few browser windows, Discord and some game launchers open. He saw four Microsoft telemetry endpoints, plus Grammarly logging hosts, 1Password's telemetry service and Sentry error reporting.
A DNS lookup shows a name was requested, not what data was sent or why. Plenty of this traffic is routine for modern software. It's still a useful reminder of how many background services an "idle" desktop keeps alive.
GOG Galaxy's plain-text syslog
The standout finding was GOG Galaxy. Its background service sent 19 messages to GOG's log servers in a 37-second burst over UDP port 514, which is plain syslog with no encryption. The author says the messages included:
- The PC's hostname
- The Galaxy client version
- A numeric ID tied to his GOG account
- Log lines about a service restart after a missed heartbeat, an OpenID sign-in, and subscriptions to chat, presence, gameplay and library feeds
- Three instances of "Found refresh token" followed by the first five characters of the token
He saw no password or full token and calls it sloppy rather than dangerous. That's a fair reading. A five-character fragment of a token isn't a credential, and nothing in his report suggests a compromise. Still, account-linked identifiers crossing the internet readable by anyone on the path is poor hygiene, especially from a launcher he wasn't using. I can't confirm whether other Galaxy versions or accounts behave the same way. That's one capture, not a vendor audit.
The TCL TV: chatty, not proven sinister
The TCL TV moved 80 MB, mostly streaming. It looked up 44 domains. Its most-contacted TV-side host was a leiniao.com API endpoint, with 25 TLS sessions in 30 minutes. The author counted 11 leiniao.com subdomains, plus TCL account, launcher and registration hosts. He cites an independent teardown of TCL's Android TV software that describes Leiniao (also sold as FFalcon) as TCL's internet-TV, content and ads subsidiary. I couldn't verify that teardown myself.
The TV also sent a broadcast to UDP port 6537 about 690 times, roughly every 2.6 seconds. Nothing on his network replied.
A hostname and a session count don't prove what was transmitted. Still, they're a good reason to do what the author did and give a smart TV its own firewall rules or VLAN.
DNS: nobody bypassed it, but filtering wasn't in play either
The author expected to catch a device with a hardcoded public DNS server. He filtered for DNS traffic not addressed to his router:
dns && !(ip.dst == 192.168.4.1) && !(ipv6.dst == fd6f:bf7e:7e73:1::1)
Only his two Technitium nodes, acting as recursive resolvers, talked to outside DNS servers. Everything else, including the TV, asked the eero router.
There's a catch. The eero answers from its own resolver, not Technitium. He tried pointing it at his cluster earlier this month, it broke the network, and he reverted. So "nobody bypassed my DNS" really means nobody bypassed the router. His Technitium filtering never applied to these lookups. The result is also specific to his addresses and his filter. It doesn't rule out other bypass methods such as DNS over HTTPS.
What the rest of the network said
Most other outbound traffic was TLS-encrypted. Before encryption starts, though, the handshake includes the hostname in the Server Name Indication field. Wireshark can show it with the filter tls.handshake.extensions_server_name.
The author's SNI and lookup findings:
- Synology NAS: Active Insight and Plex servers.
- Home Assistant: GitHub, Nabu Casa, Airthings and Sentry. The Sentry traffic was crash reporting, because he had enabled the Diagnostics toggle himself.
- Hue Bridge: a diagnostics host.
- Eufy HomeBase: P2P hosts under anker-in.com, 56 lookups in total.
The HomeBase also contacted three AWS addresses on UDP port 32100 about every 13 seconds each. The author reads this as a peer-to-peer relay kept open so the app can reach the doorbell remotely. That purpose is his interpretation of the packets.
Local discovery noise was heavy too:
- The Hue Bridge sent 390 SSDP announcements.
- Sonos speakers advertised model numbers and firmware builds.
- An Anker device sent 756 mDNS packets advertising an
_anker_powerservice. - The NAS sent 2,151 Plex discovery broadcasts.
His standalone Strix Halo box sent about 900 broadcasts on UDP port 13305, roughly one every two seconds. That is Lemonade Server's discovery beacon. Lemonade's configuration documentation confirms that broadcast is a setting for UDP server discovery. The same documentation lists --broadcast and --no-broadcast as non-persistent command-line overrides for lemond. The author's fix is to set broadcast to false in config.json. On Windows, Lemonade's docs put that file at %USERPROFILE%\.config\lemonade\config.json. Check the docs for your installed version, because the CLI flag doesn't persist across restarts.
How to try this yourself
- Confirm your switch supports port mirroring. Menus vary by model. You need a monitor (destination) port, one or more mirrored (source) ports, and a direction: ingress, egress or both. Zyxel's guide, as summarized in the research notes, warns that a port can't be both the monitor and a mirrored port. I couldn't retrieve that guide directly.
- Mirror the uplink to your router. That captures everything crossing between your wired devices and the rest of the network.
- Use a dedicated capture PC if you can. It avoids the duplicate-packet and checksum problems the author hit.
- Start Wireshark on the monitor port. Run a short test first, because a single backup job can swamp the capture.
- Use filters such as the DNS and SNI ones above to identify destinations.
- Know the blind spots. Wi-Fi devices only show up when they talk to something wired or broadcast. Traffic between Proxmox containers stays on the host. Encrypted payloads stay unreadable. A 30-minute snapshot will miss anything that phones home once a day.
The takeaway
The author's strongest conclusion holds up. A short capture exposed contacts and broadcasts that DNS logs couldn't, including one plain-text logging habit from a mainstream PC launcher. It also exposed gaps in his own setup: the unfiltered router DNS path and a mirror port that doubled as a workstation. His next step is capturing the Wi-Fi side of the router.
References
- I mirrored my network traffic and discovered what my devices hide from me XDA · 2026-11-16T18:00:22+00:00
- CaptureSetup/Offloading - Wireshark Wiki wiki.wireshark.org
- Disabling checksum validation in Wireshark - PacketLife.net packetlife.net