{"id":37303,"date":"2019-10-31T22:16:52","date_gmt":"2019-10-31T19:16:52","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya\/"},"modified":"2019-10-31T22:16:52","modified_gmt":"2019-10-31T19:16:52","slug":"trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 20. Ruterizimi statik","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sotiri sot do t\u00eb flasim p\u00ebr ruterizimin statik dhe do t\u00eb shqyrtojm\u00eb tre tema: \u00e7far\u00eb \u00ebsht\u00eb ruterizimi statik, si konfigurtohet ai dhe cila \u00ebsht\u00eb alternativa e tij. Ju shihni topologjin\u00eb e rrjetit, e cila p\u00ebrfshin nj\u00eb kompjuter me adres\u00ebn IP 192.168.1.10, i lidhur p\u00ebrmes nj\u00eb switch-i me nj\u00eb port\u00eb, ose router. P\u00ebr k\u00ebt\u00eb lidhje shfryt\u00ebzohet porta e router-it f0\/0 me adres\u00ebn IP 192.168.1.1.<\/p>\n

\"Trajnimi
\n
\nPorti i dyt\u00eb i k\u00ebtij router-i f0\/1 me adres\u00ebn IP 192.168.2.1 \u00ebsht\u00eb i lidhur me portin f0\/0 t\u00eb nj\u00eb router-i tjet\u00ebr, dhe ky interfaci ka adres\u00ebn 192.168.2.2. Router-i i dyt\u00eb \u00ebsht\u00eb i lidhur me portin f0\/1 me adres\u00ebn 192.168.3.2 me router-in e tret\u00eb, i cili shfryt\u00ebzon p\u00ebr k\u00ebt\u00eb lidhje portin f0\/0 me adres\u00ebn IP 192.168.3.3. <\/a><\/noindex><\/p>\n

P\u00ebrfundimisht, router-i i tret\u00eb \u00ebsht\u00eb i lidhur me switch-in e dyt\u00eb p\u00ebrmes portit f0\/1 me adres\u00ebn 192.168.4.3, dhe switch-i \u00ebsht\u00eb i lidhur me kompjuterin e dyt\u00eb me adres\u00ebn IP 192.168.4.10.
\nN\u00ebse ju dini si t\u00eb ndajm\u00eb subnetet n\u00ebp\u00ebrmjet adresave IP, at\u00ebher\u00eb p\u00ebrcaktoni se segmenti nga kompjuteri i par\u00eb deri tek router-i i par\u00eb i p\u00ebrket nj\u00eb subnetwork-u, segmenti midis router-it t\u00eb par\u00eb dhe t\u00eb dyt\u00eb i p\u00ebrket rrjetit t\u00eb dyt\u00eb, nd\u00ebrmjet router-it t\u00eb dyt\u00eb dhe t\u00eb tret\u00eb i p\u00ebrket rrjetit t\u00eb tret\u00eb dhe midis router-it t\u00eb tret\u00eb dhe kompjuterit t\u00eb dyt\u00eb i p\u00ebrket rrjetit t\u00eb kat\u00ebrt. K\u00ebshtu, ne kemi 4 rrjete t\u00eb ndryshme. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse kompjuteri 192.168.1.10 d\u00ebshiron t\u00eb komunikoj\u00eb me kompjuterin 192.168.4.10, at\u00ebher\u00eb s\u00eb pari ai duhet t\u00eb d\u00ebrgoj\u00eb t\u00eb dh\u00ebnat e tij te gateway 192.168.1.1. Ai krijon nj\u00eb frame, n\u00eb t\u00eb cilin vendos adres\u00ebn IP t\u00eb burimit dhe destinacionit, adres\u00ebn MAC t\u00eb burimit dhe destinacionit dhe e d\u00ebrgon at\u00eb te router-i. Ai hedh informacionin e nivelit t\u00eb dyt\u00eb, duke p\u00ebrfshir\u00eb adresat MAC, dhe shqyrton informacionin e nivelit t\u00eb tret\u00eb. Duke e ditur se t\u00eb dh\u00ebnat jan\u00eb t\u00eb adresuara p\u00ebr nj\u00eb pajisje me adres\u00ebn IP 192.168.4.10, router-i kupton se nj\u00eb pajisje e till\u00eb nuk \u00ebsht\u00eb e lidhur me t\u00eb, k\u00ebshtu q\u00eb ai thjesht duhet ta kaloj\u00eb k\u00ebt\u00eb frame p\u00ebrmes vetes m\u00eb tej n\u00eb rrjet. Ai i referohet tabel\u00ebs s\u00eb tij t\u00eb ruterizimit dhe sheh se t\u00eb dh\u00ebnat p\u00ebr rrjetin 4. duhet t\u00eb d\u00ebrgohen te pajisja me adres\u00ebn IP 192.168.2.2. <\/p>\n

Nj\u00ebjt\u00eb, router-i i dyt\u00eb shqyrton tabel\u00ebn e tij t\u00eb ruterizimit, ku merr vesh se t\u00eb dh\u00ebnat p\u00ebr rrjetin 4. duhet t\u00eb d\u00ebrgohen n\u00eb adres\u00ebn IP 192.168.3.3, dhe d\u00ebrgon frame-in te router-i i tret\u00eb. N\u00eb fund, router-i i tret\u00eb kontrollon tabel\u00ebn e tij, p\u00ebrcakton se rrjeti 4. \u00ebsht\u00eb i lidhur me t\u00eb, dhe d\u00ebrgon frame-in te kompjuteri i dyt\u00eb. <\/p>\n

