{"id":37271,"date":"2019-10-31T22:16:41","date_gmt":"2019-10-31T19:16:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii\/"},"modified":"2019-10-31T22:16:41","modified_gmt":"2019-10-31T19:16:41","slug":"trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","title":{"rendered":"\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 18. Z\u00e1klady sm\u011brov\u00e1n\u00ed","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes se pust\u00edme do studia router\u016f. Pokud jste pro\u0161li m\u00fdm videokurzem od prvn\u00ed do sedmn\u00e1ct\u00e9 lekce, ji\u017e jste se nau\u010dili z\u00e1klady switch\u016f. Nyn\u00ed p\u0159ech\u00e1z\u00edme k dal\u0161\u00edmu za\u0159\u00edzen\u00ed \u2013 routeru. Jak v\u00edte z p\u0159edchoz\u00edho videa, jedno z t\u00e9mat kurzu CCNA se pr\u00e1v\u011b tak naz\u00fdv\u00e1 \u2013 Cisco Switching & Routing.<\/p>\n

V t\u00e9to s\u00e9rii se nebudeme zab\u00fdvat routery Cisco, ale prozkoum\u00e1me koncept sm\u011brov\u00e1n\u00ed jako takov\u00e9ho. Budeme m\u00edt t\u0159i hlavn\u00ed t\u00e9mata. Prvn\u00ed je p\u0159ehled toho, co u\u017e v\u00edte o routerech a rozhovor o tom, jak to m\u016f\u017ee b\u00fdt aplikov\u00e1no spole\u010dn\u011b se znalostmi, kter\u00e9 jste z\u00edskali p\u0159i studiu switch\u016f. Mus\u00edme pochopit, v \u010dem spo\u010d\u00edv\u00e1 spolupr\u00e1ce switch\u016f a router\u016f.<\/p>\n

\"\u0160kolen\u00ed
\n
\nD\u00e1le se pod\u00edv\u00e1me, co to vlastn\u011b sm\u011brov\u00e1n\u00ed je, co znamen\u00e1 a jak funguje, a pot\u00e9 p\u0159ejdeme k typ\u016fm sm\u011brovac\u00edch protokol\u016f. Dnes pou\u017e\u00edv\u00e1m topologii, kterou jste ji\u017e vid\u011bli v p\u0159edchoz\u00edch lekc\u00edch. <\/a><\/noindex><\/p>\n

Prozkoumali jsme, jak se data pohybuj\u00ed v s\u00edti a jak prob\u00edh\u00e1 t\u0159\u00edf\u00e1zov\u00e9 TCP handshake. Prvn\u00ed zpr\u00e1va odes\u00edlan\u00e1 v s\u00edti je SYN paket. Zjist\u00edme, jak prob\u00edh\u00e1 t\u0159\u00edf\u00e1zov\u00e9 handshake, kdy\u017e po\u010d\u00edta\u010d s IP adresou 10.1.1.10 chce nav\u00e1zat kontakt se serverem 30.1.1.10, tj. pokou\u0161\u00ed se nav\u00e1zat FTP spojen\u00ed.
\nAbychom za\u010dali spojen\u00ed, po\u010d\u00edta\u010d vytv\u00e1\u0159\u00ed port zdroje s n\u00e1hodn\u00fdm \u010d\u00edslem 25113. Pokud jste zapomn\u011bli, jak to prob\u00edh\u00e1, doporu\u010duji znovu si prohl\u00e9dnout p\u0159edchoz\u00ed videolekce, kde jsme tuto ot\u00e1zku prob\u00edrali. <\/p>\n

\"\u0160kolen\u00ed
\n
\nD\u00e1le um\u00edst\u00ed do r\u00e1mce \u010d\u00edslo c\u00edlov\u00e9ho portu, proto\u017ee v\u00ed, \u017ee se mus\u00ed spojit s portem 21, pot\u00e9 p\u0159id\u00e1v\u00e1 informace t\u0159et\u00ed \u00farovn\u011b OSI, tj. vlastn\u00ed IP adresu a IP adresu c\u00edlov\u00e9ho bodu. Data, obkrou\u017een\u00e1 te\u010dkovan\u011b, se nem\u011bn\u00ed, dokud nedos\u00e1hnou koncov\u00e9ho bodu. Po dosa\u017een\u00ed serveru se tak\u00e9 nem\u011bn\u00ed, ale server p\u0159id\u00e1v\u00e1 k r\u00e1mce informace druh\u00e9 \u00farovn\u011b, tj. MAC adresu. To souvis\u00ed s t\u00edm, \u017ee switche pracuj\u00ed pouze s informacemi druh\u00e9 \u00farovn\u011b OSI. V tomto sc\u00e9n\u00e1\u0159i je router jedin\u00fdm s\u00ed\u0165ov\u00fdm za\u0159\u00edzen\u00edm, kter\u00e9 zpracov\u00e1v\u00e1 informace t\u0159et\u00ed \u00farovn\u011b, samoz\u0159ejm\u011b po\u010d\u00edta\u010d tak\u00e9 pracuje s t\u011bmito informacemi. Tak\u017ee switch pracuje pouze s informacemi druh\u00e9 \u00farovn\u011b, zat\u00edmco router \u2013 t\u0159et\u00ed. <\/p>\n

Switch zn\u00e1 p\u016fvodn\u00ed MAC adresu XXXX:XXXX:1111 a chce zjistit MAC adresu serveru, ke kter\u00e9mu se po\u010d\u00edta\u010d obrac\u00ed. Porovn\u00e1 p\u016fvodn\u00ed IP adresu s c\u00edlovou adresou, pochop\u00ed, \u017ee tato za\u0159\u00edzen\u00ed se nach\u00e1zej\u00ed v r\u016fzn\u00fdch pods\u00edt\u00edch, a rozhodne se pou\u017e\u00edt br\u00e1nu pro v\u00fdstup do jin\u00e9 pods\u00edt\u011b.<\/p>\n

\u010casto se m\u011b ptaj\u00ed, kdo ur\u010duje, jak\u00e1 m\u00e1 b\u00fdt IP adresa br\u00e1ny. P\u0159edev\u0161\u00edm to ur\u010duje s\u00ed\u0165ov\u00fd administr\u00e1tor, kter\u00fd vytv\u00e1\u0159\u00ed s\u00ed\u0165 a p\u0159id\u011bluje IP adresu ka\u017ed\u00e9mu za\u0159\u00edzen\u00ed. Jako administr\u00e1tor m\u016f\u017eete routeru p\u0159id\u011blit jakoukoli adresu, kter\u00e1 se nach\u00e1z\u00ed v rozmez\u00ed povolen\u00fdch adres va\u0161\u00ed pods\u00edt\u011b. Obvykle to je prvn\u00ed nebo posledn\u00ed platn\u00e1 adresa, ale neexistuj\u00ed \u017e\u00e1dn\u00e1 p\u0159\u00edsn\u00e1 pravidla ohledn\u011b jej\u00edho p\u0159id\u011blen\u00ed. V na\u0161em p\u0159\u00edpad\u011b administr\u00e1tor p\u0159id\u011blil adresu br\u00e1ny, nebo routeru, 10.1.1.1 a p\u0159i\u0159adil ji portu F0\/0. <\/p>\n

Kdy\u017e nastavujete s\u00ed\u0165 na po\u010d\u00edta\u010di se statickou IP adresou 10.1.1.10, p\u0159id\u011blujete masku pods\u00edt\u011b 255.255.255.0 a v\u00fdchoz\u00ed br\u00e1nu 10.1.1.1. Pokud nepou\u017e\u00edv\u00e1te statickou adresu, znamen\u00e1 to, \u017ee po\u010d\u00edta\u010d pou\u017e\u00edv\u00e1 DHCP, kter\u00e9 p\u0159id\u011bluje dynamickou adresu. Nez\u00e1visle na tom, kterou IP adresu po\u010d\u00edta\u010d pou\u017e\u00edv\u00e1, statickou nebo dynamickou, mus\u00ed existovat adresa br\u00e1ny pro v\u00fdstup do jin\u00e9 s\u00edt\u011b. <\/p>\n

Tak\u017ee po\u010d\u00edta\u010d 10.1.1.10 v\u00ed, \u017ee mus\u00ed odeslat r\u00e1mec routeru 10.1.1.1. Tento p\u0159enos prob\u00edh\u00e1 uvnit\u0159 lok\u00e1ln\u00ed s\u00edt\u011b, kde IP adresa nem\u00e1 \u017e\u00e1dn\u00fd v\u00fdznam, zde je d\u016fle\u017eit\u00e1 pouze MAC adresa. P\u0159edpokl\u00e1dejme, \u017ee po\u010d\u00edta\u010d p\u0159edt\u00edm nikdy nekomunikoval s routerem a nezn\u00e1 jeho MAC adresu, tak\u017ee nejprve mus\u00ed poslat ARP dotaz, kter\u00fdm se pt\u00e1 v\u0161ech za\u0159\u00edzen\u00ed v pods\u00edti: \u201eHej, kdo z v\u00e1s m\u00e1 adresu 10.1.1.1? Pros\u00edm, sd\u011blte mi svou MAC adresu!\u201c. Proto\u017ee ARP je vys\u00edlac\u00ed zpr\u00e1va, dost\u00e1v\u00e1 se k v\u0161em port\u016fm v\u0161ech za\u0159\u00edzen\u00ed, v\u010detn\u011b routeru. <\/p>\n

Po\u010d\u00edta\u010d 10.1.1.12, kdy\u017e obdr\u017e\u00ed ARP, si mysl\u00ed: \u201ene, moje adresa nen\u00ed 10.1.1.1\u201c, a \u017e\u00e1dost odm\u00edt\u00e1, obdobn\u011b postupuje po\u010d\u00edta\u010d 10.1.1.13. Router, kdy\u017e dostane \u017e\u00e1dost, ch\u00e1pe, \u017ee se ptaj\u00ed pr\u00e1v\u011b jeho, a ode\u0161le MAC adresu portu F0\/0 \u2013 v\u0161echny porty maj\u00ed r\u016fzn\u00e9 MAC adresy \u2013 po\u010d\u00edta\u010di 10.1.1.10. Nyn\u00ed, kdy\u017e zn\u00e1 adresu br\u00e1ny XXXX:AAAA, kter\u00e1 v tomto p\u0159\u00edpad\u011b je c\u00edlovou adresou, po\u010d\u00edta\u010d ji p\u0159id\u00e1v\u00e1 na konec r\u00e1mce adresovan\u00e9ho serveru. Spolu s t\u00edm nastavuje hlavi\u010dku r\u00e1mce FCS\/CRC, co\u017e p\u0159edstavuje mechanismus pro kontrolu chyb p\u0159enosu. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPot\u00e9 je r\u00e1mec po\u010d\u00edta\u010de 10.1.1.10 odesl\u00e1n dr\u00e1ty k routeru 10.1.1.1. Po obdr\u017een\u00ed r\u00e1mce router odstran\u00ed FCS\/CRC a pou\u017eije ke kontrole tent\u00fd\u017e algoritmus jako po\u010d\u00edta\u010d. Data jsou nic jin\u00e9ho ne\u017e soubor nul a jedni\u010dek. Pokud jsou data po\u0161kozena, tj. 1 se stane 0 nebo 0 se stane 1, nebo dojde k \u00faniku dat, kter\u00fd se \u010dasto objevuje p\u0159i pou\u017eit\u00ed hubu, za\u0159\u00edzen\u00ed mus\u00ed r\u00e1mec znovu odeslat. <\/p>\n

Pokud kontrola FCS\/CRC prob\u011bhla \u00fasp\u011b\u0161n\u011b, router se pod\u00edv\u00e1 na MAC adresy zdroje a c\u00edle a odstran\u00ed je, proto\u017ee to jsou informace 2. \u00farovn\u011b, a p\u0159ejde k t\u011blu r\u00e1mce, ve kter\u00e9m jsou informace 3. \u00farovn\u011b. Z t\u00e9 se dozv\u00ed, \u017ee informace, kter\u00e9 r\u00e1mec obsahuje, jsou ur\u010deny pro za\u0159\u00edzen\u00ed s IP adresou 30.1.1.10. <\/p>\n

Router v\u00ed, kde se toto za\u0159\u00edzen\u00ed nach\u00e1z\u00ed. Tento probl\u00e9m jsme ne\u0159e\u0161ili, kdy\u017e jsme se zab\u00fdvali fungov\u00e1n\u00edm switch\u016f, proto se na n\u011bj nyn\u00ed pod\u00edvejme. Router m\u00e1 4 porty, proto jsem k n\u011bmu p\u0159idal n\u011bkolik dal\u0161\u00edch spojen\u00ed. Tak odkud router v\u00ed, \u017ee data pro za\u0159\u00edzen\u00ed s IP adresou 30.1.1.10 je t\u0159eba poslat p\u0159es port F0\/1? Pro\u010d je nepos\u00edl\u00e1 p\u0159es port F0\/3 nebo F0\/2?<\/p>\n

Faktem je, \u017ee router pracuje s sm\u011brovac\u00ed tabulkou. Ka\u017ed\u00fd router m\u00e1 takovou tabulku, kter\u00e1 mu umo\u017e\u0148uje rozhodnout, p\u0159es kter\u00fd port m\u00e1 konkr\u00e9tn\u00ed r\u00e1mec p\u0159en\u00e1\u0161et. <\/p>\n

\"\u0160kolen\u00ed
\n
\nV tomto p\u0159\u00edpad\u011b je port F0\/0 nastaven na IP adresu 10.1.1.1, co\u017e znamen\u00e1, \u017ee je p\u0159ipojen k s\u00edti 10.1.1.10\/24. Podobn\u011b je port F0\/1 nastaven na adresu 20.1.1.1, tak\u017ee je p\u0159ipojen k s\u00edti 20.1.1.0\/24. Router zn\u00e1 ob\u011b tyto s\u00edt\u011b, proto\u017ee jsou p\u0159\u00edmo p\u0159ipojeny k jeho port\u016fm. Informace o tom, \u017ee provoz pro s\u00ed\u0165 10.1.10\/24 m\u00e1 prob\u00edhat p\u0159es port F0\/0 a pro s\u00ed\u0165 20.1.1.0\/24 \u2013 p\u0159es port F0\/1, je zn\u00e1m\u00e1 standardn\u011b. Odkud ale router v\u00ed, jak\u00e9 porty pou\u017e\u00edt pro ostatn\u00ed s\u00edt\u011b?<\/p>\n

Vid\u00edme, \u017ee s\u00ed\u0165 40.1.1.0\/24 je p\u0159ipojena k portu F0\/2, s\u00ed\u0165 50.1.1.0\/24 \u2013 k portu F0\/3, a s\u00ed\u0165 30.1.1.0\/24 spojuje druh\u00fd router se serverem. Druh\u00fd router m\u00e1 tak\u00e9 sm\u011brovac\u00ed tabulku, kter\u00e1 uv\u00e1d\u00ed, \u017ee s\u00ed\u0165 30. je p\u0159ipojena k jeho portu, ozna\u010dme ho 0\/1, a s prvn\u00edm routerem je spojen pomoc\u00ed portu 0\/0. Tento router v\u00ed, \u017ee jeho port 0\/0 je spojen se s\u00edt\u00ed 20., a port 0\/1 je spojen se s\u00edt\u00ed 30., a nic v\u00edc nev\u00ed.<\/p>\n

Podobn\u011b prvn\u00ed router zn\u00e1 s\u00edt\u011b 40. a 50., p\u0159ipojen\u00e9 k port\u016fm 0\/2 a 0\/3, ale nic nev\u00ed o s\u00edti 30. Sm\u011brovac\u00ed protokol poskytuje router\u016fm informace, kter\u00e9 nemaj\u00ed standardn\u011b. Mechanismus, pomoc\u00ed kter\u00e9ho si tyto routery vz\u00e1jemn\u011b p\u0159ed\u00e1vaj\u00ed informace, je z\u00e1kladem sm\u011brov\u00e1n\u00ed, p\u0159i\u010dem\u017e existuje dynamick\u00e9 a statick\u00e9 sm\u011brov\u00e1n\u00ed. <\/p>\n

Statick\u00e9 sm\u011brov\u00e1n\u00ed spo\u010d\u00edv\u00e1 v tom, \u017ee prvn\u00edmu routeru je d\u00e1na informace: pokud je pot\u0159eba nav\u00e1zat spojen\u00ed se s\u00edt\u00ed 30.1.1.0\/24, musej\u00ed se pou\u017e\u00edt porty F0\/1. Kdy\u017e v\u0161ak druh\u00e9mu routeru p\u0159ich\u00e1z\u00ed provoz ze serveru, kter\u00fd je ur\u010den pro po\u010d\u00edta\u010d 10.1.1.10, nev\u00ed, co s t\u00edm m\u00e1 d\u011blat, proto\u017ee v jeho sm\u011brovac\u00ed tabulce jsou pouze informace o s\u00edt\u00edch 30. a 20. Proto je t\u0159eba tomuto routeru tak\u00e9 zapsat statick\u00e9 sm\u011brov\u00e1n\u00ed: pokud p\u0159ijme provoz pro s\u00ed\u0165 10., mus\u00ed jej poslat p\u0159es port 0\/0. <\/p>\n

Probl\u00e9m statick\u00e9ho sm\u011brov\u00e1n\u00ed spo\u010d\u00edv\u00e1 v tom, \u017ee mus\u00edm ru\u010dn\u011b nastavit prvn\u00ed router pro pr\u00e1ci se s\u00edt\u00ed 30. a druh\u00fd router pro pr\u00e1ci se s\u00edt\u00ed 10. Je to jednoduch\u00e9, pokud m\u00e1m pouze 2 rout\u00e9ry, ale kdy\u017e m\u00e1m 10 router\u016f, nastaven\u00ed statick\u00e9ho sm\u011brov\u00e1n\u00ed zabere hromadu \u010dasu. V takov\u00e9m p\u0159\u00edpad\u011b m\u00e1 smysl pou\u017e\u00edt dynamick\u00e9 sm\u011brov\u00e1n\u00ed.
\nTak\u017ee pot\u00e9, co po\u010d\u00edta\u010d obdr\u017e\u00ed r\u00e1mec, prvn\u00ed router se pod\u00edv\u00e1 do sv\u00e9 sm\u011brovac\u00ed tabulky a rozhodne se jej odeslat p\u0159es port F0\/1. P\u0159i tom p\u0159id\u00e1v\u00e1 k r\u00e1mci MAC adresu zdroje XXXX.BBBB a MAC adresu c\u00edle XXXX.CCCC. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPo obdr\u017een\u00ed tohoto r\u00e1mce druh\u00fd router \"odstran\u00ed\" MAC adresy, kter\u00e9 se vztahuj\u00ed k druh\u00e9 vrstv\u011b OSI, a p\u0159ejde k informac\u00edm t\u0159et\u00ed vrstvy. Vid\u00ed, \u017ee IP adresa c\u00edle 30.1.1.10 pat\u0159\u00ed do t\u00e9\u017ee s\u00edt\u011b jako port 0\/1 routeru, p\u0159id\u00e1 k r\u00e1mci MAC adresu zdroje a MAC adresu c\u00edlov\u00e9ho za\u0159\u00edzen\u00ed a ode\u0161le r\u00e1mec serveru. <\/p>\n

\"\u0160kolen\u00ed
\n
\nJak jsem ji\u017e zm\u00ednil, d\u00e1le se stejn\u00fd proces opakuje v opa\u010dn\u00e9m sm\u011bru, tedy prob\u00edh\u00e1 druh\u00e1 f\u00e1ze handshake, kdy server pos\u00edl\u00e1 zp\u011bt SYN ACK zpr\u00e1vu. P\u0159ed t\u00edm odstran\u00ed ve\u0161ker\u00e9 zbyte\u010dn\u00e9 informace a ponech\u00e1 pouze SYN paket.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPo obdr\u017een\u00ed tohoto paketu druh\u00fd router zpracov\u00e1v\u00e1 obdr\u017een\u00ed informace, dopln\u00ed ji a ode\u0161le d\u00e1l. <\/p>\n

Tak\u017ee v p\u0159edchoz\u00edch lekc\u00edch jsme se nau\u010dili, jak funguj\u00ed switche, a nyn\u00ed jsme zjistili, jak funguj\u00ed routery. Poj\u010fme si odpov\u011bd\u011bt na ot\u00e1zku, co p\u0159edstavuje sm\u011brov\u00e1n\u00ed v glob\u00e1ln\u00edm smyslu. P\u0159edstavte si, \u017ee naraz\u00edte na takovou cestu, kter\u00e1 je um\u00edst\u011bna na k\u0159i\u017eovatce s okru\u017en\u00edmi j\u00edzdami. Vid\u00edte, \u017ee prvn\u00ed odbo\u010dka vede k z\u00e1kladn\u011b Kr\u00e1lovsk\u00e9ho letectva Fairfax, druh\u00e1 na leti\u0161t\u011b, t\u0159et\u00ed na jih. Pokud zvol\u00edte \u010dtvrt\u00fd v\u00fdjezd, dostanete se do slep\u00e9 uli\u010dky, a p\u0159es p\u00e1t\u00fd m\u016f\u017eete projet st\u0159edem m\u011bsta k hradu Braxby. <\/p>\n

\"\u0160kolen\u00ed
\n
\nObecn\u011b plat\u00ed, \u017ee sm\u011brov\u00e1n\u00ed je to, co nut\u00ed router p\u0159ij\u00edmat rozhodnut\u00ed o tom, kam sm\u011brovat provoz. V tomto p\u0159\u00edpad\u011b byste, jako \u0159idi\u010d, m\u011bli u\u010dinit rozhodnut\u00ed, jakou v\u00fdjezd z k\u0159i\u017eovatky vyu\u017e\u00edt. V s\u00edt\u00edch mus\u00ed routery \u010dinit rozhodnut\u00ed, kam pos\u00edlat pakety nebo r\u00e1mce. Mus\u00edte pochopit, \u017ee sm\u011brov\u00e1n\u00ed umo\u017e\u0148uje vytv\u00e1\u0159et tabulky, na jejich\u017e z\u00e1klad\u011b routery p\u0159ij\u00edmaj\u00ed tato rozhodnut\u00ed. <\/p>\n

Jak jsem \u0159ekl, existuje statick\u00e9 a dynamick\u00e9 sm\u011brov\u00e1n\u00ed. Poj\u010fme prozkoumat statick\u00e9 sm\u011brov\u00e1n\u00ed, k tomu nakresl\u00edm 3 za\u0159\u00edzen\u00ed, kter\u00e1 jsou navz\u00e1jem propojena, p\u0159i\u010dem\u017e prvn\u00ed a t\u0159et\u00ed za\u0159\u00edzen\u00ed jsou p\u0159ipojena k s\u00edt\u00edm. P\u0159edstavte si, \u017ee jedna s\u00ed\u0165 10.1.1.0 chce komunikovat se s\u00edt\u00ed 40.1.1.0, a mezi routery se nach\u00e1zej\u00ed s\u00edt\u011b 20.1.1.0 a 30.1.1.0.<\/p>\n

\"\u0160kolen\u00ed
\n
\nV tomto p\u0159\u00edpad\u011b mus\u00ed b\u00fdt porty router\u016f p\u0159i\u0159azeny k r\u016fzn\u00fdm pods\u00edt\u00edm. Router 1 ve v\u00fdchoz\u00edm stavu zn\u00e1 pouze s\u00edt\u011b 10. a 20. a nic nev\u00ed o ostatn\u00edch s\u00edt\u00edch. Router 2 zn\u00e1 pouze s\u00edt\u011b 20. a 30., proto\u017ee jsou k n\u011bmu p\u0159ipojeny, a router 3 zn\u00e1 jen s\u00edt\u011b 30. a 40. Pokud chce s\u00ed\u0165 10. komunikovat se s\u00edt\u00ed 40., mus\u00edm routeru 1 sd\u011blit informace o s\u00edti 30. a \u017ee pokud chce p\u0159en\u00e9st r\u00e1mec ze s\u00edt\u011b 40., m\u011bl by pou\u017e\u00edt rozhran\u00ed pro s\u00ed\u0165 20. a poslat r\u00e1mec p\u0159es tuto s\u00ed\u0165 20.<\/p>\n

Druh\u00e9mu routeru mus\u00edm p\u0159i\u0159adit 2 trasy: pokud chce odeslat paket ze s\u00edt\u011b 40. do s\u00edt\u011b 10., mus\u00ed pou\u017e\u00edt port s\u00edt\u011b 20., a pro odesl\u00e1n\u00ed paketu ze s\u00edt\u011b 10. do s\u00edt\u011b 40. \u2013 port s\u00edt\u011b 30. Podobn\u011b mus\u00edm informovat router 3 o s\u00edt\u00edch 10. a 20.<\/p>\n

Pokud m\u00e1te mal\u00e9 s\u00edt\u011b, je statickou routov\u00e1n\u00ed snadn\u00e9 nastavit. \u010c\u00edm v\u011bt\u0161\u00ed v\u0161ak s\u00ed\u0165 roste, t\u00edm v\u00edce probl\u00e9m\u016f se statickou routov\u00e1n\u00edm vznik\u00e1. P\u0159edstavte si, \u017ee jste vytvo\u0159ili nov\u00e9 p\u0159ipojen\u00ed, kter\u00e9 p\u0159\u00edmo spojuje prvn\u00ed a t\u0159et\u00ed router. V takov\u00e9m p\u0159\u00edpad\u011b protokol dynamick\u00e9 routov\u00e1n\u00ed automaticky aktualizuje routovac\u00ed tabulku routeru 1, \u0159\u00edkaj\u00edc\u00ed: \u201ePokud chcete komunikovat s routerem 3, pou\u017eijte p\u0159\u00edmou trasu\u201c!<\/p>\n

\"\u0160kolen\u00ed
\n
\nExistuj\u00ed dva typy routovac\u00edch protokol\u016f: protokol vnit\u0159n\u00edho br\u00e1ny IGP a protokol vn\u011bj\u0161\u00ed br\u00e1ny EGP. Prvn\u00ed protokol pracuje s odd\u011blen\u00fdm, autonomn\u00edm syst\u00e9mem, zn\u00e1m\u00fdm jako dom\u00e9na routov\u00e1n\u00ed. P\u0159edstavte si, \u017ee m\u00e1te malou organizaci, ve kter\u00e9 je pouze 5 router\u016f. Pokud hovo\u0159\u00edme pouze o komunikaci mezi t\u011bmito routery, znamen\u00e1 to IGP; pokud v\u0161ak pou\u017e\u00edv\u00e1te svou s\u00ed\u0165 pro p\u0159ipojen\u00ed k internetu, jako to d\u011blaj\u00ed ISP poskytovatel\u00e9, pou\u017e\u00edv\u00e1te EGP. <\/p>\n

\"\u0160kolen\u00ed
\n
\nIGP pou\u017e\u00edv\u00e1 3 popul\u00e1rn\u00ed protokoly: RIP, OSPF a EIGRP. V u\u010debn\u00edm pl\u00e1nu CCNA se zmi\u0148uj\u00ed pouze o dvou posledn\u00edch protokolech, proto\u017ee RIP je zastaral\u00fd. Je to nejjednodu\u0161\u0161\u00ed z routovac\u00edch protokol\u016f, kter\u00fd se st\u00e1le pou\u017e\u00edv\u00e1 v n\u011bkter\u00fdch p\u0159\u00edpadech, ale nezaji\u0161\u0165uje pot\u0159ebnou s\u00ed\u0165ovou bezpe\u010dnost. To je jeden z d\u016fvod\u016f, pro\u010d Cisco vylou\u010dilo RIP z u\u010debn\u00edho pl\u00e1nu. P\u0159esto v\u00e1m o n\u011bm r\u00e1da pov\u00edm, proto\u017ee jeho studium pom\u00e1h\u00e1 k pochopen\u00ed z\u00e1klad\u016f routov\u00e1n\u00ed. <\/p>\n

\"\u0160kolen\u00ed
\n
\nKlasifikace protokol\u016f EGP vyu\u017e\u00edv\u00e1 dva protokoly: BGP a samotn\u00fd protokol EGP. V r\u00e1mci kurzu CCNA budeme zva\u017eovat pouze BGP, OSPF a EIGRP. Informace o RIP m\u016f\u017eete pova\u017eovat za bonus, kter\u00e1 bude zm\u00edn\u011bna v jednom z videon\u00e1vod\u016f.
\nExistuj\u00ed tak\u00e9 dal\u0161\u00ed dva typy protokol\u016f routov\u00e1n\u00ed: protokoly vzd\u00e1lenostn\u00edho vektoru Distance Vector a protokoly routov\u00e1n\u00ed stavu spojen\u00ed Link State. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPrvn\u00ed protokol se zam\u011b\u0159uje na vektory vzd\u00e1lenosti a sm\u011bru. Nap\u0159\u00edklad mohu nav\u00e1zat p\u0159ipojen\u00ed p\u0159\u00edmo mezi routerem R1 a R4 nebo m\u016f\u017eu zrealizovat p\u0159ipojen\u00ed p\u0159es cestu R1-R2-R3-R4. Pokud mluv\u00edme o protokolech routov\u00e1n\u00ed, kter\u00e9 pou\u017e\u00edvaj\u00ed metodu vzd\u00e1lenostn\u00edho vektoru, pak bude p\u0159ipojen\u00ed v\u017edy realizov\u00e1no po nejkrat\u0161\u00ed cest\u011b. P\u0159i tom nez\u00e1le\u017e\u00ed na tom, \u017ee toto p\u0159ipojen\u00ed bude m\u00edt minim\u00e1ln\u00ed rychlost. V na\u0161em p\u0159\u00edpad\u011b je to 128 kbit\/s, co\u017e je mnohem pomalej\u0161\u00ed ne\u017e p\u0159ipojen\u00ed po trase R1-R2-R3-R4, kde rychlost \u010din\u00ed 100 Mbit\/s. <\/p>\n

Pod\u00edvejme se na protokol vzd\u00e1lenostn\u00edho vektoru RIP. P\u0159id\u00e1m p\u0159ed router R1 s\u00ed\u0165 10. a za routerem R4 \u2013 s\u00ed\u0165 40. P\u0159edpokl\u00e1dejme, \u017ee v t\u011bchto s\u00edt\u00edch je mnoho po\u010d\u00edta\u010d\u016f. Pokud chci nav\u00e1zat spojen\u00ed mezi s\u00edt\u00ed 10. R1 a s\u00edt\u00ed 40. R4, nastav\u00edm R1 statickou routu typu: \u201epokud se pot\u0159ebujete spojit se s\u00edt\u00ed 40., pou\u017eijte p\u0159\u00edm\u00e9 spojen\u00ed s routerem R4\u201c. Na v\u0161ech \u010dty\u0159ech routrech mus\u00edm tak\u00e9 ru\u010dn\u011b nastavit RIP. Pot\u00e9 tabulka routov\u00e1n\u00ed R1 automaticky ozna\u010d\u00ed, \u017ee pokud s\u00ed\u0165 10. chce komunikovat se s\u00edt\u00ed 40., je t\u0159eba pou\u017e\u00edt p\u0159\u00edm\u00e9 spojen\u00ed R1-R4. I kdy\u017e by alternativn\u00ed cesta mohla b\u00fdt rychlej\u0161\u00ed, protokol Distance Vector i tak zvol\u00ed nejkrat\u0161\u00ed cestu s nejmen\u0161\u00ed vzd\u00e1lenost\u00ed p\u0159enosu. <\/p>\n

OSPF je protokol routov\u00e1n\u00ed stavu spojen\u00ed, kter\u00fd v\u017edy sleduje stav jednotliv\u00fdch \u010d\u00e1st\u00ed s\u00edt\u011b. V tomto p\u0159\u00edpad\u011b hodnot\u00ed rychlost kan\u00e1l\u016f a pokud zjist\u00ed, \u017ee rychlost p\u0159enosu dat po kan\u00e1lu R1-R4 je velmi n\u00edzk\u00e1, vybere cestu s vy\u0161\u0161\u00ed rychlost\u00ed R1-R2-R3-R4, i kdy\u017e je d\u00e9lka del\u0161\u00ed ne\u017e nejkrat\u0161\u00ed cesta. Tak\u017ee pokud nastav\u00edm protokol OSPF na v\u0161ech routerech, p\u0159i pokusu o spojen\u00ed s\u00edt\u011b 40. se s\u00edt\u00ed 10. bude provoz odesl\u00e1n po trase R1-R2-R3-R4. Tak\u017ee RIP je protokol vzd\u00e1lenostn\u00edho vektoru, zat\u00edmco OSPF je protokol routov\u00e1n\u00ed stavu spojen\u00ed.<\/p>\n

Existuje je\u0161t\u011b jeden protokol \u2013 EIGRP, propriet\u00e1rn\u00ed routovac\u00ed protokol Cisco. Pokud hovo\u0159\u00edme o s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00edch jin\u00fdch v\u00fdrobc\u016f, nap\u0159\u00edklad Juniper, EIGRP nen\u00ed podporov\u00e1n. Je to vynikaj\u00edc\u00ed routovac\u00ed protokol, kter\u00fd je mnohem efektivn\u011bj\u0161\u00ed ne\u017e RIP a OSPF, ale lze jej pou\u017e\u00edvat pouze v s\u00edt\u00edch zalo\u017een\u00fdch na za\u0159\u00edzen\u00edch v\u00fdroby Cisco. Pozd\u011bji v\u00e1m podrobn\u011bji vysv\u011btl\u00edm, \u010d\u00edm je tento protokol tak dobr\u00fd. Prozat\u00edm poznamen\u00e1m, \u017ee EIGRP kombinuje rysy vzd\u00e1len\u011b-vektorov\u00fdch protokol\u016f a protokol\u016f routov\u00e1n\u00ed stavu odkazu, co\u017e z n\u011bj \u010din\u00ed hybridn\u00ed protokol. <\/p>\n

V n\u00e1sleduj\u00edc\u00edm videoz\u00e1znamu se podrobn\u011b pod\u00edv\u00e1me na routery Cisco, trochu v\u00e1m pov\u00edm o opera\u010dn\u00edm syst\u00e9mu Cisco IOS, kter\u00fd je ur\u010den jak pro switche, tak pro routery. Douf\u00e1m, \u017ee v hodin\u00e1ch 19 nebo 20 za\u010dneme podrobn\u011b studovat routovac\u00ed protokoly, a na p\u0159\u00edkladu mal\u00fdch s\u00edt\u00ed uk\u00e1\u017eu, jak konfigurovat routery Cisco.<\/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\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443. \u041a\u0430\u043a \u0432\u044b \u0437\u043d\u0430\u0435\u0442\u0435 \u0438\u0437 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0433\u043e \u0432\u0438\u0434\u0435\u0443\u0440\u043e\u043a\u0430, \u043e\u0434\u043d\u0430 \u0438\u0437 \u0442\u0435\u043c \u043a\u0443\u0440\u0441\u0430 CCNA \u0442\u0430\u043a \u0438 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u2013 Cisco Switching & Routing. \u0412 \u044d\u0442\u043e\u0439 \u0441\u0435\u0440\u0438\u0438 \u043c\u044b \u043d\u0435 \u0441\u0442\u0430\u043d\u0435\u043c \u0438\u0437\u0443\u0447\u0430\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27956,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37271","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\udd47Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 18. Z\u00e1klady routov\u00e1n\u00ed | ProHoster","description":"Dnes za\u010dneme studovat routery. Pokud jste pro\u0161li m\u00fdm videokurzem od prvn\u00edho do 17. lekce, ji\u017e m\u00e1te z\u00e1klady switch\u016f. Nyn\u00ed p\u0159ech\u00e1z\u00edme k dal\u0161\u00edmu za\u0159\u00edzen\u00ed \u2013 routeru.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","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 18. \u041e\u0441\u043d\u043e\u0432\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","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:41+00:00","article:modified_time":"2019-10-31T19:16:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37271","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:03:35","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:30:00","updated":"2026-01-23 17:03:35","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\/37271","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=37271"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37271\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/27956"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}