export OPT=/opt
export BUILDS=/some/where/mini_linux
mkdir -p $BUILDS
#!/usr/bin/env bash | |
# --slave /usr/bin/$1 $1 /usr/bin/$1-\${version} \\ | |
function register_clang_version { | |
local version=$1 | |
local priority=$2 | |
update-alternatives \ | |
--install /usr/bin/llvm-config llvm-config /usr/bin/llvm-config-${version} ${priority} \ |
There are plenty of tutorials online on how to install clang on windows with visual studioIDE and MinGW. However, there are none on clang with visual studio build tools.
- 64-bit Windows 7 SP1 or newer with the latest updates installed
- 6 GB of free space on the partition where Windows is installed
- internet connection (for installation only)
%VS2017BuildToolsDir%
= installation directory of VS 2017 build tools
- Two type of DNS network activities:
- lookup: DNS client queries a DNS server for information
- zone transfers: DNS server (the secondary server) requests from another DNS server (the primary server)
- DNS lookups are usualy executed usin UDP. (If some of data is lost in transit by UDP, the lookup will be redone using TCP)
- DNS sever uses well-known port 53 (UDP/TCP)
- Proxying characteristics of DNS:
add forwarding interface: | |
netsh interface portproxy add v4tov4 listenport={srcPort} listenaddress={srcIp} connectport={DesPort} connectaddress={DesIp} | |
show interface: | |
netsh interface portproxy show v4tov4 | |
delete interface: | |
netsh interface portproxy delete v4tov4 listenport={srcPort} listenaddress={srcIp} | |
----------------------------- |
#EXTINF:-1,CCTV-1 | |
rtp://239.3.1.1:8000 | |
#EXTINF:-1,CCTV-2 | |
rtp://239.3.1.2:8004 | |
#EXTINF:-1,CCTV-4 | |
rtp://239.3.1.4:8216 | |
#EXTINF:-1,CCTV-7 |
#EXTM3U name="北京联通IPTV(RTP)” | |
#EXTINF:-1,CCTV-1高清(1) | |
rtp://239.2.1.129:8000 | |
#EXTINF:-1,CCTV-2高清(2) | |
rtp://239.2.1.60:8084 | |
#EXTINF:-1,CCTV-4高清(4) | |
rtp://239.2.1.105:8092 | |
#EXTINF:-1,CCTV-7高清(7) | |
rtp://239.2.1.61:8104 | |
#EXTINF:-1,CCTV-9高清(9) |
If you're encountering ping github.com
failing inside WSL with a Temporary failure in name resolution
, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf
.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,