Le t\u00eb shohim se si krijohet nj\u00eb tabel\u00eb routingu. P\u00ebr k\u00ebt\u00eb do t\u00eb p\u00ebrdorim Cisco Packet Tracer dhe do t\u00eb shikojm\u00eb se si realizohet koncepti i routing-ut. K\u00ebtu \u00ebsht\u00eb e nj\u00ebjta topologji e rrjetit, dhe tani do t'i jap router\u00ebve adresat e tyre p\u00ebrkat\u00ebse IP, duke treguar gjithashtu adresat e portave t\u00eb paracaktuar. <\/p>\n

\"Trajnimi
\n
\nNe nuk b\u00ebjm\u00eb asgj\u00eb me switch-in, sepse ai funksionon me konfigurimet e paracaktuara dhe p\u00ebrdor VLAN1. Le t\u00eb fillojm\u00eb me konfigurimin e routerit t\u00eb par\u00eb, Router0. S\u00eb pari, i japim atij emrin e hostit R1, pastaj shkruajm\u00eb adres\u00ebn IP dhe mask\u00ebn e n\u00ebndark\u00ebs p\u00ebr nd\u00ebrfaqen f0\/0. M\u00eb pas duhet t\u00eb aplikojm\u00eb komand\u00ebn no shutdown. Ju shihni se si markeri i nd\u00ebrfaqes \u00ebsht\u00eb ndryshuar nga i kuq n\u00eb t\u00eb gjelb\u00ebr, q\u00eb do t\u00eb thot\u00eb se porta iu aktivizua n\u00eb rrjet. <\/p>\n

Pastaj duhet t\u00eb konfigurojm\u00eb portin e dyt\u00eb t\u00eb routerit f0\/1, p\u00ebr derisa emri i hostit mbetet i nj\u00ebjt\u00eb, thjesht shtojm\u00eb adres\u00ebn IP 192.168.2.1 dhe mask\u00ebn e n\u00ebndark\u00ebs 255.255.255.0. Nuk ka asgj\u00eb t\u00eb re k\u00ebtu, \u00ebsht\u00eb konfigurim i thjesht\u00eb, ju tashm\u00eb e dini t\u00eb gjitha komandat, prandaj do t\u00eb kaloj shpejt p\u00ebr te routerat e tjer\u00eb. Nd\u00ebrsa do t\u00eb caktoj adresat IP dhe do t\u00eb p\u00ebrdor komand\u00ebn no shut, portat e router\u00ebve do t\u00eb ndryshojn\u00eb ngjyr\u00ebn n\u00eb t\u00eb gjelb\u00ebr, duke treguar se \u00ebsht\u00eb vendosur lidhja nd\u00ebrmjet pajisjeve. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, un\u00eb po krijoj rrjetet 1, 2, 3 dhe 4. Okteti i fundit i adres\u00ebs IP t\u00eb portit t\u00eb routerit tregon numrin e vet\u00eb routerit, nd\u00ebrsa okteti para t\u00eb fundit tregon numrin e rrjetit t\u00eb lidhur me k\u00ebt\u00eb port. <\/p>\n

Pra, adresat e portave t\u00eb routerit t\u00eb par\u00eb do t\u00eb jen\u00eb 192.168.1.1 (routeri i par\u00eb, rrjeti i par\u00eb) dhe 192.168.2.1 (routeri i par\u00eb, rrjeti i dyt\u00eb), p\u00ebr routerin e dyt\u00eb \u2014 192.168.2.2 (routeri i dyt\u00eb, rrjeti i dyt\u00eb) dhe 192.168.3.2 (routeri i dyt\u00eb, rrjeti i tret\u00eb) dhe p\u00ebr routerin e tret\u00eb \u2014 192.168.3.3 (routeri i tret\u00eb, rrjeti i tret\u00eb) dhe 192.168.4.3 (routeri i tret\u00eb, rrjeti i kat\u00ebrt). Mendoj se \u00ebsht\u00eb mjaft e leht\u00eb p\u00ebr tu mbajtur mend, megjithat\u00eb n\u00eb realitet adresat mund t\u00eb formohen ndryshe, n\u00eb var\u00ebsi t\u00eb rregullave t\u00eb pranuara n\u00eb kompanin\u00eb tuaj. Ju duhet t\u00eb ndiqni rregullat e kompanis\u00eb, sepse kolegu juaj do t\u00eb ket\u00eb m\u00eb t\u00eb leht\u00eb t\u00eb diagnostikoj\u00eb problemet n\u00eb rrjetin tuaj n\u00ebse e formoni at\u00eb sipas rregullave. <\/p>\n

K\u00ebshtu, un\u00eb p\u00ebrfundoj duke caktuar adresat IP p\u00ebr portat e routerit, dhe ju shihni q\u00eb porta e dyt\u00eb e switch-it gjithashtu ndryshoi ngjyr\u00ebn n\u00eb t\u00eb gjelb\u00ebr, pasi lidhja nd\u00ebrmjet tij dhe kompjuterit t\u00eb dyt\u00eb u krijua automatikisht. <\/p>\n

\"Trajnimi
\n
\nTani do ta shqiptoj terminalin e komandave t\u00eb kompjuterit t\u00eb par\u00eb dhe do t\u00eb pingoj kompjuterin e dyt\u00eb me adres\u00eb 192.168.4.10. Le t\u00eb kalojm\u00eb n\u00eb modin simuluese \u2013 tani po shihni l\u00ebvizjen e animuar t\u00eb paketimeve t\u00eb pingut n\u00ebp\u00ebr segmentet e rrjetit. Tani do ta filloj s\u00ebrish pingimin, p\u00ebr t\u00eb mund\u00ebsuar q\u00eb t\u00eb shikoni me kujdes se \u00e7far\u00eb po ndodh. N\u00eb an\u00ebn e djatht\u00eb n\u00eb tabel\u00eb shihni ICMP, Internet Control Message Protocol \u2013 k\u00ebshtu njihet ping. Ping \u00ebsht\u00eb nj\u00eb protokoll q\u00eb p\u00ebrdorim p\u00ebr t\u00eb verifikuar lidhjen. <\/p>\n

