Livetcpudpwatch
Author: m | 2025-04-25
Download LiveTcpUdpWatch [EN] Download do LiveTcpUdpWatch [PT] LiveTcpUdpWatch 다운로드 [KO] Download LiveTcpUdpWatch [NL] Pobierz LiveTcpUdpWatch [PL] Tải xuống LiveTcpUdpWatch [VI] Descargar LiveTcpUdpWatch [ES] Скачать LiveTcpUdpWatch [RU] 下载LiveTcpUdpWatch [ZH] Unduh LiveTcpUdpWatch [ID] T l charger LiveTcpUdpWatch [FR]
LiveTcpUdpWatch 1.55 - Download, Review
EnvironmentWindows build number: 10.0.19042.804Your Distribution version: Ubuntu 20.04Whether the issue is on WSL 2 and/or WSL 1: WSL2Steps to reproduceInside WSL2 Ubuntu:time dig +time=20 somenonexistentdomain.comshould return pretty fast, but when I connect my OpenVPN, it starts to take ~12 seconds which causes all sorts of trouble, knowing the WSL DNS is somehow queuing the requests in single thread as mentioned in #4285Problem seems to be between windows services "Dnscache" and "SharedAccess" doing their part in DNS relaying.Different setups and results:Without VPN everything worksWith our older Sophos OpenVPN everything works (uses Sophos SSL network adapter, hereafter "SophosTap")With our new OpenVPN this strange delay happens (uses TAP-Windows Adapter V9, hereafter "OpenTap")I have 2 Wiresharks monitoring both the "vEthernet (WSL)" and the "SophosTap"/"OpenTap" adapter to see how it goes. The dns traffic visible in the "WSL" adapter is logical and immediate in all cases (request goes immediately out to one of the Taps and when reply is seen in WSL adapter, dig terminates immediately.Thus it is mostly interesting to see what happens in the Tap adapters and compare the two VPN setups. For better understanding of the participants, I have used LiveTcpUdpWatch tool to translate UDP traffic to PIDs. The process in "SophosTap"/"OpenTap" goes:Windows service "Dnscache" sends DNS request to correct DNS serverServer replies logically and fast. NOTE: This reply does not cause any activity in "WSL" interface!At this point, the ~10sec delay happens with "OpenTap"Windows service "SharedAccess" sends again the same DNS request to correct DNS serverServer replies logically and fast.This reply causes a (translated) reply to be immediately sent to "WSL" interface, which completes the activitySome additional things found/tried:It does not matter in which order the VPNs/WSL are started upCorrect requests always return fast and the "SharedAccess" service does not play a role in the trafficThe first reply from DNS server in both cases is identical and does not explain the difference in what happens nextThe DNS sequence is immediate even in the problem conditions if the correct target server is provided to dig command, bypassing the WSL host side resolver mechanismSpecifying the correct target DNS inside WSL Ubuntu (bypassing theDownload LiveTcpUdpWatch 1.55 - MajorGeeks
. Download LiveTcpUdpWatch [EN] Download do LiveTcpUdpWatch [PT] LiveTcpUdpWatch 다운로드 [KO] Download LiveTcpUdpWatch [NL] Pobierz LiveTcpUdpWatch [PL] Tải xuống LiveTcpUdpWatch [VI] Descargar LiveTcpUdpWatch [ES] Скачать LiveTcpUdpWatch [RU] 下载LiveTcpUdpWatch [ZH] Unduh LiveTcpUdpWatch [ID] T l charger LiveTcpUdpWatch [FR] LiveTcpUdpWatch การดาวน์โหลดฟรีและปลอดภัย LiveTcpUdpWatch เวอร์ชันล่าสุด LiveTcpUdpWatchLiveTcpUdpWatch Alternatives and Similar Software
List of Dropbox connection in LiveTcpUdpWatch
LiveTcpUdpWatch v1.30免费版下载-LiveTcpUdpWatch下载 - 手
. Download LiveTcpUdpWatch [EN] Download do LiveTcpUdpWatch [PT] LiveTcpUdpWatch 다운로드 [KO] Download LiveTcpUdpWatch [NL] Pobierz LiveTcpUdpWatch [PL] Tải xuống LiveTcpUdpWatch [VI] Descargar LiveTcpUdpWatch [ES] Скачать LiveTcpUdpWatch [RU] 下载LiveTcpUdpWatch [ZH] Unduh LiveTcpUdpWatch [ID] T l charger LiveTcpUdpWatch [FR] LiveTcpUdpWatch การดาวน์โหลดฟรีและปลอดภัย LiveTcpUdpWatch เวอร์ชันล่าสุด LiveTcpUdpWatchLiveTcpUdpWatch 1.55 - Download, Review, Screenshots
Comments
EnvironmentWindows build number: 10.0.19042.804Your Distribution version: Ubuntu 20.04Whether the issue is on WSL 2 and/or WSL 1: WSL2Steps to reproduceInside WSL2 Ubuntu:time dig +time=20 somenonexistentdomain.comshould return pretty fast, but when I connect my OpenVPN, it starts to take ~12 seconds which causes all sorts of trouble, knowing the WSL DNS is somehow queuing the requests in single thread as mentioned in #4285Problem seems to be between windows services "Dnscache" and "SharedAccess" doing their part in DNS relaying.Different setups and results:Without VPN everything worksWith our older Sophos OpenVPN everything works (uses Sophos SSL network adapter, hereafter "SophosTap")With our new OpenVPN this strange delay happens (uses TAP-Windows Adapter V9, hereafter "OpenTap")I have 2 Wiresharks monitoring both the "vEthernet (WSL)" and the "SophosTap"/"OpenTap" adapter to see how it goes. The dns traffic visible in the "WSL" adapter is logical and immediate in all cases (request goes immediately out to one of the Taps and when reply is seen in WSL adapter, dig terminates immediately.Thus it is mostly interesting to see what happens in the Tap adapters and compare the two VPN setups. For better understanding of the participants, I have used LiveTcpUdpWatch tool to translate UDP traffic to PIDs. The process in "SophosTap"/"OpenTap" goes:Windows service "Dnscache" sends DNS request to correct DNS serverServer replies logically and fast. NOTE: This reply does not cause any activity in "WSL" interface!At this point, the ~10sec delay happens with "OpenTap"Windows service "SharedAccess" sends again the same DNS request to correct DNS serverServer replies logically and fast.This reply causes a (translated) reply to be immediately sent to "WSL" interface, which completes the activitySome additional things found/tried:It does not matter in which order the VPNs/WSL are started upCorrect requests always return fast and the "SharedAccess" service does not play a role in the trafficThe first reply from DNS server in both cases is identical and does not explain the difference in what happens nextThe DNS sequence is immediate even in the problem conditions if the correct target server is provided to dig command, bypassing the WSL host side resolver mechanismSpecifying the correct target DNS inside WSL Ubuntu (bypassing the
2025-04-20