VPN na Windows yana nuna 255.255.255.255: shin mask ɗin ba daidai ba ne?

Ramin yana haɗawa, ka buɗe bayanan adaftan kuma mask ɗin yana nuna 255.255.255.255. Idan an kwatanta da 255.255.255.0 na LAN ɗin ofis ɗin yana kama da lalacewa, kuma a nan ne kuskuren kan fara. A haɗin point-to-point mask na host shine ainihin bayanin ƙarshen gida, kuma cibiyoyin sadarwa na nesa suna zuwa a matsayin hanyoyi maimakon a matsayin subnet da aka haɗa. Hanyar da ke ƙasa ta raba tambayoyin biyu don kada ka sake gina kewayon DHCP mai aiki kawai don gyara ƙimar da aka nuna.

Haɗin point-to-point ba yanki ne na Ethernet ba

Interface na Ethernet yana buƙatar mask na subnet saboda kowane adireshi a cikin wannan kewayon ana iya isa gare shi a kan igiya ɗaya. Rami irin na PPP yana da peer ɗaya kawai a wancan ƙarshen. Babu yankin watsa labarai, babu ARP kuma babu dalilin da adireshin gida zai bayyana kewayon.

Tattaunawar adireshi na wannan ƙirar an bayyana ta a cikin RFC 1332, wadda ta shafi yadda ɓangarorin biyu suka yarda kan adireshinsu. Abin da ba ta yi ba shi ne ba da LAN ɗin ofis ga abokin ciniki a matsayin cibiyar sadarwa da aka haɗa kai tsaye. Abokin ciniki yana koyan inda ofis ɗin yake ta hanyar shigar da hanyoyi ta hanyar haɗin, kuma waɗannan hanyoyin ne ke yanke shawarar isa ga gaske.

Wannan ba yana nufin kowane mask ɗin da za ka gani daidai ne ba. Abokin ciniki da ba a daidaita shi ba zai iya haifar da adireshi mai ban mamaki. Batun ya fi ƙunci: mask na host a irin wannan adaftan ana tsammaninsa, don haka shi kaɗai ba hujja ba ce ta kuskure.

Mataki 1: tabbatar da ƙirar interface

Duba menene adaftan kafin ka yi hukunci kan abin da yake faɗa. Jerin bayanin yana gano direba, kuma tsawon prefix ɗin da ke kan adireshin da aka ba shi yana tabbatar da abin da abokin ciniki ya tattauna:

Get-NetAdapter | Select-Object Name,InterfaceDescription,Status,ifIndex
Get-NetIPAddress -InterfaceAlias 'Corp VPN' | Select-Object IPAddress,PrefixLength,PrefixOrigin
Get-NetIPInterface -InterfaceAlias 'Corp VPN' | Select-Object AddressFamily,ConnectionState,NlMtu

Umurnin na uku shine wanda ke warware yawancin muhawara. Ƙaramin matsakaicin sashin watsawa yana nuna alamar haɗin da aka lulluɓe, yayin da ƙimar kama da Ethernet tana nuna wani ƙirar adaftan kama-da-wane daban. Idan bayanin ya ambaci direban PPP ko RAS kuma prefix ɗin 32 ne, kana kallon ainihin ƙirar da aka bayyana a sama kuma za ka iya daina damuwa game da mask ɗin.

Mataki 2: karanta hanyar manufar da ke kasawa

Ana yanke shawarar isa ga kowane manufa, kuma interface ɗaya da aka haɗa ba ya gaya maka komai game da hakan. Tambayi teburin hanyoyi kai tsaye game da adireshin da mai amfani yake ƙoƙarin isa:

Get-NetRoute -InterfaceAlias 'Corp VPN' | Select-Object DestinationPrefix,NextHop,RouteMetric
Find-NetRoute -RemoteIPAddress 10.24.6.15
route print -4

Find-NetRoute ita ce amsa kai tsaye: tana ambaton interface da adireshin tushen da tsarin zai yi amfani da shi ga wannan manufa. Idan ta dawo da ramin, zirga-zirgar zuwa wannan host ɗin tana tafiya ta ramin kuma mask ɗin bai taɓa zama matsalar ba.

