{"id":81265,"date":"2020-05-12T01:42:43","date_gmt":"2020-05-11T23:42:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux"},"modified":"2020-05-12T01:42:43","modified_gmt":"2020-05-11T23:42:43","slug":"bystryj-routing-i-nat-v-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux","title":{"rendered":"Brzo rutiranje i NAT u Linuxu","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>S obzirom na iscrpljivanje IPv4 adresa, mnogi telekomunikacijski operateri suo\u010dili su se s potrebom organizacije pristupa svojim klijentima na mre\u017eu putem prevo\u0111enja adresa. U ovom \u010dlanku \u0107u objasniti kako se mo\u017ee posti\u0107i izvedba na razini Carrier Grade NAT na konvencionalnim poslu\u017eiteljima.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Malo povijesti<\/h3>\n<p>\nTema iscrpljivanja adresnog prostora IPv4 vi\u0161e nije nova. U nekom trenutku u RIPE su se pojavile liste \u010dekanja, zatim su se otvorile razmjene na kojima su se trgovali blokovi adresa i sklapali ugovori o njihovom najmu. Postupno su telekomunikacijski operateri po\u010deli pru\u017eati pristup internetu koriste\u0107i prevo\u0111enje adresa i portova. Neki nisu uspjeli dobiti dovoljno adresa da dodijele \u201ebijelu\u201c adresu svakom korisniku, a neki su po\u010deli \u0161tedjeti sredstva odbijanjem kupnje adresa na sekundarnom tr\u017ei\u0161tu. Proizvo\u0111a\u010di mre\u017ene opreme podr\u017eali su ovu ideju, budu\u0107i da ta funkcionalnost obi\u010dno zahtijeva dodatne ekspanzijske module ili licence. Na primjer, kod Junipera u liniji MX usmjeriva\u010da (osim najnovijih MX104 i MX204) obavljanje NAPT mo\u017ee se izvr\u0161iti na zasebnoj servisnoj kartici MS-MIC, dok je na Cisco ASR1k potrebna SGN licenca, na Cisco ASR9k \u2014 zaseban modul A9K-ISM-100 i licenca A9K-CGN-LIC za njega. Ukratko, cijena nije mala.<\/p>\n<h3>IPTables<\/h3>\n<p>\nIzvr\u0161avanje NAT zadatka ne zahtijeva specijalizirane ra\u010dunarske resurse, to mogu rje\u0161avati procesori op\u0107e namjene, koji se nalaze, primjerice, u bilo kojem ku\u0107nom usmjeriva\u010du. U okviru telekomunikacijskog operatera, taj zadatak mo\u017ee se rije\u0161iti kori\u0161tenjem konvencionalnih poslu\u017eitelja pod upravljanjem FreeBSD (ipfw\/pf) ili GNU\/Linux (iptables). Ne\u0107emo razmatrati FreeBSD, jer sam se prije dosta vremena odriceo kori\u0161tenja ovog OS-a, tako da \u0107emo se usredoto\u010diti na GNU\/Linux.<\/p>\n<p>Uklju\u010divanje prevo\u0111enja adresa nije te\u0161ko. Prvo, potrebno je napisati pravilo u iptables u nat tabelu:<\/p>\n<pre><code class=\"bash\">iptables -t nat -A POSTROUTING -s 100.64.0.0\/10 -j SNAT --to - --persistent\n<\/code><\/pre>\n<p>\nOperacijski sustav \u0107e u\u010ditati nf_conntrack modul, koji \u0107e pratiti sve aktivne veze i izvoditi potrebne transformacije. Postoji nekoliko suptilnosti. Prvo, budu\u0107i da se radi o NAT-u na razini telekomunikacijskog operatera, potrebno je prilagoditi timeout vrijednosti, jer \u0107e s zadanim vrijednostima veli\u010dina tablice prevo\u0111enja brzo narasti do katastrofalnih razmjera. Ispod je primjer postavki koje sam koristio na svojim poslu\u017eiteljima:<\/p>\n<pre><code class=\"bash\">net.ipv4.ip_forward = 1\nnet.ipv4.ip_local_port_range = 8192 65535\n\nnet.netfilter.nf_conntrack_generic_timeout = 300\nnet.netfilter.nf_conntrack_tcp_timeout_syn_sent = 60\nnet.netfilter.nf_conntrack_tcp_timeout_syn_recv = 60\nnet.netfilter.nf_conntrack_tcp_timeout_established = 600\nnet.netfilter.nf_conntrack_tcp_timeout_fin_wait = 60\nnet.netfilter.nf_conntrack_tcp_timeout_close_wait = 45\nnet.netfilter.nf_conntrack_tcp_timeout_last_ack = 30\nnet.netfilter.nf_conntrack_tcp_timeout_time_wait = 120\nnet.netfilter.nf_conntrack_tcp_timeout_close = 10\nnet.netfilter.nf_conntrack_tcp_timeout_max_retrans = 300\nnet.netfilter.nf_conntrack_tcp_timeout_unacknowledged = 300\nnet.netfilter.nf_conntrack_udp_timeout = 30\nnet.netfilter.nf_conntrack_udp_timeout_stream = 60\nnet.netfilter.nf_conntrack_icmpv6_timeout = 30\nnet.netfilter.nf_conntrack_icmp_timeout = 30\nnet.netfilter.nf_conntrack_events_retry_timeout = 15\nnet.netfilter.nf_conntrack_checksum=0\n<\/code><\/pre>\n<p>\nI drugo, s obzirom na to da veli\u010dina tablice prevo\u0111enja prema zadanim postavkama nije prilago\u0111ena radu na razini telekomunikacijskog operatera, potrebno ju je pove\u0107ati:<\/p>\n<pre><code class=\"plaintext\">net.netfilter.nf_conntrack_max = 3145728\n<\/code><\/pre>\n<p>\n Tako\u0111er je potrebno pove\u0107ati i broj buckets za hash-tablicu koja pohranjuje sve prevo\u0111enje (ova opcija se odnosi na modul nf_conntrack): <\/p>\n<pre><code class=\"plaintext\">options nf_conntrack hashsize=1572864\n<\/code><\/pre>\n<p>\nNakon ovih jednostavnih manipulacija dobiva se sasvim funkcionalna struktura koja mo\u017ee prevesti veliki broj klijentskih adresa u skup vanjskih. Me\u0111utim, performanse ovog rje\u0161enja ostavljaju mnogo prostora za pobolj\u0161anje. U svojim prvim poku\u0161ajima kori\u0161tenja GNU\/Linux-a za NAT (otprilike 2013. godina) uspio sam posti\u0107i performanse oko 7Gbit\/s pri 0.8Mpps na jedan poslu\u017eitelj (Xeon E5-1650v2). Od tada je u mre\u017enoj hrpi kernela GNU\/Linux-a napravljeno mnogo optimizacija, a performanse jednog poslu\u017eitelja na istom hardveru porasle su prakti\u010dki na 18-19 Gbit\/s pri 1.8-1.9 Mpps (to su bili ekstremni limiti), ali potreba za obradom prometa od strane jednog poslu\u017eitelja rasla je mnogo br\u017ee. Na kraju su razvijeni sustavi za raspodjelu optere\u0107enja na razli\u010dite poslu\u017eitelje, ali sve to pove\u0107ava slo\u017eenost konfiguracije, odr\u017eavanja i kvalitete usluga koje se pru\u017eaju.<\/p>\n<h3>NFTables<\/h3>\n<p>\nTrenutno je popularno usmjerenje u softverskom \"prebacivanju paketa\" kori\u0161tenje DPDK i XDP. O ovoj temi napisano je dosta \u010dlanaka, odr\u017eano mnogo razli\u010ditih prezentacija, pojavljuju se komercijalni proizvodi (na primjer, SKAT od VasExperts). Me\u0111utim, u uvjetima ograni\u010denih resursa programera kod telekomunikacijskih operatera, prilikom izrade nekog \"proizvoda\" na temelju ovih okvira, prili\u010dno je problemati\u010dno. Daljnje kori\u0161tenje takvog rje\u0161enja bit \u0107e znatno slo\u017eenije, osobito \u0107e biti potrebno razvijati dijagnosti\u010dke alate. Na primjer, standardni tcpdump s DPDK-om ne mo\u017ee se lako koristiti, a ni paketi koji se \u0161alju natrag putem XDP-a ne\u0107e biti \"vidljivi\". Na pozadini svih razgovora o novim tehnologijama za usmjeravanje paketa u korisni\u010dkom prostoru, neprimije\u0107eni su ostali <noindex><a rel=\"nofollow\" href=\"https:\/\/netdevconf.info\/0x13\/session.html?workshop-netfilter-mini\">izvje\u0161taji<\/a><\/noindex> i <noindex><a rel=\"nofollow\" href=\"https:\/\/lwn.net\/Articles\/738214\/\">\u010dlanaka<\/a><\/noindex> Pablo Neira Ayuso, odr\u017eava\u010d iptables, o razvoju flow offloadinga u nftables. Poglejmo ovaj mehanizam detaljnije.<\/p>\n<p>Osnovna ideja je da, ako ruter propu\u0161ta pakete jedne sesije u oba smjera toka (TCP sesija prelazi u stanje ESTABLISHED), nema potrebe propu\u0161tati kasnije pakete te sesije kroz sva pravila vatrozida jer \u0107e svi ti pregledi ionako zavr\u0161iti prijenosom paketa u usmjeravanje. Zapravo, odabir rute tako\u0111er nije potreban \u2014 ve\u0107 znamo u koji \u0107e se su\u010delje i kojem hostu paketi poslati unutar ove sesije. Ostaje samo zadr\u017eati te informacije i koristiti ih za usmjeravanje u ranoj fazi obrade paketa. Pri izvo\u0111enju NAT-a potrebno je dodatno pohraniti informacije o promjenama adresa i portova, koje je transformirao modul nf_conntrack. Da, naravno, u ovom slu\u010daju prestaju raditi razli\u010diti policeri i druga informati\u010dko-statisti\u010dka pravila u iptables, ali u okviru zadatka posebnog pripadaju\u0107eg NAT-a ili, na primjer, bordera \u2014 to nije tako va\u017eno, jer su usluge raspore\u0111ene po ure\u0111ajima.<\/p>\n<h4>Konfiguracija<\/h4>\n<p>\nDa bismo iskoristili ovu funkciju, trebamo:<\/p>\n<ul>\n<li>Koristiti svje\u017eu jezgru. Iako je sama funkcionalnost uvedena jo\u0161 u jezgri 4.16, dugo je vremena bila prili\u010dno \"siroma\u0161na\" i redovito je uzrokovala kernel panic. Stabilizirala se otprilike u prosincu 2019. godine, kada su objavljene LTS jezgre 4.19.90 i 5.4.5.<\/li>\n<li>Prepisivanje pravila iptables u nftables format koriste\u0107i dovoljno novu verziju nftables. To\u010dno radi u verziji 0.9.0<\/li>\n<\/ul>\n<p>\nAko je prvi punkt u osnovi jasan, va\u017eno je ne zaboraviti uklju\u010diti modul u konfiguraciju pri kompilaciji (CONFIG_NFT_FLOW_OFFLOAD=m), drugi punkt zahtijeva obja\u0161njenje. Pravila nftables opisuju se posve druga\u010dije nego u iptables. <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.nftables.org\/wiki-nftables\/index.php\/Main_Page\">Dokumentacija<\/a><\/noindex> otkriva prakti\u010dki sve aspekte, tako\u0111er postoje posebni <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.nftables.org\/wiki-nftables\/index.php\/Moving_from_iptables_to_nftables\">konverteri<\/a><\/noindex> pravila iz iptables u nftables. Stoga \u0107u navesti samo primjer postavke NAT-a i flow offloada. Mala legenda za primjer: &lt;i_if&gt;, &lt;o_if&gt; \u2014 to su mre\u017eni interfejsi kroz koje prolazi promet, stvarno mo\u017ee biti vi\u0161e od dva. &lt;pool_addr_start&gt;, &lt;pool_addr_end&gt; \u2014 po\u010detna i zavr\u0161na adresa raspona \"bijelih\" adresa.<\/p>\n<p>Konfiguracija NAT-a je vrlo jednostavna:<\/p>\n<pre><code class=\"bash\">#! \/usr\/sbin\/nft -f\n\ntable nat {\n        chain postrouting {\n                type nat hook postrouting priority 100;\n                oif &lt;o_if&gt; snat to &lt;pool_addr_start&gt;-&lt;pool_addr_end&gt; persistent\n        }\n}\n<\/code><\/pre>\n<p>\nS flow offload-om je malo slo\u017eenije, ali sasvim razumljivo:<\/p>\n<pre><code class=\"bash\">#! \/usr\/sbin\/nft -f\n\ntable inet filter {\n        flowtable fastnat {\n                hook ingress priority 0\n                devices = { &lt;i_if&gt;, &lt;o_if&gt; }\n        }\n\n        chain forward {\n                type filter hook forward priority 0; policy accept;\n                ip protocol { tcp , udp } flow offload @fastnat;\n        }\n}\n<\/code><\/pre>\n<p>\nEto, to je cijela konfiguracija. Sada \u0107e sav TCP\/UDP promet ulaziti u tablicu fastnat i obra\u0111ivati se puno br\u017ee.<\/p>\n<h3>Rezultati<\/h3>\n<p>\nDa bi bilo jasnije koliko je to \"puno br\u017ee\", prila\u017eem snimku optere\u0107enja na dva stvarna servera, sa istim komponentama (Xeon E5-1650v2), identi\u010dno pode\u0161enima, koriste\u0107i isto jezgro Linuxa, ali izvr\u0161avaju\u0107i NAT u iptables (NAT4) i u nftables (NAT5).<\/p>\n<p><img decoding=\"async\" alt=\"Brzo rutiranje i NAT u Linuxu\" src=\"\/wp-content\/uploads\/2020\/05\/94bd3f58bf499ceb9837cd771cc9ef9f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNa snimci nema grafika paketa u sekundi, ali u profilu optere\u0107enja ovih servera prosje\u010dna veli\u010dina paketa je oko 800 bajta, tako da vrijednosti dosegnu do 1.5Mpps. Kao \u0161to se mo\u017ee vidjeti, kapacitet performansi servera s nftables je ogroman. Trenutno ovaj server obra\u0111uje do 30Gbit\/s pri 3Mpps i o\u010dito mo\u017ee dosegnuti fizi\u010dko ograni\u010denje mre\u017ee od 40Gbps, pri \u010demu ima slobodne resurse CPU-a.<\/p>\n<p>Nadam se da \u0107e ovaj materijal biti koristan mre\u017enim in\u017eenjerima koji poku\u0161avaju pobolj\u0161ati performanse svojih servera.<br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/501234\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043e \u043c\u0435\u0440\u0435 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u0438\u044f \u0430\u0434\u0440\u0435\u0441\u043e\u0432 IPv4, \u043c\u043d\u043e\u0433\u0438\u0435 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u044b \u0441\u0432\u044f\u0437\u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0438\u0441\u044c \u0441 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u044c\u044e \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0441\u0432\u043e\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u0432 \u0441\u0435\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 \u0430\u0434\u0440\u0435\u0441\u043e\u0432. \u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u043a\u0430\u043a \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0443\u0440\u043e\u0432\u043d\u044f Carrier Grade NAT \u043d\u0430 commodity \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445. \u041d\u0435\u043c\u043d\u043e\u0433\u043e \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0422\u0435\u043c\u0430 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u0438\u044f \u0430\u0434\u0440\u0435\u0441\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u0430 IPv4 \u0443\u0436\u0435 \u043d\u0435 \u043d\u043e\u0432\u0430. \u0412 \u043a\u0430\u043a\u043e\u0439-\u0442\u043e \u043c\u043e\u043c\u0435\u043d\u0442 \u0432 RIPE \u043f\u043e\u044f\u0432\u0438\u043b\u0438\u0441\u044c \u043e\u0447\u0435\u0440\u0435\u0434\u0438 \u043e\u0436\u0438\u0434\u0430\u043d\u0438\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":81266,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-81265","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043e \u043c\u0435\u0440\u0435 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u0438\u044f \u0430\u0434\u0440\u0435\u0441\u043e\u0432 IPv4, \u043c\u043d\u043e\u0433\u0438\u0435 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u044b \u0441\u0432\u044f\u0437\u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0438\u0441\u044c \u0441 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u044c\u044e \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0441\u0432\u043e\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u0432 \u0441\u0435\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 \u0430\u0434\u0440\u0435\u0441\u043e\u0432.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0411\u044b\u0441\u0442\u0440\u044b\u0439 \u0440\u043e\u0443\u0442\u0438\u043d\u0433 \u0438 NAT \u0432 Linux | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043e \u043c\u0435\u0440\u0435 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u0438\u044f \u0430\u0434\u0440\u0435\u0441\u043e\u0432 IPv4, \u043c\u043d\u043e\u0433\u0438\u0435 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u044b \u0441\u0432\u044f\u0437\u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0438\u0441\u044c \u0441 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u044c\u044e \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0441\u0432\u043e\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u0432 \u0441\u0435\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 \u0430\u0434\u0440\u0435\u0441\u043e\u0432.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-05-11T23:42:43+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-11T23:42:43+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Brza usmjeravanja i NAT u Linuxu | ProHoster","description":"Kako se IPv4 adrese iscrpljuju, mnogi operateri telekomunikacija suo\u010davaju se s potrebom da organiziraju pristup svojim klijentima u mre\u017eu putem prevo\u0111enja adresa.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\u0411\u044b\u0441\u0442\u0440\u044b\u0439 \u0440\u043e\u0443\u0442\u0438\u043d\u0433 \u0438 NAT \u0432 Linux | ProHoster","og:description":"\u041f\u043e \u043c\u0435\u0440\u0435 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u0438\u044f \u0430\u0434\u0440\u0435\u0441\u043e\u0432 IPv4, \u043c\u043d\u043e\u0433\u0438\u0435 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u044b \u0441\u0432\u044f\u0437\u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0438\u0441\u044c \u0441 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u044c\u044e \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f \u0441\u0432\u043e\u0438\u0445 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u0432 \u0441\u0435\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0440\u0430\u043d\u0441\u043b\u044f\u0446\u0438\u0438 \u0430\u0434\u0440\u0435\u0441\u043e\u0432.","og:url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/bystryj-routing-i-nat-v-linux","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":"2020-05-11T23:42:43+00:00","article:modified_time":"2020-05-11T23:42:43+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"81265","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 16:01:23","updated":"2022-09-28 04:47:17","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/81265","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=81265"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/81265\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/81266"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=81265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=81265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=81265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}