DOCSLIB.ORG

Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Guide Intra-site Automatic Tunnel Addressing Protocol (ISATAP) Guide Microsoft Corporation Abstract The Intra-site Automatic Tunnel Addressing Protocol (ISATAP) in the Microsoft® Windows Server® 2008 R2, Windows Server 2008, Windows 7,and Windows Vista operating systems provides an Internet Protocol version 6 (IPv6) connectivity option for test labs and fortemporary connectivityon an existing Internet Protocol version 4 (IPv4)-only network. This white paper describes how to use ISATAP with Windows-based ISATAP hosts and routers and assumes that the reader has a basic understanding of networking, IPv6, and IPv6 transition technologies. Microsoft® Windows Server® 2008 R2 White Paper The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. © 2010Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Windows, Windows Server, and Windows Vistaare either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners. Microsoft® Windows Server® 2008 R2 White Paper Contents Introduction ........................................................................................................................................ 2 Appropriate Uses for ISATAP on Intranets ......................................................................................... 2 ISATAP in Windows XP and Windows Server 2003 ........................................................................... 2 ISATAP Overview ............................................................................................................................... 3 ISATAP Addressing .......................................................................................................................... 3 Name Resolution for ISATAP Addresses ........................................................................................... 4 ISATAP Router ................................................................................................................................. 5 ISATAP Router Discovery Process .................................................................................................... 5 Intra-ISATAP Subnet Routing ............................................................................................................ 6 Inter-ISATAP Subnet Routing ............................................................................................................ 7 Routing Between ISATAP Hosts and an IPv6-capable Network ......................................................... 8 Configuring ISATAP with Windows-based ISATAP Hosts and Routers ........................................ 10 ISATAP Host Configuration ............................................................................................................. 10 Configuring ISATAP Host Settings Using Group Policy in Windows Server 2008 R2 and Windows 710 ISATAP Router Configuration .......................................................................................................... 11 Advertising and Forwarding ISATAP Router ................................................................................. 12 Summary ........................................................................................................................................... 13 Appendix A ± ISATAP and Active Directory Sites and Services Configuration............................. 14 Related Links .................................................................................................................................... 15 Intra-Site Automatic Tunnel Addressing Protocol Guide 1 Microsoft® Windows Server® 2008 R2 White Paper Introduction IPv6 is the next generation Internet protocol. Although IPv6 has been standardized for over a decade, recent attention has increased because of a decrease in unallocated public IPv4 addresses, a quickly expanding Internet, and a demand for ubiquitous connectivity. The next generation Internet that uses IPv6 promises to enable a new breed of applications. This white paper describes the Intra-site Automatic Tunnel Addressing Protocol (ISATAP) IPv6 transition technology defined in RFC 4214. ISATAP allows the deployment of IPv6 on an existing IPv4-only networking environment without an upgrade to any routers or other support infrastructure. With ISATAP, IPv4-dependent applications can continue to utilize IPv4 while newer applications can be deployed utilizing IPv6. Both types of traffic share a single common IPv4 infrastructure. The benefit of ISATAP is that an existing IPv4-only infrastructure can provide IPv6 connectivity immediately with no requirements for router software or hardware upgrades. Appropriate Uses for ISATAP on Intranets ISATAP in Windows is not designed for production networks.On a production network, ISATAP should be used in a limited capacity for testing while you deploy native IPv6 capabilities. Microsoft does not recommend the use of ISATAP across entire production networks. Instead, you should deploy native IPv6 routing capability. This document describes how ISATAP works and how to configure Windows-based ISATAP hosts and routers for test labs and for IPv6 connectivity testing on production network deployments. ISATAP in Windows XP and Windows Server 2003 Although Windows XP and Windows Server 2003 support ISATAP host and router functionality, most of the built-in applications and system services of these operating systems do not support IPv6. Therefore, Microsoft does not recommend the use of ISATAP for IPv6 connectivity to computers running Windows XP or Windows Server 2003. Intra-Site Automatic Tunnel Addressing Protocol Guide 2 Microsoft® Windows Server® 2008 R2 White Paper ISATAP Overview ISATAP uses a tunneling approach to transport IPv6 traffic across an existing IPv4 infrastructure. ISATAP utilizes an innovative principle in which the whole IPv4 network emulates a single IPv6 logical link or subnet to a set of ISATAP hosts. This principle allows all ISATAP nodes, no matter where they are located on the IPv4 network, to automatically create IPv6 tunnels without having to traverse any IPv6-capable routers. Figure 1 shows a logical ISATAP subnet. Figure 1: A logical ISATAP subnet ISATAP Addressing In ISATAP, the IPv4 address of an ISATAP host is also stored as part of the IPv6 address so that any ISATAP host can determine the IPv4 address of the IPv6-over-IPv4 tunnel endpoint without having to utilize some other protocol. The ISATAP address format is one of the following: 64-bit_Unicast_Prefix:0:5efe:w.x.y.z 64-bit_Unicast_Prefix:200:5efe:w.x.y.z y 64-bit_Unicast_Prefix can be a global, link-local, or unique local unicast address prefix. ISATAP was designed for use within an intranet or autonomy, in which ISATAP logical subnets are IPv6 subnets. y For the interface ID ::0:5efe:w.x.y.z, w.x.y.z is a private IPv4 address that is assigned to an interface of an ISATAP node. For the interface ID ::200:5efe:w.x.y.z, w.x.y.z is a public IPv4 address that is assigned to an interface of an ISATAP node. Examples of ISATAP address are 2001:db8::5efe:10.98.47.117 and 2001:db8::200:5efe:131.107.98.204. ISATAP hosts communicate by tunneling IPv6 packets as the payload of IPv4 packets. There are no pre-established tunnels that are needed. The sending ISATAP host automatically performs the tunneling for each packet as it is sent. The sending ISATAP host determines the IPv4 tunnel endpoint²the destination address in the IPv4 header of the tunneled packet²from the last 32 bits of the next-hop address corresponding to the IPv6 destination address. For example, for traffic to ISATAP hosts on the same logical ISATAP subnet, the IPv4 tunnel endpoint is the last 32 bits (w.x.y.z) of the destination IPv6 address. For traffic to ISATAP or IPv6 hosts that are not Intra-Site Automatic Tunnel Addressing Protocol Guide 3 Microsoft® Windows Server® 2008 R2 White Paper on the same logical ISATAP subnet,
Load more

