<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tcpdump on CX's Blog</title><link>https://blog.imcaoxuan.cn/en/tags/tcpdump/</link><description>Recent content in Tcpdump on CX's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>imcaoxuan.cn</copyright><lastBuildDate>Fri, 23 Oct 2026 16:30:00 +0800</lastBuildDate><atom:link href="https://blog.imcaoxuan.cn/en/tags/tcpdump/index.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshooting DNS Timeouts on a Bypass Router: sing-box Upstream Queries Leave Through the Wrong Network Interface</title><link>https://blog.imcaoxuan.cn/en/posts/2026-10-23-troubleshooting-dns-timeouts-on-a-bypass-router-sing-box-upstream-queries-leave-through-the-wrong-network-interface/</link><pubDate>Fri, 23 Oct 2026 16:30:00 +0800</pubDate><guid>https://blog.imcaoxuan.cn/en/posts/2026-10-23-troubleshooting-dns-timeouts-on-a-bypass-router-sing-box-upstream-queries-leave-through-the-wrong-network-interface/</guid><description>Downstream DNS requests reach sing-box, but upstream forwarding bypasses WireGuard; locate the fault with targeted packet captures and fix it with bind_interface.</description></item></channel></rss>