DOCSLIB.ORG

Using PMTUD for a Higher DNS Responsiveness

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using PMTUD for a Higher DNS Responsiveness University of Amsterdam System and Network Engineering Research Project 1 Making do with what we've got: Using PMTUD for a higher DNS responsiveness Authors: Supervisors: Hanieh Bagheri Willem Toorop [email protected] [email protected] Victor Boteanu Benno Overeinder [email protected] [email protected] February 28, 2013 Abstract The goal of this research project is to find out if ICMPv6 Packet Too Big (PTB) messages can be used to improve a name server's responsiveness. Path MTU Discovery (PMTUD) is a mechanism used to signal the sender that its packet does not fit in the MTU of a link along its path. The sender receives a PTB message, which contains the MTU of the next link. In IPv6, the ICMPv6 PTB also contains as much of the original packet that would fit on the next link. A DNS response includes the question that generated the response. However, DNS name servers are stateless and do not remember the queries that generated the response. Once a question has been answered, it is forgotten. A client would have to timeout and requery the server to get the answer. The aim of this research is to make use of the information in ICMPv6 PTB messages to give a sense of state to name servers, and resend the response to the client. This would improve the responsiveness of the name server, as it does not have to wait for the client to time out and resend the query. Three solutions of using PTBs are presented in this report, and we covered the effects they would have if implemented. Packet captures provided by SURFnet and SIDN are analyzed to provide statistical data from real name servers. A test implementation of one of the solutions is performed using the RIPE Atlas network, and observations are made on the results. The main conclusion of this paper is that PTB messages do contain enough information to be used by name servers to resend the response to the client. 1 Contents 1 Introduction 4 1.1 Research objective . 5 1.2 Research question . 5 1.3 Related work . 6 1.4 Outline . 6 2 Background concepts 7 2.1 Fragmentation: IPv4 vs IPv6 . 7 2.2 PMTUD . 8 2.3 ICMPv6 . 8 2.3.1 Packet Too Big . 8 2.3.2 Time Exceeded Message . 9 3 Real-world observations 11 3.1 SURFnet packet captures . 12 3.2 SIDN packet captures . 15 3.3 RIPE Atlas experiment . 16 4 Proposed solutions 19 4.1 Solution 1 - TC bit solution . 19 4.2 Solution 2 - Resubmit query . 19 4.3 Solution 3 - Resubmit query with EDNS0 . 19 4.4 Implications . 20 4.5 Implementation . 21 5 Test and results 22 6 Conclusion 23 7 Future work 23 A Abbreviations 24 2 List of Figures 1 Effect of response size on its status over UDP . 4 2 DNS response . 9 3 Packet Too Big message format . 9 4 Path MTU Discovery . 10 5 RIPE Atlas network of probes . 11 6 Probes used in experiment . 17 7 Atlas Probe PMTU . 17 8 Implementation of second solution . 22 List of Tables 1 SURFnet name servers IPv4/IPv6 ratio . 12 2 SURFnet response sizes . 13 3 SURFnet large response . 14 4 SURFnet fragmented responses . 14 5 SURFnet fragment payload length . 14 6 SURFnet ICMPv6 . 15 7 SIDN response sizes . 15 8 SIDN DNSSEC response sizes . 15 9 SIDN fragment payload length . 16 10 SIDN ICMPv6 messages . 16 3 1 Introduction he Domain Name System (DNS) is an essential component of the current Internet. It T is responsible for associating information, such as IP addresses, with domain names. DNS normally uses User Datagram Protocol (UDP) as the transport layer protocol. UDP is an "stateless" and "unreliable" protocol, in that it does not implement acknowledge- ments or retransmission. By using UDP, DNS is relatively fast, and if a client does not get a response in due time, it can query the server again, or try a different server. The classical DNS protocol limits the response size over UDP to 512 bytes. When a response does not fit in the available size, it will be truncated. In this case the TC flag in the response is set and the client should resend the query over TCP. Original DNS Does not have any security mechanism to prevent forging the source or the contents of the response. The Domain Name System Security Extensions (DNSSEC) is introduced to provide authenticity and origin integrity. DNSSEC causes the zone information to be cryptographically signed. Those cryptographic signatures are conveyed in the responses, resulting into larger responses. With the growing trend towards using DNSSEC (especially after the root zones being signed in 2010), we expect larger DNS responses to become more frequent. The Extension mechanisms for DNS (EDNS) introduced (among others) a mechanism for DNS clients and servers to agree on a larger response size over UDP. With EDNS, the name servers are allowed to exchange larger responses over UDP. The immediate effect of having large DNS messages over UDP is the possibility of frag- mentation. Every link in the Internet is capable of transmitting packets with a certain size, which is called Maximum Transmission Unit (MTU). Packets larger than this limit must be fragmented before being sent over that link. As shown in Figure 1, using UDP, when the response is smaller than the size defined in EDNS option, but it is not small enough to be sent as a single network packet, it has to be fragmented. Figure 1: Effect of response size on its status over UDP Although fragmentation addresses the issue with large DNS responses that are sent over UDP, the client-side firewalls might filter fragments [1]. In IPv6, routers are not allowed to fragment the packets. Fragmentation must be done by the end hosts. Those end hosts have to do Path MTU Discovery (PMTUD) to find out the smallest MTU in the path towards the destination. In the PMTUD process, the source sends a packet into the network. If the packet encounters a router with a smaller MTU, it is dropped and an ICMPv6 PTB is sent back to the source. There is a similar message in IPv4, called 4 "ICMP fragmentation needed". The main difference between the ICMPv6 PTB and its corresponding message in IP4 is that in the former, in addition to the passable MTU by the router, it contains the trimmed part of the original message. So looking at the PTB, one can see the part of the message that can traverse the path trough the router. 1.1 Research objective In this research, we are interested in leveraging the extra payload in ICMPv6 to increase responsiveness of name servers in the case of having large responses. The advantage of ICMPv6 PTB, which makes it helpful for our problem is that it contains the first part of the payload of the dropped message, which can fit into the minimum MTU supported by all IPv6 routers (1280 bytes). Having the returned ICMPv6 PTB, the server would be able to find out the original query, in addition to the appropriate MTU size. In this research, we will explore several approaches to utilize this information. 1.2 Research question This project is mainly aimed to answer the following question: Is it feasible to leverage the original packet payload in ICMPv6 to increase a name server responsiveness? The sub-questions that will be answered in this report will be: What strategies can be applied and what effects and risks would they have? How would this be best implemented? What is the impact of fragmentation and PMTUD on the performance/responsiveness of DNS servers? 5 1.3 Related work Previous research related to the topic of this project has been done by Maikel de Boer and Jeffrey Bosma, on the IPv6 Path MTU black holes, caused by ICMPv6 filters or fragment filters [1]. They made use of the RIPE Atlas network in order to find ICMPv6 filters or fragment filters, which cause IPv6 Path MTU black holes. Their research is relevant to our project, because it gives us information regarding IP fragment filtering, which is one of the issues that we have to take into consideration for this project. In a recent research by Gijs van den Broek et. al. [4], real-world resolvers are moni- tored to analyze their behavior, when dealing with fragmented DNS responses. In this work, two server-side solutions are offered and tested to prevent the responses from being fragmented. The idea in the first solution is to set the maximum response size to 1232 bytes. The second solution is more complicated. It needs to implement a module for dynamically adjusting the EDNS size option in queries related to the resolvers behind fragment-filtering firewalls. There is an Internet-draft written by Mark Andrews [5], mentioning that PMTUD does not work well with the stateless DNS, because there is no automatic mechanism for handling PTB messages in name servers. He recommends to enable IPV6 USE MIN MTU socket option in IPv6 to fragment packets at the minimum IPv6 MTU, instead of using PMTUD. In other words, the name servers are encouraged to fragment the responses at the smallest possible size, in order to avoid receiving PTB messages. 1.4 Outline The core concepts of fragmentation and PMTUD are presented in Section 2. Packet Too Bid and Fragment Reassembly Time Exceeded messages are discussed in Subsection 2.3 and we describe their importance to this research. In section 3, we describe the resources that were used. The packet captures from SURFnet and SIDN are treated in separate subsections, as well as the initial RIPE Atlas experiment.
Load more