Recommended publications
  • Routing Loop Attacks Using Ipv6 Tunnels
    Routing Loop Attacks using IPv6 Tunnels Gabi Nakibly Michael Arov National EW Research & Simulation Center Rafael – Advanced Defense Systems Haifa, Israel {gabin,marov}@rafael.co.il Abstract—IPv6 is the future network layer protocol for A tunnel in which the end points’ routing tables need the Internet. Since it is not compatible with its prede- to be explicitly configured is called a configured tunnel. cessor, some interoperability mechanisms were designed. Tunnels of this type do not scale well, since every end An important category of these mechanisms is automatic tunnels, which enable IPv6 communication over an IPv4 point must be reconfigured as peers join or leave the tun- network without prior configuration. This category includes nel. To alleviate this scalability problem, another type of ISATAP, 6to4 and Teredo. We present a novel class of tunnels was introduced – automatic tunnels. In automatic attacks that exploit vulnerabilities in these tunnels. These tunnels the egress entity’s IPv4 address is computationally attacks take advantage of inconsistencies between a tunnel’s derived from the destination IPv6 address. This feature overlay IPv6 routing state and the native IPv6 routing state. The attacks form routing loops which can be abused as a eliminates the need to keep an explicit routing table at vehicle for traffic amplification to facilitate DoS attacks. the tunnel’s end points. In particular, the end points do We exhibit five attacks of this class. One of the presented not have to be updated as peers join and leave the tunnel. attacks can DoS a Teredo server using a single packet. The In fact, the end points of an automatic tunnel do not exploited vulnerabilities are embedded in the design of the know which other end points are currently part of the tunnels; hence any implementation of these tunnels may be vulnerable.
    [Show full text]
  • Allied Telesis Solutions Tested Solution:Ipv6 Transition Technologies
    Allied Telesis Solutions IPv6 Transition Technologies Tested Solution: IPv6 Transition Technologies Moving a network from IPv4 addressing to IPv6 addressing cannot be performed in a single step. The transition necessarily proceeds in stages, with islands of IPv6 developing within the IPv4 network, and gradually growing until they cover the whole network. During this transition process, the islands of IPv6 need to be able to communicate with each other across the IPv4 network. Additionally, it is desirable to be able to transition some network functions across to IPv6 while the majority of the network is still using IPv4. Allied Telesis provides robust solutions for IPv4-to-IPv6 network transitioning, using IPv6 tunneling and dual IPv4/IPv6 network management. The Allied Telesis IPv6 transition technologies integrate seamlessly with the complementary facilities provided within Microsoft server and workstation operating systems. The Allied Telesis IPv6 transition solution will be presented here by a detailed description of an example IPv4/IPv6 hybrid network, consisting of Allied Telesis switches and servers and workstations running various versions of Microsoft Windows Network topology The example network used in this example consists of two sections of IPv4 network, and a section of pure IPv6 network. IPv4 133.27.65.34 v4 router 139.72.129.56/24 Vista 136.34.23.11/24 133.27.65.2 6to4 host/router x600 6to4 relay XP 2002:8B48:8139::10/64 136.34.23.10/24 139.72.129.57/24 2002:8B48:8139:1001::12/64 6to4 host/router IPv6 router Server 2008 2002:8b48:8139:1003::12/642002:8b48:8139:1002::12/64 ISATAP router 2002:8b48:8139:1003::10/64 192.168.2.254 192.168.2.54 IPv6 v4 router Server 2008 192.168.3.254 2002:8b48:8139:1002::10/64 192.168.3.11 IPv4 8000S ISATAP The workstations in the upper IPv4 network are able to communicate using both IPv4 and IPv6.
    [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]
  • S5800 Series Ipv6 Service CLI | FS.COM
    FiberstoreOS IPv6 Service Command Line Reference Contents 1 Tunnel Commands...........................................................................................................................4 1.1 interface..............................................................................................................................................................4 1.2 tunnel mode ipv6ip............................................................................................................................................ 5 1.3 tunnel source...................................................................................................................................................... 6 1.4 tunnel destination...............................................................................................................................................7 1.5 tunnel ttl............................................................................................................................................................. 7 1.6 tunnel dscp......................................................................................................................................................... 8 1.7 ipv6 mtu............................................................................................................................................................. 9 1.8 show interface tunnel....................................................................................................................................... 10 1.9 show
    [Show full text]
  • Security Vulnerabilities of Ipv6 Tunnels
    Security Vulnerabilities of IPv6 Tunnels This article talks about novel security vulnerabilities of IPv6 tunnels – an important type of migration mechanisms from IPv4 to IPv6 implemented by all major operating systems and routers. The vulnerabilities allow an attacker to form routing loops which can easily produce DoS attacks. I will describe the principles of the attack and then show how to actually implement it. The vulnerabilities were first presented at Usenix W00T ’09 in a paper I co-authored with Michael Arov. IPv6 background IPv6 is the next generation version of the omnipresent Internet Protocol. It was designed to answer the future exhaustion of the IPv4 address pool. IPv4 address space is 32 bits which translates to just above 4 billion addresses. IPv6 address space is 128 bits. This roughly translates to the entire address space of the IPv4 for every square nanometer on planet earth (a square nanometer is about the size of a molecule!). The IPv6 specification has been released almost 13 years ago, however it has seen little adoption so far since the IPv4 address space hasn’t depleted yet. But this is about to change very soon. ISPs in Asia-Pacific are already unable to request new IPv4 addresses for their customers. In other regions of the world IPv4 address pools are expected to drain within a year or so. So IPv6 is definitely here to stay. Migration to IPv6 using tunnels As one might imagine the migration to IPv6 will be very gradual. Some estimate that IPv4 and IPv6 will co-exist on the Internet for decades.
    [Show full text]
  • Ipv4 to Ipv6 Transition Mechanism in a Fixed Environment
    الجمهورية اليمنية Republic of Yemen جامعة صنعاء Sanaꞌa University كلية الهندسة Faculty of Engineering قسم الهندسة الكهربائية Electrical Engineering Department IPv4 to IPv6 transition mechanism in a fixed environment: The case of Yemen Abdulsalam Alkholidi, Sanaꞌa University, Faculty of Engineering [email protected] MENOG16 Istanbul Turkey 1 23-24 March 2016 Agenda: Introduction IPv6 in Yemen: a short history Necessity of transition to IPv6 IPv6 Transition Mechanism (TM): Proposed scenarios - Scenario 1: Dual stack mechanism - Scenario 2: Tunneling mechanism - Scenario 3: Static NAT-PT Mechanism Simulation results and discussion - Delay - Throughput - Jitter and latency Challenges and obstacles Conclusions Introduction -1 IPv6 transition mechanisms have become an important issue for most Internet Service Providers (ISPs) to: - Expand IP address space - Increase Internet usage -> increasing demand for IP addresses - Introduce new services for customers - Use the Smart Home Platform. Action plan for the deployment of IPv6 in Yemen is slowly Transition mechanism in Yemen from IPv4 toward IPv6 needs more time to startup seriously Internet density in this country is considered as among the lowest in the Middle East Introduction 2 - Motivation Explore the present status of internet in Yemen Propose scientific solutions based on series of simulations results Describe step by step of proposed transition scenarios Concentrate on analyzing performance proposed scenarios Discuss and share the transition scenarios with MENOG 16 experts Benefit IPv6 as a bigger address space Transition to IPv6 is not possible that quickly as the installed general network infrastructure is IPv4 based Demand co-existence of them and integration between them for a period of time until the process of migration is complete.
    [Show full text]
  • Internet Address Space: Economic Considerations in the Management of Ipv4”, OECD Digital Economy Papers, No
    Please cite this paper as: OECD (2008-06-18), “Internet Address Space: Economic Considerations in the Management of IPv4”, OECD Digital Economy Papers, No. 145, OECD Publishing, Paris. http://dx.doi.org/10.1787/230461618475 OECD Digital Economy Papers No. 145 Internet Address Space ECONOMIC CONSIDERATIONS IN THE MANAGEMENT OF IPV4 OECD DSTI/ICCP(2007)20/FINAL FOREWORD The report provides an analysis of economic considerations associated with the transition from IPv4 to IPv6. It provides background analysis supporting the forthcoming ICCP-organised Ministerial-level meeting on ―The Future of the Internet Economy‖, to take place in Seoul, Korea on 17-18 June 2008. This report was prepared by Ms. Karine Perset of the OECD‘s Directorate for Science Technology and Industry. It was declassified by the ICCP Committee at its 54th Session on 5-7 March 2008. It is published under the responsibility of the Secretary-General of the OECD. This paper has greatly benefited from the expert input of Geoff Huston from APNIC, David Conrad from the IANA, Patrick Grossetête from CISCO Systems, Bill Woodcock from Packet Clearing House, Marcelo Bagnulo Braun from the University of Madrid, Alain Durand from Comcast, and Vincent Bataille from Mulot Déclic, although interpretations, unless otherwise stated, are those of the author. 2 DSTI/ICCP(2007)20/FINAL TABLE OF CONTENTS FOREWORD ................................................................................................................................................... 2 MAIN POINTS ..............................................................................................................................................
    [Show full text]
  • Ipv6 Intranet Intranet/Internet
    How to Securely Operate an IPv6 Network BRKSPG-2603 Eric Vyncke, [email protected] @evyncke Abstract • This intermediate session describes how an IPv6 network can be securely operated. • The session explains how the management, control and data planes can be secured. • It also covers topics such as forensic, telemetry and lawful intercept. • The content is mainly geared to Service Providers but enterprises may also find it useful. • It is targeted to security and network architects with operational background. • There is also enterprise versions of this session BRKSEC-2003 (on-line only) / BRKSEC- 3200 which is more protocol oriented than operational. Beware that there is 30% overlap between BRKSEC-3200 and BRKSPG-2603. 3 Roadmap For IPv6 Security Sessions On www.ciscolive.com BRKSEC-2003 IPv6 Security Threats and Mitigations BRKSPG-2603 How to Securely Operate an IPv6 Network BRKSEC-3003 BRKSEC-3200 Operation Advanced IPv6 Security in Advanced IPv6 Security in the LAN the Core Architecture and design BRKSEC-3036 Advanced IPsec LTRSEC-3001 Advanced - IOS Dual-stack designs with FlexVPN FlexVPN Lab Products 4 IETF OPSEC Working Group 5 For Your Reference For Reference Slides • There are more slides in the hand-outs than presented during the class • Those slides are mainly for reference and are indicated by the book icon on the top right corner (as on this slide) • Some slides have also a call-out to another session (see below) BRKSEC- 3200 6 7 Agenda • Management Plane • Control Plane • Routing Information • Neighbor Discovery • Control
    [Show full text]
  • ETSI White Paper on Ipv6 Best Practices, Benefits, Transition
    ETSI White Paper No. 35 IPv6 Best Practices, Benefits, Transition Challenges and the Way Forward First edition – August 2020 ISBN No. 979-10-92620-31-1 ETSI 06921 Sophia Antipolis CEDEX, France Tel +33 4 92 94 42 00 [email protected] www.etsi.org Contributing organizations and authors CAICT Zhiruo Liu China Telecom Chongfeng Xie, Cong Li Cisco Patrick Wetterwald, Pascal Thubert, Francois Clad Hewlett-Packard Enterprise Yanick Pouffary Huawei Giuseppe Fioccola, Xipeng Xiao, Georgios Karagiannis, Shucheng(Will) Liu KPN Eduard Metz Luxembourg University Latif Ladid PT Telecom Jose Cananao, Jose Palma Post Luxembourg Sébastien Lourdez Telefonica Luis M. Contreras IPv6 Best Practices, Benefits, Transition Challenges and the Way Forward 2 Contents Contributing organizations and authors 2 Contents 3 Executive Summary 6 1 Background 8 1.1 Why should IPv6 become a priority again? 8 1.2 Goals of this White Paper 9 2 IPv6 progress in the last 5 years 10 2.1 Devices supporting IPv6 10 2.2 Content (web sites, cloud services) supporting IPv6 11 2.3 Networks supporting IPv6 12 2.4 Number of IPv6 users 12 2.5 Amount of IPv6 traffic 13 2.6 IPv6 standardization progress 14 3 IPv6 service design for Mobile, Fixed broadband and enterprises 14 3.1 IPv6 transition solutions from operator perspective 15 3.1.1 For IPv6 introduction 16 3.1.2 For IPv6-only service delivery 17 3.2 IPv6 prefix and address assignment at the CPEs 22 3.2.1 For MBB UEs 23 3.2.2 For FBB RGs 23 3.2.3 For Enterprise CPEs 23 3.3 IPv6 Packet Transport 24 3.4 IPv6 deployment inside enterprise
    [Show full text]
  • Deploying Ipv6 in Ipv4 Networks
    Deploying IPv6 in IPv4 networks Marc Blanchet, CTO [email protected] © HEXAGO 2003 www.hexago.com Plan • Application •IP stack •Network – IPv6 transition mechanisms © HEXAGO 2003 :: 2 User-app to User-app • Three pieces – Application –IP stack –Network User Interface Application App Protocol Applications Applications TCP-UDP OS stack OS stack IPv4-IPv6 Network Network © HEXAGO 2003 :: 3 User Interface • Nothing to do except: © HEXAGO 2003 :: 4 Porting Application to IPv6 • Few changes to socket calls – ex: gethostbyname() -> getaddrinfo() • If user may enter/view an IP address – Address: 192.0.2.1 – with IPv6: 3ffe:b00:1:1::1 – URL: http://192.0.2.1:81/intro.html – with IPv6: http://[3ffe:b00:1:1::1]:81/intro.htmlfor most applications, code is localized and small • After porting, the application becomes IP version independent • Application chooses the IP version based on DNS answers © HEXAGO 2003 :: 5 Application Protocol • IP address processing inside the application protocol – New revision of the protocol – Possible signaling needs to be done • Broadcast use -> Multicast – Need to register a multicast address – Some logic to change © HEXAGO 2003 :: 6 Applications • Applications need to be ported – Usually small changes for porting – Then deployed • New applications • One by one application © HEXAGO 2003 :: 7 IP stack • Integrated (or add-on) to operating system • Manage the upgrading to a new version of the operating system that supports IPv6 • Features needed? – Default address selection – Mobility – IP security –etc. © HEXAGO
    [Show full text]
  • Ipv6 Security DREN Networking and Security Conference 2011 August 16, 2011
    IPv6 Security DREN Networking and Security Conference 2011 August 16, 2011 Scott Hogg GTRI - Director of Technology Solutions CCIE #5133, CISSP #4610 8/18/2011 © 2011 Global Technology Resources, Inc. All Rights Reserved. 1 IPv6 Security – Latent Threat • Even if you haven’t started using IPv6 yet, you probably have some IPv6 running on your networks already and didn’t know it • Do you use Linux, Mac OS X, BSD, or Microsoft Vista/Windows 7 systems in your environment? – They all come with IPv6 capability, some even have IPv6 enabled by default (IPv6 preferred) – They may try to use IPv6 first and then fall-back to IPv4 – Or they may create IPv6-in-IPv4 tunnels to Internet resources to reach IPv6 content – Some of these techniques take place regardless of user input or configuration • If you are not protecting your IPv6 nodes then you have just allowed a huge back-door to exist 8/18/2011 © 2011 Global Technology Resources, Inc. All Rights Reserved. 2 IPv6 Security Threats • There isn’t a large hacker community focusing on IPv6 today but it is starting to gain the attacker’s attention • THC IPv6 Attack Toolkit, IPv6 port scan tools, IPv6 packet forgery tools and IPv6 DoS tools all exist and continue to evolve • Many major vendors and open-source software have already published IPv6 bugs/vulnerabilities • Attacks at the layers below and above the network layer are unaffected by the security of IPv6 – Buffer overflows, SQL Injection, cross-site scripting will all remain valid attacks on IPv6 servers – E-mail/SPAM is still a problem in IPv6 nets 8/18/2011 © 2011 Global Technology Resources, Inc.
    [Show full text]
  • Niria Ipv6 Security
    IPv6 Security Aspecten KIVI NIRIA IPv6 themabijeenkomst Frans van Leuven 29/05/2013 29/05/2013 Frans van Leuven Content ▶ Introduction to IPv6 – Basics and terminology – Common misperceptions ▶ Required knowhow – What’s new with IPv6 – Something about transition technologies ▶ IP-security and mitigation • Disabling IPv6? • Controlling deployments of transition technologies • New technology aspects requiring mitigation ▶ Question time 2 29/05/2013 Ways how IPv6 can be implemented Frans van Leuven Also essential for used terminology ▶ Single Stack implementation – Closed community IT applications may be kept on IPv4 till End Of Live ▶ Dual Stack implementation – This is the way to go where possible – Main disadvantage is duplication of various network tasks and activities. ▶ Encapsulating IPv6 in IPv4 or vice versa for transport (=Transition technologies) – Essential for migration and should be understood very well by many ▶ Supporting Network Address Translation including Protocol Translation – If all other options are not possible – Using a Load Balancer may be a better alternative 3 29/05/2013 Using ADC’s for IPv4 <=> IPv6 Frans van Leuven Quick solution for External/Internet access IPv4 Users IPv4 Only Servers WAN IPv4+IPv6 Network ADC with IPv6 Users IPv4 IPv6 Address Mapping 4 29/05/2013 Positive effects of using IPv6 Frans van Leuven More than just a bigger address space ▶ There are several structural improvements coming with IPv6 – It solves the IP-space scalability problem (32 bits 128 bits addressing) – It effectively deals with
    [Show full text]