\"Trajnimi
\n
\nJu d\u00ebrgoni nj\u00eb paket\u00eb prove n\u00eb nj\u00eb pajisje tjet\u00ebr, dhe n\u00ebse ajo e kthen, lidhja \u00ebsht\u00eb vendosur me sukses. N\u00ebse klikoni mbi paket\u00ebn e pingut n\u00eb diagram, mund t\u00eb shihni informacionin mbi transmetimin. <\/p>\n

\"Trajnimi
\n
\nJu shihni t\u00eb dh\u00ebnat e nivelit 3 t\u00eb OSI \u2013 k\u00ebto jan\u00eb adresat IP t\u00eb burimit dhe destinacionit t\u00eb pingut, t\u00eb dh\u00ebnat e nivelit 2 n\u00eb form\u00ebn e adresave MAC p\u00ebrkat\u00ebse dhe t\u00eb dh\u00ebnat e nivelit 1 n\u00eb form\u00ebn e shenjave t\u00eb portit (portave) \u2013 k\u00ebto jan\u00eb FastEthernet0. Ju gjithashtu mund t\u00eb shihni formatin e kadrr\u00ebs s\u00eb pingut: kreu, tipi dhe trupi i paket\u00ebs. <\/p>\n

\"Trajnimi
\n
\nKadrja d\u00ebrgohet n\u00eb switch, switch-i analizon adresat MAC dhe e d\u00ebrgon at\u00eb m\u00eb tej n\u00eb rrjet tek router-i. Router-i sheh adres\u00ebn IP 192.168.4.10 dhe hodh paket\u00ebn, sepse nuk e njeh nj\u00eb adres\u00eb t\u00eb till\u00eb. Le t\u00eb shohim se \u00e7far\u00eb ndodh n\u00eb koh\u00eb reale, p\u00ebr k\u00ebt\u00eb le t\u00eb kthehemi tek pingimi n\u00eb dritaren e komandave. <\/p>\n

\"Trajnimi
\n
\nJu shihni se n\u00eb tentativ\u00ebn p\u00ebr t\u00eb pinguar kompjuterin 192.168.4.10, t\u00eb gjitha 4 paketat u humb\u00ebn \u2013 nga router-i 192.168.1.1 u mor p\u00ebrgjigje se hosti i destinacionit nuk \u00ebsht\u00eb i arritsh\u00ebm. Le t\u00eb kthehemi n\u00eb dritaren e nd\u00ebrfaqes s\u00eb komandave t\u00eb router-it dhe t\u00eb fusim komand\u00ebn show ip route. Ju shihni pjes\u00ebn m\u00eb t\u00eb r\u00ebnd\u00ebsishme \u2013 tabel\u00ebn e rutimit, dhe komanda q\u00eb kam futur \u00ebsht\u00eb nj\u00eb nga komandat kryesore t\u00eb routing-ut Cisco. N\u00eb k\u00ebt\u00eb moment, kjo tabel\u00eb p\u00ebrmban 2 regjistrime. N\u00eb fillim t\u00eb tabel\u00ebs ndodhet nj\u00eb list\u00eb e shkurtoreve t\u00eb p\u00ebrdorura, nga e cila shihet se letra C p\u00ebrfaq\u00ebson lidhjet. Regjistrimi i par\u00eb informon se rrjeti 192.168.1.0\/24 \u00ebsht\u00eb lidhur drejtp\u00ebrdrejt me portin FastEthernet0\/0, dhe rrjeti 192.168.2.0\/24 \u00ebsht\u00eb lidhur drejtp\u00ebrdrejt me portin FastEthernet0\/1. Kjo do t\u00eb thot\u00eb se n\u00eb k\u00ebt\u00eb moment router-i njeh vet\u00ebm k\u00ebto dy rrjete. <\/p>\n

\"Trajnimi
\n
\nVlera 192.168.1.0\/24 \u00ebsht\u00eb identifikuesi i rrjetit. Kur krijuam n\u00ebnrrjetet, ne krijuam nj\u00ebkoh\u00ebsisht edhe identifikuesit e tyre. K\u00ebta identifikues i thon\u00eb router-it se t\u00eb gjith\u00eb pajisjet, adresat IP t\u00eb t\u00eb cilave jan\u00eb n\u00eb intervalin nga 192.168.1.1 deri n\u00eb 192.168.1.254, ndodhen n\u00eb k\u00ebt\u00eb n\u00ebnrrjet. K\u00ebshtu, t\u00eb gjitha k\u00ebto pajisje teknikisht duhet t\u00eb jen\u00eb t\u00eb arritshme p\u00ebr router-in, pasi ai \u00ebsht\u00eb i lidhur me k\u00ebt\u00eb rrjet. <\/p>\n

N\u00ebse n\u00eb fund t\u00eb identifikuesit ndodhet vlera \/24, kjo do t\u00eb thot\u00eb se t\u00eb gjitha pajisjet e k\u00ebtij rrjeti nga 1 deri n\u00eb 254-tin do t\u00eb d\u00ebrgojn\u00eb nj\u00eb k\u00ebrkes\u00eb t\u00eb p\u00ebrgjithshme. Pra, n\u00eb k\u00ebt\u00eb router jan\u00eb t\u00eb lidhura vet\u00ebm rrjetet 1 dhe 2, k\u00ebshtu q\u00eb ai di vet\u00ebm p\u00ebr k\u00ebto rrjete. Prandaj, kur ping-u me adres\u00eb 192.168.4.10 arrin n\u00eb router, ai nuk e di se kjo adres\u00eb \u00ebsht\u00eb e arritshme p\u00ebrmes rrug\u00ebs Router0- Router1- Router2. <\/p>\n

