OpenVPN ba ya tashi ba tare da kuskure ba? Duba journal

Umarnin yana dawowa, sabis ɗin yana nunawa a matsayin ya kasa, kuma babu wani abu mai kama da bayani da ya isa tashar. Wannan shiru shine alamar da mutane ke kwatanta da «OpenVPN baya tashi», kuma kusan ba ya nufin shirin ya mutu ba tare da ya ce komai ba. Yana nufin saƙon ya tafi wata tashar da ba ku karanta ba, ko kuma abin da kuka fara ba shine abin da kuka daidaita ba. Ana iya gano duka biyun cikin ƙasa da minti ɗaya da zarar kun daina ɗaukan bayanan a matsayin wanda ake zargi.

Wurare huɗu suna shan fitarwar: journal ɗin unit ɗin, plugin ɗin da ya mallaki haɗin, wancan ƙarshen ramin da kuma wani binary daban da wanda kuke tsammanin yana gudana. Kowanne yana da nasa binciken.

Shiru yana nufin ba ku kalli tashar da ta dace ba

Kiran gaba yana bugawa zuwa tashar ku. Unit yana bugawa zuwa journal, kuma unit ɗin da ya kasa zai iya fita kafin ya rubuta komai idan gazawar tana cikin yadda aka fara shi ba wai abin da aka gaya masa ba. Bambancin yana da muhimmanci: babu wani shigarwa a journal yana nufin tsarin bai taɓa gudana da gaske ba, yayin da shigarwa ɗaya da fitowa bayansa yana nufin ya gudana kuma ya ƙi wani abu.

systemctl status openvpn-client@office
journalctl -u openvpn-client@office -b --no-pager

Ƙara systemctl show -p Result -p ExecMainStatus openvpn-client@office don raba fita mai tsabta daga sigina. Matsayi 1 tare da Result=exit-code shari'ar shirin ne; Result=signal ko lokaci mai ƙarewa suna nuna yanayi maimakon haka, kuma babu adadin gyaran bayanan da zai canza hakan. Rubuta duka ƙimar biyu kafin sake farawa wani abu, domin sake farawa yana share yanayin wucin gadi da ya samo su.

Sunan instance ɗin wani ɓangare ne na hanyar

Unit ɗin samfurin da aka fakiti baya ɗaukar hanyar fayil. Yana ɗaukar sunan instance, kuma ana ƙara wannan sunan zuwa wani directory don nemo bayanan: office yana warwarewa zuwa /etc/openvpn/client/office.conf a cikin fakiti na Debian da Ubuntu. Fayil mai suna office-v2.conf wanda aka fara a matsayin @office ba a taɓa karanta shi ba, kuma unit ɗin yana fita shiru domin a ganinsa babu abin da za a yi. Directory ɗin bincike ya bambanta tsakanin yanayin client da server, don haka irin wannan kuskuren yana nuni zuwa wani wuri daban gaba ɗaya idan kun canza samfurin.

Wannan sabani shine mafi yawan tushen gazawar shiru, kuma ba a ganinsa a cikin bayanan domin bayanan suna da kyau. Lissafa abin da ke akwai da gaske kuma kwatanta sunayen biyu harafi da harafi, gami da duk wani tsawo da fakiti ke tsammani.

ls -l /etc/openvpn/client/
systemctl list-units 'openvpn*' --all

Idan unit ɗin yana aiki amma ba a lissafa wani instance ba, ƙaddamarwar kanta na iya nuni ga sunan da aka sake masa suna daga baya. Sake kunna instance ɗin daidai yawanci ya isa, kuma ya dace a goge tsohon fayil ɗin unit da ya rage don kada ya rikita mutum na gaba. Fayil ɗin unit da ya rage abu ne ƙarami da ke kashe wani awa ɗaya daga baya.

Idan plugin ɗin ya mallaki ramin, tashar ba ta ganin komai

