{"id":37723,"date":"2019-10-31T22:19:20","date_gmt":"2019-10-31T19:19:20","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-29-pat-i-nat\/"},"modified":"2019-10-31T22:19:20","modified_gmt":"2019-10-31T19:19:20","slug":"trening-cisco-200-125-ccna-v3-0-den-29-pat-i-nat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-29-pat-i-nat","title":{"rendered":"Tr\u00e9ning Cisco 200-125 CCNA v3.0. De\u0148 29. PAT a NAT","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes sa budeme zaobera\u0165 PAT (Port Address Translation), technol\u00f3giou prekladu IP adries s pou\u017eit\u00edm portov, a NAT (Network Address Translation), technol\u00f3giou premeny IP adries transitn\u00fdch paketov. PAT je osobitn\u00fdm pr\u00edpadom NAT. Venujeme sa trom t\u00e9mam: <\/p>\n

\u2014 s\u00fakromn\u00e9 alebo vn\u00fatorn\u00e9 (lok\u00e1lne) IP adresy a verejn\u00e9 alebo vonkaj\u0161ie IP adresy;
\n \u2014 NAT a PAT;
\n \u2014 nastavenie NAT\/PAT.<\/p>\n

Za\u010dneme s vn\u00fatorn\u00fdmi adresami Private IP. Vieme, \u017ee s\u00fa rozdelen\u00e9 do troch tried: A, B a C. <\/p>\n

\"Tr\u00e9ning
\n
\nVn\u00fatorn\u00e9 adresy triedy A sa nach\u00e1dzaj\u00fa v rozsahu \u201edesa\u0165\u201c od 10.0.0.0 do 10.255.255.255, zatia\u013e \u010do vonkaj\u0161ie v rozsahu od 1.0.0.0 do 9.255.255.255 a od 11.0.0.0 do 126.255.255.255. <\/p>\n

Vn\u00fatorn\u00e9 adresy triedy B sa nach\u00e1dzaj\u00fa v rozsahu od 172.16.0.0 do 172.31.255.255, zatia\u013e \u010do vonkaj\u0161ie od 128.0.0.0 do 172.15.255.255 a od 172.32.0.0 do 191.255.255.255.<\/a><\/noindex><\/p>\n

Vn\u00fatorn\u00e9 adresy triedy C sa nach\u00e1dzaj\u00fa v rozsahu od 192.168.0.0 do 192.168.255.255, zatia\u013e \u010do vonkaj\u0161ie od 192.0.0 do 192.167.255.255 a od 192.169.0.0 do 223.255.255.255.<\/p>\n

\"Tr\u00e9ning
\n
\nAdresy triedy A s\u00fa adresy \/8, triedy B \u2014 \/12 a triedy C \u2014 \/16. Tak\u017ee vonkaj\u0161ie a vn\u00fatorn\u00e9 IP adresy r\u00f4znych tried zaberaj\u00fa r\u00f4zne rozsahy. <\/p>\n

Viackr\u00e1t sme sa zaoberali, v \u010dom spo\u010d\u00edva rozdiel medzi s\u00fakromn\u00fdmi a verejn\u00fdmi IP adresami. V skratke, ak m\u00e1me router a skupinu vn\u00fatorn\u00fdch IP adries, pri pokuse o ich pripojenie na internet router konvertuje ich na vonkaj\u0161ie IP adresy. Vn\u00fatorn\u00e9 adresy sa pou\u017e\u00edvaj\u00fa iba v miestnych sie\u0165ach, nie na internete. <\/p>\n

Ak si cez pr\u00edkazov\u00fd riadok pozriem sie\u0165ov\u00e9 parametre svojho po\u010d\u00edta\u010da, uvid\u00edm tam svoju vn\u00fatorn\u00fa LAN IP adresu 192.168.1.103.<\/p>\n

\"Tr\u00e9ning
\n
\nAk chcete zisti\u0165 svoju verejn\u00fa IP adresu, m\u00f4\u017eete vyu\u017ei\u0165 internetov\u00fd servis typu \u201eAk\u00fa m\u00e1m IP?\u201c Ako vid\u00edte, vonkaj\u0161ia adresa po\u010d\u00edta\u010da 78.100.196.163 sa l\u00ed\u0161i od jeho vn\u00fatornej adresy. <\/p>\n

\"Tr\u00e9ning
\n
\nV v\u0161etk\u00fdch pr\u00edpadoch je m\u00f4j po\u010d\u00edta\u010d na internete vidite\u013en\u00fd pr\u00e1ve pod vonkaj\u0161ou IP adresou. Tak\u017ee, vn\u00fatorn\u00e1 adresa m\u00f4jho po\u010d\u00edta\u010da je 192.168.1.103, zatia\u013e \u010do vonkaj\u0161ia je 78.100.196.163. Vn\u00fatorn\u00e1 adresa sa pou\u017e\u00edva iba na lok\u00e1lnu komunik\u00e1ciu, na pripojenie na internet potrebujete verejn\u00fa IP adresu. M\u00f4\u017eete si pripomen\u00fa\u0165, pre\u010do bola vykonan\u00e1 separ\u00e1cia na s\u00fakromn\u00e9 a verejn\u00e9 adresy, t\u00fdm, \u017ee si prehliadnete video lekciu De\u0148 3. <\/p>\n

Pozrime sa, \u010do je to NAT. Existuj\u00fa tri typy NAT: statick\u00fd, dynamick\u00fd a \u201epre\u0165a\u017een\u00fd\u201c NAT, alebo PAT.<\/p>\n

\"Tr\u00e9ning
\n
\nV spolo\u010dnosti Cisco existuj\u00fa 4 term\u00edny popisuj\u00face NAT. Ako som povedal, NAT je mechanizmus, ktor\u00fd prev\u00e1dza intern\u00e9 adresy na vonkaj\u0161ie. Ak sa zariadenie pripojen\u00e9 k internetu dostane k paketu z in\u00e9ho zariadenia v miestnej sieti, jednoducho ho odmietne, preto\u017ee form\u00e1t internej adresy nezodpoved\u00e1 form\u00e1tu adries pou\u017e\u00edvan\u00fdch v glob\u00e1lnej sieti internetu. Preto mus\u00ed zariadenie z\u00edska\u0165 verejn\u00fa IP adresu na pr\u00edstup do internetu.
\nPrv\u00fd term\u00edn je Inside Local, \u010do znamen\u00e1 IP adresu hostite\u013ea v internej, lok\u00e1lnej sieti. Jednoduch\u0161ie povedan\u00e9, je to prim\u00e1rna adresa zdroja typu 192.168.1.10. Druh\u00fd term\u00edn, Inside Global, je IP adresa lok\u00e1lneho hostite\u013ea, pod ktorou je vidite\u013en\u00fd vo vonkaj\u0161ej sieti. V na\u0161om pr\u00edpade je to IP adresa vonkaj\u0161ieho portu smerova\u010da 200.124.22.10.<\/p>\n

\"Tr\u00e9ning
\n
\nM\u00f4\u017eeme poveda\u0165, \u017ee Inside Local je s\u00fakromn\u00e1 IP adresa, zatia\u013e \u010do Inside Global je verejn\u00e1 IP adresa. Pam\u00e4tajte, \u017ee term\u00edn Inside sa pou\u017e\u00edva v s\u00favislosti so zdrojom prev\u00e1dzky, zatia\u013e \u010do Outside sa vz\u0165ahuje na cie\u013e prev\u00e1dzky. Outside Local je IP adresa hostite\u013ea vo vonkaj\u0161ej sieti, pod ktorou je vidite\u013en\u00fd pre vn\u00fatorn\u00fa sie\u0165. Jednoduch\u0161ie povedan\u00e9, je to adresa pr\u00edjemcu, vidite\u013en\u00e1 z internej siete. Pr\u00edklad takejto adresy je IP adresa 200.124.22.100 zariadenia nach\u00e1dzaj\u00faceho sa na internete. <\/p>\n

\"Tr\u00e9ning
\n
\nOutside Global je IP adresa hostite\u013ea, ktor\u00e1 je vidite\u013en\u00e1 vo vonkaj\u0161ej sieti. V v\u00e4\u010d\u0161ine pr\u00edpadov sa adresy Outside Local a Outside Global javia identicky, preto\u017ee aj po prevode je IP adresa ur\u010denia pre zdroj vidite\u013en\u00e1 tak\u00e1 ist\u00e1 ako pred prevodom. <\/p>\n

\"Tr\u00e9ning
\n
\nPozrime sa, \u010do predstavuje statick\u00fd NAT. Statick\u00fd NAT znamen\u00e1 vz\u00e1jomn\u00e9 jednozna\u010dn\u00e9 premenovanie intern\u00fdch IP adries na vonkaj\u0161ie, alebo premenovanie \u201ejeden na jedn\u00e9ho\u201c. Ke\u010f zariadenia posielaj\u00fa prev\u00e1dzku do internetu, ich intern\u00e9 adresy Inside Local sa prev\u00e1dzaj\u00fa na intern\u00e9 adresy Inside Global.<\/p>\n

\"Tr\u00e9ning
\n
\nV na\u0161ej miestnej sieti s\u00fa 3 zariadenia a ke\u010f sa chystaj\u00fa vyrazi\u0165 do internetu, ka\u017ed\u00e9 z nich dostane svoju vlastn\u00fa adresu Inside Global. Tieto adresy s\u00fa staticky priraden\u00e9 k zdrojom prev\u00e1dzky. Princ\u00edp \u201ejeden na jedn\u00e9ho\u201c znamen\u00e1, \u017ee ak je v miestnej sieti 100 zariaden\u00ed, dostan\u00fa 100 vonkaj\u0161\u00edch adries. <\/p>\n

NAT vznikol na to, aby zachr\u00e1nil internet, v ktorom doch\u00e1dzalo k vy\u010derpaniu verejn\u00fdch IP adries. V\u010faka NAT m\u00f4\u017ee mno\u017estvo spolo\u010dnost\u00ed a mno\u017estvo siet\u00ed ma\u0165 jednu spolo\u010dn\u00fa vonkaj\u0161iu IP adresu, na ktor\u00fa sa lok\u00e1lne adresy zariaden\u00ed prev\u00e1dzaj\u00fa pri pripojen\u00ed na internet. M\u00f4\u017eete poveda\u0165, \u017ee v tomto pr\u00edpade statick\u00fd NAT \u017eiadnym sp\u00f4sobom ne\u0161etr\u00ed po\u010det adries, preto\u017ee sto lok\u00e1lnym po\u010d\u00edta\u010dom je pridelen\u00fdch sto vonkaj\u0161\u00edch adries, a budete \u00faplne pravdiv\u00fd. Napriek tomu m\u00e1 statick\u00fd NAT st\u00e1le nieko\u013eko v\u00fdhod.<\/p>\n

Napr\u00edklad m\u00e1me server s vn\u00fatornou IP adresou 192.168.1.100. Ak by sa nejak\u00e9 zariadenie z internetu chcelo s n\u00edm spoji\u0165, nebude to m\u00f4c\u0165 urobi\u0165 pomocou vn\u00fatornej adresy, na to potrebuje vyu\u017ei\u0165 vonkaj\u0161iu adresu servera 200.124.22.3. Ak je na smerova\u010di nastaven\u00fd statick\u00fd NAT, cel\u00fd prenos adresovan\u00fd 200.124.22.3 sa automaticky presmeruje na 192.168.1.100. Takto je zabezpe\u010den\u00fd vonkaj\u0161\u00ed pr\u00edstup k zariadeniam lok\u00e1lnej siete, v tomto pr\u00edpade k webov\u00e9mu serveru spolo\u010dnosti, \u010do m\u00f4\u017ee by\u0165 v ur\u010dit\u00fdch pr\u00edpadoch potrebn\u00e9. <\/p>\n

Pozrime sa na dynamick\u00fd NAT. Je ve\u013emi podobn\u00fd statick\u00e9mu, ale nepridel\u00ed trval\u00e9 vonkaj\u0161ie adresy ka\u017ed\u00e9mu lok\u00e1lnemu zariadeniu. Napr\u00edklad m\u00e1me 3 lok\u00e1lne zariadenia a iba 2 vonkaj\u0161ie adresy. Ak druh\u00e9 zariadenie chce \u00eds\u0165 na internet, bude mu pridelen\u00e1 prv\u00e1 vo\u013en\u00e1 IP adresa. Ak po \u0148om chce \u00eds\u0165 na internet webov\u00fd server, smerova\u010d mu pridel\u00ed druh\u00fa dostupn\u00fa vonkaj\u0161iu adresu. Ak sa po tom pok\u00fasi o vonkaj\u0161\u00ed pr\u00edstup prv\u00e9 zariadenie, nebude dostupn\u00e1 \u017eiadna IP adresa a smerova\u010d jeho paket zahod\u00ed. <\/p>\n

\"Tr\u00e9ning
\n
\nM\u00f4\u017eeme ma\u0165 stovku zariaden\u00ed s vn\u00fatorn\u00fdmi IP adresami a ka\u017ed\u00e9 z t\u00fdchto zariaden\u00ed m\u00f4\u017ee \u00eds\u0165 na internet. Ale preto\u017ee nem\u00e1me statick\u00e9 priradenie vonkaj\u0161\u00edch adries, m\u00f4\u017eu naraz \u00eds\u0165 na internet maxim\u00e1lne 2 zariadenia zo stovky, preto\u017ee m\u00e1me len dve dynamicky pridelovan\u00e9 vonkaj\u0161ie adresy. <\/p>\n

V zariadeniach Cisco je stanoven\u00fd pevn\u00fd \u010das na prevod adries, ktor\u00fd je predvolene nastaven\u00fd na 24 hod\u00edn. Tento \u010das m\u00f4\u017eete zmeni\u0165 na 1, 2, 3, 10 min\u00fat alebo na ak\u00fdko\u013evek \u010das, ktor\u00fd v\u00e1m vyhovuje. Po uplynut\u00ed tejto doby sa vonkaj\u0161ie adresy uvo\u013enia a automaticky sa vr\u00e1tia do adresov\u00e9ho poolu. Ak v tomto momente prv\u00e9 zariadenie chce \u00eds\u0165 na internet a nejak\u00e1 vonkaj\u0161ia adresa je dostupn\u00e1, z\u00edska ju. Router obsahuje NAT tabu\u013eku, ktor\u00e1 sa dynamicky aktualizuje, a pokia\u013e \u010das prevodu nevypr\u0161al, pridelen\u00e1 adresa ost\u00e1va pri zariaden\u00ed. Jednoducho povedan\u00e9, dynamick\u00fd NAT funguje na princ\u00edpe: \u201ekto pri\u0161iel prv\u00fd, toho obsl\u00fa\u017eili.\u201c <\/p>\n

Pozrime sa, \u010do predstavuje pre\u0165a\u017een\u00fd NAT, alebo PAT. Toto je najbe\u017enej\u0161\u00ed typ NAT. Vo va\u0161ej dom\u00e1cej sieti m\u00f4\u017ee by\u0165 mno\u017estvo zariaden\u00ed \u2013 PC, smartf\u00f3n, notebook, tablet, a v\u0161etky sa prip\u00e1jaj\u00fa k routeru, ktor\u00fd m\u00e1 jednu vonkaj\u0161iu IP adresu. PAT umo\u017e\u0148uje mnoh\u00fdm zariadeniam s vn\u00fatorn\u00fdmi IP adresami s\u00fa\u010dasne sa pripoji\u0165 na internet pod jednou vonkaj\u0161ou IP adresou. Je to mo\u017en\u00e9 v\u010faka tomu, \u017ee ka\u017ed\u00e1 s\u00fakromn\u00e1, vn\u00fatorn\u00e1 IP adresa pou\u017e\u00edva po\u010das komunik\u00e1cie ur\u010dit\u00fd \u010d\u00edslo portu.
\nPredpokladajme, \u017ee m\u00e1me jednu verejn\u00fa adresu 200.124.22.1 a mno\u017estvo miestnych zariaden\u00ed. Pri pripojen\u00ed na internet bud\u00fa v\u0161etky tieto hosty z\u00edska\u0165 rovnak\u00fa adresu 200.124.22.1. Jedin\u00e9, \u010do ich odl\u00ed\u0161i, je \u010d\u00edslo portu.
\nAk si pam\u00e4t\u00e1te diskusiu o transportnej \u00farovni, viete, \u017ee transportn\u00e1 \u00farove\u0148 obsahuje \u010d\u00edsla portov, pri\u010dom \u010d\u00edslo portu zdroja je n\u00e1hodn\u00e9 \u010d\u00edslo. <\/p>\n

\"Tr\u00e9ning
\n
\nPredpokladajme, \u017ee vo vonkaj\u0161ej sieti je hostite\u013e s IP adresou 200.124.22.10, ktor\u00fd je pripojen\u00fd na internet. Ak sa po\u010d\u00edta\u010d 192.168.1.11 chce skontaktova\u0165 s po\u010d\u00edta\u010dom 200.124.22.10, vytvor\u00ed n\u00e1hodn\u00fd port zdroja 51772. Port ur\u010denia po\u010d\u00edta\u010da vo vonkaj\u0161ej sieti bude 80. <\/p>\n

Ke\u010f router prijme paket z lok\u00e1lneho po\u010d\u00edta\u010da, ktor\u00fd je smerovan\u00fd do vonkaj\u0161ej siete, prekl\u00e1da jeho lok\u00e1lnu adresu Inside Local na adresu Inside Global 200.124.22.1 a pridel\u00ed portu \u010d\u00edslo 23556. Paket dosiahne po\u010d\u00edta\u010d 200.124.22.10, ktor\u00fd bude musie\u0165 posla\u0165 sp\u00e4\u0165 odpove\u010f pod\u013ea proced\u00fary handshake, pri\u010dom adresou ur\u010denia bude 200.124.22.1 a port 23556. <\/p>\n

Router m\u00e1 NAT prekladov\u00fa tabu\u013eku, a tak po prijat\u00ed paketu z vonkaj\u0161ieho po\u010d\u00edta\u010da ur\u010d\u00ed Inside Local adresu zodpovedaj\u00facu Inside Global adrese 192.168.1.11: 51772 a po\u0161le mu paket. Po tomto sa spojenie medzi dvoma po\u010d\u00edta\u010dmi m\u00f4\u017ee pova\u017eova\u0165 za nadviazan\u00e9.
\nZ\u00e1rove\u0148 m\u00f4\u017eete ma\u0165 stovku zariaden\u00ed, ktor\u00e9 pou\u017e\u00edvaj\u00fa na komunik\u00e1ciu rovnak\u00fa adresu 200.124.22.1, ale s r\u00f4znymi \u010d\u00edslami portov, v\u010faka \u010domu m\u00f4\u017eu v\u0161etky s\u00fa\u010dasne vyjs\u0165 na internet. Preto je PAT tak popul\u00e1rnym sp\u00f4sobom prekladu.<\/p>\n

Pozrime sa na nastavenie statick\u00e9ho NAT. Pre ka\u017ed\u00fa sie\u0165 je najprv potrebn\u00e9 ur\u010di\u0165 vstupn\u00e9 a v\u00fdstupn\u00e9 rozhrania. Na sch\u00e9me je zobrazen\u00fd router, cez ktor\u00fd sa pren\u00e1\u0161a trafik z portu G0\/0 na port G0\/1, teda z vn\u00fatornej siete do vonkaj\u0161ej siete. Tak\u017ee m\u00e1me vstupn\u00e9 rozhranie 192.168.1.1 a v\u00fdstupn\u00e9 rozhranie 200.124.22.1. <\/p>\n

\"Tr\u00e9ning
\n
\nPre nastavenie NAT prech\u00e1dzame na rozhranie G0\/0 a zad\u00e1me parametre ip addres 192.168.1.1 255.255.255.0 a ozna\u010d\u00edme, \u017ee toto rozhranie je vstupn\u00e9 pomocou pr\u00edkazu ip nat inside. <\/p>\n

\"Tr\u00e9ning
\n
\nPodobn\u00fdm sp\u00f4sobom nastav\u00edme NAT na v\u00fdstupnom rozhran\u00ed G0\/1, uveden\u00edm ip address 200.124.22.1, masky podsiete 255.255.255.0 a ip nat outside. Pam\u00e4tajte si, \u017ee konverzia dynamick\u00e9ho NAT sa v\u017edy uskuto\u010d\u0148uje od vstupn\u00e9ho k v\u00fdstupn\u00e9mu rozhraniu, teda od inside k outside. Samozrejme, \u017ee pri dynamickom NAT odpove\u010f prich\u00e1dza na vstupn\u00e9 rozhranie cez v\u00fdstupn\u00e9, ale pri inici\u00e1cii trafiku funguje pr\u00e1ve smer in-out. Pri statickom NAT m\u00f4\u017ee inici\u00e1cia trafiku prebieha\u0165 v akomko\u013evek smere \u2013 in-out alebo out-in. <\/p>\n

\u010ealej potrebujeme zostavi\u0165 tabu\u013eku statick\u00e9ho NAT, kde ka\u017ed\u00e9mu lok\u00e1lnemu adresu zodpoved\u00e1 samostatn\u00e1 glob\u00e1lna adresa. V na\u0161om pr\u00edpade m\u00e1me 3 zariadenia, preto tabu\u013eka bude pozost\u00e1va\u0165 z 3 z\u00e1znamov, v ktor\u00fdch sa uv\u00e1dza Inside Local IP-adresa zdroja, ktor\u00fd sa preklad\u00e1 na Inside Global adresu: ip nat inside static 192.168.1.10 200.124.22.1.
\nTak\u017ee v statickom NAT ru\u010dne zad\u00e1vate preklad pre ka\u017ed\u00fa adresu lok\u00e1lneho hosta. Teraz prech\u00e1dzam k Packet Tracer a vykon\u00e1m vy\u0161\u0161ie uveden\u00e9 nastavenia. <\/p>\n

\"Tr\u00e9ning
\n
\nNa vrchu m\u00e1me server 192.168.1.100, ni\u017e\u0161ie sa nach\u00e1dza po\u010d\u00edta\u010d 192.168.1.10 a \u00faplne dole je po\u010d\u00edta\u010d 192.168.1.11. Port G0\/0 smerova\u010da Router0 m\u00e1 IP adresu 192.168.1.1, zatia\u013e \u010do port G0\/1 - 200.124.22.1. V 'oblaku', zobrazuj\u00facom internet, som umiestnil Router1, ktor\u00e9mu som priradil IP adresu 200.124.22.10.<\/p>\n

Vstupujem do nastaven\u00ed Router1 a zad\u00e1m pr\u00edkaz debug ip icmp. Teraz, ke\u010f ping dosiahne toto zariadenie, v okne nastaven\u00ed sa objav\u00ed spr\u00e1va o laden\u00ed, ktor\u00e1 ukazuje, ak\u00fd paket to bol.
\nPrejdime k nastaveniu smerova\u010da Router0. Prech\u00e1dzam do re\u017eimu glob\u00e1lnych nastaven\u00ed a vol\u00e1m rozhranie G0\/0. Potom zad\u00e1m pr\u00edkaz ip nat inside, n\u00e1sledne prejdeme k rozhraniu G0\/1 a zad\u00e1m pr\u00edkaz ip nat outside. T\u00fdmto sp\u00f4sobom som priradil vstupn\u00e9 a v\u00fdstupn\u00e9 rozhrania smerova\u010da. Teraz mus\u00edm ru\u010dne nastavi\u0165 IP adresy, teda prenies\u0165 do nastaven\u00ed riadky z predt\u00fdm uvedenej tabu\u013eky: <\/p>\n

Ip nat inside source static 192.168.1.10 200.124.22.1
\nIp nat inside source static 192.168.1.11 200.124.22.2
\nIp nat inside source static 192.168.1.100 200.124.22.3 <\/p>\n

\"Tr\u00e9ning
\n
\nTeraz pingujem Router1 z ka\u017ed\u00e9ho z na\u0161ich zariaden\u00ed a pozriem sa, ak\u00e9 IP adresy uk\u00e1\u017ee prijat\u00fd ping. Na tento \u00fa\u010del umiest\u0148ujem otvoren\u00e9 okno CLI smerova\u010da R1 na pravej strane obrazovky, aby som videl spr\u00e1vy o laden\u00ed. Potom prech\u00e1dzam do termin\u00e1lu pr\u00edkazov\u00e9ho riadku PC0 a pingujem adresu 200.124.22.10. N\u00e1sledne sa objav\u00ed spr\u00e1va, \u017ee ping bol prijat\u00fd z IP adresy 200.124.22.1. To znamen\u00e1, \u017ee IP adresa lok\u00e1lneho po\u010d\u00edta\u010da 192.168.1.10 bola premenen\u00e1 na glob\u00e1lnu adresu 200.124.22.1.<\/p>\n

\"Tr\u00e9ning
\n
\nTo ist\u00e9 rob\u00edm s \u010fal\u0161\u00edm lok\u00e1lnym po\u010d\u00edta\u010dom a vid\u00edm, \u017ee jeho adresa bola premenen\u00e1 na 200.124.22.2. Potom posielam ping zo servera a vid\u00edm adresu 200.124.22.3.
\nTak\u017ee, ke\u010f sa prev\u00e1dzka z zariadenia lok\u00e1lnej siete dostane do smerova\u010da, na ktorom je nastaven\u00fd statick\u00fd NAT, smerova\u010d pod\u013ea tabu\u013eky premen\u00ed lok\u00e1lnu IP adresu na glob\u00e1lnu a odosiela prev\u00e1dzku do vonkaj\u0161ej siete. Aby som skontroloval tabu\u013eku NAT, zad\u00e1m pr\u00edkaz show ip nat translations.<\/p>\n

\"Tr\u00e9ning
\n
\nTeraz m\u00f4\u017eeme prezrie\u0165 v\u0161etky transform\u00e1cie, ktor\u00e9 vykon\u00e1va router. V prvej kolonke Inside Global sa nach\u00e1dza adresa zariadenia pred prekladom, teda t\u00e1 adresa, pod ktorou je zariadenie vidite\u013en\u00e9 z vonkaj\u0161ej siete. \u010ealej nasleduje adresa Inside Local, to znamen\u00e1 adresa zariadenia v lok\u00e1lnej sieti. Tretia kol\u00f3nka ukazuje Outside Local a \u0161tvrt\u00e1 - adresu Outside Global, pri\u010dom obe tieto adresy s\u00fa rovnak\u00e9, preto\u017ee nepodrobujeme prekladu IP adresu cie\u013ea. Ako vid\u00edte, po nieko\u013ek\u00fdch sekund\u00e1ch sa tabu\u013eka vypr\u00e1zdnila, preto\u017ee v Packet Tracer je nastaven\u00fd kr\u00e1tky \u010dasov\u00fd limit pingu. <\/p>\n

M\u00f4\u017eem pingn\u00fa\u0165 zo smerova\u010da R1 server na adrese 200.124.22.3, a ak sa op\u00e4\u0165 pozriem na nastavenia smerova\u010da, m\u00f4\u017eem vidie\u0165, \u017ee tabu\u013eka sa op\u00e4\u0165 zaplnila \u0161tyrmi riadkami pingu s prelo\u017eenou adresou cie\u013ea 192.168.1.100.<\/p>\n

\"Tr\u00e9ning
\n
\nAko som u\u017e povedal, aj ke\u010f uplynul \u010dasov\u00fd limit prekladu, pri inici\u00e1cii prem\u00e1vky z vonkaj\u0161ieho zdroja sa mechanizmus NAT automaticky aktivuje. K tomu doch\u00e1dza iba pri pou\u017eit\u00ed statick\u00e9ho NAT. <\/p>\n

Teraz sa pozrime, ako funguje dynamick\u00fd NAT. V na\u0161om pr\u00edklade m\u00e1me 2 verejn\u00e9 adresy pre tri zariadenia v lok\u00e1lnej sieti, av\u0161ak m\u00f4\u017eu existova\u0165 desiatky a stovky tak\u00fdchto s\u00fakromn\u00fdch hostite\u013eov. Z\u00e1rove\u0148 sa na internet m\u00f4\u017eu pripoji\u0165 iba 2 zariadenia. Pozrime sa, v \u010dom, okrem tohto, spo\u010d\u00edva rozdiel medzi statick\u00fdm a dynamick\u00fdm NAT.<\/p>\n

Rovnako ako v predch\u00e1dzaj\u00facom pr\u00edpade, najprv mus\u00edme ur\u010di\u0165 vstupn\u00e9 a v\u00fdstupn\u00e9 rozhrania smerova\u010da. Potom vytvor\u00edme ak\u00fdsi pr\u00edstupov\u00fd zoznam, av\u0161ak nejde o ten ACL, o ktorom sme hovorili v predch\u00e1dzaj\u00facej lekcii. Tento pr\u00edstupov\u00fd zoznam sa pou\u017e\u00edva na identifik\u00e1ciu prem\u00e1vky, ktor\u00fa chceme prelo\u017ei\u0165. Tu prich\u00e1dza nov\u00fd term\u00edn 'interesting traffic', alebo 'zauj\u00edmav\u00e1 prem\u00e1vka'. Je to prem\u00e1vka, ktor\u00e1 v\u00e1s z nejak\u00e9ho d\u00f4vodu zauj\u00edma, a ke\u010f t\u00e1to prem\u00e1vka spln\u00ed podmienky pr\u00edstupov\u00e9ho zoznamu, podlieha NAT a je preveden\u00e1. Tento term\u00edn je aplikovate\u013en\u00fd na prem\u00e1vku v mnoh\u00fdch pr\u00edpadoch, napr\u00edklad v pr\u00edpade VPN sa 'zauj\u00edmavou' naz\u00fdva prem\u00e1vka, ktor\u00fa pl\u00e1nujete pusti\u0165 cez VPN tunel. <\/p>\n

Mus\u00edme vytvori\u0165 ACL, ktor\u00fd identifikuje interesting traffic, v na\u0161om pr\u00edpade je to prem\u00e1vka celej siete 192.168.1.0, spolu s ktorou sa uv\u00e1dza sp\u00e4tn\u00e1 maska 0.0.0.255. <\/p>\n

\"Tr\u00e9ning
\n
\nPotom mus\u00edme vytvori\u0165 NAT pool, na \u010do pou\u017eijeme pr\u00edkaz ip nat pool a uvedieme pool IP adries 200.124.22.1 200.124.22.2. To znamen\u00e1, \u017ee poskytneme iba dve extern\u00e9 IP adresy. N\u00e1sledne sa v pr\u00edkaze pou\u017eije k\u013e\u00fa\u010dov\u00e9 slovo netmask a zad\u00e1 sa maska podsiete 255.255.255.252. Posledn\u00fd oktet masky je (255 \u2013 po\u010det adries poolu \u2013 1), tak\u017ee ak m\u00e1te v poole 254 adresy, maska podsiete bude 255.255.255.0. Toto je ve\u013emi d\u00f4le\u017eit\u00fd parameter, preto si pri nastavovan\u00ed dynamick\u00e9ho NAT dajte pozor, aby ste zadali spr\u00e1vnu hodnotu netmask. <\/p>\n

\u010ealej pou\u017e\u00edvame pr\u00edkaz, ktor\u00fd sp\u00fa\u0161\u0165a NAT mechanizmus: ip nat inside source list 1 pool NWKING, kde NWKING je n\u00e1zov poolu a list 1 znamen\u00e1 ACL \u010d\u00edslo 1. Pam\u00e4tajte \u2013 aby tento pr\u00edkaz fungoval, najprv mus\u00edte vytvori\u0165 pool dynamick\u00fdch adries a pr\u00edstupov\u00fd zoznam. <\/p>\n

Tak\u017ee za na\u0161ich podmienok prv\u00e9 zariadenie, ktor\u00e9 chce \u00eds\u0165 na internet, to m\u00f4\u017ee urobi\u0165, druh\u00e9 zariadenie tie\u017e, ale tretie bude musie\u0165 \u010daka\u0165, k\u00fdm sa neuvo\u013en\u00ed jedna z adries poolu. Nastavenie dynamick\u00e9ho NAT pozost\u00e1va z 4 krokov: ur\u010denie vstupn\u00e9ho a v\u00fdstupn\u00e9ho rozhrania, ur\u010denie \u201ezauj\u00edmav\u00e9ho\u201c trafficu, vytvorenie NAT poolu a samotn\u00e9 nastavenie.
\nTeraz prejdeme na Packet Tracer a pok\u00fasime sa nastavi\u0165 dynamick\u00fd NAT. Najprv mus\u00edme odstr\u00e1ni\u0165 nastavenia statick\u00e9ho NAT, na \u010do postupne zad\u00e1me pr\u00edkazy:<\/p>\n

no Ip nat inside source static 192.168.1.10 200.124.22.1
\nno Ip nat inside source static 192.168.1.11 200.124.22.2
\nno Ip nat inside source static 192.168.1.100 200.124.22.3. <\/p>\n

N\u00e1sledne vytv\u00e1ram pr\u00edstupov\u00fd zoznam List 1 pre cel\u00fa sie\u0165 pr\u00edkazom access-list 1 permit 192.168.1.0 0.0.0.255 a formujem NAT pool pomocou pr\u00edkazu ip nat pool NWKING 200.124.22.1 200.124.22.2 netmask 255.255.255.252. V tomto pr\u00edkaze som uvedol n\u00e1zov poolu, adresy, ktor\u00e9 do neho patria, a sie\u0165ov\u00fa masku.<\/p>\n

Potom uv\u00e1dzam, ak\u00fd typ NAT je \u2013 intern\u00fd alebo extern\u00fd, a zdroj, z ktor\u00e9ho by mal NAT \u010derpa\u0165 inform\u00e1cie. V na\u0161om pr\u00edpade je to list, pomocou pr\u00edkazu ip nat inside source list 1. N\u00e1sledne syst\u00e9m vyzve na v\u00fdber, \u010di je potrebn\u00fd cel\u00fd pool alebo konkr\u00e9tne rozhranie. Vol\u00edm pool, preto\u017ee m\u00e1me viac ako 1 extern\u00fa adresu. Ak zvol\u00edte rozhranie, je potrebn\u00e9 uvies\u0165 port s konkr\u00e9tnym IP-adresou. V kone\u010dnej podobe bude pr\u00edkaz vyzera\u0165 takto: ip nat inside source list 1 pool NWKING. Tento pool moment\u00e1lne pozost\u00e1va z dvoch adries 200.124.22.1 200.124.22.2, av\u0161ak m\u00f4\u017eete ich vo\u013ene zmeni\u0165 alebo prida\u0165 nov\u00e9 adresy, ktor\u00e9 nie s\u00fa viazan\u00e9 na konkr\u00e9tne rozhranie. <\/p>\n

Mus\u00edte sa uisti\u0165, \u017ee va\u0161a smerovacia tabu\u013eka sa aktualizovala tak, aby ak\u00e1ko\u013evek z t\u00fdchto IP adries v poole bola smerovan\u00e1 na toto zariadenie, inak nedostanete sp\u00e4tn\u00fa prev\u00e1dzku. Aby sme sa uistili o \u00fa\u010dinnosti nastaven\u00ed, zopakujeme postup pingovania cloudov\u00e9ho smerova\u010da, ktor\u00fd sme vykonali pri statickom NAT. Otvor\u00edm okno smerova\u010da Router 1, aby som videl spr\u00e1vy re\u017eimu ladenia, a pingujem ho z ka\u017ed\u00e9ho z 3 zariaden\u00ed.<\/p>\n

\"Tr\u00e9ning
\n
\nVid\u00edme, \u017ee v\u0161etky adresy zdrojov, z ktor\u00fdch prich\u00e1dzaj\u00fa pakety pingu, zodpovedaj\u00fa nastaveniam. Pritom ping z po\u010d\u00edta\u010da PC0 neprech\u00e1dza, preto\u017ee mu ch\u00fdbal vo\u013en\u00fd extern\u00fd adresa. Ak sa pozriete do nastaven\u00ed Router 1, vidno, \u017ee v s\u00fa\u010dasnosti s\u00fa pou\u017e\u00edvan\u00e9 adresy poolu 200.124.22.1 a 200.124.22.2. Teraz vypnem preklad a uvid\u00edte, ako sa riadky vytr\u00e1caj\u00fa jeden po druhom. Znova sp\u00fa\u0161\u0165am ping z po\u010d\u00edta\u010da PC0 a, ako vid\u00edte, teraz v\u0161etko funguje, preto\u017ee mohol z\u00edska\u0165 uvo\u013enen\u00fa extern\u00fa adresu 200.124.22.1. <\/p>\n

Ako m\u00f4\u017eeme vy\u010disti\u0165 NAT tabu\u013eku a zru\u0161i\u0165 zadan\u00e9 prelo\u017eenie adries? Ideme do nastaven\u00ed smerova\u010da Router0 a zad\u00e1vame pr\u00edkaz clear ip nat translation * so \u201ehviezdi\u010dkou\u201c na konci. Ak sa teraz pozrieme na stav prekladu pomocou pr\u00edkazu show ip nat translation, syst\u00e9m n\u00e1m poskytne pr\u00e1zdny riadok. <\/p>\n

Na zobrazenie \u0161tatistiky NAT sa pou\u017e\u00edva pr\u00edkaz show ip nat statistics. <\/p>\n

\"Tr\u00e9ning
\n
\nToto je ve\u013emi u\u017eito\u010dn\u00fd pr\u00edkaz, ktor\u00fd v\u00e1m umo\u017e\u0148uje zisti\u0165 celkov\u00fd po\u010det dynamick\u00fdch, statick\u00fdch a roz\u0161\u00edren\u00fdch prevodov NAT\/PAT. Vid\u00edte, \u017ee je rovn\u00fd 0, preto\u017ee sme predch\u00e1dzaj\u00facim pr\u00edkazom vymazali \u00fadaje o prevode. Tu s\u00fa zobrazen\u00e9 vstupn\u00e9 a v\u00fdstupn\u00e9 rozhrania, po\u010det \u00faspe\u0161n\u00fdch a ne\u00faspe\u0161n\u00fdch prevodov hits a misses (po\u010det ne\u00faspechov s\u00favis\u00ed s nedostatkom vo\u013enej vonkaj\u0161ej adresy pre vn\u00fatorn\u00fd hostite\u013e), n\u00e1zov pr\u00edstupov\u00e9ho zoznamu a poolu. <\/p>\n

Teraz prejdeme k najpopul\u00e1rnej\u0161iemu typu prevodu IP adries \u2013 roz\u0161\u00edren\u00e9mu NAT, alebo PAT. Na nastavenie PAT je potrebn\u00e9 vykona\u0165 tie ist\u00e9 kroky, ako pri nastaven\u00ed dynamick\u00e9ho NAT: ur\u010di\u0165 vstupn\u00e9 a v\u00fdstupn\u00e9 rozhrania smerova\u010da, identifikova\u0165 'zauj\u00edmav\u00fd' prenos, vytvori\u0165 NAT pool a nastavi\u0165 PAT. M\u00f4\u017eeme vytvori\u0165 rovnak\u00fd pool z viacer\u00fdch adries, ako v predch\u00e1dzaj\u00facom pr\u00edpade, ale nie je to potrebn\u00e9, preto\u017ee v PAT sa neust\u00e1le pou\u017e\u00edva t\u00e1 ist\u00e1 vonkaj\u0161ia adresa. Rozdiel medzi nastaven\u00edm dynamick\u00e9ho NAT a PAT spo\u010d\u00edva len v k\u013e\u00fa\u010dovom slove overload, ktor\u00fdm kon\u010d\u00ed posledn\u00fd pr\u00edkaz na nastavenie. Po zadan\u00ed tohto slova sa dynamick\u00e9 NAT automaticky pred\u00e1va na PAT.<\/p>\n

\"Tr\u00e9ning
\n
\nNavy\u0161e pou\u017e\u00edvate len jednu adresu v poole NWKING, napr\u00edklad 200.124.22.1, ale uv\u00e1dzate ju dvakr\u00e1t ako po\u010diato\u010dn\u00fa a kone\u010dn\u00fa vonkaj\u0161iu adresu so sie\u0165ovou maskou 255.255.255.0. M\u00f4\u017eete to urobi\u0165 jednoduch\u0161ie, pou\u017eit\u00edm namiesto pr\u00edkazu ip nat 1 pool NWKING 200.124.22.1 200.124.22.1 netmask 255.255.255.0 parametra source interface a pevnej adresy 200.124.22.1 rozhrania G0\/1. V tomto pr\u00edpade sa v\u0161etky lok\u00e1lne adresy pri odchode na internet premenia na t\u00fato IP adresu. <\/p>\n

V poole je mo\u017en\u00e9 pou\u017ei\u0165 aj ak\u00fako\u013evek in\u00fa IP adresu, ktor\u00e1 nemus\u00ed zodpoveda\u0165 konkr\u00e9tnemu fyzick\u00e9mu rozhraniu. Av\u0161ak v tomto pr\u00edpade mus\u00edte zabezpe\u010di\u0165, aby v\u0161etky smerova\u010de v sieti dok\u00e1zali smerova\u0165 sp\u00e4tn\u00fd prenos k zariadeniu, ktor\u00e9 ste si vybrali. Nedostatok NAT spo\u010d\u00edva v tom, \u017ee ho nemo\u017eno pou\u017ei\u0165 na priechodn\u00fa adres\u00e1ciu, preto\u017ee k\u00fdm sa sp\u00e4tn\u00fd paket vr\u00e1ti k lok\u00e1lnemu zariadeniu, jeho dynamick\u00e1 NAT IP adresa sa m\u00f4\u017ee zmeni\u0165. To znamen\u00e1, \u017ee mus\u00edte ma\u0165 istotu, \u017ee vybran\u00e1 IP adresa zostane dostupn\u00e1 po\u010das cel\u00e9ho trvania komunika\u010dn\u00e9ho rel\u00e1cie. <\/p>\n

Pozrime sa na to cez Packet Tracer. Najprv mus\u00edm odstr\u00e1ni\u0165 dynamick\u00fd NAT pr\u00edkazom no Ip nat inside source list 1 NWKING a odstr\u00e1ni\u0165 NAT pool pomocou pr\u00edkazu no Ip nat pool NWKING 200.124.22.1 200.124.22.2 netmask 225.255.255.252. <\/p>\n

Potom mus\u00edm vytvori\u0165 PAT pool pr\u00edkazom Ip nat pool NWKING 200.124.22.2 200.124.22.2 netmask 225.255.255.255. Tentoraz pou\u017e\u00edvam IP adresu, ktor\u00e1 nepatr\u00ed fyzick\u00e9mu zariadeniu, preto\u017ee fyzick\u00e9 zariadenie m\u00e1 adresu 200.124.22.1, a chcem pou\u017ei\u0165 200.124.22.2. V na\u0161om pr\u00edpade to funguje, preto\u017ee m\u00e1me lok\u00e1lnu sie\u0165.<\/p>\n

\u010ealej nastavujem PAT pr\u00edkazom Ip nat inside source list 1 pool NWKING overload. Po zadan\u00ed tohto pr\u00edkazu sa aktivuje prevod adries PAT. Aby som skontroloval spr\u00e1vnos\u0165 nastavenia, prech\u00e1dzam k na\u0161im zariadenia, serveru a dvom po\u010d\u00edta\u010dom, a pingujem z po\u010d\u00edta\u010da PC0 Router1 na adresu 200.124.22.10. V okne nastaven\u00ed routera vid\u00edm riadky ladenia, ktor\u00e9 ukazuj\u00fa, \u017ee zdrojom pingu, ako sme o\u010dak\u00e1vali, je IP adresa 200.124.22.2. Z tej istej adresy prich\u00e1dza ping, ktor\u00fd posiela po\u010d\u00edta\u010d PC1 a server Server0. <\/p>\n

Pozrime sa, \u010do sa deje v tabu\u013eke prevodov routera Router0. Vid\u00edte, \u017ee v\u0161etky prevody s\u00fa \u00faspe\u0161n\u00e9, ka\u017ed\u00e9mu zariadeniu je pridelen\u00fd vlastn\u00fd port a v\u0161etky lok\u00e1lne adresy s\u00fa prepojen\u00e9 s Router1 cez IP adresu poolu 200.124.22.2. <\/p>\n

\"Tr\u00e9ning
\n
\nPou\u017e\u00edvam pr\u00edkaz show ip nat statistics, aby som si pozrel \u0161tatistiku PAT. <\/p>\n

\"Tr\u00e9ning
\n
\nVid\u00edme, \u017ee celkov\u00fd po\u010det prevodov, alebo transl\u00e1ci\u00ed adries, je 12, vid\u00edme charakteristiku poolu a \u010fal\u0161ie inform\u00e1cie. <\/p>\n

Teraz urob\u00edm e\u0161te nie\u010do \u2014 zad\u00e1m pr\u00edkaz Ip nat inside source list 1 interface gigabit Ethernet g0\/1 overload. Ak po tom pingujem router z po\u010d\u00edta\u010da PC0, vid\u00edm, \u017ee paket pri\u0161iel z adresy 200.124.22.1, teda z fyzick\u00e9ho rozhrania! Je to jednoduch\u0161\u00ed sp\u00f4sob: ak nechcete vytv\u00e1ra\u0165 pool, \u010do sa naj\u010dastej\u0161ie deje pri pou\u017e\u00edvan\u00ed dom\u00e1cich routerov, m\u00f4\u017eete pou\u017ei\u0165 IP adresu fyzick\u00e9ho rozhrania routera ako extern\u00fa NAT adresu. Presne tak sa naj\u010dastej\u0161ie realizuje prevod adresy v\u00e1\u0161ho priv\u00e1tneho hosta pre verejn\u00fa sie\u0165.
\nDnes sme presk\u00famali ve\u013emi d\u00f4le\u017eit\u00fa t\u00e9mu, tak\u017ee je potrebn\u00e9 si ju precvi\u010di\u0165. Pou\u017eite Packet Tracer na overenie va\u0161ich teoretick\u00fdch znalost\u00ed pri rie\u0161en\u00ed praktick\u00fdch \u00faloh t\u00fdkaj\u00facich sa nastavenia NAT a PAT. Dostali sme sa na koniec \u0161t\u00fadia t\u00e9my ICND1 \u2014 prvej sk\u00fa\u0161ky kurzu CCNA, tak\u017ee nasleduj\u00faci videoz\u00e1znam budem pravdepodobne venova\u0165 zhrnutiu. <\/p>\n

\r\n \"Prehrajte\r\n
<\/div>\r\n <\/div><\/center>
\n\u010eakujeme, \u017ee s nami zost\u00e1vate. P\u00e1\u010dia sa v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vidie\u0165 viac zauj\u00edmav\u00fdch materi\u00e1lov? Podporte n\u00e1s objednan\u00edm alebo odpor\u00fa\u010dan\u00edm priate\u013eom, 30% z\u013eava pre pou\u017e\u00edvate\u013eov Chabra na unik\u00e1tny ekvivalent entry-level serverov, ktor\u00fd sme pre v\u00e1s vytvorili:<\/b> V\u0161etky pravdy o VPS (KVM) E5-2650 v4 (6 jadier) 10GB DDR4 240GB SSD 1Gbps od 20 dol\u00e1rov alebo ako spr\u00e1vne rozdeli\u0165 server?<\/a><\/noindex> (k dispoz\u00edcii varianty s RAID1 a RAID10, a\u017e 24 jadier a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd za polovicu?<\/b> Len u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 dol\u00e1rov<\/a><\/noindex> v Holandsku! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 dol\u00e1rov!<\/b><\/b> Pre\u010d\u00edtajte si o tom Ako vybudova\u0165 infra\u0161trukt\u00faru korpor\u00e1tneho typu s pou\u017eit\u00edm serverov Dell R730xd E5-2650 v4 s cenou 9000 eur za zlomok ceny?<\/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 \u0431\u0443\u0434\u0435\u043c \u0438\u0437\u0443\u0447\u0430\u0442\u044c PAT (Port Address Translation), \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 IP- \u0430\u0434\u0440\u0435\u0441\u043e\u0432 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043f\u043e\u0440\u0442\u043e\u0432, \u0438 NAT (Network Address Translation), \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e \u043f\u0440\u0435\u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u043d\u0438\u044f IP-\u0430\u0434\u0440\u0435\u0441\u043e\u0432 \u0442\u0440\u0430\u043d\u0437\u0438\u0442\u043d\u044b\u0445 \u043f\u0430\u043a\u0435\u0442\u043e\u0432. PAT \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0447\u0430\u0441\u0442\u043d\u044b\u043c \u0441\u043b\u0443\u0447\u0430\u0435\u043c NAT. \u041c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0442\u0440\u0438 \u0442\u0435\u043c\u044b: \u2014 \u043f\u0440\u0438\u0432\u0430\u0442\u043d\u044b\u0435, \u0438\u043b\u0438 \u0432\u043d\u0443\u0442\u0440\u0435\u043d\u043d\u0438\u0435 (\u0432\u043d\u0443\u0442\u0440\u0438\u0441\u0435\u0442\u0435\u0432\u044b\u0435, \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0435) IP-\u0430\u0434\u0440\u0435\u0441\u0430 \u0438 \u043f\u0443\u0431\u043b\u0438\u0447\u043d\u044b\u0435, \u0438\u043b\u0438 \u0432\u043d\u0435\u0448\u043d\u0438\u0435 IP-\u0430\u0434\u0440\u0435\u0441\u0430; \u2014 NAT \u0438 PAT; \u2014 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 NAT\/ PAT. \u041d\u0430\u0447\u043d\u0435\u043c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28314,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37723","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\u00e9ning Cisco 200-125 CCNA v3.0. De\u0148 29. PAT a NAT | ProHoster","description":"Dnes sa budeme zaobera\u0165 PAT (prevod adresy portu), technol\u00f3giou prevodu IP adries pomocou portov, a NAT (prevod sie\u0165ovej adresy), technol\u00f3giou konverzie IP adries transitn\u00fdch paketov.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-29-pat-i-nat","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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 29. PAT \u0438 NAT | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0438\u0437\u0443\u0447\u0430\u0442\u044c PAT (Port Address Translation), \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 IP- \u0430\u0434\u0440\u0435\u0441\u043e\u0432 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043f\u043e\u0440\u0442\u043e\u0432, \u0438 NAT (Network Address Translation), \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e \u043f\u0440\u0435\u043e\u0431\u0440\u0430\u0437\u043e\u0432\u0430\u043d\u0438\u044f IP-\u0430\u0434\u0440\u0435\u0441\u043e\u0432 \u0442\u0440\u0430\u043d\u0437\u0438\u0442\u043d\u044b\u0445 \u043f\u0430\u043a\u0435\u0442\u043e\u0432.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-29-pat-i-nat","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:19:20+00:00","article:modified_time":"2019-10-31T19:19:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37723","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 19:02:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:22:28","updated":"2026-01-23 19:02:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=37723"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37723\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28314"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}