Musafaha yana aiki, intanet ba: me za a fara gyara a Windows 11

A Windows 11, sabbin musafaha sukan kasance kusa da browsers da ba sa buɗe komai. Musafaha yana tabbatar da cewa musayar UDP da peer ta kammala kawai. Ba ya faɗin komai game da hanyar da Windows ya sanya, resolver da yake amfani da ita, ko ko fitarwa tana tura wani abu.

Sharuddan huɗu ne ke yanke shawarar wace Layer daga cikin waɗannan ta kasa. Yin su bi da bi yana ɗaukar mintuna, yayin da sake rubuta makullai yana ɗaukar lokaci mafi tsawo kuma ba ya canza komai.

Yanke shawara Layer kafin ka taɓa makullai

Bi wurare uku, a wannan tsari. Fara da adireshin gefen tunnel, sannan IP na jama’a a matsayin lamba, kuma ka ƙare da sunan host. Inda jerin ya karye, anan ake ambaton Layer. Rashin nasara a mataki na farko shine routing, a na biyu shine turawa ko NAT, kuma a na uku shine warware sunaye.

Wannan tsari shine dukkan hanyar. Yana hana a gano kuskuren DNS a matsayin tunnel da ya karye, wanda shine mafi yawan kuskuren hanya a nan.

wg show
Find-NetRoute -RemoteIPAddress 1.1.1.1
Resolve-DnsName example.com -Server 1.1.1.1

Idan lokacin musafaha babu komai

Lokacin da lokacin musafaha babu komai, musayar da aka ɓoye ba ta taɓa kammala ba. Don haka kuskuren yana gaban routing. Ka duba adireshin endpoint da port da farko, sannan ko cibiyar sadarwa tana tace UDP. Mai ba da hosting da ke watsar da zirga-zirgar WireGuard yana haifar da daidai wannan, haka ma client da ya kwafi endpoint daga tsohuwar profile.

Bytes da ke fita ba tare da wani ya shigo ba wani yanayi ne. Wannan yana nufin NAT ko firewall da ke mayar da zirga-zirga zuwa wurin da bai dace ba.

Idan hanyar ta sha kashi a hannun adaftar jiki

Don cikakken tunnel, sashen peer dole ne ya rufe wuraren da kake tsammanin amfani da su. Windows wani lokacin yana riƙe da tsohuwar hanyar adaftar jiki ko da an saita ƙa’idar da ta shafi komai. Rarraba ƙa’idar da ta shafi komai zuwa 0.0.0.0/1 da 128.0.0.0/1 yana ƙirƙirar prefixes biyu mafi takamaimai waɗanda ke cin nasarar bincike. Rarraba aikin da aka rubuta ne, ba zaɓi ba.

Tabbatar da hakan da route print ko binciken adireshin jama’a. Interface da aka zaɓa yakamata ya zama adaftar tunnel. Idan na jiki har yanzu yana cin nasara, gyara jeri na peer kafin ka taɓa uwar garken.

Idan adireshi suna aiki amma sunaye sun kasa

WireGuard yana ɗaukar fakiti na IP kuma ba shi da ra’ayi game da DNS. Saka layin DNS = a sashen interface, ko saita adaftar ta Windows. Ba tare da shi ba, ping ta adireshi yana yin nasara yayin da kowane sunan host ke kasa, kuma masu amfani suna ba da rahoton hakan a matsayin babu intanet.

Duba waɗanne sabar Windows ke amfani da su da gaske bayan haɗi. Resolver da ya ragu a kan adaftar jiki yana bayanin gazawa ta wani ɓangare, inda wasu sunaye ke warwarewa wasu kuma ba sa. Ka share shi maimakon ƙara na biyu a kai.

Idan na’urar Windows ita ce fitarwa

Internet Connection Sharing yana sake rubuta adireshi idan an kunna shi, wanda zai iya motsa adaftar da aka raba zuwa wani jeri. Client da ke nuni ga ainihin adireshin zai daina aiki. Ƙimar rajista ScopeAddress da StandaloneDHCPAddress suna sarrafa wannan jeri, kuma saitin na iya komawa bayan sake kunnawa.

Wasu rikice-rikice biyu na musamman na Windows sun cancanci dubawa. Sabis ɗin Routing and Remote Access na iya tsoma baki da tunnel. Mai sakawa da aka gina don tsarin da bai dace ba yana kasa da saƙon da ba ya taɓa ambaton tsarin.

Gyara Layer da gwajin ya ambata, sannan sake gudanar da wurare ukun. Canjin da ya gyara gwajin sunan host amma ya karya adireshin tunnel an yi shi ne a Layer da bai dace ba.