Idan ta dawo da adaftan zahiri, kwatanta hanyoyin biyu masu yiwuwa da ma’aunansu. Hanya mafi ƙayyadaddun gida, saura daga wani abokin ciniki ko ƙaramin ma’auni a kan hanyar zahiri duk suna cin nasara a kan faffadan hanyar rami. Sakamakon da ake gani shine arzikin da ba a iya isa gare shi yayin da komai yana aiki. Dogayen prefix kullum suna cin nasara, don haka wanda ya ci nasara yawanci hanya ce ta host da wani ya ƙara watanni da suka wuce kuma ya manta.

Duba kuma ɓangarorin biyu yayin da kake nan. Hanya zuwa ɓangaren uwar garke tana da muhimmanci amma ba ta isa ba, domin amsar dole ta dawo ta ramin. Lokacin da host na ciki ɗaya yake aiki ɗayan kuma ba ya, bambancin yawanci yana cikin wannan teburin ba cikin daidaitawar adaftan ba.

Mataki 3: raba warwarewar suna daga shiga sabis

Manhajar da ba ta buɗe rabo tana iya kasawa a ɗaya daga cikin matakai biyu mabambanta. Warware sunan, sannan ka isa adireshin. Idan na farko ya kasa kuma na biyu ya yi aiki, ramin yana lafiya kuma mai warwarewa ba ya lafiya:

Resolve-DnsName files.corp.example.internal
Get-DnsClientServerAddress -InterfaceAlias 'Corp VPN'
Test-NetConnection -ComputerName 10.24.6.15 -Port 445

Gwajin adireshi mai nasara tare da gwajin suna mai kasawa yana gano matsalar a warwarewa, kuma umurnin na biyu yana nuna ko interface ɗin rami ya sami uwar garke kwata-kwata. Yawancin abokan ciniki suna tura DNS a matsayin ɓangare na daidaitawar rami, kuma bayanin da ya yi watsi da waɗannan zaɓuɓɓukan da aka tura zai bar na’urar tana amfani da mai warwarewa wanda ba ya ganin yankin sirri.

Kada ka ɗauki adireshi mai aiki a matsayin maganin dindindin. Haɗawa da adireshi yana ƙetare warwarewar suna kuma zai iya lalata tabbacin ainihi na uwar garke da manhajar za ta yi in ba haka ba. Wannan koma-baya ne na tsaro da aka kama da maganin wucin gadi. Yi amfani da shi don gano kuskuren, sannan ka gyara warwarewar.

Komawa baya: kada ka sake gina DHCP saboda ƙimar da aka nuna

Idan ka riga ka fara canza sabis ɗin adireshi, tsaya ka duba ko wani abu da ka canza yana da muhimmanci. Sake ƙirƙirar yanki, sake fitar da leases ko motsa tafkin yana canza yanayin da wasu abokan ciniki suka dogara da shi, kuma babu ɗaya daga cikinsu da mask na host a kan adaftan point-to-point ya tabbatar da shi.

Get-DnsClientServerAddress -InterfaceAlias 'Corp VPN'
Find-NetRoute -RemoteIPAddress 10.24.6.15
Test-NetConnection -ComputerName files.corp.example.internal -Port 445

Gudanar da waɗannan ukun bayan kowane canji da aka yi niyya sannan ka kwatanta da gudun da ya gabata. Sakamakon da ke da amfani shine hanyar da aka rubuta zuwa ga arzikin, ba adaftan da mask ɗinsa ya yi kama da LAN ɗin ofis ba.

Sannan ka rubuta abin da mask ɗin ya ke nufi da gaske, domin mutum na gaba zai buɗe wannan tattaunawa kuma ya kai ga wannan kuskuren ƙarshe. Jumla ɗaya a cikin bayanan martabar, tana cewa ramin point-to-point ne kuma subnets na nesa suna zuwa a matsayin hanyoyi, tana ceton dukan binciken a gaba.