DNS-ka martida VirtualBox wuu xumaadaa marka host-ku ku biiro VPN

Barnaamij gudaha ah ayaa lagu xalliyaa host-ka Windows isla marka uu VPN-ku xidhmo, halka martida Ubuntu ee ka dambeysa NAT-ka VirtualBox ay wali aysan heli karin. Martidu waxay leedahay resolver u gaar ah, adapter-ka NAT-na wuxuu DNS ku maareyn karaa in ka badan hal siyaabood. Beddelaadda resolver-ka martida oo lagu beddelo server guud waxay ka dhigtaa shabakadaha caadiga ah inay shaqeeyaan iyo magacyada gaarka ah inay fashilmaan, taasoo dhibaatada u rartaa halkii ay xalin lahayd. Afarta baaritaan si isku xigta u samee oo ku joogso midda ugu horeysa ee aan waafaqsaneyn.

Xaqiiji habka adapter-ka ee aad baarayso

Kaliya adapter ku jira habka NAT caadiga ah ayaa u dhaqma sida maqaalkani sharraxayo. Adapter-ka buundada wuxuu ku fadhiyaa shabakadda jireed isagoo leh aqoonsigiisa, shabakadda NAT waa isku-beddel virtual ah oo magac leh oo leh DHCP iyo DNS u gaar ah, iyo macmiilka VPN ee gudaha martida wuxuu ku daraa resolver labaad oo dhan. Xaqiiji habka ka hor intaadan sii akhrin, sababtoo ah hagaajinta way ku kala duwan tahay mid kasta oo ka mid ah kiisaskan.

Hal VM waxay qaadi kartaa laba adapter oo ku jira habab kala duwan, kan la saameeyayna mar walba ma aha kan ugu horeeya.

Sidoo kale xaqiiji in host-ku uu magaca xalliyo. Fur isla barnaamijka host-ka iyadoo tunnel-ku kor yahay, adigoo isticmaalaya isla magaca buuxa ee martidu isticmaali doonto. Haddii host-kuna fashilmo, khaladku ma aha martida oo isbeddel kasta oo shabakadda virtual ah ma hagaajin doono.

Raac hal magac iyada oo loo marayo resolver-ka martida

Dooro hal magac gudaha ah iyo hal magac kontorool oo guud, ka dib labadaba ku tijaabi labada goobood. Magaca guud ee la xalliyo halka kan gaarka ah aan la xallin wuxuu khaladka u tilmaamaa wadada gaarka ah ee aan ahayn xallinta magacyada guud ahaan. Tijaabinta magaca gaarka ah oo kaliya kuma siiso awood aad ku kala garto resolver jaban iyo waddo jaban.

Gudaha martida, eeg waxa resolver-ka dhab ahaan loo qaabeeyay. Martida Ubuntu ee ordineysa systemd-resolved, xaaladda xiriir kastaa waxay muujineysaa server-yada soo gaaray, faylka resolv.conf-na wuxuu yeelan karaa oo kaliya cinwaan stub, taas oo sax ah oo aan shaki lahayn. Fayl gacan lagu tafatiray ama macmiil DNS sir ah oo gaar ah ayaa u diri kara weydiimaha meel kale gebi ahaan. Qor waxa aad heshay ka hor intaadan beddelin.

resolvectl status
resolvectl query app.internal.example

Halkan kala sooc xallinta iyo gaaritaanka. Cinwaanka yimaada iyadoo adeeggu aan la gaari karin waa su'aal waddo ama siyaasad, ma aha DNS.

Isku day habka resolver-ka host-ka ee adapter-kaas

Doorashooyinka NAT DNS ee VirtualBox waxay sharraxaan habab kala duwan, farqiguna wuxuu muhiim noqdaa marka resolver-ka host-ka laftiisu uu tunnel-ka la beddelo. Proxy-ga DNS wuxuu codsiyada martida u gudbiyaa server-yada la siiyay. Habka resolver-ka host-ku wuxuu qabtaa codsiyada oo wuxuu wacaa DNS API-ga host-ka, taasna waa habka raaca resolver-ka Windows ee uu dib u qaabeeyay macmiilka VPN.

Daar habka khaldan oo amarku wali wuu guuleysan doonaa halka dhaqanku aanu isbeddelin, taas oo ah qaab jahawareer leh oo duhurnimo lumis ah.

VBoxManage modifyvm "work-ubuntu" --natdnshostresolver1 on

Qor dejinta hadda ee VM-ka, dami oo u jeedi adapter-ka aad horay u xaqiijisay. Lambarka ugu dambeeya ee doorashada waa lambarka adapter-ka ee ma aha joogto, sidaas darteed ku dabaqidda mashiinka adapter-ka la saameeyay uu yahay kan labaad waa hawlgalka aamusan oo aan saameyn lahayn. Bilow martida oo hubi qaabeynta resolver-ka ee ay dhab ahaan heshay, sababtoo ah dejinta gacan ku qoran ee martida waxay ka sarreyso wax kasta oo lakabka NAT bixiyo. Xusuuso in habka resolver-ka host-ku uu sidoo kale u maleynayo in wadada DNS ee host-ka laftiisu ay tahay tan aad rabtay inaad wadaagto.

Ku celi isla tijaabooyinka inta lagu jiro dib u xidhitaanka VPN

Ku celi labada weydiin ee martida, ka dib fur barnaamijka dhabta ah oo u ogolow inuu shahaadada isagu xaqiijiyo. Tijaabada cinwaan oo kaliya ayaa faa'iido u leh in lagu go'doomiyo xallinta magacyada mana la mid tahay fadhi TLS shaqeynaya, sidaas darteed ha ku joogin ping. Ka dib, waqti la ansixiyay, jar oo dib u xidh tunnel-ka host-ka oo mar kale ku celi. Dhaqanka ku sii jira oo kaliya xiriirka ugu horeeya ee ka dib boot-ka waa dhibaato meertada nololeed oo la soo sheego, ma aha sir DNS oo resolver kale lagu daba galo.

In xallinta guud ay shaqeyso ma caddeyso in weydiimaha gaarka ah ay ku sii jireen wadada siyaasaddaadu u baahan tahay.

Marka habka resolver-ka host-ku uusan waxba beddelin, soo celi qaabeynta la qoray oo hayso afarta indho-indheyn: waxa host-ku soo celiyay, waxa martidu soo celisay, habka adapter-ka iyo xaaladda resolver-ka. Server gudaha ah oo aan la gaari karin, shaandheyn ka saarta maraakiibta hypervisor-ka iyo dib u qoris dhinaca martida mid kastaa wuxuu u baahan yahay sixid kala duwan. U beddelashada adapter-ka buundo waxay beddeshaa naqshadda shabakadda mana aha dib u dejinta DNS.