Por ju si administrator i rrjetit e dini se kjo rrug\u00eb \u00ebsht\u00eb e arritshme, pra q\u00eb router-i i par\u00eb mund t\u00eb d\u00ebrgoj\u00eb k\u00ebt\u00eb paket\u00eb n\u00eb router-in e dyt\u00eb. Prandaj, duhet t\u00eb organizoni nj\u00eb rrug\u00ebzim statik. Le t\u00eb p\u00ebrpiqemi ta b\u00ebjm\u00eb k\u00ebt\u00eb. <\/p>\n

Ne do t'i themi k\u00ebtij router-i se \u00e7do paket\u00eb dhe \u00e7do trafik q\u00eb \u00ebsht\u00eb i destinuar p\u00ebr rrjetin 192.168.4.0\/24 duhet t\u00eb d\u00ebrgohet n\u00eb router-in e dyt\u00eb. Formati i komand\u00ebs p\u00ebr vendosjen e rrug\u00ebzimit statik ka k\u00ebt\u00eb form\u00eb: ip route . <\/p>\n

\"Trajnimi
\n
\nTani do t'ju tregoj se \u00e7far\u00eb do t\u00eb thot\u00eb kjo. Ne do t\u00eb p\u00ebrdorim p\u00ebr k\u00ebt\u00eb komand\u00ebn n\u00eb modin e konfigurimit global t\u00eb router-it. Un\u00eb shkruaj ip route 192.168.4.0 255.255.255.0 \u2013 kjo do t\u00eb thot\u00eb se \u00e7do trafik p\u00ebr pajisjet e rrjetit, t\u00eb cilat kan\u00eb adres\u00ebn IP me vler\u00ebn e oktetit t\u00eb fundit nga 1 deri n\u00eb 254, do t\u00eb shkoj\u00eb k\u00ebtu, dhe pastaj shkruaj ose IP-adres\u00ebn, ose emrin e port\u00ebs, ku duhet t\u00eb d\u00ebrgohet ky trafik. N\u00eb k\u00ebt\u00eb rast, un\u00eb shkruaj emrin e interfesit f0\/1, k\u00ebshtu q\u00eb komanda merr k\u00ebt\u00eb form\u00eb: ip route 192.168.4.0 255.255.255.0 f0\/1.<\/p>\n

\"Trajnimi
\n
\nN\u00eb vend t\u00eb interfesit t\u00eb port\u00ebs, mund t\u00eb spesifikoj adres\u00ebn e tij IP, at\u00ebher\u00eb komanda e rrug\u00ebzimit statik do t\u00eb duket si ip route 192.168.4.0 255.255.255.0 192.168.2.2.<\/p>\n

Mund t\u00eb pyesni se cila \u00ebsht\u00eb m\u00eb e mira. Mendoj se p\u00ebr rrjetet e transmetimeve, si Ethernet, \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb specifikoni adres\u00ebn IP. N\u00ebse p\u00ebrdorni rrjete t\u00eb tipit 'pik\u00eb n\u00eb pik\u00eb', si Frame Relay, \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb p\u00ebrdorni exit interface. M\u00eb von\u00eb do t\u00eb shqyrtojm\u00eb rrjetet Frame Relay, tani po p\u00ebrdor nj\u00eb variant m\u00eb t\u00eb p\u00ebrshtatsh\u00ebm t\u00eb komand\u00ebs s\u00eb routingu -192.168.4.0 255.255.255.0.<\/p>\n

Tani le t\u00eb shohim tabel\u00ebn e routingut, duke p\u00ebrdorur komand\u00ebn do show ip address. Shihni se ka nj\u00eb sh\u00ebnim t\u00eb ri, me titullin S, q\u00eb do t\u00eb thot\u00eb static. <\/p>\n

\"Trajnimi
\n
\nKy sh\u00ebnim tregon se n\u00ebse ka trafik p\u00ebr rrjetin 192.168.4.0\/24, ai duhet t\u00eb d\u00ebrgohet te adresati p\u00ebrmes pajisjes me adres\u00ebn IP 192.168.2.2. Kthehemi n\u00eb komand\u00ebn e linj\u00ebs s\u00eb komandave dhe pingojm\u00eb adres\u00ebn e nevojshme edhe nj\u00eb her\u00eb. Tani trafiku duhet t\u00eb kaloj\u00eb p\u00ebrmes routerit t\u00eb par\u00eb dhe t\u00eb arrij\u00eb routerin e dyt\u00eb, i cili duhet t\u00eb hedhi paketat.<\/p>\n

