{"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 e 20. Ruterimi statik","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot do t\u00eb flasim p\u00ebr ruterimin statik dhe do t\u00eb shqyrtojm\u00eb tre tema: \u00e7far\u00eb \u00ebsht\u00eb ruterimi statik, si e konfiguroni at\u00eb dhe cilat jan\u00eb alternativat e tij. 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-in. P\u00ebr k\u00ebt\u00eb lidhje p\u00ebrdoret porta e router-it f0\/0 me adres\u00ebn IP 192.168.1.1.<\/p>\n

\"Trajnimi
\n
\nPorta e dyt\u00eb e k\u00ebtij router-i f0\/1 me adres\u00ebn IP 192.168.2.1 \u00ebsht\u00eb e lidhur me port\u00ebn f0\/0 t\u00eb nj\u00eb router-i tjet\u00ebr, dhe ky interface 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 p\u00ebrdor p\u00ebr k\u00ebt\u00eb lidhje portin f0\/0 me adres\u00ebn IP 192.168.3.3. <\/a><\/noindex><\/p>\n

N\u00eb fund, router-i i tret\u00eb \u00ebsht\u00eb i lidhur me switch-in e dyt\u00eb n\u00ebp\u00ebrmjet port\u00ebs f0\/1 me adres\u00ebn 192.168.4.3, nd\u00ebrsa switch-i \u00ebsht\u00eb i lidhur me kompjuterin e dyt\u00eb me adres\u00ebn IP 192.168.4.10.
\nN\u00ebse e dini se si ndahen n\u00ebnnj\u00ebsi sipas adresave IP, p\u00ebrcaktoni q\u00eb pjesa nga kompjuteri i par\u00eb deri te routeri i par\u00eb i p\u00ebrket nj\u00eb n\u00ebnnj\u00ebsi, pjesa midis routerit t\u00eb par\u00eb dhe t\u00eb dyt\u00eb \u2013 nj\u00eb rrjeti t\u00eb dyt\u00eb, midis routerit t\u00eb dyt\u00eb dhe t\u00eb tret\u00eb \u2013 nj\u00eb rrjeti t\u00eb tret\u00eb, dhe midis routerit t\u00eb tret\u00eb dhe kompjuterit t\u00eb dyt\u00eb \u2013 nj\u00eb rrjeti 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 lidhet me kompjuterin 192.168.4.10, 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 routeri. Ai e l\u00eb m\u00ebnjan\u00eb informacionin e nivelit t\u00eb dyt\u00eb, dmth adresat MAC, dhe sheh informacionin e nivelit t\u00eb tret\u00eb. Duke zbuluar se t\u00eb dh\u00ebnat jan\u00eb adresuar pajisjes me adres\u00ebn IP 192.168.4.10, routeri kupton se nj\u00eb pajisje e till\u00eb nuk \u00ebsht\u00eb e lidhur me t\u00eb, prandaj thjesht duhet ta kaloj\u00eb k\u00ebt\u00eb frame m\u00eb tej n\u00eb rrjet. Ai i referohet tabel\u00ebs s\u00eb tij t\u00eb routing 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

N\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme, routeri i dyt\u00eb kontrollon tabel\u00ebn e tij t\u00eb routing-ut, ku kupton 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 tek routeri i tret\u00eb. S\u00eb fundi, routeri 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 tek kompjuteri i dyt\u00eb. <\/p>\n

Le t\u00eb shohim se si krijohet tabela e routing-ut. P\u00ebr k\u00ebt\u00eb do t\u00eb p\u00ebrdorim Cisco Packet Tracer dhe do t\u00eb shohim se si implementohet koncepti i routing-ut. K\u00ebtu \u00ebsht\u00eb e nj\u00ebjta topologji e rrjetit, dhe tani do t'i caktoj adresat IP router\u00ebve, 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 punon me cil\u00ebsimet e paracaktuar dhe p\u00ebrdor VLAN1. Le t\u00eb fillojm\u00eb me cil\u00ebsimet e router-it t\u00eb par\u00eb Router0. S\u00eb pari, do t'i japim emrin e hostit R1, pastaj do t\u00eb shkruajm\u00eb adres\u00ebn IP dhe mask\u00ebn e n\u00ebnrrjetit p\u00ebr nd\u00ebrfaqen f0\/0. M\u00eb pas duhet t\u00eb aplikojm\u00eb komand\u00ebn no shutdown. E shihni si treguesi i nd\u00ebrfaqes kaloi nga e kuqe n\u00eb t\u00eb gjelb\u00ebr, q\u00eb do t\u00eb thot\u00eb se porta u aktivizua n\u00eb rrjet. <\/p>\n

M\u00eb pas, na nevojitet t\u00eb konfiguroni portin e dyt\u00eb t\u00eb routerit f0\/1, me emrin e hostit q\u00eb mbetet i nj\u00ebjt\u00eb; ne thjesht shtojm\u00eb adres\u00ebn IP 192.168.2.1 dhe mask\u00ebn e n\u00ebndit\u00ebs 255.255.255.0. Nuk ka asgj\u00eb t\u00eb re k\u00ebtu, \u00ebsht\u00eb nj\u00eb konfigurim i thjesht\u00eb, ju tashm\u00eb i njihni t\u00eb gjitha komandat, prandaj do ta kaloj shpejt edhe te routerat e tjer\u00eb. Me kalimin e adresave IP dhe p\u00ebrdorimin e komand\u00ebs no shut, portet e routerave do t\u00eb ndryshojn\u00eb ngjyr\u00eb n\u00eb gjelb\u00ebr, duke treguar se lidhja mes pajisjeve \u00ebsht\u00eb vendosur. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, 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 fundit tregon numrin e rrjetit t\u00eb lidhur me k\u00ebt\u00eb port. <\/p>\n

K\u00ebshtu, adresat e porteve t\u00eb ruterit t\u00eb par\u00eb do t\u00eb jen\u00eb 192.168.1.1 (ruteri i par\u00eb, rrjeta e par\u00eb) dhe 192.168.2.1 (ruteri i par\u00eb, rrjeta e dyt\u00eb), p\u00ebr ruterin e dyt\u00eb \u2014 192.168.2.2 (ruteri i dyt\u00eb, rrjeta e dyt\u00eb) dhe 192.168.3.2 (ruteri i dyt\u00eb, rrjeta e tret\u00eb), nd\u00ebrsa p\u00ebr ruterin e tret\u00eb \u2014 192.168.3.3 (ruteri i tret\u00eb, rrjeta e tret\u00eb) dhe 192.168.4.3 (ruteri i tret\u00eb, rrjeta e kat\u00ebrt). Mendoj se \u00ebsht\u00eb mjaft e leht\u00eb p\u00ebr t'u kujtuar, megjithat\u00eb n\u00eb praktik\u00eb, adresat mund t\u00eb formohen ndryshe, var\u00ebsisht nga rregullat e pranuara n\u00eb kompanin\u00eb tuaj. Duhet t\u00eb ndiheni t\u00eb angazhuar pas rregullave t\u00eb kompanis\u00eb, sepse koleg\u00ebve tuaj do t'u jet\u00eb m\u00eb e leht\u00eb t\u00eb rregullojn\u00eb problemet n\u00eb rrjetin tuaj n\u00ebse e formoni at\u00eb sipas rregullave. <\/p>\n

Pra, p\u00ebrfundova s\u00eb bashku me caktimin e adresave IP p\u00ebr portet e ruterit, dhe mund t\u00eb shihni se porti i dyt\u00eb i kalimtarit gjithashtu ka ndryshuar ngjyr\u00eb n\u00eb t\u00eb gjelb\u00ebr, pasi lidhja midis tij dhe kompjuterit t\u00eb dyt\u00eb u krijua automatikisht. <\/p>\n

\"Trajnimi
\n
\nTani do t\u00eb th\u00ebrras terminalin e komandave t\u00eb kompjuterit t\u00eb par\u00eb dhe do t\u00eb pingoj kompjuterin e dyt\u00eb n\u00eb adres\u00ebn 192.168.4.10. Le t\u00eb kalojm\u00eb n\u00eb modin e simulimit - tani po shihni l\u00ebvizjen animuese t\u00eb paketave t\u00eb pingut n\u00eb pjes\u00ebt e rrjetit. Tani do t\u00eb filloj p\u00ebrs\u00ebri pingimin, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb keni mund\u00ebsi t\u00eb shikoni me kujdes se \u00e7far\u00eb po ndodh. N\u00eb an\u00ebn e djatht\u00eb n\u00eb tabel\u00eb shihni ICMP, Protokolli i Kontrollit t\u00eb Mesazheve t\u00eb Internetit - k\u00ebshtu quhet ping. Ping \u00ebsht\u00eb nj\u00eb protokoll q\u00eb p\u00ebrdorim p\u00ebr t\u00eb kontrolluar lidhjen. <\/p>\n

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

\"Trajnimi
\n
\nJu shihni t\u00eb dh\u00ebnat e nivelevit 3 t\u00eb OSI - kjo jan\u00eb adresat IP t\u00eb burimit dhe destinacionit t\u00eb pingut, t\u00eb dh\u00ebnat e niveleve 2 n\u00eb form\u00ebn e adresave MAC p\u00ebrkat\u00ebse dhe t\u00eb dh\u00ebnat e niveleve 1 n\u00eb form\u00ebn e sh\u00ebnimin t\u00eb portit (porteve) - kjo \u00ebsht\u00eb FastEthernet0. Ju gjithashtu mund t\u00eb shihni formatin e frames s\u00eb pingut: kodi, lloji dhe trupi i paket\u00ebs. <\/p>\n

\"Trajnimi
\n
\nFrami d\u00ebrgohet te switch-i, switch-i analizon adresat MAC dhe e d\u00ebrgon m\u00eb tej n\u00eb rrjet te routeri. Routeri sheh adres\u00ebn IP 192.168.4.10 dhe e hedh paket\u00ebn posht\u00eb, 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 do t\u00eb kthehemi te ping n\u00eb dritaren e komandave. <\/p>\n

\"Trajnimi
\n
\nShihni se n\u00eb p\u00ebrpjekjen p\u00ebr t\u00eb ping-uar kompjuterin 192.168.4.10, t\u00eb gjitha 4 paketat jan\u00eb humbur \u2013 nga routeri 192.168.1.1 \u00ebsht\u00eb marr\u00eb nj\u00eb p\u00ebrgjigje q\u00eb host-i i destinacionit nuk \u00ebsht\u00eb i arritsh\u00ebm. Le t\u00eb kthehemi n\u00eb dritaren e nd\u00ebrfaqes s\u00eb komandave t\u00eb routerit dhe t\u00eb shkruajm\u00eb komand\u00ebn show ip route. Shihni pjes\u00ebn m\u00eb t\u00eb r\u00ebnd\u00ebsishme \u2013 tabel\u00ebn e routes, dhe komanda q\u00eb citoj \u00ebsht\u00eb nj\u00eb nga komandat kryesore t\u00eb rutimit Cisco. Momentalisht, kjo tabel\u00eb p\u00ebrmban 2 hyrje. N\u00eb fillim t\u00eb tabel\u00ebs ndodhet nj\u00eb list\u00eb e shkurtimeve t\u00eb p\u00ebrdorura, nga e cila del se letra C tregon lidhjet. Hyrja e par\u00eb njofton se rrjeti 192.168.1.0\/24 \u00ebsht\u00eb lidhur direkt n\u00eb portin FastEthernet0\/0, nd\u00ebrsa rrjeti 192.168.2.0\/24 \u00ebsht\u00eb lidhur direkt n\u00eb portin FastEthernet0\/1. Kjo do t\u00eb thot\u00eb se momentalisht router-i di vet\u00ebm p\u00ebr k\u00ebto dy rrjete. <\/p>\n

\"Trajnimi
\n
\nVlera 192.168.1.0\/24 \u00ebsht\u00eb identifikuesi i rrjetit. Kur krijuam n\u00ebnrrjetet, ne gjithashtu krijuam identifikuesit e tyre. K\u00ebta identifikues i tregojn\u00eb router-it se t\u00eb gjitha pajisjet, t\u00eb cilat kan\u00eb adresat IP 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 qasshme 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 do t\u00eb d\u00ebrgojn\u00eb nj\u00eb k\u00ebrkes\u00eb p\u00ebr transmisjon t\u00eb gjer\u00eb. Pra, p\u00ebr k\u00ebt\u00eb router jan\u00eb t\u00eb lidhura vet\u00ebm rrjetet 1 dhe 2, prandaj ai \u00ebsht\u00eb i njohur vet\u00ebm me k\u00ebto rrjete. K\u00ebshtu, kur nj\u00eb ping nga adresa 192.168.4.10 arrin tek router-i, ai nuk e di se kjo adres\u00eb \u00ebsht\u00eb e qasshme p\u00ebrmes rrug\u00ebs Router0 - Router1 - Router2. <\/p>\n

Por ju si administrator i rrjetit e dini se kjo rrug\u00eb \u00ebsht\u00eb e qasshme, dmth se router-i i par\u00eb mund t\u00eb d\u00ebrgoj\u00eb k\u00ebt\u00eb paket\u00eb tek router-i i dyt\u00eb. Prandaj, ju duhet t\u00eb organizoni rrug\u00ebzimin statik. Le t\u00eb provojm\u00eb ta b\u00ebjm\u00eb k\u00ebt\u00eb. <\/p>\n

Ne do t\u00eb 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 te router-i i dyt\u00eb. Formati i komand\u00ebs p\u00ebr caktimin e routing-it 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 p\u00ebrdorim p\u00ebr k\u00ebt\u00eb komand\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 k\u00ebtu arrin \u00e7do trafik p\u00ebr pajisjet e rrjetit, t\u00eb cilat kan\u00eb nj\u00eb adres\u00eb IP q\u00eb ka vler\u00ebn e oktet\u00ebs s\u00eb fundit nga 1 n\u00eb 254, dhe m\u00eb pas shkruaj ose IP-adres\u00ebn ose emrin e portit, ku duhet t\u00eb d\u00ebrgohet ky trafik. N\u00eb k\u00ebt\u00eb rast, un\u00eb shkruaj emrin e interface-it f0\/1, k\u00ebshtu q\u00eb komand\u00ebs i jepet ky format: ip route 192.168.4.0 255.255.255.0 f0\/1.<\/p>\n

\"Trajnimi
\n
\nN\u00eb vend t\u00eb interface-it t\u00eb port\u00ebs, un\u00eb mund t\u00eb specifikoj IP-adres\u00ebn e tij, at\u00ebher\u00eb komanda e routing-ut 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 \u00e7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb. Un\u00eb mendoj se p\u00ebr rrjetet e transmetimit, si Ethernet, \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb tregoni adres\u00ebn IP. N\u00ebse po p\u00ebrdorni rrjete t\u00eb tipit 'pik\u00eb-pik\u00eb', si Frame Relay (rrjete me ri-mbushje ose nd\u00ebrlidhje kornizash), \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb p\u00ebrdorni interface-n e daljes. M\u00eb von\u00eb do t\u00eb diskutojm\u00eb m\u00eb shum\u00eb rreth rrjeteve Frame Relay, p\u00ebr tani po p\u00ebrdor nj\u00eb variant m\u00eb t\u00eb p\u00ebrshtatsh\u00ebm t\u00eb komand\u00ebs s\u00eb ruterit -192.168.4.0 255.255.255.0.<\/p>\n

Tani le t\u00eb shikojm\u00eb tabel\u00ebn e ruterit, duke p\u00ebrdorur komand\u00ebn do show ip address. Shikoni se ka nj\u00eb regjistrim t\u00eb ri, t\u00eb titulluar me shkronj\u00ebn S, q\u00eb do t\u00eb thot\u00eb static. <\/p>\n

\"Trajnimi
\n
\nKy regjistrim thot\u00eb se n\u00ebse ka trafik p\u00ebr rrjetin 192.168.4.0\/24, ai duhet t\u00eb d\u00ebrgohet te adresa p\u00ebrkat\u00ebse p\u00ebrmes pajisjes me adres\u00ebn IP 192.168.2.2. T\u00eb kthehemi tek komand\u00ebn e terminalit n\u00eb kompjuter dhe t\u00eb pingojm\u00eb adres\u00ebn e nevojshme p\u00ebrs\u00ebri. Tani trafiku duhet t\u00eb kaloj\u00eb p\u00ebrmes ruterit t\u00eb par\u00eb dhe t\u00eb arrij\u00eb n\u00eb ruterin e dyt\u00eb, i cili duhet t\u00eb hedh\u00eb paketat.<\/p>\n

N\u00eb rastin e par\u00eb, routi nuk thjesht hodhi paketat, ai gjithashtu i p\u00ebrgjigj kompjuterit q\u00eb adresa IP 192.168.4.10 nuk \u00ebsht\u00eb e disponueshme. Megjithat\u00eb, routi i dyt\u00eb mund t\u00eb p\u00ebrgjigjet vet\u00ebm p\u00ebr routin e par\u00eb nga i cili mori trafik. Le t\u00eb shohim tabel\u00ebn e routimit t\u00eb routit t\u00eb dyt\u00eb. K\u00ebtu thuhet se Router1 e 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\u00eb d\u00ebrgonte nj\u00eb mesazh kthimi q\u00eb tregon se hosti i destinacionit nuk \u00ebsht\u00eb i disponuesh\u00ebm, por nuk di se si t\u00eb lidhet me komputerin 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 disponueshm\u00ebrin\u00eb e hostit t\u00eb destinacionit, mor\u00ebm mesazhin \"Request timed out\" \u2013 koha e pritjes p\u00ebr k\u00ebrkes\u00ebn skadoi. Pajisjet e ndryshme rrjetore kan\u00eb vlera t\u00eb ndryshme p\u00ebr TTL, prandaj, kur paketat IP arrijn\u00eb n\u00eb k\u00ebt\u00eb vler\u00eb, ato shp\u00ebrndahen. Kjo ndodh duke b\u00ebr\u00eb 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 arrin 0 dhe paketa shkat\u00ebrrohet. <\/p>\n

K\u00ebshtu funksionon mekanizmi p\u00ebr parandalimin e cikleve t\u00eb IP-paketeve. Pra, 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. Pra, le t\u00eb kalojm\u00eb te cil\u00ebsimet e routerit t\u00eb dyt\u00eb dhe t'i tregojm\u00eb atij se si t\u00eb arrij\u00eb n\u00eb subnetin e kat\u00ebrt. P\u00ebr k\u00ebt\u00eb, do t\u00eb p\u00ebrdor komanden ip route 192.168.4.0 255.255.255.0 192.168.3.3. Tani, regjistrimi p\u00ebrkat\u00ebs shfaqet n\u00eb tabel\u00ebn e rrug\u00ebve q\u00eb e kemi thirrur me komand\u00ebn do show ip route. <\/p>\n

\"Trajnimi
\n
\nTani Router1 e di se si t\u00eb d\u00ebrgoj\u00eb trafik te destinatar\u00ebt e subnetit t\u00eb kat\u00ebrt. Ai e d\u00ebrgon at\u00eb te routeri i tret\u00eb. Routeri i tret\u00eb Router2, pasi \u00ebsht\u00eb i lidhur me rrjetin 4., me siguri e di si t\u00eb d\u00ebrgoj\u00eb paket\u00ebn te 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 rrjet k\u00ebtu 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 kam th\u00ebn\u00eb m\u00eb par\u00eb, ICMP p\u00ebrfaq\u00ebson nj\u00eb protokoll komunikimi n\u00eb t\u00eb dyja drejtime, k\u00ebshtu q\u00eb n\u00ebse dikush d\u00ebrgon paketa ping, ato duhet t\u00eb kthehen prapa. Ruting p\u00ebrfshin q\u00eb \u00e7do pajisje rrjeti duhet t\u00eb dij\u00eb jo vet\u00ebm si t\u00eb d\u00ebrgoj\u00eb nj\u00eb mesazh te dikush, por gjithashtu si t\u00eb d\u00ebrgoj\u00eb nj\u00eb mesazh p\u00ebrgjigje te d\u00ebrguesi i k\u00ebrkes\u00ebs. Pra, paketa e d\u00ebrguar nga kompjuteri i par\u00eb arriti me sukses n\u00eb kompjuterin e dyt\u00eb. Kompjuteri i dyt\u00eb mendon: \"shk\u00eblqyesh\u00ebm, mora mesazhin tuaj dhe tani duhet t'ju d\u00ebrgoj nj\u00eb p\u00ebrgjigje\". Kjo p\u00ebrgjigje, e adresuar pajisjes me IP 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 subnetin e par\u00eb, por n\u00eb tabel\u00ebn e tij t\u00eb rutimit ka vet\u00ebm regjistrime p\u00ebr subnetet e tret\u00eb dhe t\u00eb kat\u00ebrt. Prandaj, 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 q\u00eb \u00ebsht\u00eb i destinuar p\u00ebr rrjetin me identifikues 192.168.1.0 duhet t\u00eb d\u00ebrgohet te routeri i dyt\u00eb me IP 192.168.3.2. <\/p>\n

\u00c7far\u00eb do t\u00eb ndodh\u00eb pas k\u00ebsaj? Ruter i dyt\u00eb e di p\u00ebr rrjetet 2., 3. dhe 4., por nuk di asgj\u00eb p\u00ebr rrjetin e par\u00eb. Prandaj, duhet t\u00eb hysh n\u00eb cil\u00ebsimet e ruterit t\u00eb dyt\u00eb Router1 dhe t\u00eb p\u00ebrdor\u00ebsh komand\u00ebn ip route 192.168.1.0 255.255.255.0 192.168.2.1, dometh\u00ebn\u00eb t\u00eb tregosh se trafik p\u00ebr rrjetin 1. duhet t\u00eb d\u00ebrgohet p\u00ebrmes rrjetit 2. n\u00eb ruterin e par\u00eb Router0.<\/p>\n

Pas k\u00ebsaj, paketa arrin n\u00eb ruterin e par\u00eb, i cili di p\u00ebr pajisjen 192.168.1.10, sepse rrjeti i par\u00eb, ku ndodhet ky kompjuter, \u00ebsht\u00eb i lidhur me portin e k\u00ebtij ruteri. V\u00ebrej se tani ruter i par\u00eb nuk di asgj\u00eb p\u00ebr rrjetin 3., dhe ruteri 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 p\u00ebrk\u00ebdhel\u00ebse. <\/p>\n

Po marr nj\u00eb her\u00eb tjet\u00ebr ping adres\u00ebn 192.168.4.0, dhe ju e shihni se k\u00ebt\u00eb her\u00eb pingimi ka shkuar me sukses. Paketat kaluan t\u00eb gjith\u00eb rrug\u00ebn nga kompjuteri i par\u00eb n\u00eb kompjuterin e dyt\u00eb dhe p\u00ebrgjigjja u kthye te d\u00ebrguesi. N\u00eb dritaren e komand\u00ebs shihet mesazhi se secila nga 4 p\u00ebrgjigjet e paketave 192.168.4.0 p\u00ebrb\u00ebn 32 byte, TTL = 125 ms, dhe suksesi i pingut arrin 100%. Kjo do t\u00eb thot\u00eb se burimi i transmetimit mori nj\u00eb p\u00ebrgjigje nga host-i i destinacionit. Pra, edhe n\u00ebse pajisjet nuk e din\u00eb p\u00ebr ekzistenc\u00ebn e disa rrjeteve nd\u00ebrmjet\u00ebs, kjo nuk ka r\u00ebnd\u00ebsi, n\u00ebse ato punojn\u00eb sipas parimit \"d\u00ebrguesi fundor \u2013 marr\u00ebsi fundor\". Kompjuteri i par\u00eb e di se si t\u00eb arrij\u00eb te kompjuteri i dyt\u00eb, dhe kompjuteri i dyt\u00eb e di se 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 komunikoj\u00eb me sukses me kompjuterin e dyt\u00eb, nd\u00ebrsa trafiku kalon p\u00ebrmes t\u00eb gjitha k\u00ebtyre pajisjeve. Le t\u00eb shohim n\u00ebse PC0 mund t\u00eb lidhet me ruterin e tret\u00eb Router2 n\u00eb adres\u00ebn 192.168.3.3 \u2013 ky \u00ebsht\u00eb porta e rrjetit 3 t\u00eb ruterit t\u00eb tret\u00eb. Ping-u tregon se kjo \u00ebsht\u00eb e pamundur \u2013 host-i i destinacionit nuk \u00ebsht\u00eb i disponuesh\u00ebm. <\/p>\n

Le t\u00eb shohim se \u00e7far\u00eb \u00ebsht\u00eb shkaku. Duke hapur tabel\u00ebn e routingut t\u00eb routerit t\u00eb par\u00eb, shohim se ai njeh vet\u00ebm 3 rrjeta \u2013 t\u00eb par\u00ebn, t\u00eb dyt\u00ebn dhe t\u00eb kat\u00ebrt\u00ebn, por nuk di asgj\u00eb p\u00ebr rrjetin e tret\u00eb. Prandaj, n\u00ebse dua t\u00eb lidhem me k\u00ebt\u00eb rrjet, duhet t\u00eb vendos nj\u00eb rrug\u00eb statike p\u00ebr t\u00eb. <\/p>\n

K\u00ebshtu, shqyrtuam se si mund t\u00eb konfigurojm\u00eb routingun statik p\u00ebr tre routera. N\u00ebse keni 10 routera dhe 50 subnet-e t\u00eb ndryshme, konfigurimi manual i routingut statik do t\u00eb marr\u00eb shum\u00eb koh\u00eb. K\u00ebtu hyn n\u00eb loj\u00eb routingu dinamik.
\nTani do t\u00eb fshij t\u00eb gjitha rrug\u00ebt q\u00eb kam krijuar. P\u00ebr k\u00ebt\u00eb, do t\u00eb th\u00ebrras nj\u00eb nga nj\u00eb tabelat e routingut t\u00eb t\u00eb gjith\u00eb routerave dhe do t\u00eb shtoj fjal\u00ebn \"no\" n\u00eb fillim t\u00eb \u00e7do regjistrimi t\u00eb routingut statik, dmth do t\u00eb p\u00ebrdor komand\u00ebn e mohimit. Tani mund t\u00eb shqyrtojm\u00eb se \u00e7far\u00eb p\u00ebrfaq\u00ebson routingu dinamik. <\/p>\n

P\u00ebr rrug\u00ebzimin dinamik, 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\u00ebzimi statik, dhe do t\u00eb doja t\u00eb tregoj se sa pun\u00eb t\u00eb lodhshme \u00ebsht\u00eb kjo. Do t\u00eb demonstroj shpejt se si funksionon RIP, i cili do t\u00eb shqyrtohet m\u00eb n\u00eb detaje n\u00eb m\u00ebsimin e ardhsh\u00ebm.
\nN\u00eb shembullin e router-it t\u00eb par\u00eb, p\u00ebrdor komand\u00ebn router rip, pastaj do t\u00eb shkruaj ver 2, p\u00ebr t\u00eb specifikuar versionin e protokollit, dhe pastaj do t\u00eb listoj nj\u00eb nga nj\u00eb rrjetet p\u00ebr t\u00eb cilat duhet t\u00eb p\u00ebrdoret protokolli i rrug\u00ebzimit dinamik: 192.168.1.0, 192.168.2.0, pas s\u00eb cil\u00ebs do t\u00eb kaloj n\u00eb router-in e dyt\u00eb dhe do t\u00eb veproj n\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme. N\u00eb thelb, vet\u00ebm po specifikoj rrjetet q\u00eb jan\u00eb t\u00eb lidhura me k\u00ebt\u00eb pajisje, k\u00ebshtu q\u00eb p\u00ebr router-in e dyt\u00eb do t\u00eb specifikoj 192.168.2.0 dhe 192.168.3.0, dhe p\u00ebr t\u00eb tretin, pas komand\u00ebs rip ver 2 \u2013 adresat 192.168.3.0 dhe 192.168.4.0. Pastaj, do t\u00eb kthehem n\u00eb router-in e par\u00eb dhe do t\u00eb shoh tabel\u00ebn e rrug\u00ebzimit. <\/p>\n

\"Trajnimi
\n
\nShihni se n\u00eb t\u00eb ka dal\u00eb magjikisht t\u00eb gjith\u00eb rrjetet, dy t\u00eb parat jan\u00eb ato q\u00eb jan\u00eb lidhur direkt me router-in, nd\u00ebrsa dy t\u00eb tjerat jan\u00eb ato p\u00ebr t\u00eb cilat lidhja krijohet p\u00ebrmes protokollit t\u00eb ruterizimit dinamik RIP. Nj\u00eb situat\u00eb e ngjashme v\u00ebrehet n\u00eb tabelat e ruterizimit t\u00eb router\u00ebve t\u00eb dyt\u00eb dhe t\u00eb tret\u00eb. N\u00ebse un\u00eb e lidh rrjetet 5 dhe 6 me router-in e dyt\u00eb, t\u00eb gjith\u00eb pajisjet q\u00eb p\u00ebrdorin RIP do t\u00eb din\u00eb p\u00ebr k\u00ebto rrjete t\u00eb reja. Ky \u00ebsht\u00eb avantazhi i ruterizimit dinamik.<\/p>\n

\"Trajnimi
\n
\nN\u00ebse tani un\u00eb pingoj kompjuterin e dyt\u00eb, lidhja do t\u00eb funksionoj\u00eb pa probleme. Mund t\u00eb pingoj router-in e tret\u00eb dhe ping-u do t\u00eb jet\u00eb i suksessh\u00ebm, sepse router-i i par\u00eb fal\u00eb RIP e di p\u00ebr t\u00eb gjitha pajisjet e t\u00eb gjitha rrjeteve. Nj\u00eb njohuri t\u00eb ngjashme do t\u00eb ken\u00eb edhe router-i i dyt\u00eb dhe i tret\u00eb. Nuk po them se RIP \u00ebsht\u00eb protokolli m\u00eb i mir\u00eb, por ai \u00ebsht\u00eb n\u00eb gjendje t\u00eb realizoj\u00eb shum\u00eb gj\u00ebra n\u00eb m\u00ebnyr\u00eb efektive. P\u00ebr tani, vet\u00ebm dua q\u00eb ju t\u00eb kuptoni se \u00e7far\u00eb \u00ebsht\u00eb ruterizimi dhe si funksionon, \u00e7far\u00eb \u00ebsht\u00eb tabela e ruterizimit dhe \u00e7far\u00eb do t\u00eb thot\u00eb ajo. <\/p>\n

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

Pra, sot m\u00ebsuat se rrug\u00ebzimi \u00ebsht\u00eb procesi q\u00eb siguron krijimin e regjistrimeve t\u00eb rrug\u00ebve n\u00eb tabelat e rrug\u00ebve n\u00eb m\u00ebnyr\u00eb q\u00eb router-i t\u00eb mund t\u00eb marr\u00eb nj\u00eb vendim p\u00ebr d\u00ebrgimin e trafikut p\u00ebrmes rrjetit. <\/p>\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nFaleminderit q\u00eb jeni me ne. Ju p\u00ebrqejn\u00eb artikujt tan\u00eb? Doni t\u00eb shihni m\u00eb shum\u00eb materiale interesante? Na mb\u00ebshtesni me nj\u00eb porosi ose duke na rekomanduar miqve tuaj, 30% zbritje p\u00ebr p\u00ebrdoruesit e Habra p\u00ebr nj\u00eb alternativ\u00eb unike t\u00eb server\u00ebve entry-level, e cila \u00ebsht\u00eb krijuar nga ne p\u00ebr ju:<\/b> E gjith\u00eb e v\u00ebrteta rreth VPS (KVM) E5-2650 v4 (6 Ndot\u00ebs) 10GB DDR4 240GB SSD 1Gbps nga $20, ose si ta ndash n\u00eb m\u00ebnyr\u00eb t\u00eb duhur serverin?<\/a><\/noindex> (disponohen variante me RAID1 dhe RAID10, deri n\u00eb 24 b\u00ebrthama dhe deri n\u00eb 40GB DDR4).<\/p>\n

Dell R730xd p\u00ebr dy her\u00eb m\u00eb lir\u00eb?<\/b> Vet\u00ebm k\u00ebtu 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\u00ebrtosh nj\u00eb infrastruktur\u00eb t\u00eb klas\u00ebs korporative me p\u00ebrdorimin e server\u00ebve Dell R730xd E5-2650 v4 me \u00e7mim prej 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. Rrug\u00ebzimi statik | ProHoster","description":"Sot do t\u00eb flasim p\u00ebr rrug\u00ebzimin statik dhe do t\u00eb shqyrtojm\u00eb tre tema: \u00e7far\u00eb \u00ebsht\u00eb rrug\u00ebzimi statik, si konfigurohet ai dhe \u00e7far\u00eb alternative ka. Ju shihni topologjin\u00eb e rrjetit q\u00eb p\u00ebrfshin nj\u00eb kompjuter me adres\u00eb IP 192.168.1.10, i lidhur p\u00ebrmes nj\u00eb switch-i me nj\u00eb gateway ose router. P\u00ebr k\u00ebt\u00eb lidhje p\u00ebrdoret porta e router-it f0\/0 me adres\u00eb IP 192.168.1.1. Porta e dyt\u00eb e k\u00ebtij router-i","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. \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","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}]}}