<p>Internet is growing every day and this is leading to an address depletion of the current IPv4 addresses. A new version of IPv4, called IPv6, is the protocol for addressing computers that will deal with this problem. IPv4 and IPv6 are unfortunately not compatible with each other. IPv4 and IPv6 have to co-exist for a long time until IPv6 will be the dominant protocol.</p><p>The purpose of this thesis is to examine how a transition could be done or more correctly, how to deploy IPv6 in an already existing IPv4 network. After that part of the report a case study at the local Internet service provider Junet AB will be conducted. This case study will investigate an IPv6 deployment scenario for Junet AB.</p><p>A theoretical background has been written that describes some steps an Internet service provider has to go through to deploy IPv6. The case study was conducted after the theoretical background was written. The result of this report shows that a deployment of IPv6 in an IPv4 network is technically achievable. All the main components to maintain and use IPv6 in a commercial network exist.</p><p>The case study indicates that it is possible to deploy IPv6 in Junet AB´s network. IPv4 and IPv6 could be used in their network without any major effort. IPv6 have been around for many years now but have not had that break through many early adopters have hoped for. A lack of documentation and experience is an obstacle for a deployment of IPv6.One thing that remains now is to prove that there is a need for IPv6, but that is out of scope for this thesis.</p>

Internet is growing every day and this is leading to an address depletion of the current IPv4 addresses. A new version of IPv4, called IPv6, is the protocol for addressing computers that will deal with this problem. IPv4 and IPv6 are unfortunately not compatible with each other. IPv4 and IPv6 have to co-exist for a long time until IPv6 will be the dominant protocol. The purpose of this thesis is to examine how a transition could be done or more correctly, how to deploy IPv6 in an already existing IPv4 network. After that part of the report a case study at the local Internet service provider Junet AB will be conducted. This case study will investigate an IPv6 deployment scenario for Junet AB. A theoretical background has been written that describes some steps an Internet service provider has to go through to deploy IPv6. The case study was conducted after the theoretical background was written. The result of this report shows that a deployment of IPv6 in an IPv4 network is technically achievable. All the main components to maintain and use IPv6 in a commercial network exist. The case study indicates that it is possible to deploy IPv6 in Junet AB´s network. IPv4 and IPv6 could be used in their network without any major effort. IPv6 have been around for many years now but have not had that break through many early adopters have hoped for. A lack of documentation and experience is an obstacle for a deployment of IPv6.One thing that remains now is to prove that there is a need for IPv6, but that is out of scope for this thesis.

Den här rapporten tog sin början i det faktum att många företag och organisationer idag inte är insatta i vad IPv6 innebär och hur de ska gå tillväga för att implementera IPv6. Det fanns vid tillfället ingen komplett metod för hur en analys av ett nätverk gick till, vad som var viktigt att tänka på, vilka tekniker som fanns tillgängliga och hur dessa implementerades. För att underlätta framtida övergångar till IPv6 bestämde vi oss för att utveckla en generell metod som användaren kan följa och läsa sig till vad de behöver tänka på vid varje steg. Metoden ger också exempel på hur användaren kan göra analyser och undersökningar som leder fram till en lösning som kan fungera för deras behov. Metoden besvarade frågeställningen ”Vad behöver ett företag göra för att kunna implementera IPv6 i en existerande nätverksmiljö?” Övergången till IPv6 är igång och många tekniker är inte färdigutvecklade. För att ta fram lösningar som fungerar för olika scenarier gjordes efterforskningar på både IP version fyra och version sex samt vilka övergångs-tekniker som är att rekommendera. Ett antal övergångs-tekniker valdes ut och sattes upp i ett testlabb där IPv6-funktionaliteten verifierades. För att ta fram en metod som täckte upp de vanligaste scenarierna diskuterades frågan med Empir AB, ett företag som arbetar med IT-lösningar och som tillhandahåller egna tjänster. Deras nätverk analyserades och det arbetet låg till grund för utformningen av metoden. Eftersom alla tekniker i metoden testades i laborations-nätverket fastställdes IPv6-funktionalitet genom att testa olika tjänster över nätverket. Testerna visade att det var fullt möjligt att implementera IPv6 efter en steg för steg-modell. Resultatet av arbetet kan användas för att initiera och fullfölja en övergång till IPv6 då användaren har en metod att följa, rekommendationer på vad som behöver göras och föreslagna lösningar som kan implementeras enligt anvisningar. / This report began with the fact that many companies and organizations today do not have any or little knowledge about IPv6 and what it means, nor do they know how to implement it. At the time of writing there were no complete method for how an analysis of a network were done, what was important to think on and which techniques were available. To ease future transitions to IPv6, we decided to develop a general method that a user could follow step by step, with instructions for what to think on at each step. The method also gives examples on how the user could do an analysis and examinations, and it eventually leads to a solution based on their needs. The method answers the question "what does a company need to do to be able to implement IPv6 in an already existing network?" The transition to IPv6 is happening and many techniques is still in development. To be able to present solutions that work with different needs, research in IP version four, version six and in transfer techniques were done as well. A set of transfer techniques was chosen and set up in a lab network where IPv6 functionality was verified. To develop a method that covered most of the common scenarios, the question were discussed with Empir AB, a company that works with IT solutions that hosts their own services. Their network was analyzed and the result was the foundation for the method. Since all techniques in the method were tested in the lab network, the IPv6 functionality was verified by testing different services over the network. The tests showed that it was possible to implement IPv6 after a step by step model. The result of this work can be used to initiate and follow through with a transition to IPv6 since the user have a method to follow, recommendations to what needs to be done and proposed solutions that can be implemented after instructions.

