{"id":1544,"date":"2018-02-26T02:53:58","date_gmt":"2018-02-25T19:53:58","guid":{"rendered":"https:\/\/www.routecloud.net\/blog\/?p=1544"},"modified":"2018-03-05T16:16:27","modified_gmt":"2018-03-05T09:16:27","slug":"membuat-koneksi-vpn-ipsec-aws-dengan-pfsense","status":"publish","type":"post","link":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/","title":{"rendered":"Membuat Koneksi VPN IPsec AWS Dengan pfSense"},"content":{"rendered":"<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" class=\"size-full\" src=\"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png\" width=\"600\" height=\"370\" \/><\/p>\n<p style=\"text-align: justify;\">Umumnya, server atau instance di AWS diakses menggunakan IP Public (atau hostname yang dipointing ke IP public). Namun selain menggunakan IP Public, kita juga dapat mengakses melalui private IP, namun untuk mengakses instance menggunakan IP private kita harus membuat tunnel terlebih dahulu ke network VPC di AWS. Tunnel-nya bisa menggunakan jalur dedicated line (AWS Direct Connect) atau menggunakan VPN.<\/p>\n<p style=\"text-align: justify;\">Tutorial kali ini akan menjelaskan langkah-langkah membuat koneksi <em>site-to-site VPN<\/em> antara VPC di AWS dengan network diluar AWS menggunakan pfSense.<\/p>\n<p style=\"text-align: justify;\">Topologi di bawah ini adalah contoh implementasi yang akan dibuat.<\/p>\n<p style=\"text-align: justify;\"><strong><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo.png\"><img loading=\"lazy\" class=\"alignnone wp-image-1545 size-full\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo.png\" alt=\"\" width=\"908\" height=\"301\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo.png 908w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo-300x99.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo-768x255.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/topo-200x66.png 200w\" sizes=\"(max-width: 908px) 100vw, 908px\" \/><\/a><\/strong><\/p>\n<p style=\"text-align: justify;\">Agar kedua network dapat berkomunikasi, subnet antara kedua network tersebut tidak boleh overlap. Jika network memiliki CIDR yang overlap maka kamu harus ubah salah satunya agar tidak overlap. Pada tutorial ini, di office network diasumsikan memiliki subnet 192.168.0.0\/24 dibelakang pfSense yang akan dihubungkan dengan AWS VPC 172.31.0.0\/16. Saya tidak akan menjelaskan pembuatan AWS VPC di tutorial ini, jadi diasumsikan bahwa kamu sudah memiliki VPC, dan biasanya di tiap region AWS sudah membuatkan default VPC. Untuk keperluan pengetesan, saya sudah siapkan masing-masing VM\/instance baik di office network maupun di AWS. Nantinya kita akan coba ping dari masing-masing VM untuk mengetahui apakah koneksi VPN berhasil atau tidak.<\/p>\n<p style=\"text-align: justify;\">Okeh langsung mulai aja yuk ikutin tutorialnya di bawah ini :<\/p>\n<p><!--more--><\/p>\n<h3 style=\"text-align: justify;\"><strong>Step 1. Create AWS Customer Gateway<\/strong><\/h3>\n<ol style=\"text-align: justify;\">\n<li>Dari AWS Management Console, masuk ke menu <strong>VPC<\/strong>.<\/li>\n<li>Di bagian VPN Connection, klik <strong>Customer Gateway<\/strong><\/li>\n<li>Pilih <strong>Create Customer Gateway<\/strong><\/li>\n<li>Masukkan nama Customer Gateway, dan di kolom IP Address masukkan IP Public \/ WAN dari pfSense.<br \/>\n<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1.png\"><img loading=\"lazy\" class=\"alignnone wp-image-1546 size-full\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1.png\" alt=\"\" width=\"940\" height=\"368\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1-300x117.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1-768x301.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture1-1-200x78.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<\/ol>\n<h3 style=\"text-align: justify;\"><strong>Step 2. Create Virtual Private Gateway (VPG)<\/strong><\/h3>\n<ol style=\"text-align: justify;\">\n<li>Dari console AWS VPC, klik menu <strong>Virtual Private Gateways<\/strong>.<\/li>\n<li>Pilih <strong>Create Virtual Private Gateway<\/strong><\/li>\n<li>Ketikkan nama VPG-nya, dan di pilihan ASN, pilih <strong>Amazon default ASN<\/strong>.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture2.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1548\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture2.jpg\" alt=\"\" width=\"418\" height=\"160\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture2.jpg 418w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture2-300x115.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture2-200x77.jpg 200w\" sizes=\"(max-width: 418px) 100vw, 418px\" \/><\/a><\/li>\n<li>Pilih VPG yang baru dibuat, lalu pilih menu <strong><strong>Actions &gt; Attach to VPC<\/strong><\/strong><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1549\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1.png\" alt=\"\" width=\"940\" height=\"262\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1-300x84.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1-768x214.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture3-1-200x56.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<li>Pilih VPC AWS Anda yang ingin dikoneksikan ke network luar.<br \/>\n<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1551\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1.png\" alt=\"\" width=\"940\" height=\"319\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1-300x102.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1-768x261.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/Picture4-1-200x68.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<\/ol>\n<h3 style=\"text-align: justify;\"><strong>Step 3. Tambahkan Routing Table<\/strong><\/h3>\n<p style=\"text-align: justify;\">Agar VPC dapat berkomunikasi dengan network lain, maka perlu ditambahkan routing ke network tujuan. Sebenarnya saat VPN sudah established, biasanya network tujuan akan otomatis ditambahkan. Namun berdasarkan pengalaman saya, seringkali networknya tidak otomatis sehingga harus ditambah manual. Jadi agar amannya, lebih baik kita tambahkan saja routingnya dari awal secara manual.<\/p>\n<ol style=\"text-align: justify;\">\n<li>Dari console AWS VPC, klik menu <strong>Route Tables<\/strong>.<\/li>\n<li>Pilih VPC yang diinginkan, lalu klik tab <strong>Routes<\/strong> di bagian bawah.<\/li>\n<li>Klik menu <strong>Edit<\/strong>, lalu klik tombol <strong>Add another route<\/strong><\/li>\n<li>Di bagian <strong>Destination<\/strong>, masukkan CIDR network office, dan dibagian <strong>Target<\/strong> pilih VPG yang sebelumnya dibuat. Jika sudah klik tombol <strong>Save<\/strong>.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-RT.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1552\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-RT.jpg\" alt=\"\" width=\"451\" height=\"384\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-RT.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-RT-300x255.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-RT-200x170.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><\/a><\/li>\n<\/ol>\n<h3 style=\"text-align: justify;\"><strong>Step 4. Create AWS VPN Connection<\/strong><\/h3>\n<ol style=\"text-align: justify;\">\n<li>Masih dari console AWS VPC, pilih menu <strong>VPN Connections<\/strong><\/li>\n<li>Pilih <strong>Create VPN Connection<\/strong>\n<ul>\n<li><strong>Name tag<\/strong> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : Masukkan nama koneksi VPN<\/li>\n<li><strong>Virtual Private Gateway<\/strong> : Pilih VPG yang sebelumnya dibuat.<\/li>\n<li><strong>Customer Gateway<\/strong> : Existing<\/li>\n<li><strong>Customer Gateway ID<\/strong> : Pilih Customer Gateway yang sebelumnya dibuat<\/li>\n<li><strong>Routing Options<\/strong> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : Static<\/li>\n<li><strong>Static IP Prefixes<\/strong> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : Masukkan prefix network tujuanUntuk parameter lain biarkan default. Klik tombol <strong>Create VPN Connection<\/strong> di bagian bawah<br \/>\n<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/aws-createVPN.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1553\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/aws-createVPN.jpg\" alt=\"\" width=\"451\" height=\"307\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/aws-createVPN.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/aws-createVPN-300x204.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/aws-createVPN-200x136.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><\/a><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<ol style=\"text-align: justify;\" start=\"3\">\n<li>Tunggu beberpa saat sampai state profile VPN yang dibuat menjadi \u201c<strong>Available<\/strong>\u201d<\/li>\n<li>Jika sudah available, Klik <strong>Download Configuration<\/strong> untuk mendownload konfigurasi VPN AWS tersebut.\n<ul>\n<li>Vendor : Pilih pfSense<\/li>\n<li>Platform : pfSense<\/li>\n<li>Software : pfSense<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p style=\"text-align: left;\"><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-downloadconf.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1554\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-downloadconf.jpg\" alt=\"\" width=\"451\" height=\"329\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-downloadconf.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-downloadconf-300x219.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-downloadconf-200x146.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Berikut adalah contoh isi file konfigurasi VPN AWS.<\/p>\n<pre class=\"line-height:10 height-set:true lang:default decode:true\">! Amazon Web Services\r\n! Virtual Private Cloud\r\n\r\n! AWS utilizes unique identifiers to manipulate the configuration of \r\n! a VPN Connection. Each VPN Connection is assigned an identifier and is \r\n! associated with two other identifiers, namely the \r\n! Customer Gateway Identifier and Virtual Private Gateway Identifier.\r\n!\r\n! Your VPN Connection ID \t\t  : vpn-53958932\r\n! Your Virtual Private Gateway ID  : vgw-85e91eec\r\n! Your Customer Gateway ID\t\t  : cgw-0c00f765\r\n!\r\n!\r\n! This configuration consists of two tunnels. Both tunnels must be \r\n! configured on your Customer Gateway for redundancy.\r\n!\r\n! --------------------------------------------------------------------------------\r\n! IPSec Tunnel #1\r\n! --------------------------------------------------------------------------------\r\n! #1: Internet Key Exchange (IKE) Configuration\r\n!\r\n! A policy is established for the supported ISAKMP encryption, authentication, Diffie-Hellman, lifetime, \r\n! and key parameters.The IKE peer is configured with the supported IKE encryption,  authentication, Diffie-Hellman, lifetime, and key \r\n! parameters.Please note, these sample configurations are for the minimum requirement of AES128, SHA1, and DH Group 2.\r\n! You will need to modify these sample configuration files to take advantage of AES256, SHA256,  or other DH \r\n! groups like 2, 14-18, 22, 23, and 24.\r\n! Higher parameters are only available for VPNs of category \"VPN,\" and not for \"VPN-Classic\".\r\n! The address of the external interface for your customer gateway must be a static address.\r\n! Your customer gateway may reside behind a device performing network address translation (NAT). To \r\n! ensure that NAT traversal (NAT-T) can function, you must adjust your firewall \r\n! rules to unblock UDP port 4500. If not behind NAT, we recommend disabling NAT-T.\r\n!\r\n!\r\nGo to VPN--&gt;IPSec. Add a new Phase1 entry (click + button )\r\n\r\nGeneral information\r\n a. Disabled : uncheck\r\n b. Key Exchange version :V1\r\n c. Internet Protocol : IPv4\r\n d. Interface : WAN\r\n e. Remote Gateway: 52.6.19.127\r\n f. Description: Amazon-IKE-vpn-53958932-0\r\n \r\n Phase 1 proposal (Authentication)\r\n a. Authentication Method: Mutual PSK\r\n b. Negotiation mode : Main\r\n c. My identifier : My IP address\r\n d. Peer identifier : Peer IP address\r\n e. Pre-Shared Key: 5zo9St7h43QmA_ADXBwlxNPqWPH.CTCF\r\n \r\n Phase 1 proposal (Algorithms)\r\n a. Encryption algorithm : aes128 \r\n b. Hash algorithm :  sha1\r\n c. DH key group :  2\r\n d. Lifetime : 28800 seconds\r\n \r\n Advanced Options\r\n a. Disable Rekey : uncheck\r\n b. Responder Only : uncheck\r\n c. NAT Traversal : Auto\r\n d. Deed Peer Detection : Enable DPD\r\n    Delay between requesting peer acknowledgement : 10 seconds\r\n\tNumber of consecutive failures allowed before disconnect : 3 retries\r\n\t\r\n\t\r\n\r\n! #2: IPSec Configuration\r\n! \r\n! The IPSec transform set defines the encryption, authentication, and IPSec\r\n! mode parameters.\r\n! Please note, you may use these additionally supported IPSec parameters for encryption like AES256 and other DH groups like 2, 5, 14-18, 22, 23, and 24.\r\n! Higher parameters are only available for VPNs of category \"VPN,\" and not for \"VPN-Classic\".\r\n\r\nExpand the VPN configuration clicking in \"+\" and then create a new Phase2 entry as follows:\r\n\r\n a. Disabled :uncheck\r\n b. Mode : Tunnel\r\n c. Local Network : Type: LAN subnet\r\n    Address :  ! Enter your local network CIDR in the Address tab \r\n d. Remote Network : Type : Network \r\n    Address :  ! Enter your remote network CIDR in the Address tab\r\n e. Description : Amazon-IPSec-vpn-53958932-0\r\n \r\n Phase 2 proposal (SA\/Key Exchange)\r\n a. Protocol : ESP\r\n b. Encryption algorigthms :aes128 \r\n  c. Hash algorithms : sha1\r\n  d. PFS key group :   2\r\ne. Lifetime : 3600 seconds \r\n\r\nAdvanced Options\r\n\r\nAutomatically ping host : ! Provide the IP address of an EC2 instance in VPC that will respond to ICMP.\r\n\r\n\r\n! --------------------------------------------------------------------------------\r\n\r\n\r\n! --------------------------------------------------------------------------------\r\n! IPSec Tunnel #2\r\n! --------------------------------------------------------------------------------\r\n! #1: Internet Key Exchange (IKE) Configuration\r\n!\r\n! A policy is established for the supported ISAKMP encryption, authentication, Diffie-Hellman, lifetime, \r\n! and key parameters.The IKE peer is configured with the supported IKE encryption,  authentication, Diffie-Hellman, lifetime, and key \r\n! parameters.Please note, these sample configurations are for the minimum requirement of AES128, SHA1, and DH Group 2.\r\n! You will need to modify these sample configuration files to take advantage of AES256, SHA256,  or other DH \r\n! groups like 2, 14-18, 22, 23, and 24.\r\n! Higher parameters are only available for VPNs of category \"VPN,\" and not for \"VPN-Classic\".\r\n! The address of the external interface for your customer gateway must be a static address.\r\n! Your customer gateway may reside behind a device performing network address translation (NAT). To \r\n! ensure that NAT traversal (NAT-T) can function, you must adjust your firewall \r\n! rules to unblock UDP port 4500. If not behind NAT, we recommend disabling NAT-T.\r\n!\r\n!\r\nGo to VPN--&gt;IPSec. Add a new Phase1 entry (click + button )\r\n\r\nGeneral information\r\n a. Disabled : uncheck\r\n b. Key Exchange version :V1\r\n c. Internet Protocol : IPv4\r\n d. Interface : WAN\r\n e. Remote Gateway: 52.206.12.74\r\n f. Description: Amazon-IKE-vpn-53958932-1\r\n \r\n Phase 1 proposal (Authentication)\r\n a. Authentication Method: Mutual PSK\r\n b. Negotiation mode : Main\r\n c. My identifier : My IP address\r\n d. Peer identifier : Peer IP address\r\n e. Pre-Shared Key: E9brcI2yQVAQS31yu3brCs3HS.SGpucV\r\n \r\n Phase 1 proposal (Algorithms)\r\n a. Encryption algorithm : aes128 \r\n b. Hash algorithm :  sha1\r\n c. DH key group :  2\r\n d. Lifetime : 28800 seconds\r\n \r\n Advanced Options\r\n a. Disable Rekey : uncheck\r\n b. Responder Only : uncheck\r\n c. NAT Traversal : Auto\r\n d. Deed Peer Detection : Enable DPD\r\n    Delay between requesting peer acknowledgement : 10 seconds\r\n\tNumber of consecutive failures allowed before disconnect : 3 retries\r\n\t\r\n\t\r\n\r\n! #2: IPSec Configuration\r\n! \r\n! The IPSec transform set defines the encryption, authentication, and IPSec\r\n! mode parameters.\r\n! Please note, you may use these additionally supported IPSec parameters for encryption like AES256 and other DH groups like 2, 5, 14-18, 22, 23, and 24.\r\n! Higher parameters are only available for VPNs of category \"VPN,\" and not for \"VPN-Classic\".\r\n\r\nExpand the VPN configuration clicking in \"+\" and then create a new Phase2 entry as follows:\r\n\r\n a. Disabled :uncheck\r\n b. Mode : Tunnel\r\n c. Local Network : Type: LAN subnet\r\n    Address :  ! Enter your local network CIDR in the Address tab \r\n d. Remote Network : Type : Network \r\n    Address :  ! Enter your remote network CIDR in the Address tab\r\n e. Description : Amazon-IPSec-vpn-53958932-1\r\n \r\n Phase 2 proposal (SA\/Key Exchange)\r\n a. Protocol : ESP\r\n b. Encryption algorigthms :aes128 \r\n  c. Hash algorithms : sha1\r\n  d. PFS key group :   2\r\ne. Lifetime : 3600 seconds \r\n\r\nAdvanced Options\r\n\r\nAutomatically ping host : ! Provide the IP address of an EC2 instance in VPC that will respond to ICMP.\r\n\r\n\r\n! --------------------------------------------------------------------------------\r\n\r\n\r\n\r\n! Additional Notes and Questions\r\n!  - Amazon Virtual Private Cloud Getting Started Guide: \r\n!       http:\/\/docs.amazonwebservices.com\/AmazonVPC\/latest\/GettingStartedGuide\r\n!  - Amazon Virtual Private Cloud Network Administrator Guide: \r\n!       http:\/\/docs.amazonwebservices.com\/AmazonVPC\/latest\/NetworkAdminGuide\r\n!  - XSL Version: 2009-07-15-1119716\r\n<\/pre>\n<p>File konfigurasi tersebut berisi beberapa informasi penting yang kita butuhkan untuk konfigurasi di sisi pfSense, seperti IP remote gateway AWS dan pre-shared key untuk Phase 1.<\/p>\n<p>&nbsp;<\/p>\n<h3 style=\"text-align: justify;\"><strong>Step 5. Buat Konfigurasi IPsec di pfSense<\/strong><\/h3>\n<ol style=\"text-align: justify;\">\n<li>Pilih web GUI pfSense, pilih menu <strong>VPN &gt; IPsec<\/strong><\/li>\n<li>Klik menu <strong>Add P1<\/strong>. Masukkan parameter seperti gambar di bawah ini.<br \/>\nNote : untuk kolom <em>Remote Gateway<\/em> dan <em>Pre-Shared Key<\/em> sesuaikan dengan yang ada di file konfigurasi yang sebelumnya didownload.<\/li>\n<\/ol>\n<p><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1.jpg\"><img loading=\"lazy\" class=\"alignnone wp-image-1559\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1.jpg\" alt=\"\" width=\"495\" height=\"306\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-300x186.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-200x124.jpg 200w\" sizes=\"(max-width: 495px) 100vw, 495px\" \/><\/a><br \/>\n<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-2.jpg\"><img loading=\"lazy\" class=\"alignnone wp-image-1560\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-2.jpg\" alt=\"\" width=\"491\" height=\"317\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-2.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-2-300x194.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-2-200x129.jpg 200w\" sizes=\"(max-width: 491px) 100vw, 491px\" \/><\/a><\/p>\n<ul>\n<li>Setelah disimpan, klik menu <strong>Show Phase 2 &gt; Add P2<\/strong> di konfigurasi Phase 1 yang sudah dibuat.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-3-1.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1562\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-3-1.jpg\" alt=\"\" width=\"451\" height=\"193\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-3-1.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-3-1-300x128.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p1-3-1-200x86.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><\/a><\/li>\n<li>Masukkan parameter Phase 2 seperti gambar di bawah ini.\n<ul>\n<li>Untuk pilihan <strong>Local Network<\/strong>, kamu juga bisa memilih \u201cLAN Network\u201d. Namun berdasarkan pengalaman, beberapa kali routing tidak tembus padahal status IPsec sudah established. Jadi saran saya sebaiknya pilih Network dan masukkan subnet LAN manual.<\/li>\n<li>Untuk pilihan <strong>Remote Network<\/strong>, masukkan CIDR AWS VPC kamu.<\/li>\n<li>Untuk bagian <strong>Automatically Ping Host<\/strong>, kamu bisa masukkan IP instance AWS kamu, namun bisa juga kamu kosongkan karena ini optional.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-general.jpg\"><img loading=\"lazy\" class=\"alignnone wp-image-1563\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-general.jpg\" alt=\"\" width=\"495\" height=\"290\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-general.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-general-300x176.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-general-200x117.jpg 200w\" sizes=\"(max-width: 495px) 100vw, 495px\" \/><\/a><br \/>\n<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-key.jpg\"><img loading=\"lazy\" class=\"alignnone wp-image-1564\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-key.jpg\" alt=\"\" width=\"492\" height=\"339\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-key.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-key-300x207.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-key-200x138.jpg 200w\" sizes=\"(max-width: 492px) 100vw, 492px\" \/><\/a>\u00a0<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1567\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv.jpg\" alt=\"\" width=\"451\" height=\"88\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv-300x59.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv-200x39.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<ol style=\"text-align: justify;\" start=\"5\">\n<li>Klik menu <strong>Apply Changes<\/strong> untuk menyimpan konfigurasi IPSec<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1565\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-p2-adv.jpg\" alt=\"\" width=\"451\" height=\"88\" \/><\/a><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1569\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save.png\" alt=\"\" width=\"940\" height=\"374\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save-300x119.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save-768x306.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-save-200x80.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<li>Tambahan : Berdasarkan beberapa dokumentasi yang saya baca, ada parameter tambahan yang dapat diubah untuk meningkatkan reliability IPsec, yaitu MSS. Untuk mengubah parameter MSS, klik tab <strong>Advanced Settings<\/strong>, lalu masukkan angka <strong>1387<\/strong> di kolom <strong>Maximum MSS.<\/strong><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-advance.jpg\"><img loading=\"lazy\" class=\"alignnone wp-image-1566\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-advance.jpg\" alt=\"\" width=\"509\" height=\"397\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-advance.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-advance-300x234.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-advance-200x156.jpg 200w\" sizes=\"(max-width: 509px) 100vw, 509px\" \/><\/a><\/li>\n<\/ol>\n<h3 style=\"text-align: justify;\"><strong>Step 5. Start pfSense IPsec Service for AWS<\/strong><\/h3>\n<ol style=\"text-align: justify;\">\n<li>Dari web GUI pfSense, pilih menu <strong>Status &gt; IPsec<\/strong><\/li>\n<li>Pilih konfigurasi IPsec yang sebelumnya dibuat, lalu klik pilihan <strong>Connect VPN<\/strong>.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-start.jpg\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1568\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-start.jpg\" alt=\"\" width=\"451\" height=\"131\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-start.jpg 451w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-start-300x87.jpg 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-start-200x58.jpg 200w\" sizes=\"(max-width: 451px) 100vw, 451px\" \/><br \/>\n<\/a><\/li>\n<li>Jika koneksi berhasil, maka status IPsec akan berubah menjadi <em>ESTABLISHED<\/em> seperti gambar di bawah ini.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1570\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est.png\" alt=\"\" width=\"940\" height=\"267\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est-300x85.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est-768x218.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-ipsec-est-200x57.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<li>Status VPN di AWS juga akan berubah menjadi <em>UP<\/em>.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status.png\"><img loading=\"lazy\" class=\"alignnone wp-image-1571\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status.png\" alt=\"\" width=\"790\" height=\"239\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status-300x91.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status-768x232.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/awsvpn-vpn-status-200x60.png 200w\" sizes=\"(max-width: 790px) 100vw, 790px\" \/><\/a><\/li>\n<\/ol>\n<p style=\"text-align: justify;\">Note : Saya pernah beberapa mengalami kasus dimana status IPsec di pfSense sudah established namun di AWS masih DOWN. Jika hal ini terjadi, pastikan konfigurasi Phase 1 dan Phase 2 sudah benar terutama di bagian LOCAL dan REMOTE network.<\/p>\n<h3 style=\"text-align: justify;\"><strong>Step 6. Create Firewall Rule<\/strong><\/h3>\n<p style=\"text-align: justify;\">Meskipun network sudah terhubung, kita masih harus menambahkan rule firewall agar traffic yang diinginkan dapat lewat. Firewall rule ini harus dibuat baik disisi pfSense maupun di <em>AWS Security Group<\/em>. Di tutorial ini saya tidak akan menjelaskan cara konfigurasi AWS Security Group melainkan hanya firewall rule di pfSense saja.<\/p>\n<ol style=\"text-align: justify;\">\n<li>Pilih menu <strong>Firewall &gt; Aliases<\/strong>.<br \/>\nDisini saya menggunakan alias firewall agar memudahkan penamaan dan agar lebih mudah mengingat rule tersebut. Ketikkan nama serta Network VPC AWS seperti contoh di gambar berikut ini :<\/li>\n<\/ol>\n<p><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1572\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias.png\" alt=\"\" width=\"940\" height=\"528\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias-300x169.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias-768x431.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-alias-200x112.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/p>\n<ul>\n<li>Tambahkan rule IPSec melalui menu <strong>Firewall &gt; Rules &gt; IPsec<\/strong>. Klik tombol Add<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1573\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1.png\" alt=\"\" width=\"940\" height=\"369\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1-300x118.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1-768x301.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-1-200x79.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<li>Silahkan atur firewall sesuai kebutuhan. Disini saya akan melewatkan (<em>Pass<\/em>) semua protocol baik dari network AWS ke subnet LAN, oleh karena itu <strong>Action<\/strong> kita pilih <em>Pass<\/em> dan <strong>Source<\/strong> ketikkan network <em>VPC AWS<\/em> atau masukkan nama alias yang sudah dibuat sebelumnya. Untuk <strong>Destination<\/strong> pilih <em>LAN<\/em>.<a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2.png\"><img loading=\"lazy\" class=\"alignnone size-full wp-image-1574\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2.png\" alt=\"\" width=\"940\" height=\"715\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2-300x228.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2-768x584.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/pfsense-firewall-rule-2-200x152.png 200w\" sizes=\"(max-width: 940px) 100vw, 940px\" \/><\/a><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3 style=\"text-align: justify;\"><strong>Step 6. Testing Connection<\/strong><\/h3>\n<p style=\"text-align: justify;\">Untuk memastikan bahwa koneksi VPN sudah berhasil dan traffic sudah tembus, kita coba lakukan Ping dari server di Local LAN ke server di AWS dan sebaliknya menggunakan IP private masing-masing server.<\/p>\n<ul style=\"text-align: justify;\">\n<li><strong>Ping dari Office LAN ke AWS<\/strong><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1.png\"><img loading=\"lazy\" class=\"alignnone wp-image-1575\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1.png\" alt=\"\" width=\"576\" height=\"224\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1.png 940w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1-300x117.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1-768x299.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi1-200x78.png 200w\" sizes=\"(max-width: 576px) 100vw, 576px\" \/><\/a><\/li>\n<li><strong>Ping dari AWS ke Office LAN<\/strong><a href=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2.png\"><img loading=\"lazy\" class=\"alignnone wp-image-1576\" src=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2.png\" alt=\"\" width=\"565\" height=\"226\" srcset=\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2.png 933w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2-300x120.png 300w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2-768x307.png 768w, https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2018\/02\/testkoneksi2-200x80.png 200w\" sizes=\"(max-width: 565px) 100vw, 565px\" \/><\/a><\/li>\n<\/ul>\n<p style=\"text-align: justify;\">Selamat!! Networknya sudah konek brooo\u2026..<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify;\"><strong>Note : \u00a0<\/strong><\/p>\n<p style=\"text-align: justify;\">Biar gak kaget kalau ada tagihan VPN yang besar, sedikit informasi saja kalau untuk koneksi VPN di AWS, customer akan dikenakan tarif sebagai berikut :<\/p>\n<ul>\n<li style=\"text-align: justify;\">$0.05 per VPN Connection per hour<\/li>\n<li style=\"text-align: justify;\">Standard AWS data transfer<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; Umumnya, server atau instance di AWS diakses menggunakan IP Public (atau hostname yang dipointing ke IP public). Namun selain menggunakan IP Public, kita juga dapat mengakses melalui private IP, namun untuk mengakses instance menggunakan IP private kita harus membuat tunnel terlebih dahulu ke network VPC di AWS. Tunnel-nya bisa menggunakan jalur dedicated line (AWS [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[137,136],"tags":[140,139,107],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v18.5.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog\" \/>\n<meta property=\"og:description\" content=\"&nbsp; Umumnya, server atau instance di AWS diakses menggunakan IP Public (atau hostname yang dipointing ke IP public). Namun selain menggunakan IP Public, kita juga dapat mengakses melalui private IP, namun untuk mengakses instance menggunakan IP private kita harus membuat tunnel terlebih dahulu ke network VPC di AWS. Tunnel-nya bisa menggunakan jalur dedicated line (AWS [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/\" \/>\n<meta property=\"og:site_name\" content=\"Routecloud Indonesia - Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-02-25T19:53:58+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-03-05T09:16:27+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png\" \/>\n<meta name=\"twitter:card\" content=\"summary\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ilmi Aji\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/#organization\",\"name\":\"Routecloud Indonesia\",\"url\":\"https:\/\/www.routecloud.net\/blog\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/#logo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2017\/03\/logo_routecloud_horz_2x_b.png\",\"contentUrl\":\"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2017\/03\/logo_routecloud_horz_2x_b.png\",\"width\":400,\"height\":80,\"caption\":\"Routecloud Indonesia\"},\"image\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/#website\",\"url\":\"https:\/\/www.routecloud.net\/blog\/\",\"name\":\"Routecloud Indonesia - Blog\",\"description\":\"Share Your Knowledge\",\"publisher\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.routecloud.net\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png\",\"contentUrl\":\"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage\",\"url\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/\",\"name\":\"Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage\"},\"datePublished\":\"2018-02-25T19:53:58+00:00\",\"dateModified\":\"2018-03-05T09:16:27+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.routecloud.net\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Membuat Koneksi VPN IPsec AWS Dengan pfSense\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage\"},\"author\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/#\/schema\/person\/e759e5ef104b873a3b893c3f37f31437\"},\"headline\":\"Membuat Koneksi VPN IPsec AWS Dengan pfSense\",\"datePublished\":\"2018-02-25T19:53:58+00:00\",\"dateModified\":\"2018-03-05T09:16:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage\"},\"wordCount\":1025,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png\",\"keywords\":[\"amazon web service\",\"aws\",\"vpn\"],\"articleSection\":[\"Amazon Web Services (AWS)\",\"Cloud Computing\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/#\/schema\/person\/e759e5ef104b873a3b893c3f37f31437\",\"name\":\"Ilmi Aji\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.routecloud.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5c9b6af97a9e398d7738ed8c1d0912ab?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5c9b6af97a9e398d7738ed8c1d0912ab?s=96&d=mm&r=g\",\"caption\":\"Ilmi Aji\"},\"url\":\"https:\/\/www.routecloud.net\/blog\/author\/ilmi\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/","og_locale":"en_US","og_type":"article","og_title":"Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog","og_description":"&nbsp; Umumnya, server atau instance di AWS diakses menggunakan IP Public (atau hostname yang dipointing ke IP public). Namun selain menggunakan IP Public, kita juga dapat mengakses melalui private IP, namun untuk mengakses instance menggunakan IP private kita harus membuat tunnel terlebih dahulu ke network VPC di AWS. Tunnel-nya bisa menggunakan jalur dedicated line (AWS [&hellip;]","og_url":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/","og_site_name":"Routecloud Indonesia - Blog","article_published_time":"2018-02-25T19:53:58+00:00","article_modified_time":"2018-03-05T09:16:27+00:00","og_image":[{"url":"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png"}],"twitter_card":"summary","twitter_misc":{"Written by":"Ilmi Aji","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Organization","@id":"https:\/\/www.routecloud.net\/blog\/#organization","name":"Routecloud Indonesia","url":"https:\/\/www.routecloud.net\/blog\/","sameAs":[],"logo":{"@type":"ImageObject","@id":"https:\/\/www.routecloud.net\/blog\/#logo","inLanguage":"en-US","url":"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2017\/03\/logo_routecloud_horz_2x_b.png","contentUrl":"https:\/\/www.routecloud.net\/blog\/wp-content\/uploads\/2017\/03\/logo_routecloud_horz_2x_b.png","width":400,"height":80,"caption":"Routecloud Indonesia"},"image":{"@id":"https:\/\/www.routecloud.net\/blog\/#logo"}},{"@type":"WebSite","@id":"https:\/\/www.routecloud.net\/blog\/#website","url":"https:\/\/www.routecloud.net\/blog\/","name":"Routecloud Indonesia - Blog","description":"Share Your Knowledge","publisher":{"@id":"https:\/\/www.routecloud.net\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.routecloud.net\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"ImageObject","@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage","inLanguage":"en-US","url":"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png","contentUrl":"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png"},{"@type":"WebPage","@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage","url":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/","name":"Membuat Koneksi VPN IPsec AWS Dengan pfSense - Routecloud Indonesia - Blog","isPartOf":{"@id":"https:\/\/www.routecloud.net\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage"},"datePublished":"2018-02-25T19:53:58+00:00","dateModified":"2018-03-05T09:16:27+00:00","breadcrumb":{"@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.routecloud.net\/blog\/"},{"@type":"ListItem","position":2,"name":"Membuat Koneksi VPN IPsec AWS Dengan pfSense"}]},{"@type":"Article","@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#article","isPartOf":{"@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage"},"author":{"@id":"https:\/\/www.routecloud.net\/blog\/#\/schema\/person\/e759e5ef104b873a3b893c3f37f31437"},"headline":"Membuat Koneksi VPN IPsec AWS Dengan pfSense","datePublished":"2018-02-25T19:53:58+00:00","dateModified":"2018-03-05T09:16:27+00:00","mainEntityOfPage":{"@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#webpage"},"wordCount":1025,"commentCount":2,"publisher":{"@id":"https:\/\/www.routecloud.net\/blog\/#organization"},"image":{"@id":"https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#primaryimage"},"thumbnailUrl":"https:\/\/d1.awsstatic.com\/security-center\/ExternalCloudSecurityAWS.2d07fb2e44160a8b950339e61eb82972c5865113.png","keywords":["amazon web service","aws","vpn"],"articleSection":["Amazon Web Services (AWS)","Cloud Computing"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.routecloud.net\/blog\/membuat-koneksi-vpn-ipsec-aws-dengan-pfsense\/#respond"]}]},{"@type":"Person","@id":"https:\/\/www.routecloud.net\/blog\/#\/schema\/person\/e759e5ef104b873a3b893c3f37f31437","name":"Ilmi Aji","image":{"@type":"ImageObject","@id":"https:\/\/www.routecloud.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/secure.gravatar.com\/avatar\/5c9b6af97a9e398d7738ed8c1d0912ab?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5c9b6af97a9e398d7738ed8c1d0912ab?s=96&d=mm&r=g","caption":"Ilmi Aji"},"url":"https:\/\/www.routecloud.net\/blog\/author\/ilmi\/"}]}},"_links":{"self":[{"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/posts\/1544"}],"collection":[{"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/comments?post=1544"}],"version-history":[{"count":11,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/posts\/1544\/revisions"}],"predecessor-version":[{"id":1623,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/posts\/1544\/revisions\/1623"}],"wp:attachment":[{"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/media?parent=1544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/categories?post=1544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.routecloud.net\/blog\/wp-json\/wp\/v2\/tags?post=1544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}