{"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\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-20-staticheskaya-marshrutizatsiya","title":{"rendered":"\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 20. Statick\u00e1 sm\u011brov\u00e1n\u00ed","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes budeme hovo\u0159it o statick\u00e9m sm\u011brov\u00e1n\u00ed a probereme t\u0159i t\u00e9mata: co je to statick\u00e9 sm\u011brov\u00e1n\u00ed, jak se nastavuje a jak\u00e1 je jeho alternativa. Vid\u00edte s\u00ed\u0165ovou topologii, kter\u00e1 zahrnuje po\u010d\u00edta\u010d s IP adresou 192.168.1.10, p\u0159ipojen\u00fd p\u0159es switch ke br\u00e1n\u011b nebo routeru. Pro toto p\u0159ipojen\u00ed se pou\u017e\u00edv\u00e1 port routeru f0\/0 s IP adresou 192.168.1.1.<\/p>\n

\"\u0160kolen\u00ed
\n
\nDruh\u00fd port tohoto routeru f0\/1 s IP adresou 192.168.2.1 je p\u0159ipojen k portu f0\/0 druh\u00e9ho routeru, jeho\u017e rozhran\u00ed m\u00e1 adresu 192.168.2.2. Druh\u00fd router je p\u0159ipojen portem f0\/1 s adresou 192.168.3.2 k t\u0159et\u00edmu routeru, kter\u00fd pro toto p\u0159ipojen\u00ed pou\u017e\u00edv\u00e1 port f0\/0 s IP adresou 192.168.3.3. <\/a><\/noindex><\/p>\n

Nakonec je t\u0159et\u00ed router spojen s druh\u00fdm switchem p\u0159es port f0\/1 s adresou 192.168.4.3, a switch je p\u0159ipojen k druh\u00e9mu po\u010d\u00edta\u010di s IP adresou 192.168.4.10.
\nPokud v\u00edte, jak podle IP adres odd\u011blit pods\u00edt\u011b, ur\u010dete, \u017ee \u010d\u00e1st od prvn\u00edho po\u010d\u00edta\u010de k prvn\u00edmu routeru pat\u0159\u00ed do jedn\u00e9 pods\u00edt\u011b, \u010d\u00e1st mezi prvn\u00edm a druh\u00fdm routerem \u2013 do druh\u00e9 s\u00edt\u011b, mezi druh\u00fdm a t\u0159et\u00edm routerem \u2013 do t\u0159et\u00ed s\u00edt\u011b a mezi t\u0159et\u00edm routerem a druh\u00fdm po\u010d\u00edta\u010dem \u2013 do \u010dtvrt\u00e9 s\u00edt\u011b. Tak m\u00e1me 4 r\u016fzn\u00e9 s\u00edt\u011b. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud chce po\u010d\u00edta\u010d 192.168.1.10 komunikovat s po\u010d\u00edta\u010dem 192.168.4.10, mus\u00ed nejprve odeslat sv\u00e1 data br\u00e1n\u011b 192.168.1.1. Vytv\u00e1\u0159\u00ed r\u00e1mec, do kter\u00e9ho umis\u0165uje IP adresu zdroje a c\u00edle, MAC adresu zdroje a c\u00edle a odes\u00edl\u00e1 ho routeru. Ten odstran\u00ed informace 2. \u00farovn\u011b, tedy MAC adresy, a pod\u00edv\u00e1 se na informace 3. \u00farovn\u011b. Zjist\u00ed, \u017ee data jsou adresov\u00e1na za\u0159\u00edzen\u00ed s IP adresou 192.168.4.10, a router ch\u00e1p\u011b, \u017ee takov\u00e9 za\u0159\u00edzen\u00ed k n\u011bmu nen\u00ed p\u0159ipojeno, proto jednodu\u0161e mus\u00ed pustit tento r\u00e1mec p\u0159es sebe d\u00e1l po s\u00edti. Oslov\u00ed svou tabulku sm\u011brov\u00e1n\u00ed a vid\u00ed, \u017ee data pro s\u00ed\u0165 4. je t\u0159eba pos\u00edlat za\u0159\u00edzen\u00ed s IP adresou 192.168.2.2. <\/p>\n

Podobn\u011b druh\u00fd router kontroluje svou tabulku sm\u011brov\u00e1n\u00ed, zji\u0161\u0165uje, \u017ee data pro s\u00ed\u0165 4. je t\u0159eba poslat na IP adresu 192.168.3.3, a odes\u00edl\u00e1 r\u00e1mec t\u0159et\u00edmu routeru. Nakonec t\u0159et\u00ed router kontroluje svou tabulku, zji\u0161\u0165uje, \u017ee s\u00ed\u0165 4. je p\u0159ipojena k n\u011bmu samotn\u00e9mu, a odes\u00edl\u00e1 r\u00e1mec druh\u00e9mu po\u010d\u00edta\u010di. <\/p>\n

Pod\u00edvejme se, jak se vytv\u00e1\u0159\u00ed sm\u011brovac\u00ed tabulka. K tomu pou\u017eijeme Cisco Packet Tracer a uvid\u00edme, jak se implementuje koncept sm\u011brov\u00e1n\u00ed. Zde je zn\u00e1zorn\u011bna stejn\u00e1 s\u00ed\u0165ov\u00e1 topologie a nyn\u00ed p\u0159i\u0159ad\u00edm router\u016fm odpov\u00eddaj\u00edc\u00ed IP adresy, v\u010detn\u011b adres v\u00fdchoz\u00edch br\u00e1n. <\/p>\n

\"\u0160kolen\u00ed
\n
\nNic ned\u011bl\u00e1me se switchem, proto\u017ee pracuje s nastaven\u00edm podle v\u00fdchoz\u00edch hodnot a pou\u017e\u00edv\u00e1 VLAN1. P\u0159ejdeme k nastaven\u00ed prvn\u00edho routeru Router0. Nejprve mu p\u0159i\u0159ad\u00edme hostname R1, pot\u00e9 nastav\u00edme IP adresu a masku pods\u00edt\u011b pro rozhran\u00ed f0\/0. D\u00e1le je t\u0159eba pou\u017e\u00edt p\u0159\u00edkaz no shutdown. Vid\u00edte, jak se indik\u00e1tor rozhran\u00ed zm\u011bnil z \u010derven\u00e9 na zelenou, co\u017e znamen\u00e1, \u017ee port byl p\u0159ipojen do s\u00edt\u011b. <\/p>\n

D\u00e1le mus\u00edme nastavit druh\u00e9 rozhran\u00ed routeru f0\/1, p\u0159i\u010dem\u017e hostname z\u016fst\u00e1v\u00e1 stejn\u00fd, pouze p\u0159id\u00e1me IP adresu 192.168.2.1 a masku pods\u00edt\u011b 255.255.255.0. Nen\u00ed to nic nov\u00e9ho, je to jednoduch\u00e9 nastaven\u00ed, v\u0161echny p\u0159\u00edkazy u\u017e zn\u00e1te, tak\u017ee rychle p\u0159ejdu k dal\u0161\u00edm router\u016fm. Jak budu p\u0159i\u0159azovat IP adresy a pou\u017e\u00edvat p\u0159\u00edkaz no shut, porty router\u016f budou m\u011bnit barvu na zelenou, co\u017e ukazuje, \u017ee spojen\u00ed mezi za\u0159\u00edzen\u00edmi bylo nav\u00e1z\u00e1no. Vytv\u00e1\u0159\u00edm t\u00edmto s\u00edt\u00ed 1., 2., 3. a 4. Posledn\u00ed oktet IP adresy portu routeru ukazuje \u010d\u00edslo samotn\u00e9ho routeru a p\u0159edposledn\u00ed oktet \u2013 \u010d\u00edslo s\u00edt\u011b p\u0159ipojen\u00e9 k tomuto portu. <\/p>\n

T\u00edmto zp\u016fsobem budou adresy port\u016f prvn\u00edho routeru 192.168.1.1 (prvn\u00ed router, prvn\u00ed s\u00ed\u0165) a 192.168.2.1 (prvn\u00ed router, druh\u00e1 s\u00ed\u0165), u druh\u00e9ho routeru \u2013 192.168.2.2 (druh\u00fd router, druh\u00e1 s\u00ed\u0165) a 192.168.3.2 (druh\u00fd router, t\u0159et\u00ed s\u00ed\u0165) a u t\u0159et\u00edho routeru \u2013 192.168.3.3 (t\u0159et\u00ed router, t\u0159et\u00ed s\u00ed\u0165) a 192.168.4.3 (t\u0159et\u00ed router, \u010dtvrt\u00e1 s\u00ed\u0165). Domn\u00edv\u00e1m se, \u017ee je to docela snadn\u00e9 zapamatovat, nicm\u00e9n\u011b ve skute\u010dnosti se adresy mohou vytv\u00e1\u0159et jinak v z\u00e1vislosti na pravidlech p\u0159ijat\u00fdch ve va\u0161\u00ed spole\u010dnosti. Mus\u00edte se dr\u017eet firemn\u00edch pravidel, proto\u017ee va\u0161emu kolegovi bude snaz\u0161\u00ed odstra\u0148ovat probl\u00e9my ve va\u0161\u00ed s\u00edti, pokud ji vytvo\u0159\u00edte v souladu s pravidly. <\/p>\n

Tak\u017ee jsem dokon\u010dil p\u0159i\u0159azov\u00e1n\u00ed IP adres port\u016fm routeru a vid\u00edte, \u017ee port druh\u00e9ho switche tak\u00e9 zm\u011bnil barvu na zelenou, proto\u017ee spojen\u00ed mezi n\u00edm a druh\u00fdm po\u010d\u00edta\u010dem bylo automaticky nav\u00e1z\u00e1no. <\/p>\n

\"\u0160kolen\u00ed
\n
\nNyn\u00ed spust\u00edm termin\u00e1l p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku prvn\u00edho po\u010d\u00edta\u010de a provedu ping druh\u00e9ho po\u010d\u00edta\u010de na adrese 192.168.4.10. P\u0159epneme do simula\u010dn\u00edho re\u017eimu \u2013 nyn\u00ed vid\u00edte animovan\u00e9 pohyby pingovac\u00edch paket\u016f p\u0159es \u010d\u00e1sti s\u00edt\u011b. Nyn\u00ed znovu spust\u00edm ping, abyste se mohli pod\u00edvat, co se p\u0159i tom d\u011bje. Vpravo v tabulce vid\u00edte ICMP, Internet Control Message Protocol \u2013 t\u00edmto je ping ozna\u010dov\u00e1n. Ping je protokol, kter\u00fd pou\u017e\u00edv\u00e1me pro testov\u00e1n\u00ed p\u0159ipojen\u00ed. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPos\u00edl\u00e1te testovac\u00ed paket na jin\u00e9 za\u0159\u00edzen\u00ed, a pokud ho vr\u00e1t\u00ed, pak je spojen\u00ed \u00fasp\u011b\u0161n\u011b nav\u00e1z\u00e1no. Kdy\u017e kliknete na pingovac\u00ed paket na sch\u00e9matu, m\u016f\u017eete vid\u011bt informace o p\u0159enosu. <\/p>\n

\"\u0160kolen\u00ed
\n
\nVid\u00edte data 3. \u00farovn\u011b OSI \u2013 to jsou IP adresy zdroje a c\u00edle pingu, data 2. \u00farovn\u011b formou odpov\u00eddaj\u00edc\u00edch MAC adres a data 1. \u00farovn\u011b jako ozna\u010den\u00ed portu (port\u016f) \u2013 to je FastEthernet0. M\u016f\u017eete se tak\u00e9 pod\u00edvat na form\u00e1t pingovac\u00edho r\u00e1mce: hlavi\u010dka, typ a t\u011blo paketu. <\/p>\n

\"\u0160kolen\u00ed
\n
\nR\u00e1mec je nasm\u011brov\u00e1n ke switchi, switch analyzuje MAC adresy a pos\u00edl\u00e1 ho d\u00e1le p\u0159es s\u00ed\u0165 k routeru. Router zobrazuje IP adresu 192.168.4.10 a odm\u00edt\u00e1 paket, proto\u017ee takovou adresu nezn\u00e1. Pod\u00edvejme se, co se d\u011bje v re\u00e1ln\u00e9m \u010dase, a vra\u0165me se k pingu v okn\u011b p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku. <\/p>\n

\"\u0160kolen\u00ed
\n
\nVid\u00edte, \u017ee p\u0159i pokusu o pingov\u00e1n\u00ed po\u010d\u00edta\u010de 192.168.4.10 byly v\u0161echny 4 pakety ztraceny \u2013 od routeru 192.168.1.1 byla p\u0159ijata odpov\u011b\u010f, \u017ee c\u00edlov\u00fd hostitel nen\u00ed dostupn\u00fd. Vra\u0165me se do okna p\u0159\u00edkazov\u00e9ho rozhran\u00ed routeru a zadejme p\u0159\u00edkaz show ip route. Vid\u00edte nejd\u016fle\u017eit\u011bj\u0161\u00ed \u010d\u00e1st \u2013 tabulku sm\u011brov\u00e1n\u00ed, a zadan\u00fd p\u0159\u00edkaz je jedn\u00edm z hlavn\u00edch sm\u011brovac\u00edch p\u0159\u00edkaz\u016f Cisco. V tuto chv\u00edli tato tabulka obsahuje 2 z\u00e1znamy. Na za\u010d\u00e1tku tabulky se nach\u00e1z\u00ed seznam pou\u017e\u00edvan\u00fdch zkratek, z n\u011bj\u017e je z\u0159ejm\u00e9, \u017ee p\u00edsmeno C ozna\u010duje p\u0159ipojen\u00ed. Prvn\u00ed z\u00e1znam uv\u00e1d\u00ed, \u017ee s\u00ed\u0165 192.168.1.0\/24 je p\u0159\u00edmo p\u0159ipojena k portu FastEthernet0\/0, a s\u00ed\u0165 192.168.2.0\/24 je p\u0159\u00edmo p\u0159ipojena k portu FastEthernet0\/1. To znamen\u00e1, \u017ee v sou\u010dasnosti router zn\u00e1 pouze tyto dv\u011b s\u00edt\u011b. <\/p>\n

\"\u0160kolen\u00ed
\n
\nHodnota 192.168.1.0\/24 je identifik\u00e1tor s\u00edt\u011b. Kdy\u017e jsme vytv\u00e1\u0159eli pods\u00edt\u011b, sou\u010dasn\u011b jsme vytv\u00e1\u0159eli jejich identifik\u00e1tory. Tyto identifik\u00e1tory \u0159\u00edkaj\u00ed routeru, \u017ee v\u0161echna za\u0159\u00edzen\u00ed, jejich\u017e IP adresy se pohybuj\u00ed v rozmez\u00ed od 192.168.1.1 do 192.168.1.254, se nach\u00e1zej\u00ed v t\u00e9to pods\u00edti. Tak\u017ee v\u0161echna tato za\u0159\u00edzen\u00ed by technicky m\u011bla b\u00fdt dostupn\u00e1 pro router, proto\u017ee je p\u0159ipojen k t\u00e9to s\u00edti. <\/p>\n

Pokud se na konci identifik\u00e1toru nach\u00e1z\u00ed hodnota \/24, znamen\u00e1 to, \u017ee v\u0161em za\u0159\u00edzen\u00edm v t\u00e9to s\u00edti od 1 do 254 bude zas\u00edl\u00e1na broadcastov\u00e1 zpr\u00e1va. Tak\u017ee k tomuto routeru jsou p\u0159ipojeny pouze s\u00edt\u011b 1. a 2., tak\u017ee zn\u00e1 pouze tyto s\u00edt\u011b. Kdy\u017e tedy ping z adresy 192.168.4.10 doraz\u00ed k routeru, nev\u00ed, \u017ee tato adresa je dostupn\u00e1 p\u0159es trasu Router0 - Router1 - Router2. <\/p>\n

Ale nap\u0159\u00edklad vy jako spr\u00e1vce s\u00edt\u011b v\u00edte, \u017ee tato trasa je dostupn\u00e1, to znamen\u00e1, \u017ee prvn\u00ed router m\u016f\u017ee tento paket odeslat druh\u00e9mu routeru. Proto byste m\u011bli zorganizovat statick\u00e9 sm\u011brov\u00e1n\u00ed. Poj\u010fme se to pokusit ud\u011blat. <\/p>\n

Pov\u00edme tomuto routeru, \u017ee ka\u017ed\u00fd paket a ve\u0161ker\u00fd provoz ur\u010den\u00fd pro s\u00ed\u0165 192.168.4.0\/24 by m\u011bl b\u00fdt odesl\u00e1n druh\u00e9mu routeru. Form\u00e1t p\u0159\u00edkazu pro nastaven\u00ed statick\u00e9ho sm\u011brov\u00e1n\u00ed vypad\u00e1 takto: ip route . <\/p>\n

\"\u0160kolen\u00ed
\n
\nTe\u010f v\u00e1m uk\u00e1\u017eu, co to znamen\u00e1. Pro tento p\u0159\u00edkaz pou\u017e\u00edv\u00e1me re\u017eim glob\u00e1ln\u00ed konfigurace nastaven\u00ed routeru. Zad\u00e1v\u00e1m ip route 192.168.4.0 255.255.255.0 \u2013 to znamen\u00e1, \u017ee sem pat\u0159\u00ed ve\u0161ker\u00fd provoz pro za\u0159\u00edzen\u00ed s\u00edt\u011b, jejich\u017e IP adresa m\u00e1 hodnotu posledn\u00edho oktetu od 1 do 254, a pot\u00e9 zad\u00e1v\u00e1m bu\u010f IP adresu, nebo ozna\u010den\u00ed portu, kam by m\u011bl b\u00fdt tento provoz odesl\u00e1n. V tomto p\u0159\u00edpad\u011b zad\u00e1v\u00e1m ozna\u010den\u00ed rozhran\u00ed f0\/1, tak\u017ee p\u0159\u00edkaz vypad\u00e1 takto: ip route 192.168.4.0 255.255.255.0 f0\/1.<\/p>\n

\"\u0160kolen\u00ed
\n
\nM\u00edsto rozhran\u00ed br\u00e1ny mohu uv\u00e9st jej\u00ed IP adresu, pak bude p\u0159\u00edkaz statick\u00e9ho sm\u011brov\u00e1n\u00ed vypadat jako ip route 192.168.4.0 255.255.255.0 192.168.2.2.<\/p>\n

M\u016f\u017eete se pt\u00e1t, co je lep\u0161\u00ed. Mysl\u00edm, \u017ee pro broadcastov\u00e9 s\u00edt\u011b, jako je Ethernet, je lep\u0161\u00ed uv\u00e9st IP adresu. Pokud pou\u017e\u00edv\u00e1te s\u00edt\u011b typu point-to-point, jako je Frame Relay, je lep\u0161\u00ed pou\u017e\u00edt exit interface. Pozd\u011bji se pod\u00edv\u00e1me na s\u00edt\u011b Frame Relay, nyn\u00ed pou\u017e\u00edv\u00e1m vhodn\u011bj\u0161\u00ed variantu p\u0159\u00edkazu pro routov\u00e1n\u00ed -192.168.4.0 255.255.255.0.<\/p>\n

Nyn\u00ed se pod\u00edvejme na routovac\u00ed tabulku, pou\u017eijeme p\u0159\u00edkaz do show ip address. Vid\u00edte, \u017ee se v n\u00ed objevila nov\u00e1 polo\u017eka ozna\u010den\u00e1 p\u00edsmenem S, tedy statick\u00e1. <\/p>\n

\"\u0160kolen\u00ed
\n
\nTato polo\u017eka \u0159\u00edk\u00e1, \u017ee pokud existuje provoz pro s\u00ed\u0165 192.168.4.0\/24, m\u011bl by b\u00fdt p\u0159eposl\u00e1n na adres\u00e1ta prost\u0159ednictv\u00edm za\u0159\u00edzen\u00ed s IP adresou 192.168.2.2. Vra\u0165me se k p\u0159\u00edkazov\u00e9mu \u0159\u00e1dku po\u010d\u00edta\u010de a pingneme pot\u0159ebnou adresu znovu. Nyn\u00ed by provoz m\u011bl proj\u00edt p\u0159es prvn\u00ed router a dos\u00e1hnout druh\u00e9ho routeru, kter\u00fd by m\u011bl odhodit pakety.<\/p>\n

V prvn\u00edm p\u0159\u00edpad\u011b router nejen\u017ee odhodil pakety, ale tak\u00e9 odpov\u011bd\u011bl po\u010d\u00edta\u010di, \u017ee IP adresa 192.168.4.10 nen\u00ed dostupn\u00e1. Druh\u00fd router v\u0161ak m\u016f\u017ee odpov\u011bd\u011bt pouze prvn\u00edmu routeru, od kter\u00e9ho p\u0159ijal provoz. Pod\u00edvejme se na routovac\u00ed tabulku druh\u00e9ho routeru. Zde se \u0159\u00edk\u00e1, \u017ee Router1 zn\u00e1 pouze s\u00edt\u011b 2. a 3., ale nic nev\u00ed o s\u00edti 4., kam by m\u011bl pos\u00edlat pakety prvn\u00edho po\u010d\u00edta\u010de. Odeslal by zp\u011bt zpr\u00e1vu, \u017ee hostitel je nedostupn\u00fd, ale nev\u00ed, jak se spojit s po\u010d\u00edta\u010dem, kter\u00fd tyto pakety poslal, proto\u017ee nic nev\u00ed o s\u00edti 1. Proto m\u00edsto zpr\u00e1vy o nedostupnosti hostitele jsme obdr\u017eeli zpr\u00e1vu Request timed out \u2013 \u010dasov\u00fd limit po\u017eadavku vypr\u0161el. R\u016fzn\u00e9 s\u00ed\u0165ov\u00e9 za\u0159\u00edzen\u00ed maj\u00ed r\u016fzn\u00e9 hodnoty TTL, tak\u017ee kdy\u017e IP pakety dos\u00e1hnou t\u00e9to hodnoty, jsou zni\u010deny. P\u0159itom prob\u00edh\u00e1 odpo\u010d\u00edt\u00e1v\u00e1n\u00ed \u2013 uskute\u010dn\u00ed se jeden hop, a hodnoti\u010dka TTL se m\u011bn\u00ed z 16 na 15, druh\u00fd \u2013 z 15 na 14 a tak d\u00e1le, dokud hodnota TTL nedos\u00e1hne 0 a paket bude zni\u010den. <\/p>\n

Takto funguje mechanismus ochrany p\u0159ed cykl\u00edc\u00edmi IP pakety. Pokud za\u0159\u00edzen\u00ed nedostane po\u017eadavek v nastaven\u00e9m \u010dase, syst\u00e9m vyd\u00e1 podobnou zpr\u00e1vu. Poj\u010fme se tedy pod\u00edvat na nastaven\u00ed druh\u00e9ho routeru a uk\u00e1zat mu, jak dos\u00e1hnout \u010dtvrt\u00e9 pods\u00edt\u011b. K tomu pou\u017eiji p\u0159\u00edkaz ip route 192.168.4.0 255.255.255.0 192.168.3.3. Nyn\u00ed se p\u0159\u00edslu\u0161n\u00fd z\u00e1znam objevil v tabulce sm\u011brov\u00e1n\u00ed, kterou jsme vyvolali p\u0159\u00edkazem do show ip route. <\/p>\n

\"\u0160kolen\u00ed
\n
\nNyn\u00ed Router1 v\u00ed, jak pos\u00edlat provoz adres\u00e1t\u016fm \u010dtvrt\u00e9 pods\u00edt\u011b. Odes\u00edl\u00e1 ho t\u0159et\u00edmu routeru. T\u0159et\u00ed router Router2, proto\u017ee je p\u0159ipojen k s\u00edti 4., rozhodn\u011b v\u00ed, jak odeslat paket druh\u00e9mu po\u010d\u00edta\u010di.<\/p>\n

Co se stane, kdy\u017e po\u0161lu ping znovu? V\u017edy\u0165 nyn\u00ed v\u0161echny s\u00ed\u0165ov\u00e9 za\u0159\u00edzen\u00ed v\u011bd\u00ed, jak dos\u00e1hnout druh\u00e9ho po\u010d\u00edta\u010de. Bude te\u010f pingov\u00e1n\u00ed IP adresy 192.168.4.10 \u00fasp\u011b\u0161n\u00e9? Ne, nebude! <\/p>\n

Jak u\u017e jsem zm\u00ednil, ICMP je protokol obousm\u011brn\u00e9 komunikace, tak\u017ee pokud n\u011bkdo pos\u00edl\u00e1 pingov\u00e9 pakety, mus\u00ed se vr\u00e1tit zp\u011bt. Sm\u011brov\u00e1n\u00ed spo\u010d\u00edv\u00e1 v tom, \u017ee ka\u017ed\u00e9 s\u00ed\u0165ov\u00e9 za\u0159\u00edzen\u00ed mus\u00ed nejen v\u011bd\u011bt, jak poslat zpr\u00e1vu n\u011bkomu, ale tak\u00e9 mus\u00ed v\u011bd\u011bt, jak doru\u010dit odpov\u011bdn\u00ed zpr\u00e1vu odes\u00edlateli po\u017eadavku. Tak\u017ee paket odeslan\u00fd prvn\u00edm po\u010d\u00edta\u010dem \u00fasp\u011b\u0161n\u011b dos\u00e1hl druh\u00e9ho po\u010d\u00edta\u010de. Druh\u00fd po\u010d\u00edta\u010d si \u0159\u00edk\u00e1: \"skv\u011ble, dostal jsem va\u0161i zpr\u00e1vu a te\u010f v\u00e1m mus\u00edm poslat odpov\u011b\u010f\". Tato odpov\u011b\u010f, adresovan\u00e1 za\u0159\u00edzen\u00ed s IP adresou 192.168.1.10, se dost\u00e1v\u00e1 k routeru Router2. T\u0159et\u00ed router vid\u00ed, \u017ee m\u00e1 odeslat paket do prvn\u00ed pods\u00edt\u011b, ale ve sv\u00e9 tabulce sm\u011brov\u00e1n\u00ed m\u00e1 z\u00e1znamy pouze o t\u0159et\u00ed a \u010dtvrt\u00e9 pods\u00edti. Proto mus\u00edme vytvo\u0159it statickou trasu pomoc\u00ed p\u0159\u00edkazu ip route 192.168.1.0 255.255.255.0 192.168.3.2. Tento p\u0159\u00edkaz \u0159\u00edk\u00e1, \u017ee provoz ur\u010den\u00fd pro s\u00ed\u0165 s identifik\u00e1torem 192.168.1.0 by m\u011bl b\u00fdt odesl\u00e1n druh\u00e9mu routeru s IP adresou 192.168.3.2. <\/p>\n

Co se stane pot\u00e9? Druh\u00fd router v\u00ed o s\u00edt\u00edch 2., 3. a 4., ale nic nev\u00ed o prvn\u00ed s\u00edti. Proto se mus\u00edme dostat do nastaven\u00ed druh\u00e9ho routeru Router1 a pou\u017e\u00edt p\u0159\u00edkaz ip route 192.168.1.0 255.255.255.0 192.168.2.1, co\u017e znamen\u00e1, \u017ee provoz pro s\u00ed\u0165 1. by m\u011bl b\u00fdt odesl\u00e1n p\u0159es s\u00ed\u0165 2. prvn\u00edmu routeru Router0.<\/p>\n

Po t\u00e9to f\u00e1zi paket doraz\u00ed k prvn\u00edmu routeru, kter\u00fd zn\u00e1 za\u0159\u00edzen\u00ed 192.168.1.10, proto\u017ee prvn\u00ed s\u00ed\u0165, ve kter\u00e9 se tento po\u010d\u00edta\u010d nach\u00e1z\u00ed, je p\u0159ipojena k portu tohoto routeru. Upozor\u0148uji, \u017ee nyn\u00ed prvn\u00ed router nic nev\u00ed o s\u00edti 3, a t\u0159et\u00ed router nic nev\u00ed o druh\u00e9 s\u00edti. To m\u016f\u017ee zp\u016fsobit probl\u00e9m, proto\u017ee tyto routery neznaj\u00ed existenci mezi subnet\u016f. <\/p>\n

Znovu pinguji adresu 192.168.4.0 a vid\u00edte, \u017ee tentokr\u00e1t byl ping \u00fasp\u011b\u0161n\u00fd. Pakety pro\u0161ly celou cestu od prvn\u00edho k druh\u00e9mu po\u010d\u00edta\u010di a odpov\u011b\u010f se vr\u00e1tila odes\u00edlateli. V okn\u011b p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku je vid\u011bt zpr\u00e1va, \u017ee ka\u017ed\u00fd z 4 odpov\u011bdn\u00edch paket\u016f 192.168.4.0 m\u00e1 velikost 32 bajt\u016f, TTL= 125 ms a \u00fasp\u011b\u0161nost pingu je 100 %. To znamen\u00e1, \u017ee zdroj p\u0159enosu obdr\u017eel odpov\u011b\u010f od c\u00edlov\u00e9ho hostitele. Tak\u017ee i kdy\u017e za\u0159\u00edzen\u00ed neznaj\u00ed existenci n\u011bkter\u00fdch mezi subnet\u016f, nen\u00ed to probl\u00e9m, pokud funguj\u00ed na principu \u201ekone\u010dn\u00fd odes\u00edlatel \u2013 kone\u010dn\u00fd p\u0159\u00edjemce\u201c. Prvn\u00ed po\u010d\u00edta\u010d v\u00ed, jak se dostat k druh\u00e9mu po\u010d\u00edta\u010di, a druh\u00fd v\u00ed, jak se dostat k prvn\u00edmu. <\/p>\n

Pod\u00edvejme se na jinou situaci. Tak\u017ee prvn\u00ed po\u010d\u00edta\u010d m\u016f\u017ee \u00fasp\u011b\u0161n\u011b komunikovat s druh\u00fdm po\u010d\u00edta\u010dem, p\u0159i\u010dem\u017e provoz proch\u00e1z\u00ed v\u0161emi t\u011bmito za\u0159\u00edzen\u00edmi. Pod\u00edvejme se, zda se PC0 m\u016f\u017ee spojit s t\u0159et\u00edm routerem Router2 na adrese 192.168.3.3 \u2013 to je port s\u00edt\u011b 3 t\u0159et\u00edho routeru. Ping ukazuje, \u017ee to nen\u00ed mo\u017en\u00e9 \u2013 c\u00edlov\u00fd hostitel nen\u00ed dostupn\u00fd. <\/p>\n

Pod\u00edvejme se, co je p\u0159\u00ed\u010dinou. Otev\u0159en\u00edm sm\u011brovac\u00ed tabulky prvn\u00edho routeru vid\u00edme, \u017ee zn\u00e1 pouze 3 s\u00edt\u011b \u2013 prvn\u00ed, druhou a \u010dtvrtou, ale nic nev\u00ed o t\u0159et\u00ed s\u00edti. Proto pokud se chci spojit s touto s\u00edt\u00ed, je pot\u0159eba pro ni nastavit statickou trasu. <\/p>\n

Tak\u017ee jsme prozkoumali, jak lze nastavit statickou routov\u00e1n\u00ed pro t\u0159i routery. Pokud m\u00e1te 10 router\u016f a 50 r\u016fzn\u00fdch subnet\u016f, manu\u00e1ln\u00ed nastaven\u00ed statick\u00e9 routov\u00e1n\u00ed zabere hodn\u011b \u010dasu. Proto pot\u0159ebujeme dynamick\u00e9 routov\u00e1n\u00ed.
\nTe\u010f odstran\u00edm v\u0161echny trasy, kter\u00e9 jsem vytvo\u0159il. Za t\u00edmto \u00fa\u010delem postupn\u011b vyvol\u00e1m tabulky sm\u011brov\u00e1n\u00ed v\u0161ech router\u016f a na za\u010d\u00e1tek ka\u017ed\u00e9ho statick\u00e9ho sm\u011brov\u00e1n\u00ed p\u0159id\u00e1m slovo \u201eno\u201c, tedy pou\u017eiji p\u0159\u00edkaz negace. Nyn\u00ed se m\u016f\u017eeme pod\u00edvat, co p\u0159edstavuje dynamick\u00e9 sm\u011brov\u00e1n\u00ed. <\/p>\n

Pro dynamick\u00e9 sm\u011brov\u00e1n\u00ed mus\u00edm aktivovat protokol RIP, co\u017e je velmi rychl\u00fd protokol. Ale dnes nebudeme diskutovat o RIP, na\u0161e t\u00e9ma je statick\u00e9 sm\u011brov\u00e1n\u00ed, a cht\u011bl jsem v\u00e1m uk\u00e1zat, jak n\u00e1ro\u010dn\u00e9 a vy\u010derp\u00e1vaj\u00edc\u00ed to je. Rychle v\u00e1m v\u0161ak demonstruji, jak RIP funguje, kter\u00e9mu se podrobn\u011b v\u011bnujeme v n\u00e1sleduj\u00edc\u00ed lekci.
\nNa p\u0159\u00edkladu prvn\u00edho routeru pou\u017eiji p\u0159\u00edkaz router rip, pot\u00e9 zad\u00e1m ver 2, abych ur\u010dil verzi protokolu, a pot\u00e9 jednotliv\u00fdmi \u0159\u00e1dky uvedu s\u00edt\u011b, pro kter\u00e9 je t\u0159eba pou\u017e\u00edt protokol dynamick\u00e9ho sm\u011brov\u00e1n\u00ed: 192.168.1.0, 192.168.2.0, pot\u00e9 p\u0159ejdu k druh\u00e9mu routeru a s n\u00edm postupn\u011b ud\u011bl\u00e1m tot\u00e9\u017e. Technicky pouze uv\u00e1d\u00edm s\u00edt\u011b, kter\u00e9 jsou p\u0159ipojeny k dan\u00e9mu za\u0159\u00edzen\u00ed, tak\u017ee pro druh\u00fd router uvedu 192.168.2.0 a 192.168.3.0, a pro t\u0159et\u00ed po p\u0159\u00edkazu rip ver 2 \u2013 adresy 192.168.3.0 a 192.168.4.0. Pak se vr\u00e1t\u00edm k prvn\u00edmu routeru a pod\u00edv\u00e1m se na tabulku sm\u011brov\u00e1n\u00ed. <\/p>\n

\"\u0160kolen\u00ed
\n
\nVid\u00edte, \u017ee v n\u00ed kouzeln\u011b objevily v\u0161echny s\u00edt\u011b, prvn\u00ed dv\u011b jsou ty, kter\u00e9 jsou p\u0159\u00edmo p\u0159ipojeny k routeru, a zb\u00fdvaj\u00edc\u00ed dv\u011b jsou ty, jejich\u017e spojen\u00ed prob\u00edh\u00e1 pomoc\u00ed protokolu dynamick\u00e9ho sm\u011brov\u00e1n\u00ed RIP. Podobn\u00e1 situace je v tabulk\u00e1ch sm\u011brov\u00e1n\u00ed druh\u00e9ho a t\u0159et\u00edho routeru. Pokud p\u0159ipoj\u00edm k druh\u00e9mu routeru s\u00edt\u011b 5. a 6., v\u0161echna za\u0159\u00edzen\u00ed, kter\u00e1 pou\u017e\u00edvaj\u00ed RIP, se dozv\u011bd\u00ed o t\u011bchto nov\u00fdch s\u00edt\u00edch. A to je v\u00fdhoda dynamick\u00e9ho sm\u011brov\u00e1n\u00ed.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud nyn\u00ed pingnu druh\u00fd po\u010d\u00edta\u010d, spojen\u00ed bude fungovat bez probl\u00e9m\u016f. M\u016f\u017eu pingnout t\u0159et\u00ed router a ping bude \u00fasp\u011b\u0161n\u00fd, proto\u017ee prvn\u00ed router d\u00edky RIP v\u00ed o v\u0161ech za\u0159\u00edzen\u00edch v v\u0161ech s\u00edt\u00edch. Podobn\u00fdm \u201eznalostem\u201c budou disponovat druh\u00fd a t\u0159et\u00ed router. Ne\u0159\u00edk\u00e1m, \u017ee RIP je nejlep\u0161\u00ed protokol, ale je schopen efektivn\u011b vykon\u00e1vat mnoho v\u011bc\u00ed. Zat\u00edm si chci, abyste pochopili, co je to sm\u011brov\u00e1n\u00ed a jak funguje, co je to sm\u011brovac\u00ed tabulka a jak\u00fd m\u00e1 v\u00fdznam. <\/p>\n

Bez ohledu na to, zda pou\u017e\u00edv\u00e1te statick\u00e9 nebo dynamick\u00e9 sm\u011brov\u00e1n\u00ed, \u00falohou protokol\u016f je vyplnit sm\u011brovac\u00ed tabulku. Tato tabulka mus\u00ed zn\u00e1t v\u0161echny trasy k v\u0161em za\u0159\u00edzen\u00edm v s\u00edti, aby jedno za\u0159\u00edzen\u00ed mohlo nav\u00e1zat spojen\u00ed s jin\u00fdm za\u0159\u00edzen\u00edm. <\/p>\n

Dnes jste se tedy dozv\u011bd\u011bli, \u017ee sm\u011brov\u00e1n\u00ed je proces, kter\u00fd zaji\u0161\u0165uje vznik z\u00e1znam\u016f o tras\u00e1ch ve sm\u011brovac\u00edch tabulk\u00e1ch, aby mohl router rozhodovat o zas\u00edl\u00e1n\u00ed provozu s\u00edt\u00ed. <\/p>\n

\r\n \"P\u0159ehr\u00e1t\r\n
<\/div>\r\n <\/div><\/center>
\nD\u011bkujeme, \u017ee s n\u00e1mi z\u016fst\u00e1v\u00e1te. L\u00edb\u00ed se v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vid\u011bt v\u00edce zaj\u00edmav\u00fdch materi\u00e1l\u016f? Podpo\u0159te n\u00e1s objedn\u00e1vkou nebo doporu\u010den\u00edm zn\u00e1m\u00fdm, 30 % sleva pro u\u017eivatele Habra na jedine\u010dn\u00fd analog entry-level server\u016f, kter\u00fd jsme pro v\u00e1s vymysleli:<\/b> Ve\u0161ker\u00e1 pravda o VPS (KVM) E5-2650 v4 (6 jader) 10GB DDR4 240GB SSD 1Gbps od 20 $ nebo jak spr\u00e1vn\u011b rozd\u011blit server?<\/a><\/noindex> (k dispozici varianty s RAID1 a RAID10, a\u017e 24 jader a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd za polovinu ceny?<\/b> Jen u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 $<\/a><\/noindex> v Nizozemsku! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> \u010ct\u011bte o tom Jak postavit infrastrukturu podnikov\u00e9 t\u0159\u00eddy s pou\u017eit\u00edm server\u016f Dell R730xd E5-2650 v4 v hodnot\u011b 9000 eur za pakatel?<\/a><\/noindex>
\n
Zdroj: 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\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\udd47\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 20. Statick\u00e9 sm\u011brov\u00e1n\u00ed | ProHoster","description":"Dnes budeme hovo\u0159it o statick\u00e9m sm\u011brov\u00e1n\u00ed a probereme t\u0159i t\u00e9mata: co je to statick\u00e9 sm\u011brov\u00e1n\u00ed, jak se nastavuje a jak\u00e1 m\u00e1 alternativa.","canonical_url":"https:\/\/prohoster.info\/cs\/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":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/37303","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=37303"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37303\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/27983"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37303"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}