N\u00eb rastin e par\u00eb, routeri jo vet\u00ebm q\u00eb hodhi paketat, por gjithashtu i p\u00ebrgjigjej kompjuterit se adresa IP 192.168.4.10 nuk \u00ebsht\u00eb e aksesueshme. Megjithat\u00eb, routeri i dyt\u00eb mund t\u00eb p\u00ebrgjigjet vet\u00ebm routerit t\u00eb par\u00eb, nga i cili mori trafik. Le t\u00eb shohim tabel\u00ebn e routingut t\u00eb routerit t\u00eb dyt\u00eb. K\u00ebtu thuhet se Router1 njeh vet\u00ebm rrjetet 2 dhe 3 dhe nuk di asgj\u00eb p\u00ebr rrjetin 4, ku duhet t\u00eb d\u00ebrgoj\u00eb paketat e kompjuterit t\u00eb par\u00eb. Ai do t'i d\u00ebrgonte prapa nj\u00eb mesazh se hosti i destinacionit nuk \u00ebsht\u00eb i aksesuesh\u00ebm, por nuk di si t\u00eb lidhet me kompjuterin q\u00eb d\u00ebrgoi k\u00ebto paketa, sepse nuk di asgj\u00eb p\u00ebr rrjetin 1. Kjo \u00ebsht\u00eb arsyeja pse n\u00eb vend t\u00eb nj\u00eb mesazhi p\u00ebr pap\u00ebrshtatshm\u00ebrin\u00eb e hostit t\u00eb destinacionit, mor\u00ebm nj\u00eb mesazh 'Request timed out' \u2013 koha p\u00ebr pritjen e k\u00ebrkes\u00ebs skadoi. Pajisjet e ndryshme rrjetore kan\u00eb vlera t\u00eb ndryshme TTL, k\u00ebshtu q\u00eb, kur paketat IP arrijn\u00eb k\u00ebt\u00eb vler\u00eb, ato shkat\u00ebrrohen. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ndodh nj\u00eb num\u00ebrim mbrapsht \u2013 b\u00ebhet nj\u00eb hop, dhe numri i TTL ndryshon nga 16 n\u00eb 15, i dyti \u2013 nga 15 n\u00eb 14 dhe k\u00ebshtu me radh\u00eb, derisa vlera e TTL t\u00eb arrij\u00eb 0 dhe paketa t\u00eb shkat\u00ebrrohet. <\/p>\n

K\u00ebshtu funksionon mekanizmi i parandalimit t\u00eb rrethrrotullimit t\u00eb paketeve IP. Prandaj, n\u00ebse nj\u00eb pajisje nuk merr nj\u00eb k\u00ebrkes\u00eb brenda nj\u00eb kohe t\u00eb caktuar, sistemi jep nj\u00eb mesazh t\u00eb till\u00eb. Prandaj, le t\u00eb kalojm\u00eb n\u00eb cil\u00ebsimet e routerit t\u00eb dyt\u00eb dhe t'i tregojm\u00eb atij si t\u00eb arrij\u00eb n\u00eb subnets e kat\u00ebrt. P\u00ebr k\u00ebt\u00eb, un\u00eb p\u00ebrdor komand\u00ebn ip route 192.168.4.0 255.255.255.0 192.168.3.3. Tani, p\u00ebrkat\u00ebsja \u00ebsht\u00eb shfaqur n\u00eb tabel\u00ebn e rrug\u00ebve q\u00eb e thirr\u00ebm me komand\u00ebn do show ip route. <\/p>\n

\"Trajnimi
\n
\nTani Router1 di se si t\u00eb d\u00ebrgoj\u00eb trafik te adresat e subnets s\u00eb kat\u00ebrt. Ai e d\u00ebrgon at\u00eb tek routeri i tret\u00eb. Routeri i tret\u00eb, Router2, pasi \u00ebsht\u00eb i lidhur me rrjetin 4, e di me siguri si t\u00eb d\u00ebrgoj\u00eb paket\u00ebn tek kompjuteri i dyt\u00eb.<\/p>\n

\u00c7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse d\u00ebrgoj p\u00ebrs\u00ebri nj\u00eb ping? Tani t\u00eb gjitha pajisjet rrjetit e din\u00eb se si t\u00eb arrijn\u00eb kompjuterin e dyt\u00eb. A do t\u00eb jet\u00eb tani pingimi i IP-adres\u00ebs 192.168.4.10 i suksessh\u00ebm? Jo, nuk do t\u00eb jet\u00eb! <\/p>\n

Si\u00e7 e thash\u00eb, ICMP p\u00ebrfaq\u00ebson nj\u00eb protokoll t\u00eb komunikimit dyansh\u00ebm, k\u00ebshtu q\u00eb, n\u00ebse dikush d\u00ebrgon paketa ping, ato duhet t\u00eb kthehen prapa. Rrug\u00ebzimi \u00ebsht\u00eb se \u00e7do pajisje rrjeti duhet jo vet\u00ebm t\u00eb di si t'i d\u00ebrgoj\u00eb nj\u00eb mesazh dikujt, por gjithashtu t\u00eb di si t\u00eb d\u00ebrgoj\u00eb p\u00ebrgjigjen te d\u00ebrguesi i k\u00ebrkes\u00ebs. Pra, paketa e d\u00ebrguar nga kompjuteri i par\u00eb arriti me sukses tek kompjuteri i dyt\u00eb. Kompjuteri i dyt\u00eb mendon: \"super, mora mesazhin tuaj dhe tani duhet t'ju d\u00ebrgoj nj\u00eb p\u00ebrgjigje\". Kjo p\u00ebrgjigje, drejtuar pajisjes me IP-adres\u00ebn 192.168.1.10, arrin n\u00eb routerin Router2. Routeri i tret\u00eb sheh se duhet t\u00eb d\u00ebrgoj\u00eb paket\u00ebn n\u00eb subnets e par\u00eb, por n\u00eb tabel\u00ebn e tij t\u00eb rrug\u00ebve ka vet\u00ebm t\u00eb dh\u00ebna p\u00ebr subnets e tret\u00eb dhe t\u00eb kat\u00ebrt. Prandaj, ne duhet t\u00eb krijojm\u00eb nj\u00eb rrug\u00eb statike me komand\u00ebn ip route 192.168.1.0 255.255.255.0 192.168.3.2. Kjo komand\u00eb thot\u00eb se trafiku i destinuar p\u00ebr rrjetin me identifikuesin 192.168.1.0 duhet t\u00eb d\u00ebrgohet tek routeri i dyt\u00eb me IP-adres\u00ebn 192.168.3.2. <\/p>\n