OMNeT++ is a discrete-event simulator commonly used to build various network simulations. It can be extended by INET framework that supplies models of protocols and devices from TCP/IP environment. This paper explores current capabilities of INET to model IPv6, particularly routing. Implemented extension includes modules of dual-stack router and dual-stack host that support XML-based configuration of IPv6 addressing and static routing. We also introduce an OSPFv3 module that implements most of auxiliary features and is ready for future development of the routing protocol core.

Made available in DSpace on 2016-04-04T18:31:39Z (GMT). No. of bitstreams: 1 Deivis Fernandes Pirani.pdf: 1504986 bytes, checksum: e4989c06d3fc9c76df085862e18609d0 (MD5) Previous issue date: 2014-02-07 / This paper shows a field-trial investigation comparing the use of IPv4 and IPv6 protocols on web pages access considering the real user perspective and the transition period from IPv4 to IPv6. To perform this study, it was developed a testbed in which three adressing configurations of Internet Protocol, IPv4, IPv6, and Duas Stack (IPv4+IPv6), were used to access the top 100 world most visited web pages with an IPv6 enabled address. In addiction, several software tools were developed, that enabled more than 600 simultaneous accesses between IPv4, IPv6 and Dual Stack, to each of these pages. Those accesses were performed every hour during the period of a month, enabling to obtain more than 20 GB of information on the web access. Results showed that lower loading times obtained by IPv6 and Dual Stack are related to the partial acquisition of the content. In fact, for IPv6, the number of web pages with faster loading times goes from 57 to 20% when the average number of bytes obtained by IPv6 and the IPv4 is similar. For Dual Stack the number goes from 25 to 5% given the same conditions. It was also noted that 18 of the 100 pages which were considered, no content would be presented to the user in more than 50% of the performed accesses. Regarding the preference for IPv6 instead of IPv4, on Dual Stack it was observed that 90% of the acquired content for 27 of 100 web pages was made by IPv6. / Este trabalho apresenta um estudo de campo, comparativo, sobre a utiliza??o dos protocolos IPv4 e IPv6 no acesso a p?ginas web. Foi considerada a perspectiva de um usu?rio real deste tipo de servi?o, no atual per?odo de transi??o do IPv4 para o IPv6. Para que tal estudo pudesse ser realizado, foi desenvolvido um arranjo no qual tr?s configura??es de endere?amento do Protocolo de Internet, IPv4, IPv6 e Pilha Dupla (IPv4+IPv6), foram utilizadas nos acessos ?s 100 p?ginas web, com suporte ao I v6, mundialmente mais visitadas. Al?m disso, foram desenvolvidas uma s?rie de shell scripts que possibilitaram mais de 600 acessos simult?neos do IPv4, IPv6 e Pilha Dupla, a cada uma dessas p?ginas. Tais acessos foram executados de hora em hora, durante o per?odo de um m?s, possibilitando a obten??o de mais de 20 GB de informa??es relativas ao acesso web. Os resultados do estudo mostraram que os tempos de carregamento menores obtidos pelo IPv6 e pela Pilha Dupla, est?o relacionados com a aquisi??o parcial do conte?do. De fato, para o IPv6, o n?mero de p?ginas web com tempos de carregamento menores diminui de 57 para 20% quando a m?dia do n?mero de bytes obtidos pelo IPv6 e pelo IPv4 ? similar. Para a Pilha Dupla, dadas as mesmas condi??es, o n?mero diminui de 25 para 5%. Tamb?m foi observado que para 18 das 100 p?ginas web consideradas, nenhum conte?do foi apresentado ao usu?rio em mais de 50% dos acessos efetuados. Com rela??o ? prefer?ncia pelo IPv6 ao IPv4, na Pilha Dupla, observou-se que 90% da aquisi??o do conte?do, de 27 das 100 p?ginas web, ocorreu pelo IPv6.