WSL2 ma lumiyay DNS ka dib isku xirka VPN? Laba sababood

Ping cinwaan ahaan wuu ka shaqeeyaa gudaha qaybinta, rakibaadda xirmooyinka iyo soo dejinta git ma shaqeeyaan, cilad-dhacaanna waxay soo muuqatay isla markiiba ka dib markii tunnel-ku soo kacay. Kaliya magacyada ayaa joojiyay xallinta, taasoo tilmaamaysa DNS halkii ay ka tilmaami lahayd isku-xirka. Dib-u-rakibidda xirmooyinka ayaa ah tallaabada koowaad ee khaldan ee ugu caansan halkan. WSL2 waxay leedahay laba siyaabood oo madax-bannaan oo soo saara isla calaamaddaas, oo mid kastaa waxay u baahan tahay hagaajin gudban.

Sababta qaybintu u haysato resolver u gaar ah

Macaamilka DNS ee Windows lagama isticmaalo gudaha qaybinta. WSL2 waxay bilaabidda ka dhistaa faylkeeda resolver, oo tilmaamaya cinwaan stub ah oo Windows ku daabacdo beddelka farsamada ee mashiinka farsamada ee caawiyaha.

Habayntaas way xasilloon tahay isbeddellada shabakadeed ee caadiga ah sababtoo ah hal mar ayaa la qoraa oo dib ayaa loo isticmaalaa. Habayntu waxay joojisaa inay sax noqoto marka macaamilka tunnel-ku dib u qoro liiska adapterrada martigeliyaha ka dib markii mashiinka farsamada caawiyaha uu hore u bilaabay.

Waxba gudaha qaybinta kama fiirsado isbeddelka, sidaas darteed faylku wuxuu sii wadaa inuu tilmaamo cinwaan laga yaabo inuusan mar dambe jirin waddada. Raadinta xigta ayaa markaas sugtaa, waqtigeeda dhammaataa, ama jawaab ka heshaa server aan waligiis maqal aagga gudaha. Gudaha, resolver-ku si fudud ayuu u joojiyaa jawaabta, magacyada oo dhanna isku mar ayay guuldarraystaan.

Marka hore ka soo ururi caddaynta labada dhinac

Diiwaangeli waxa qaybintu aragto, ka dib waxa Windows aragto, ka hor inta aadan wax beddelin. Labada aragtida oo wada jira ayaa kala sooca noocyada guuldarrada.

Gudaha qaybinta, daabac faylka resolver, shaxda waddooyinka iyo hal raadin gudaha ah iyo mid dadweyne:

ip -4 route
cat /etc/resolv.conf
getent hosts intranet.corp.example
getent hosts example.com

Windows, liis ku qor serverrada DNS adapter kasta iyo shaxda IPv4 oo leh mitirro. Macaamilka VPN wuxuu inta badan rakibaa waddo loogu talagalay subnet-ka WSL2, mitirkiisuna wuxuu go’aamiyaa in taraafikadaas ay tunnel-ka ka baxdo ama maxalli ahaan u hadho.

Get-NetAdapter | Get-DnsClientServerAddress
route print -4

Mitirka waddada ama fayl duugoobay

Cilad-dhaca koowaad waa faylka duugoobay. Resolver-ka waxaa loo qoray xaaladda adapter-ka waqtiga bilaabidda, tunnel-kuna wuu beddelay xaaladdaas. Cinwaankiisa stub hadda wuu noqon karaa mid aan la gaari karin, ama wuxuu magacaabaa server wax ka ogeyn aagga gudaha.

Kan labaad waa dhibaato waddo. Marka VPN-ku ku daro waddo daboolaysa subnet-ka WSL2 oo mitir ka hooseeya waddada xiriirka martigeliyaha, xirmooyinka loo jeediyay mashiinka farsamada caawiyaha waxay galaan tunnel-ka. Markaas waqtiga ayuu dhammaadaa adeeg kasta oo WSL2, ma aha DNS oo keliya.

Imtixaanka kala soocu hal sadar buu qaataa. Haddii cinwaan tiro ah sida resolver dadweyne uu weli ping ka jawaabo iyadoo magacyadu guuldarraystaan, waddadu way fiican tahay oo dhibaatadu waa DNS. Tani waa kiiska lagu caddeeyo beddelka resolver, kiiska aan lagu caddaynna sidoo kale wuu muuqdaa. Haddii imtixaanka tirooyinkuna guuldarraysto, mashiinka farsamada caawiyaha wuxuu lumiyay waddadiisa oo fayl resolver ah ma hagaajin doono taas.

Kiiska waddada, ka saar mitirka otomaatiga ah adapter-ka tunnel-ka oo sii lambar ka sarreeya waddada xiriirka WSL2:

Get-NetAdapter | Where-Object InterfaceDescription -Match VPN | Set-NetIPInterface -InterfaceMetric 5500
wsl.exe --shutdown

Damin ayaa muhiim ah. Beddelka mitirku dib uma qoro mashiinka farsamada caawiyaha ee socda, sidaas darteed qaybinta waa in dib loo dhisaa ka hor inta beddelku muuqan.

Faylka si ula kac ah u qaado

Haddii waddadu sax tahay oo kaliya magacyada gudaha guuldarraystaan, resolver-ka ayaa qaladka leh oo waad joojin kartaa matoorka. Kani waa isbeddel ula kac ah oo leh kharash dayactir, ma aha xal ku meel gaar ah oo si taxadar la’aan ah loo dabaqo.

Gudaha qaybinta ka samee /etc/wsl.conf oo leh qaybta shabakadda ee damisa abuurista, ka dib adiguba qor faylka resolver, server-ka shirkadda marka hore iyo mid dadweyne oo kayd ah ka dib:

[network]
generateResolvConf = false

search corp.example
nameserver 10.88.4.53
nameserver 9.9.9.9

Nidaamka ayaa muhiim ah. Resolver dadweyne ma jawaabi karo magac gudaha, kaydkuna wuxuu u jiraa kaliya raadinta internetka. Markii faylku kaaga noqdo, waxba dib uma abuurto, sidaas darteed resolver shirkadeed guuraya wuxuu noqdaa hakad adiga laftaada ah inaad aragto.

Hubi magacyada, ka dib xirmooyinka

Xaqiiji hal magac gudaha ah iyo mid dadweyne oo leh resolver-ka nidaamka, ka dib ku celi hawsha guuldarraystay. Maamulayaasha xirmooyinka mararka qaar waxay isticmaalaan resolver u gaar ah, taas ayaa sabab u ah in getent shaqeeya uu la wadaagi karo rakibaad jaban.

Haddii aad otomaatig ka dhigto dib-u-qorista, ka dhig mid isku mid ah natiijada: tunnel la’aan, hay faylka hore u jiray halkii aad qori lahayd liis server oo madhan.

getent hosts intranet.corp.example
resolvectl status | head -20
getent hosts example.com

Raadin gudaha ah oo shaqeeya iyo raadin dadweyne oo shaqeeya, laga soo bilaabo gudaha qaybinta, ayaa ah natiijada mudan in la diiwaangeliyo. Calaamadda VPN cagaaran ee martigeliyaha midkoodna ma caddeyso.