\u00c7far\u00eb do t\u00eb ndodh\u00eb pas k\u00ebsaj? Routeri i dyt\u00eb di p\u00ebr rrjetet 2., 3. dhe 4., por nuk di asgj\u00eb p\u00ebr rrjetin e par\u00eb. Prandaj, duhet t\u00eb kalojm\u00eb n\u00eb cil\u00ebsimet e routerit t\u00eb dyt\u00eb, Router1, dhe t\u00eb p\u00ebrdorim komand\u00ebn ip route 192.168.1.0 255.255.255.0 192.168.2.1, dometh\u00ebn\u00eb t\u00eb tregojm\u00eb se trafiku p\u00ebr rrjetin 1. duhet t\u00eb d\u00ebrgohet p\u00ebrmes rrjetit 2. tek routeri i par\u00eb, Router0.<\/p>\n

Pas k\u00ebtij, paketi arrin routerin e par\u00eb, i cili di p\u00ebr pajisjen 192.168.1.10, sepse rrjeti i par\u00eb, n\u00eb t\u00eb cilin ndodhet kjo kompjuter, \u00ebsht\u00eb i lidhur me portin e k\u00ebtij routeri. Dua t\u00eb theksoj se tani routeri i par\u00eb nuk di asgj\u00eb p\u00ebr rrjetin 3, nd\u00ebrsa routeri i tret\u00eb nuk di asgj\u00eb p\u00ebr rrjetin e dyt\u00eb. Kjo mund t\u00eb krijoj\u00eb nj\u00eb problem, sepse k\u00ebta router\u00eb nuk din\u00eb p\u00ebr ekzistenc\u00ebn e n\u00ebnrrjeteve nd\u00ebrmjet\u00ebs. <\/p>\n

P\u00ebrs\u00ebri po pingoj adres\u00ebn 192.168.4.0, dhe shihni, k\u00ebt\u00eb her\u00eb pingimi ka kaluar me sukses. Paketat kaluan t\u00ebr\u00eb rrug\u00ebn nga kompjuteri i par\u00eb te kompjuteri i dyt\u00eb dhe p\u00ebrgjigja u kthye te d\u00ebrguesi. N\u00eb dritaren e komandave duket mesazhi se \u00e7do nj\u00eb nga 4 p\u00ebrgjigjet nga 192.168.4.0 p\u00ebrb\u00ebn 32 byte, TTL= 125 ms, dhe suksesi i pingimit \u00ebsht\u00eb 100%. Kjo do t\u00eb thot\u00eb se burimi i transmetimit mori p\u00ebrgjigje nga hosti destinacion. Pra, edhe n\u00ebse pajisjet nuk din\u00eb p\u00ebr ekzistenc\u00ebn e disa n\u00ebnrrjeteve nd\u00ebrmjet\u00ebs, kjo nuk ka r\u00ebnd\u00ebsi, n\u00ebse ato veprojn\u00eb sipas parimit 'd\u00ebrguesi p\u00ebrfundimtar \u2013 marr\u00ebsi p\u00ebrfundimtar'. Kompjuteri i par\u00eb di si t\u00eb arrij\u00eb te kompjuteri i dyt\u00eb, dhe kompjuteri i dyt\u00eb di si t\u00eb arrij\u00eb te kompjuteri i par\u00eb. <\/p>\n

Le t\u00eb shqyrtojm\u00eb nj\u00eb situat\u00eb tjet\u00ebr. Pra, kompjuteri i par\u00eb mund t\u00eb komunikohet me sukses me kompjuterin e dyt\u00eb, derisa trafiku kalon n\u00ebp\u00ebr t\u00eb gjitha k\u00ebto pajisje. Le t\u00eb shohim n\u00ebse PC0 mund t\u00eb lidhet me routerin e tret\u00eb Router2 n\u00eb adres\u00ebn 192.168.3.3 \u2013 kjo \u00ebsht\u00eb porta e rrjetit 3 t\u00eb routerit t\u00eb tret\u00eb. Pingimi tregon se kjo \u00ebsht\u00eb e pamundur \u2013 hosti destinacion nuk \u00ebsht\u00eb i qassh\u00ebm. <\/p>\n

Le t\u00eb shohim se cila \u00ebsht\u00eb arsyeja. Duke hapur tabel\u00ebn e \u043c\u0430\u0440\u0448\u0440\u0443timit t\u00eb routerit t\u00eb par\u00eb, ne shohim se ai di vet\u00ebm 3 rrjete \u2013 t\u00eb parin, t\u00eb dytin dhe t\u00eb kat\u00ebrtin, por nuk di asgj\u00eb p\u00ebr rrjetin e tret\u00eb. Prandaj, n\u00ebse d\u00ebshiroj t\u00eb lidhem me k\u00ebt\u00eb rrjet, duhet t\u00eb caktoj nj\u00eb rrug\u00eb statike p\u00ebr t\u00eb. <\/p>\n

Pra, ne kemi shqyrtuar se si mund t\u00eb konfiguroni \u043c\u0430\u0440\u0448\u0440\u0443\u0442imin statik p\u00ebr tre routera. N\u00ebse keni 10 routera dhe 50 n\u00ebnrrjete t\u00eb ndryshme, konfigurimi manual i \u043c\u0430\u0440\u0448\u0440\u0443\u0442imit statik do t\u00eb marr\u00eb shum\u00eb koh\u00eb. Kjo \u00ebsht\u00eb arsyeja pse na nevojitet \u043c\u0430\u0440\u0448\u0440\u0443\u0442imi dinamik.
\nTani do ta heq t\u00eb gjitha rrug\u00ebt q\u00eb kam krijuar. P\u00ebr k\u00ebt\u00eb, un\u00eb do t\u00eb th\u00ebrras nj\u00eb nga nj\u00eb tabelat e rrug\u00ebs s\u00eb t\u00eb gjitha router\u00ebve dhe do t\u00eb shtoj fjal\u00ebn \u00abno\u00bb n\u00eb fillim t\u00eb \u00e7do sh\u00ebnimi t\u00eb rrug\u00ebtimit statik, pra do t\u00eb p\u00ebrdor komand\u00ebn e mohimit. Tani mund t\u00eb shqyrtojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb rrug\u00ebtimi dinamik. <\/p>\n

