Shin VM ɗinka yana amfani da VPN na host? Gwada shi daga cikin guest
Adireshin fitar host ba ya faɗin komai game da hanyoyin guest. Rubuta yanayin cibiyar sadarwa, duba hanyar guest da resolver ɗinsa, sannan gwada yanayin gazawa.
Kana duba IP na jama'a na host, yana nuna VPN, kuma ka kammala cewa VM an rufe shi. Wannan kammalawar gwajin ba ta goya ta. Guest yana da nasa teburin turawa, nasa resolver da kuma nasa interfaces, kuma adireshin fitar host ba ya faɗin komai game da su.
Dole ne a gudanar da gwajin a cikin guest, kuma dole ne ya ambaci abin da ya auna.
Fara a cikin guest, ba a browser na host ba
Da farko rubuta yanayin cibiyar sadarwa na hypervisor: NAT, bridged, host-only ko macvtap. A yanayin NAT host yana turawa guest traffic, don haka tunnel na host na iya aiki ko a'a dangane da yadda client ke shigar da hanyoyi. A yanayin bridged guest abokin tarayya ne a LAN na zahiri kuma tunnel na host ba shi da mahimmanci. Waɗannan yanayi biyu suna ba da amsoshi masu saɓani daga tsarin host ɗaya.
Rubuta yanayin kafin ka canza wani abu, domin shi ne ke ƙayyade abin da sakamakon zai iya nufi.
Yi buƙata ɗaya da ka san inda za ta je
Yi amfani da buƙata marar lahani zuwa sabis da ke bayar da adireshin tushen da ya gani. Sannan duba shawarar turawa ta guest ɗin kansa don wannan inda za a je: ip route get 203.0.113.5 yana buga interface da gateway da guest zai yi amfani da su.
Idan interface ɗin shine NIC na yau da kullum na guest, traffic ba ya wucewa ta tunnel a cikin guest.
Wani adapter na biyu, saitin proxy ko VPN client a gefen guest na iya canza amsar ga application ɗaya ba ga wani ba. Gwada application ɗin da kake da muhimmanci da shi, ba buƙata ta gama-gari daga shell ba.
Duba resolver ɗin daban
Adireshin fitar da ya canza ba ya gaya maka wane resolver ne ya kula da sunan host. Tambayi sunan a bayyane da kayan aikin da ya dace da platform, kuma lura wane server ya amsa. Rarrabe DNS yana nufin tambayar resolver da tambayar turawa suna da amsoshi daban-daban.
Waɗannan biyu na iya banbanta ta kowace hanya, kuma bambancin shine ainihin bug sau da yawa.
A host mai systemd, resolvectl query yana ambaton interface da DNS server da ke bayan amsar. Tsofaffin saiti suna nuna server a cikin fitowar dig — ko ta yaya, manufar ita ce a ga wane server ya amsa, ba kawai ko amsa ta iso ba.
Gwada manufar gazawa, ba nasara kawai ba
Idan buƙatar ita ce babu traffic da zai fita waje da tunnel, buƙata mai nasara ba ta tabbatar da komai. Yi amfani da gwajin gazawa mai sarrafawa da client ke goyan bayan: dakatar da tunnel ta hanyar da ake goyan bayan, ka ga ko an toshe sabuwar buƙata daga guest. Kada ka ɗauka cewa kill switch na client ɗin host ya rufe kowane tsarin tura na virtual. Iyakar da aka rubuta ita ce kawai abin da za ka iya dogaro da shi.
Guest da ke komawa kan NIC na zahiri lokacin da tunnel ya faɗi yana yin daidai abin da yanayin NAT ya yarda.
Rubuta yanayin da iyaka
Rubuta yanayin hypervisor, interface da hanyar guest, resolver, da application da ka gwada. Ƙara kwanan wata, domin dawo da snapshot ko sabunta hypervisor na iya canza duka huɗu.
Idan IPv4 ya bi tunnel, faɗi haka. Kada ka faɗaɗa da'awar zuwa IPv6, wani sararin suna ko wani VM a wata cibiyar sadarwa.