The project is WinUI 3 + Native AOT. Everything runs fine during debugging, but after publishing and launching, it works normally for a few seconds, then the UI thread randomly becomes unresponsive, stuck in a "fuzzy state" — not a crash and exit, but a freeze with no response.
When developing Windows networking solutions, there are times when you need to intercept DNS queries for a specific domain and return a custom IP address to achieve traffic steering, local debugging, or access control.
This article uses the interception of DNS A-record queries for www.abc.com as an example to walk through how to intercept DNS requests at the transport layer via WFP (Windows Filtering Platform) and return a specified IP address (e.g., 192.168.1.100). The focus is on the configuration flow and key decision points, supplemented by essential code snippets.
If you're doing Windows network development—especially firewalls, VPNs, network monitoring, or similar tools—WFP (Windows Filtering Platform) is unavoidable. However, terms like drivers, kernel, and Callouts can be intimidating.
This article won't dive into complex API details. Instead, it aims to explain, in the simplest terms possible, what WFP is, what it can do, and how it works internally.
In one sentence: WFP is a "universal power strip" embedded in the Windows kernel network stack.
It provides "sockets" (filtering layers) at all key points where network data passes through. You can plug your own processing logic ("plugs") into these sockets to intercept, inspect, modify, and allow/block network traffic.
The built-in Windows Firewall itself is Microsoft's own "plug" inserted into these sockets. Antivirus software, parental controls, and traffic monitoring tools all leverage this same infrastructure.
Hey network engineers, sysadmins, and anyone driven crazy by VLANs – hold up!
Today we're talking about a trick that goes against common sense. You've probably always thought: if you connect two PCs directly with a cable, they have to be on the same subnet to talk to each other (like 192.168.1.x and 192.168.1.y).
Yeah, that's the "politically correct" way. But sometimes life throws you curveballs:
Today, I'm going to show you how to break that rule. Two directly connected PCs with IPs on different subnets? Still pingable! And you don't need an extra router – just the built-in "soft router" feature in Windows.
WireGuard is known for its simplicity, efficiency, and security, and the official Windows client continues this tradition. Unlike the command-line operations on Linux, the Windows version focuses more on graphical management and tunnel switching. The configuration logic mainly revolves around generating key pairs and editing .conf files.