P\u00ebr rrug\u00ebtimin dinamik, un\u00eb duhet t\u00eb aktivizoj protokollin RIP, i cili \u00ebsht\u00eb nj\u00eb protokoll shum\u00eb i shpejt\u00eb. Por sot nuk do t\u00eb diskutojm\u00eb p\u00ebr RIP-in; tema jon\u00eb \u00ebsht\u00eb rrug\u00ebtimi statik dhe doja t\u00eb tregoja se sa e lodhshme dhe e mundimshme \u00ebsht\u00eb kjo pun\u00eb. Megjithat\u00eb, un\u00eb shpejt do t'ju demonstroj si funksionon RIP-i, i cili do t\u00eb shqyrtojm\u00eb n\u00eb m\u00ebsimin e ardhsh\u00ebm.
\nDuke marr\u00eb si shembull routerin e par\u00eb, un\u00eb p\u00ebrdor komand\u00ebn router rip, pastaj do t\u00eb jap versionin 2 p\u00ebr t\u00eb specifikuar versionin e protokollit, dhe pastaj n\u00eb rreshta t\u00eb ve\u00e7ant\u00eb do t\u00eb rendis rrjetet p\u00ebr t\u00eb cilat duhet t\u00eb p\u00ebrdoret protokolli i rrug\u00ebtimit dinamik: 192.168.1.0, 192.168.2.0, dhe pastaj do t\u00eb kaloj tek routeri i dyt\u00eb dhe do t\u00eb veproj ashtu si me t\u00eb. Teknikisht, un\u00eb thjesht po tregoj rrjetet q\u00eb jan\u00eb t\u00eb lidhura me k\u00ebt\u00eb pajisje, k\u00ebshtu q\u00eb p\u00ebr routerin e dyt\u00eb do t\u00eb specifikoj 192.168.2.0 dhe 192.168.3.0, dhe p\u00ebr routerin e tret\u00eb, pas komand\u00ebs rip ver 2 \u2013 adresat 192.168.3.0 dhe 192.168.4.0. M\u00eb pas do t\u00eb kthehem tek routeri i par\u00eb dhe do t\u00eb shoh tabel\u00ebn e rrug\u00ebs. <\/p>\n

\"Trajnimi
\n
\nJu shihni se n\u00eb t\u00eb jan\u00eb shfaqur magjikisht t\u00eb gjitha rrjetet, dy t\u00eb parat jan\u00eb ato q\u00eb jan\u00eb lidhur direkt me routerin, nd\u00ebrsa dy t\u00eb tjera jan\u00eb ato p\u00ebr t\u00eb cilat lidhja b\u00ebhet n\u00ebp\u00ebrmjet protokollit dinamik t\u00eb rrug\u00ebtimit RIP. Nj\u00eb situat\u00eb e ngjashme v\u00ebrehet n\u00eb tabelat e rrugimit t\u00eb router\u00ebve t\u00eb dyt\u00eb dhe t\u00eb tret\u00eb. N\u00ebse un\u00eb lidh rrjetet 5. dhe 6. me routerin e dyt\u00eb, t\u00eb gjitha pajisjet q\u00eb p\u00ebrdorin RIP-in do ta din\u00eb p\u00ebr k\u00ebto rrjete t\u00eb reja. K\u00ebtu \u00ebsht\u00eb p\u00ebrfitimi i rrug\u00ebtimit dinamik.<\/p>\n

\"Trajnimi
\n
\nN\u00ebse tani e pingoj kompjuterin e dyt\u00eb, lidhja do t\u00eb funksionoj\u00eb pa probleme. Mund ta pingoj rrug\u00ebn e tret\u00eb, dhe ping do t\u00eb jet\u00eb i suksessh\u00ebm, sepse rruga e par\u00eb p\u00ebr shkak t\u00eb RIP di p\u00ebr t\u00eb gjitha pajisjet e t\u00eb gjith\u00eb rrjeteve. Rrug\u00ebt e dyta dhe t\u00eb treta do t\u00eb ken\u00eb t\u00eb nj\u00ebjtin \"dije\". Nuk po them q\u00eb RIP \u00ebsht\u00eb protokolli m\u00eb i mir\u00eb, por ai \u00ebsht\u00eb n\u00eb gjendje t\u00eb kryej\u00eb nj\u00eb s\u00ebr\u00eb detyrash me efikasitet. P\u00ebr momentin, dua q\u00eb t\u00eb kuptoni se \u00e7far\u00eb \u00ebsht\u00eb routing dhe si funksionon, \u00e7far\u00eb \u00ebsht\u00eb tabela e routing dhe \u00e7far\u00eb r\u00ebnd\u00ebsie ka ajo. <\/p>\n

