Archive

Posts Tagged ‘tunneling’

Akhirnya setelah sekian lama, diajukan juga jadi Judul Penelitian :-)

October 21st, 2011 No comments

IMPLEMENTASI JARINGAN IPV6 PADA JARINGAN LAN (LOCAL AREA NETWORK)

UNIVERSITAS LAMPUNG  DENGAN MEKANISME TUNNELING


ABSTRAK

Kelemahan dari mode pengalamatan  IPv4  adalah terbatasnya  jumlah host yang dapat terhubung ke dalam jaringan, IPv6 sebagai Next Generation Protocol  menawarkan fitur-fitur terbaru dalam teknologi internet seperti real-time flows, provider selection, host mobility, end-to-end security, dan auto-reconfiguration. Sebagai universitas research, Universitas Lampung memandang perlunya agar backbone LAN (Local Area Network) juga support protocol IPv6 berjalan bersamaan dengan IPv4 yang sudah ada. Pada penelitian ini di rancang system jaringan yang mengimplementasikan protokol IPv6 pada teknologi routing BGP (Border Gateway Protocol), aplikasi web server, mail server, proxy server dan aplikasi server-client.

Keyword: IPv6, Tunneling, BGP Peer, Tunnel Broker, Dual Stack

=”http://www.giyimbayilik.com” title=”Giyim Bayilik”>Giyim BayilikKış lastiği fiyatlarıBağcılar elektrik?iGiyim bayilikAdıyamanen yakın elektrik?ifilmi full izleerkek kemer modellerioto ekspertizeba, e okulGiyim Bayilik

Tunneling IPv6 with Ubuntu Linux Behind NAT ? Why Not..

March 31st, 2011 No comments

Source from WIKI:

An IP tunnel is an Internet Protocol (IP) network communications channel between two networks. It is used to transport another network protocol by encapsulation of its packets. IP tunnels are often used for connecting two disjoint IP networks that don’t have a native routing path to each other, via an underlying routable protocol across an intermediate transport network. In conjunction with the IPsec protocol they may be used to create a virtual private network between two or more private networks across a public network such as the Internet. Another prominent use is to connect islands of IPv6 installations across the IPv4 Internet.

 

IP tunnelling encapsulation In IP tunnelling, every IP packet, including addressing information of its source and destination IP networks, is encapsulated within another packet format native to the transit network. At the borders between the source network and the transit network, as well as the transit network and the destination network, gateways are used that establish the end-points of the IP tunnel across the transit network. Thus, the IP tunnel endpoints become native IP routers that establish a standard IP route between the source and destination networks. Packets traversing these end-points from the transit network are stripped from their transit frame format headers and trailers used in the tunnelling protocol and thus converted into native IP format and injected into the IP stack of the tunnel endpoints. In addition, any other protocol encapsulations used during transit, such as IPsec or Transport Layer Security, are removed. IP in IP, sometimes called ipencap, is an example of IP encapsulation within IP and is described in RFC 2003. Other variants of the IP-in-IP variety are IPv6-in-IPv4 (6in4) and IPv4-in-IPv6 (4in6). IP tunneling often bypasses simple firewall rules transparently since the specific nature and addressing of the original datagrams are hidden. Content-control software is usually required to block IP tunnels.

Tulisan diatas saya cuplik dari penjelasan WIKI tentang IP Tunnel yang menjelaskan gambaran umum seperti apa konsep IP Tunnel. pada tulisan sebelumnya saya menulis tentang bagaimana mengimplementasikan metode 6to4 untuk membuat jaringan IPv6 meskipun tidak memiliki Blok IPv6 sendiri. http://gigihfordanama.wordpress.com/2011/03/30/mencoba-sixxs-org-ipv6-gateway/ skim pada tulisan tsb server yang digunakan langsung terhubung ke global IPv4 dan menggunakan sistem operasi FreeBSD 8.0. Nah sekarang kita akan coba bereksperimen bagaimana jika server yang akan dijadikan server tunneling berada dibelakang NAT atau menggunakan IP Private. kita lihat contoh kasus yang saya ujicobakan, dengan topologi sebagai berikut

[(DMZ FIREWALL SERV – WITH IP PUBLIC – OS FREEBSD)/NOC ROOM]  ——–> [FAKULTAS ROUTER] ——> [JURUSAN ROUTER]

202.43.189.222                                ———-       192.168.170.254    ——-  192.168.170.211

Yang perlu dilakukan adalah:

  1. Set rule di FreeBSD-Firewall dengan konfigurasi bidirectional NAT pada paket filter BSD (karena saya tidak mau pusing),contoh skrip /etc/pf.conf binat   on $eIF from 192.168.170.211 to any -> 202.43.189.222 , kenapa saya pilih binat, karena saya akan mapping dari IPPublic ke IP 192.168.170.211 secara bolak balik dan tanpa filter apa apa, sebetulnya yang dibutuhkan untuk membuka servis tunnel cukup hanya dengan menggunakan protocol 41 di pass ke tujuan. Namun karena saya juga butuh untuk yang lain lain juga, makanya firewallnya di buat PLONG kayak jalan Tol.  😀
  2. Yak sudah itu saja, tinggal dibuktikan apakah dari NAT sudah bisa keluar                       .                                                                   elektro@elektro-desktop:~$ ifconfig
    eth0      Link encap:Ethernet  HWaddr d4:85:64:cc:58:23
    inet addr:192.168.170.211  Bcast:192.168.170.255 Read more…

Mencoba tunneling 4to6 , sixxs.org Ipv6 Gateway

March 30th, 2011 No comments

Seperti biasa, buat dulu tunneling ke provider yang menyediakan tunneling IPv6, berhubung di kampus saya masih menunggu approval IPv6 dan ASN dari APNIC, buka alamat http://www.tunnelbroker.net , buat account dan create reguler tunnel. kira kira akan menjadi seperti ini

IPv6 Tunnel Endpoints
Server IPv4 address: 66.220.18.42
Server IPv6 address: 2001:470:c:eb4::1/64
Client IPv4 address: 202.43.189.208
Client IPv6 address: 2001:470:c:eb4::2/64
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver: 2001:470:20::2
Anycasted IPv4 Caching Nameserver: 74.82.42.42
Routed IPv6 Prefixes and rDNS Delegations
Routed /48: Allocate /48
Routed /64: 2001:470:d:eb4::/64
RDNS Delegation NS1: none

Jika sudah terdaftar tinggal create interface tunnel dan membuat route default IPv6, kira kira seperti ini; Read more…