Recommended publications
  • Network Layer 2
    Network Layer Topics • Network service models • Datagrams (packets), virtual circuits • IP (Internet Protocol) • Internetworking • Forwarding (Longest Matching Prefix) • Helpers: ARP and DHCP • Fragmentation and MTU discovery • Errors: ICMP (traceroute!) • IPv6, scaling IP to the world • NAT, and “middleboxs” • Routing Algorithms CSE 461 University of Washington 2 Dynamic Host Configuration Protocol (DHCP) Bootstrapping •Problem: • A node wakes up for the first time … • What is its IP address? What’s the IP address of its router? • At least Ethernet address is on NIC What’s my IP? CSE 461 University of Washington 4 Bootstrapping 1. Manual configuration (old days) • Can’t be factory set, depends on use 2. DHCP: Automatically configure addresses • Shifts burden from users to IT folk What’s my IP? Use A.B.C.D CSE 461 University of Washington 5 DHCP •DHCP (Dynamic Host Configuration Protocol), from 1993, widely used •It leases IP address to nodes •Provides other parameters too • Network prefix • Address of local router • DNS server, time server, etc. CSE 461 University of Washington 6 DHCP Protocol Stack •DHCP is a client-server application • Uses UDP ports 67, 68 DHCP UDP IP Ethernet CSE 461 University of Washington 7 DHCP Addressing •Bootstrap issue: • How does node send a message to DHCP server before it is configured? •Answer: • Node sends broadcast messages that delivered to all nodes on the network • Broadcast address is all 1s • IP (32 bit): 255.255.255.255 • Ethernet/MAC (48 bit): ff:ff:ff:ff:ff:ff CSE 461 University of Washington
    [Show full text]
  • The GINI Router
    The GINI Router: A Routing Element for User-level Micro Internet by Weiling Xu DEPARTMENT OF COMPUTER SCIENCE MCGILL UNIVERSITY, MONTREAL JUNE,2004 A THESIS SUBMITTED TO MCGILL UNIVERSITY IN PARTIAL FULFILMENT OF THE REQUlREMENTS OF THE DEGREE OF MASTER OF SCIENCE © Weiling Xu 2004 Library and Bibliothèque et 1+1 Archives Canada Archives Canada Published Heritage Direction du Branch Patrimoine de l'édition 395 Wellington Street 395, rue Wellington Ottawa ON K1A ON4 Ottawa ON K1A ON4 Canada Canada Your file Votre référence ISBN: 0-494-06476-5 Our file Notre référence ISBN: 0-494-06476-5 NOTICE: AVIS: The author has granted a non­ L'auteur a accordé une licence non exclusive exclusive license allowing Library permettant à la Bibliothèque et Archives and Archives Canada to reproduce, Canada de reproduire, publier, archiver, publish, archive, preserve, conserve, sauvegarder, conserver, transmettre au public communicate to the public by par télécommunication ou par l'Internet, prêter, telecommunication or on the Internet, distribuer et vendre des thèses partout dans loan, distribute and sell th es es le monde, à des fins commerciales ou autres, worldwide, for commercial or non­ sur support microforme, papier, électronique commercial purposes, in microform, et/ou autres formats. paper, electronic and/or any other formats. The author retains copyright L'auteur conserve la propriété du droit d'auteur ownership and moral rights in et des droits moraux qui protège cette thèse. this thesis. Neither the thesis Ni la thèse ni des extraits substantiels de nor substantial extracts from it celle-ci ne doivent être imprimés ou autrement may be printed or otherwise reproduits sans son autorisation.
    [Show full text]
  • Guidelines for the Secure Deployment of Ipv6
    Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks NIST Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 December 2010 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Dr. Patrick D. Gallagher, Director GUIDELINES FOR THE SECURE DEPLOYMENT OF IPV6 Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-119 Natl. Inst. Stand. Technol. Spec. Publ. 800-119, 188 pages (Dec. 2010) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • RFC 6349 Testing with Truespeed™ from JDSU—Experience Your
    RFC 6349 Testing with TrueSpeed™ from JDSU— Experience Your Network as Your Customers Do RFC 6349 is the new transmission control protocol (TCP) throughput test methodology that JDSU co-authored along with representatives from Bell Canada and Deutsche Telecom. Recently issued by the Internet Engineering Task Force (IETF) organization, RFC 6349 provides a repeatable test method for TCP throughput analysis with systematic processes, metrics, and guidelines to optimize the network and server performance. This application note summarizes RFC 6349, “Framework for TCP Throughput Testing,” and highlights the automated and fully compliant JDSU RFC 6349 implementation, TrueSpeed, now available on the JDSU T-BERD®/MTS-6000A Multi-Services Application Module (MSAM) and T-BERD/MTS-5800 Handheld Network Tester. This application note also discusses the integration of TrueSpeed RFC 6349 with the ITU Y.1564 Ethernet service activation standard. This powerful testing combination provides a comprehensive means to ensure an optimized end-customer experience in multi-service (such as triple play) environments. RFC 6349 TCP Test Methodology RFC 6349 specifies a practical methodology for measuring end-to-end TCP throughput in a managed IP network with a goal of providing a better indication of the user experience. In the RFC 6349 framework, TCP and IP parameters are also specified to optimize TCP throughput. RFC 6349 recommends always conducting a Layer 2/3 turn-up test before TCP testing. After verifying the network at Layer 2/3, RFC 6349 specifies conducting
    [Show full text]
  • The PTB-PTS ICMP-Based Attack Against Ipsec Gateways Vincent Roca, Saikou Fall
    Too Big or Too Small? The PTB-PTS ICMP-based Attack against IPsec Gateways Vincent Roca, Saikou Fall To cite this version: Vincent Roca, Saikou Fall. Too Big or Too Small? The PTB-PTS ICMP-based Attack against IPsec Gateways. 2016, pp.16. hal-01178390 HAL Id: hal-01178390 https://hal.inria.fr/hal-01178390 Submitted on 19 Jul 2015 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. IPsec Maintenance and Evolution (IPSECME) V. Roca Internet-Draft S. Fall Intended status: Informational INRIA Expires: January 7, 2016 July 6, 2015 Too Big or Too Small? The PTB-PTS ICMP-based Attack against IPsec Gateways draft-roca-ipsecme-ptb-pts-attack-00 Abstract This document introduces the "Packet Too Big"-"Packet Too Small" Internet Control Message Protocol (ICMP) based attack against IPsec gateways. We explain how an attacker having eavesdropping and packet injection capabilities, from the unsecure network where he only sees encrypted packets, can force a gateway to reduce the Path Maximum Transmission Unit (PMTU) of an IPsec tunnel to the minimum, which can trigger severe issues for the hosts behind this gateway: with a Linux host, depending on the PMTU discovery algorithm in use (i.e., PMTUd versus PLPMTUd) and protocol (TCP versus UDP), the attack either creates a Denial of Service or major performance penalties.
    [Show full text]
  • Exploring Usable Path MTU in the Internet
    Exploring usable Path MTU in the Internet Ana Custura Gorry Fairhurst Iain Learmonth University of Aberdeen University of Aberdeen University of Aberdeen Abstract—To optimise their transmission, Internet endpoints methodologies and tools [7] [8], providing an up-to-date need to know the largest size of packet they can send across PMTUD behaviour report for both IPv4 and IPv6. a specific Internet path, the Path Maximum Transmission Unit We include an in-depth exploration of server and client (PMTU). This paper explores the PMTU size experienced across the Internet core, wired and mobile edge networks. advertised Maximum Segment Size (MSS), taking advantage Our results show that MSS Clamping has been widely deployed of existing measurement platforms, MONROE [9] and RIPE in edge networks, and some webservers artificially reduce their Atlas [10], and using or extending existing tools Netalyzr [11] advertised MSS, both of which we expect help avoid PMTUD and PATHspider [12]. failure for TCP. The maximum packet size used by a TCP We also look at ICMP quotation health and analyze a connection is also constrained by the acMSS. MSS Clamping was observed in over 20% of edge networks tested. We find a large number of ICMP quotations from a previous large- significant proportion of webservers that advertise a low MSS scale measurement campaign. These results provide important can still be reached with a 1500 byte packet. We also find more insight to inform the design of new methods that can robustly than half of IPv6 webservers do not attempt PMTUD and clamp discover the PMTU for UDP traffic where there are currently the MSS to 1280 bytes.
    [Show full text]
  • ICMP Attacks Against TCP
    ICMP attacks against TCP Author: Fernando Gont Email: [email protected] http:/ /www.gont.com.ar Universidad Tecnológica Nacional February 200 6 Internet -Draft / ICMP attacks against TCP OWASP Papers Program February , 2006 Table of Contents Abstract .............................................................................................................................................. 3 A1 Introduction........................................................................................................................... 4 A2 Background ............................................................................................................................ 5 A2.1 The Internet Control Message Protocol (ICMP) .................. 5 2.1.1 ICMP for IP version 4 (ICMP) ................................ ...... 5 2.1.2 ICMP for IP version 6 (ICMPv6) ................................ .... 5 A2.2 Handli ng of ICMP error messages ............................... 6 A3 Constraints in the possible solutions ................................................................................... 7 A4 General counter -measures against ICMP attacks ............................................................. 8 A4.1 TCP sequence number checking ................................ .. 8 A4.2 Port randomization ................................ ............ 8 A4.3 Fil tering ICMP error messages based on the ICMP payload ....... 9 A5 Blind connection-reset attack ............................................................................................
    [Show full text]
  • On Improved Generalization of 5-State Hidden Markov Model-Based Internet Traffic
    On Improved Generalization of 5-State Hidden Markov Model-based Internet Traffic Classifiers by Grant H. R. Bartnik A Thesis presented to The University of Guelph In partial fulfilment of requirements for the degree of Master of Science in Computer Science Guelph, Ontario, Canada c Grant H. R. Bartnik, May, 2013 ABSTRACT On Improved Generalization of 5-State Hidden Markov Model-based Internet Traffic Classifiers Grant H. R. Bartnik Advisors: University of Guelph, 2013 Dr. Stefan C. Kremer The multitude of services delivered over the Internet would have been diffi- cult to fathom 40 years ago when much of the initial design was being undertaken. As a consequence, the resulting architecture did not make provisions for differentiating between, and managing the potentially conflicting requirements of different types of services such as real-time voice communication and peer-to-peer file sharing. This shortcoming has resulted in a situation whereby services with conflicting require- ments often interfere with each other and ultimately decrease the effectiveness of the Internet as an enabler of new and transformative services. The ability to passively identify different types of Internet traffic then would address this shortcoming and enable effective management of conflicting types of services, in addition to facilitating a better understanding of how the Internet is used in general. Recent attempts at developing such techniques have shown promising results in simulation environments but perform considerably worse when deployed into real-world scenarios. One possi- ble reason for this descrepancy can be attributed to the implicit assumption shared by recent approaches regarding the degree of similarity between the many networks which comprise the Internet.
    [Show full text]
  • Experttcp™ - TCP Throughput Testing (Per RFC-6349)
    ExpertTCP™ - TCP Throughput Testing (per RFC-6349) 818 West Diamond Avenue - Third Floor, Gaithersburg, MD 20878 Phone: (301) 670-4784 Fax: (301) 670-9187 Email: [email protected] Website: http://www.gl.com 1 Outline • Background ➢ RFC-2544, Y.1564 (SAM), RFC-6349, SLA • TCP Principles ➢ TCP Throughput Inter-Relationships ➢ Bandwidth * Delay Product ➢ Bottleneck Bandwidth (BB) ➢ TCP Congestion Window (TCP CWND) and TCP Receive Window (RWND) ➢ Packet Loss Rate ➢ Retransmission Schemes (Go Back N, Selective Repeat) • GL Hardware Platforms 2 Outline.. • TCP Throughput Measurement ➢ Path MTU Discovery ➢ Round Trip Time Measurement ➢ Measure TCP Throughput • Screenshot • Video 3 Background Performance Testing of Packet / Ethernet Connections and Networks For Predictable • RFC-2544 Service Level Agreements Managed Networks from Network Providers, a • ITU Y.1564 (SAM) must • RFC-6349 (TCP) User Experience, Application-Network SAM – Service Activation Methodology Sensitive, TCP Tuning TCP – Transmission Control Protocol 4 Background Packet / Ethernet Testing User Experience • End-to-End Throughput • Network Throughput • Latency • Packet Loss • Back-to-Back • Jitter 5 Background Typical SLA Typically Packet Loss 0.0005 % to 1% Latency 36 to 75 ms Availability 99% to 99.9% 6 Background RFC-2544 vs. ITU Y.1564 (SAM) Both are Connection-less • Throughput • Latency • Frame Loss • Back-to-Back • Jitter 7 Background RFC-2544 Testing Dual Port RFC-2544 Single Port RFC-2544 RFC-2544 test application includes the following tests: • Throughput - Maximum number of frames per second that can be transmitted without any error • Latency - Measures the time required for a frame to travel from the originating device through the network to the destination device.
    [Show full text]
  • VPN Ipsec Tunnels with Cisco ASA/Asav VTI on Oracle Cloud Infrastructure
    Deploying VPN IPSec Tunnels with Cisco ASA/ASAv VTI on Oracle Cloud Infrastructure O R A C L E SOLUTION GUIDE | M A R C H 2 0 1 8 | VERSION 1.1 Table of Contents Overview 4 Scope and Assumptions 4 VPN IPSec Tunnel Concepts 5 CPE Configuration 5 General Requirements for Connecting to the Oracle Cloud Infrastructure DRG via IPSec 6 Establish the IKE Security Association Using Pre-Shared Keys 6 Establish the IPSec Security Association 6 Use AES 256-Bit Encryption 6 Use the SHA-1 or SHA-256 Hashing Function 6 Use Diffie-Hellman with Perfect Forward Secrecy 7 IPSec Dead Peer Detection 7 Bind Tunnel to Logical Interface (Route-Based VPN) 7 Fragment IP Packets Before Encryption 8 Recommendations for TCP Maximum Segment Size and DF Flags 8 Data Lifetime Rekey Interval 9 VPN IPSec Tunnels on Oracle Cloud Infrastructure 9 Key Components of VPN IPSec Tunnels on OCI 10 Access Requirements for VPN IPSec Tunnels Configuration 13 Configure the VPN IPSec 14 Step 1: Create a VCN 15 Step 2: Create the DRG 16 Step 3: Attach the DRG to the VCN 17 Step 4: Modify the Default Route Table for the VCN 17 Step 6: Edit the Default Security List for the Subnet 18 2 | DEPLOYING VPN IPSEC TUNNELS WITH CISCO ASA/ASAV VTI ON ORACLE CLOUD INFRASTRUCTURE Step 7: Create a Subnet 19 Step 8: Create a CPE Object 21 Step 9: Create an IPSec Tunnel Between the DRG and CPE 22 Step 10: Verify the IPSec Tunnels 23 Summary 24 Configure the ASA/ASAv On-Premises Device 25 Step 1: Note All the Values Used in the ASA/ASAv Configuration 25 Step 2: Configure the IKE and IPSec Policy and IPSec Profile 26 Step 3: Set Up Some IPSec and Tunnel Friendly Parameters 27 Step 4: Configure the Tunnel Group 28 Step 5: Configure the VTI 28 Step 6: Configure the Static Routes 29 Step 7: Verify That the Tunnels Are Up on Oracle Cloud Infrastructure 31 Sample ASA/ASAv Configuration File from this Document 31 Conclusion 33 3 | DEPLOYING VPN IPSEC TUNNELS WITH CISCO ASA/ASAV VTI ON ORACLE CLOUD INFRASTRUCTURE Overview This guide provides step-by-step instructions for configuring VPN IPSec tunnels on Oracle Cloud Infrastructure.
    [Show full text]
  • Performance Modeling, Design and Analysis of Transport Mechanisms in Integrated Heterogeneous Wireless Networks
    Performance Modeling, Design and Analysis of Transport Mechanisms in Integrated Heterogeneous Wireless Networks by Humphrey Rutagemwa A thesis presented to the University of Waterloo in fulfillment of the thesis requirement for the degree of Doctor of Philosophy in Electrical and Computer Engineering Waterloo, Ontario, Canada, 2007 © Humphrey Rutagemwa, 2007 I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. ii Abstract Recently, wireless access to Internet applications and services has attracted a lot of attention. However, there is no single wireless network that can meet all mobile users’ requirements. Con- sequently, integrated heterogeneous wireless networks are introduced to meet diverse wireless Internet applications and services requirements. On the other hand, integrated heterogeneous wireless networks pose new challenges to the design and development of reliable transport mechanisms. Wireless Application Protocol version 2 (WAP 2.0) is one of the promising trans- port mechanisms. It uses wireless profiled TCP (WP-TCP), which is fully compatible with TCP, as one of the reliable transport protocols to cope with the wireless link impairments. For WAP 2.0 to continue providing reliable and efficient transport services in the future, one of the key is- sues is to thoroughly study, understand, and improve its performance in integrated heterogeneous wireless networks. In this thesis, we develop analytical frameworks and propose a solution to respectively study and improve the performance of WP-TCP in integrated heterogeneous wireless networks.
    [Show full text]
  • Development of Secure Ipsec Tunnelling in a Mobile IP Architecture
    Development of Secure IPsec Tunnelling in a Mobile IP Architecture Vincent Pau Supervisor: Assoc. Prof. Ray Hunt 10 November 2005 Abstract Internet Protocol security (IPsec) is a widely accepted standard for securing IP network traffic but has limited functionality in a Mobile IP environment. The aim of this research is to develop a solution that enables mobile nodes to handoff IPsec tunnels in a transparent manner when moving between different networks. Previous researches suggest two general approaches to solving this problem: to run IPsec over Mobile IP, or to dynamically update the IPsec tunnel endpoints. As part of this research, we proposed a variation of the latter approach, whereby Mobile IP registration messages are used to update the IPsec tunnel endpoints. The solution enables a mobile node to establish an IPsec tunnel once and maintain the tunnel across handoffs. A testbed was developed for evaluating the performance of the various approaches under different handoff conditions. The proposed solution was implemented and tested successfully on the testbed, proving its feasibility. The study also compares the performance of the proposed solution against running IPsec over Mobile IP, and the current approach of re-establishing new IPsec tunnels. Although the proposed solution is more complex compared to running IPsec over Mobile IP, the results show that it is more efficient in terms of bandwidth overhead. The results also show that the proposed solution has a lower handoff delay compared to the current approach of re-establishing new IPsec tunnels. Acknowledgements I would like to take this opportunity to express my gratitude to all those who have made the completion of this report possible.
    [Show full text]