Pavar\u00ebsisht n\u00ebse p\u00ebrdorni routing statik apo dinamik, roli i protokolleve \u00ebsht\u00eb t\u00eb plot\u00ebsojn\u00eb tabel\u00ebn e routing. Kjo tabel\u00eb duhet t\u00eb dij\u00eb p\u00ebr t\u00eb gjitha rrug\u00ebt p\u00ebr t\u00eb gjitha pajisjet e rrjetit, n\u00eb m\u00ebnyr\u00eb q\u00eb nj\u00eb pajisje t\u00eb mund t\u00eb krijoj\u00eb nj\u00eb lidhje me nj\u00eb pajisje tjet\u00ebr. <\/p>\n

Pra, sot m\u00ebsuat se routing \u00ebsht\u00eb nj\u00eb proces q\u00eb siguruan shfaqjen e t\u00eb dh\u00ebnave p\u00ebr rrug\u00ebt n\u00eb tabelat e routing, n\u00eb m\u00ebnyr\u00eb q\u00eb rruga t\u00eb mund t\u00eb marr\u00eb nj\u00eb vendim p\u00ebr d\u00ebrgimin e trafikut n\u00eb rrjet. <\/p>\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nFaleminderit q\u00eb q\u00ebndroni me ne. Ju p\u00eblqejn\u00eb artikujt tan\u00eb? D\u00ebshironi t\u00eb shihni m\u00eb shum\u00eb materiale interesante? Na mb\u00ebshtetni duke b\u00ebr\u00eb nj\u00eb porosi ose duke na rekomanduar miqve tuaj. 30% zbritje p\u00ebr p\u00ebrdoruesit e Habra n\u00eb nj\u00eb analog unik t\u00eb server\u00ebve entry-level, t\u00eb cilin e kemi shpikur p\u00ebr ju:<\/b> E gjith\u00eb e v\u00ebrteta p\u00ebr VPS (KVM) E5-2650 v4 (6 B\u00ebrthama) 10GB DDR4 240GB SSD 1Gbps nga $20 ose si t\u00eb ndajm\u00eb sakt\u00ebsisht serverin?<\/a><\/noindex> (opcionet me RAID1 dhe RAID10, deri n\u00eb 24 b\u00ebrthama dhe deri n\u00eb 40GB DDR4 jan\u00eb t\u00eb disponueshme).<\/p>\n

Dell R730xd p\u00ebr dy her\u00eb m\u00eb lir\u00eb?<\/b> Vet\u00ebm te ne 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB nga $199<\/a><\/noindex> n\u00eb Holand\u00eb! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 nga $99!<\/b><\/b> Lexoni rreth Si t\u00eb nd\u00ebrtoni nj\u00eb infrastruktur\u00eb t\u00eb klas\u00ebs korporative me p\u00ebrdorimin e server\u00ebve Dell R730xd E5-2650 v4 me \u00e7mim 9000 euro p\u00ebr pak para?<\/a><\/noindex>
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u0438 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0442\u0440\u0438 \u0442\u0435\u043c\u044b: \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u044f, \u043a\u0430\u043a \u043e\u043d\u0430 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u0438 \u043a\u0430\u043a\u0430\u044f \u0443 \u043d\u0435\u0451 \u0430\u043b\u044c\u0442\u0435\u0440\u043d\u0430\u0442\u0438\u0432\u0430. \u0412\u044b \u0432\u0438\u0434\u0438\u0442\u0435 \u0442\u043e\u043f\u043e\u043b\u043e\u0433\u0438\u044e \u0441\u0435\u0442\u0438, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0432\u043a\u043b\u044e\u0447\u0430\u0435\u0442 \u0432 \u0441\u0435\u0431\u044f \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440 \u0441 IP-\u0430\u0434\u0440\u0435\u0441\u043e\u043c 192.168.1.10, \u043f\u043e\u0434\u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u043d\u044b\u0439 \u0447\u0435\u0440\u0435\u0437 \u0441\u0432\u0438\u0442\u0447 \u043a \u0448\u043b\u044e\u0437\u0443, \u0438\u043b\u0438 \u0440\u043e\u0443\u0442\u0435\u0440\u0443. \u0414\u043b\u044f \u044d\u0442\u043e\u0433\u043e \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u043f\u043e\u0440\u0442 \u0440\u043e\u0443\u0442\u0435\u0440\u0430 f0\/0 \u0441 IP-\u0430\u0434\u0440\u0435\u0441\u043e\u043c 192.168.1.1. \u0412\u0442\u043e\u0440\u043e\u0439 \u043f\u043e\u0440\u0442 \u044d\u0442\u043e\u0433\u043e \u0440\u043e\u0443\u0442\u0435\u0440\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27983,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37303","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Trajnimi Cisco 200-125 CCNA v3.0. Dita 20. Shkarkimi Statik | ProHoster","description":"Sot sot do t\u00eb flasim p\u00ebr rrug\u00ebn statike dhe do t\u00eb shqyrtojm\u00eb tri tema: \u00e7far\u00eb \u00ebsht\u00eb rruga statike, si konfigurohet ajo dhe cila \u00ebsht\u00eb alternativa e saj.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0422\u0440\u0435\u043d\u0438\u043d\u0433 Cisco 200-125 CCNA v3.0. \u0414\u0435\u043d\u044c 20. \u0421\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u044f | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u0438 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0442\u0440\u0438 \u0442\u0435\u043c\u044b: \u0447\u0442\u043e \u0442\u0430\u043a\u043e\u0435 \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u044f, \u043a\u0430\u043a \u043e\u043d\u0430 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u0438 \u043a\u0430\u043a\u0430\u044f \u0443 \u043d\u0435\u0451 \u0430\u043b\u044c\u0442\u0435\u0440\u043d\u0430\u0442\u0438\u0432\u0430.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:16:52+00:00","article:modified_time":"2019-10-31T19:16:52+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37303","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 17:11:39","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:29:59","updated":"2026-01-23 17:11:39","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37303","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=37303"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37303\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27983"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37303"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}