Haɗin da aka fara daga applet ɗin tebur mallakar NetworkManager ne, kuma fitarwar OpenVPN ɗinsa tana zuwa journal ɗin wannan sabis ɗin maimakon kowane shell da kuka buɗe. Gudanar da client ɗin da hannu da rashin ganin komai abin da ake tsammani ne a cikin wannan tsari, domin tsarin da aka gudanar da hannu ba shine wanda ke ɗauke da haɗin ba.

Nemo a cikin journal ɗin sabis ɗin da ya mallake shi, sannan sake yin parsing ɗin da cikakken bayani da za ku iya karantawa. Umarnin biyu da ke ƙasa suna kallon masu shi daban-daban na gazawar ɗaya.

journalctl -b -u NetworkManager --no-pager | grep -i -A3 openvpn
openvpn --config /etc/openvpn/client/office.conf --verb 4 --log /tmp/ovpn.log

Gudanar da kai yana don karanta saƙonni ne, ba don maye gurbin haɗin da ake sarrafawa ba, kuma duka biyun sun bambanta daga baya: haɗin DNS, hanyoyi da tsawon rayuwa na plugin ɗin ne. Gyara kuskuren parsing a cikin gudanar da kai ba ya gyara warwarewar suna kai tsaye da zarar applet ɗin ya karɓi ragamar, don haka ka raba abubuwan lura biyu daban.

Binary biyu, PATH ɗaya

Ginin hannu da aka shigar a ƙarƙashin /usr/local yana yin nasara a kiran shell, domin /usr/local/sbin yana zuwa kafin /usr/sbin a PATH ɗin Ubuntu na asali. Unit ba ya amfani da PATH ɗinka; yana gudanar da cikakkiyar hanyar da aka rubuta a ExecStart. Don haka sigar da ke aiki a tasharka da sigar da ke kasawa a matsayin sabis na iya zama shirye-shirye daban-daban da gaske.

Kwatanta su biyun kafin sake gina komai. Umarni na uku shine wanda ke yanke hukunci.

command -v openvpn
whereis openvpn
systemctl cat openvpn-client@office | grep ExecStart

Wani bambancin yanayi yana ɓoye a wuri ɗaya. Unit ɗin da aka fakiti yana dogara da directory ɗin lokacin gudana ƙarƙashin /run wanda systemd ke ƙirƙira masa; unit ɗin maye gurbin da aka rubuta da hannu wanda ya bar wannan saitin zai iya kasawa kafin ya buɗe fayil ɗaya, kuma gazawar tana kama da ƙin gama-gari ba tare da wani saƙon OpenVPN ba.

Gazawar da client ɗin ba zai iya bayar da rahoto ba

Wasu sakamakon ana yanke hukunci a ƙarshen nesa. Ƙofar da ke amsawa da matsayin HTTP kuma ta rufe haɗin ta gaya muku game da yanayinta, kuma mataki na gaba mai amfani shine log ɗinta ko asusun da ke bayan takardar shaidar maimakon fayilolinku na gida. Babu wani abu na gida da ya lalace a wannan yanayin, kuma gyara bayanan don ramawa yana sa ganowa ta gaba ta fi wahala. Karanta wannan log ɗin kafin ku taɓa tsarin client ɗin.

Wata shiru case ita ce client ɗin da ke aiki daidai. Tunnel ɗin yanayin client ba ya taɓa saurare a port, don haka gwajin da ke tsammanin mai sauraro a buɗe ba zai bayar da rahoto ba kuma zai yi kama da gazawa. Tabbatar wane yanayi kuka fara kafin ku yanke shawara daga jerin port mara komai.

Yi aiki da matakai bisa tsari: unit ɗin yana nan kuma sunan instance ɗin daidai ne, wani abu ya isa journal ɗin ko fayil ɗin --log, wane binary da profayil suka gudana da gaske, kuma gazawar cikin gida ce ko ta nesa. Kowane amsa yana cire wani mataki. Farawa daga bayanan yana nufin sake rubuta fayil ɗin da wataƙila ba a taɓa buɗe shi ba.