
{"id":732,"date":"2024-07-01T18:26:01","date_gmt":"2024-07-01T15:26:01","guid":{"rendered":"https:\/\/new.arkitek.net\/cozumlerimiz\/elektronik-haberlesme-cozumleri\/carrier-grade-nat\/"},"modified":"2024-07-10T22:47:04","modified_gmt":"2024-07-10T19:47:04","slug":"carrier-grade-nat","status":"publish","type":"page","link":"https:\/\/arkitek.net\/tr\/cozumler\/elektronik-haberlesme\/carrier-grade-nat\/","title":{"rendered":"Carrier-Grade NAT"},"content":{"rendered":"\n<p>2011 y\u0131l\u0131nda, \u0130nternet Atanm\u0131\u015f Numaralar Otoritesi (IANA) kalan son \/ 8 adres blo\u011funu B\u00f6lgesel \u0130nternet Kay\u0131tlar\u0131na (RIR) a\u00e7t\u0131 ve RIR\u2019leri mevcut IPv4 adreslerinin geri kalan\u0131n\u0131n da atanmas\u0131 (ve t\u00fcketilmesi) konusunda \u00f6zg\u00fcr b\u0131rakt\u0131. Bununla beraber de, Internet Servis Sa\u011flay\u0131c\u0131lar\u0131n\u0131n (ISS) kullan\u0131lmam\u0131\u015f IPv4 adres blo\u011fu bulabilmesini imk\u00e2ns\u0131z k\u0131larken, kalan IPv4 adres alan\u0131n\u0131 verimli de\u011ferlendirmek ve IPv6\u2019ya ge\u00e7i\u015f i\u00e7in bir aksiyon plan\u0131 haz\u0131rlanmas\u0131n\u0131 da gerekli k\u0131lm\u0131\u015ft\u0131r. Bu sorunu \u00e7\u00f6zmek i\u00e7in, hepsi ortak bir ta\u015f\u0131y\u0131c\u0131 s\u0131n\u0131f\u0131 a\u011f ad adres \u00e7evirisi (CGN) temeli \u00fczerine kurulu, NAT444, DS-Lite ve 6rd de dahil olmak \u00fczere bir\u00e7ok teknoloji ortaya \u00e7\u0131km\u0131\u015ft\u0131r.  <\/p>\n\n<h2 class=\"wp-block-heading\">\u00c7\u00f6z\u00fcm<\/h2>\n\n<p>ARK\u0130TEK\u2019in CGNAT \u00e7\u00f6z\u00fcm\u00fc, Ticari Operat\u00f6rler (sabit ve mobil) ve b\u00fcy\u00fck i\u015fletmelerin CGNAT uygulamalar\u0131nda \u2013 \u00e7\u00f6z\u00fcm, tasar\u0131m, \u00f6l\u00e7eklendirme, kurulum, devreye alma, log kay\u0131tlar\u0131n\u0131n saklanmas\u0131 da dahil olmak \u00fczere \u2013 onlara g\u00fcvenilir bir yol sa\u011flar.<\/p>\n\n<p>Not: CGN\u2019e bazen B\u00fcy\u00fck \u00d6l\u00e7ekli NAT (LSN) de denir ve bu sayfada referans verilen IETF belgelerinde kullan\u0131lan terimdir.<\/p>\n\n<h2 class=\"wp-block-heading\" id=\"solution-overview\">Genel Bak\u0131\u015f<\/h2>\n\n<p>CGN, abonelere ve\/veya kullan\u0131c\u0131lara atanan adres kaynaklar\u0131n\u0131 merkezile\u015ftirerek ve bu kaynaklar\u0131 daha b\u00fcy\u00fck bir kullan\u0131c\u0131 toplulu\u011funa payla\u015ft\u0131rarak IPv4 adres blo\u011funu verimli kullanmak i\u00e7in bir y\u00f6ntem sunar. <\/p>\n\n<p>CGN genel mimarisi, bir eri\u015fim a\u011f\u0131ndan (<a rel=\"noreferrer noopener\" href=\"https:\/\/tools.ietf.org\/html\/rfc6598\" target=\"_blank\">RFC 6598<\/a> \u2013 100.64.0.0\/10 blo\u011fundan adreslenmi\u015f), bir agregasyon ve abone sonland\u0131rma katman\u0131ndan, CGN cihazlar\u0131ndan ve kamuya a\u00e7\u0131k Internet\u2019e ba\u011fl\u0131 router\u2019dan olu\u015fmaktad\u0131r. Do\u011frudan eri\u015fim a\u011f\u0131na ba\u011fl\u0131 kurumsal veya bireysel m\u00fc\u015fteriler i\u00e7in, yaln\u0131zca bir seviye NAT (NAT44) yeterlidir. Bu m\u00fc\u015fteriler do\u011frudan 100.64.0.0\/10 alt a\u011f\u0131ndan bir adres al\u0131r. Tipik olarak, bireysel m\u00fc\u015fteriler evlerinde servis sa\u011flay\u0131c\u0131 taraf\u0131ndan sa\u011flanm\u0131\u015f ve NAT yapan bir a\u011f ge\u00e7idi kullanarak, asl\u0131nda NAT444 modelini uygularlar. Bu kullan\u0131c\u0131lar, <a rel=\"noopener\" href=\"\" target=\"\">RFC 1918<\/a> ile tan\u0131mlanm\u0131\u015f IP adres alan\u0131 \u00f6zel (private) adresleri kullan\u0131r.    \u00d6zel adresler, ISS eri\u015fim altyap\u0131s\u0131 i\u00e7inde yap\u0131land\u0131r\u0131lm\u0131\u015f olan 100.64.0.0\/10 alt a\u011f\u0131ndaki adreslere \u00e7evrilir. \u0130stemci (son kullan\u0131c\u0131) trafi\u011fi daha sonra bir toplama katman\u0131 \u00fczerinden CGN cihaz\u0131na y\u00f6nlendirilir ve ard\u0131ndan IPv4 public adres\/port aral\u0131\u011f\u0131na \u00e7evrilir. CGN uygulamas\u0131 son kullan\u0131c\u0131lar i\u00e7in \u015feffaft\u0131r ve (CPE) veya bilgisayarlarda herhangi bir yap\u0131land\u0131rma de\u011fi\u015fikli\u011fi gerektirmez.  <\/p>\n\n<p>CGN, geleneksel NAT i\u015flemlerine g\u00f6re a\u015fa\u011f\u0131daki ek avantajlar\u0131 sa\u011flar:<\/p>\n\n<h3 class=\"wp-block-heading\" id=\"high-transparency\">\u015eeffafl\u0131k<\/h3>\n\n<p>CGN, U\u00e7 Noktadan Ba\u011f\u0131ms\u0131z Atama (EIM), U\u00e7 Noktadan Ba\u011f\u0131ms\u0131z Filtreleme (EIF), adres havuzu olu\u015fturma, hair-pinning ve ba\u011flant\u0131 noktas\u0131 koruma dahil olmak \u00fczere bir NAT ortam\u0131nda kesintisiz bir kullan\u0131c\u0131 deneyimi sa\u011flamak i\u00e7in \u00e7e\u015fitli \u00f6zellikler uygular. T\u00fcm bu \u00f6zellikler, istemcilerin d\u0131\u015f kaynaklara eri\u015fimi i\u00e7in \u015feffaf bir ileti\u015fim ortam\u0131 sa\u011flar, b\u00f6ylece hem istemci-sunucu hem de birebir uygulamalar, abone adreslerinin NAT\u2019land\u0131\u011f\u0131n\u0131 bilmeden, tasarland\u0131klar\u0131 gibi \u00e7al\u0131\u015fmaya devam ederler. <\/p>\n\n<h3 class=\"wp-block-heading\" id=\"well-defined-behaviour\">Well-Defined Behavior<\/h3>\n\n<p>CGN, nas\u0131l \u00e7al\u0131\u015faca\u011f\u0131, a\u015fa\u011f\u0131dakiler de dahil olmak \u00fczere birden fazla IETF RFC\u2019si ve taslaklar\u0131 ile standartla\u015ft\u0131r\u0131lm\u0131\u015f olgun bir teknolojidir:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/tools.ietf.org\/html\/rfc5382\" target=\"_blank\" rel=\"noreferrer noopener\">BEHAVE-TCP (RFC 5382<\/a> ve <a href=\"https:\/\/tools.ietf.org\/html\/rfc7857\" target=\"_blank\" rel=\"noreferrer noopener\">RFC 7857<\/a>)<\/li>\n\n\n\n<li><a href=\"https:\/\/tools.ietf.org\/html\/rfc4787\" target=\"_blank\" rel=\"noreferrer noopener\">BEHAVE-UDP (RFC 4787<\/a> ve <a href=\"https:\/\/tools.ietf.org\/html\/rfc6888\" target=\"_blank\" rel=\"noreferrer noopener\">RFC 6888<\/a>)<\/li>\n\n\n\n<li>BEHAVE-ICMP (RFC 5508)<\/li>\n\n\n\n<li>CGN (draft-nishitani-cgn-05)<\/li>\n<\/ul>\n\n<p>Bu RFC\u2019ler, uygulaman\u0131n \u015feffafl\u0131\u011f\u0131 i\u00e7in sa\u011flam bir temel olu\u015ftururken, gelecekteki uygulamalar\u0131n geli\u015ftirilmesini kolayla\u015ft\u0131rmak i\u00e7in CGN\u2019in davran\u0131\u015flar\u0131n\u0131 da resmile\u015ftirirler. <\/p>\n\n<h3 class=\"wp-block-heading\" id=\"fairness-and-resource-sharing\">Adil Kaynak Payla\u015f\u0131m\u0131<\/h3>\n\n<p>CGN \u00e7\u00f6z\u00fcm\u00fcm\u00fcz, sistem kaynaklar\u0131n\u0131 kontrol etmek i\u00e7in, hem oturum hem de kullan\u0131c\u0131 seviyesinde limitler uygulamaktad\u0131r. Bu, sistem kaynaklar\u0131n\u0131n, servis sa\u011flay\u0131c\u0131n\u0131n gereksinimlerine uygun olarak kullan\u0131c\u0131 taban\u0131na adil bir \u015fekilde da\u011f\u0131t\u0131lmas\u0131n\u0131 sa\u011flar. <\/p>\n\n<h3 class=\"wp-block-heading\" id=\"log-file-size-management\"> G\u00fcnl\u00fck Dosyas\u0131 Boyutu Y\u00f6netimi<\/h3>\n\n<p>CGN uygulamalar\u0131, servis sa\u011flay\u0131c\u0131 a\u011flar\u0131nda b\u00fcy\u00fck miktarda log kay\u0131t verileri olu\u015fturabilir. NAT cihaz\u0131n\u0131n detayl\u0131 konfig\u00fcrasyonu ile, hem g\u00fcnl\u00fck giri\u015flerinin say\u0131s\u0131n\u0131, hem de boyutlar\u0131n\u0131 s\u0131n\u0131rland\u0131rmak i\u00e7in bir\u00e7ok loglama tekni\u011fi uygulanabilir. <\/p>\n\n<h2 class=\"wp-block-heading\" id=\"commercial-references\">Ticari Referanslar<\/h2>\n\n<p>\u00c7\u00f6z\u00fcm\u00fcm\u00fcz, TURKCELL (35M aboneli mobil operat\u00f6r), TURKCELL SUPERONLINE (2M aboneli sabit operat\u00f6r), T\u00fcrk Telekom Mobil (20M aboneli mobil operat\u00f6r), DSMART (400 K aboneli sabit operat\u00f6r) ve Millenicom (200 K aboneli sabit operat\u00f6r) dahil olmak \u00fczere T\u00fcrkiye\u2019deki bir\u00e7ok sabit ve mobil operat\u00f6r altyap\u0131lar\u0131 \u00fczerinde ba\u015far\u0131yla uygulanm\u0131\u015f ve \u00e7al\u0131\u015fmaktad\u0131r.<\/p>\n\n<h2 class=\"wp-block-heading\" id=\"complementary-solutions\">Tamamlay\u0131c\u0131 \u00c7\u00f6z\u00fcmler<\/h2>\n\n<p>Yasal d\u00fczenleyici otorite (ler), operat\u00f6rlerin abonelerine ait adres \u00e7evirimlerini kaydetmelerini, bu verileri abone kimlik bilgileriyle ili\u015fkilendirmelerini ve belirli bir tarihte belirli bir IP adresini (ve port aral\u0131\u011f\u0131n\u0131) kullananan aboneyi tan\u0131mlayabilmeleri i\u00e7in bir arama altyap\u0131s\u0131 sa\u011flamalar\u0131n\u0131 gerektirebilir.<\/p>\n\n<p>Yerel yasalara ve d\u00fczenleyici otorite \u00f6zel gereksinimlerine dayal\u0131 olarak loglama, abone verisi korelasyonu ve arama uygulama altyap\u0131s\u0131 olu\u015fturmak i\u00e7in bize ula\u015fabilirsiniz.<\/p>\n\n<p class=\"more-link\"><a href=\"https:\/\/arkitek.net\/tr\/cozumler\/elektronik-haberlesme\/\">Daha fazla bilgi i\u00e7in<\/a>&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>2011 y\u0131l\u0131nda, \u0130nternet Atanm\u0131\u015f Numaralar Otoritesi (IANA) kalan son \/ 8 adres blo\u011funu B\u00f6lgesel \u0130nternet Kay\u0131tlar\u0131na (RIR) a\u00e7t\u0131 ve RIR\u2019leri mevcut IPv4 adreslerinin geri kalan\u0131n\u0131n da atanmas\u0131 (ve t\u00fcketilmesi) konusunda \u00f6zg\u00fcr b\u0131rakt\u0131. Bununla beraber de, Internet Servis Sa\u011flay\u0131c\u0131lar\u0131n\u0131n (ISS) kullan\u0131lmam\u0131\u015f IPv4 adres blo\u011fu bulabilmesini imk\u00e2ns\u0131z k\u0131larken, kalan IPv4 adres alan\u0131n\u0131 verimli de\u011ferlendirmek ve IPv6\u2019ya ge\u00e7i\u015f &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/arkitek.net\/tr\/cozumler\/elektronik-haberlesme\/carrier-grade-nat\/\" class=\"more-link\">Okumaya devam et<span class=\"screen-reader-text\"> &#8220;Carrier-Grade NAT&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1121,"parent":418,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"inline_featured_image":false,"footnotes":""},"class_list":["post-732","page","type-page","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/pages\/732","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/comments?post=732"}],"version-history":[{"count":0,"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/pages\/732\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/pages\/418"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/media\/1121"}],"wp:attachment":[{"href":"https:\/\/arkitek.net\/tr\/wp-json\/wp\/v2\/media?parent=732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}