Samun shiga lokaci-lokaci ta AWS Client VPN: duba kowace subnet da aka haɗa
Wasu zaman AWS Client VPN suna isa VPC ɗin manhajar yayin da wasu ke ƙarewa da lokaci. Kwatanta hanyoyin ƙarshen wuri da teburin hanya na VPC na kowace haɗi da farko.
Wani mai amfani ya haɗa, ya buɗe manhajar ciki kuma ya sami amsa; wani abokin aiki a kan wannan ƙarshen wuri ya sami ƙarewar lokaci daga kwamfutar tafi-da-gida iri ɗaya a kan Wi-Fi ɗaya. Wannan tsarin shine alamar ƙarshen wurin client VPN da ke da fiye da ɗaya subnet da aka haɗa, inda hanyoyin ba su daidaita ba. Ina bin wannan daga console zuwa waje, domin tabs biyu ne ke yanke shawara ko sauran binciken ya cancanci yi. Babu wani abu a cikin saitin client da ke bayyana hakan.
Fara daga ƙarshen wuri kuma jera haɗin
A cikin console ɗin VPC, buɗe Client VPN endpoints, zaɓi ƙarshen wuri kuma karanta tab ɗin Associations. Kowace haɗi subnet ce a cikin yankin samuwa, kuma client yana sauka a kan wanda sabis ɗin ya zaɓa lokacin da aka gina haɗin. Rubuta ID ɗin subnet da teburin hanya da kowace ke amfani da shi a zahiri, domin waɗannan jerin biyu sune kwatancen da za ka yi.
Idan ƙarshen wuri ya nuna haɗi ɗaya kawai, wannan ka’idar ba daidai ba ce kuma client shine mafi kyawun wanda ake zargi.
Kwatanta teburin hanyar ƙarshen wuri da kowace haɗi
Buɗe tab ɗin Route table a kan wannan ƙarshen wuri. Kowace CIDR na manufa a can tana da manufa, kuma a client VPN manufar ita ce haɗi maimakon ƙofa. AWS na buƙatar shigarwar manufa ga kowace subnet da aka haɗa, don haka hanyar da ta nufi ɗaya kawai daga cikinsu tana sa samun shiga ya dogara da inda zaman ya sauka. Duba manufar da kake buƙata da gaske, sannan duba ƙa’idar izininta, domin hanya tana ba da hanya kuma ƙa’ida ce ke yanke shawara wanda zai iya amfani da ita.
Da zarar ka tsara duka matakan biyu a teburi, wahala ne ka rasa gazawar.
| Associated subnet | Endpoint route to 10.200.0.0/16 | VPC route in that subnet |
|---|---|---|
| subnet-aaa | Targets the association | 10.200.0.0/16 to pcx-example |
| subnet-bbb | Targets the association | No matching entry |
Layi na biyu shine duk bug ɗin a yawancin tikiti. Hanyar ƙarshen wuri tana nan, don haka babu wanda ya kara duba, kuma fakitin yana mutuwa tsalle ɗaya bayan haka a cikin VPC.
Bi kowace subnet cikin teburin hanyarta mai tasiri
Subnet ɗin da ba ta da haɗin teburin hanya bayyananne tana gado babban teburin VPC. Karanta teburin da ke aiki a zahiri, ba wanda sunansa ya yi kama da daidai ba, kuma kwatanta manufa da manufa maimakon lakabin da ke kan layi.
Jagorar AWS kan samun shiga lokaci-lokaci tana bayyana wannan a matsayin rufe hanyoyi a duk haɗin, wanda shine daidaitaccen tsari. Ƙarshen wuri yana kai fakitin zuwa subnet, kuma teburin wannan subnet ɗin dole ne ya san inda cibiyar sadarwar manhajar take.
Gyara layin da ya ɓace a cikin teburin da ya mallake shi. Kwafin duk teburin hanya daga subnet mai aiki yana kwafin zaɓuɓɓukan intanet, na’ura da keɓewa waɗanda ba a taɓa nufin wannan ba, kuma wannan musayar yawanci ya fi munin katsewar da ka fara da ita.
Duba ƙa’idodin izini, sannan hanyar dawowa
Ƙa’idodin izini na kowace manufa ne kuma na kowace ƙungiya, kuma ana tantance su dabam da hanyoyi. Manufar da ke da hanyoyi a ko’ina amma ba ta da ƙa’ida ga ƙungiyar mai amfani tana aiki kamar baƙin rami da teburin hanya mai kama da lafiya.
Hanyar dawowa ta cancanci irin wannan kulawa. Haɗin peering yana buƙatar hanya a cikin VPC ɗin manhaja da ke nuni zuwa CIDR ɗin client, ƙa’idodin ƙungiyar tsaro da ke ba da izinin zirga-zirga a ɓangarorin biyu, da ACL ɗin cibiyar sadarwa waɗanda ba sa jefa shi. Isarwa ta gefe ɗaya, inda ping ke aiki amma musafaha na TCP ba ya aiki, yawanci yana nuni zuwa ACL ko ƙungiyar tsaro maimakon VPN.
Ƙungiyoyin tsaro na ƙarshen wuri da kansu suna zaune a kan mu’amalolin cibiyar sadarwa na roba na haɗin, don haka ƙa’idar da ke ba da izinin tashar manhaja daga CIDR ɗin client dole ne a haɗa ta da haɗin, ba kawai da misali ba.
Tabbatar da sake haɗawa, ba da buƙata ɗaya ta sa’a ba
Tare da split tunnel, ana tura hanyoyin ƙarshen wuri lokacin da aka kafa haɗin, don haka saitin hanyoyi da ya canza ba ya taɓa isa client ɗin da ya kasance a haɗe. Cire haɗin kuma sake haɗawa ta hanyar client ɗin da aka goyi bayan, sannan tabbatar da cewa sabbin hanyoyin suna nan a kan na’urar.
A ƙarshe, haɗa log ɗin haɗin da adireshin da client ya karɓa, kuma maimaita gwajin sau da yawa don samun fiye da haɗi ɗaya. Buƙata ɗaya mai nasara bayan gyara tana tabbatar da cewa hanya ɗaya tana aiki, kuma tikitin ya kasance game da ɗayan.