IPv6

IPv6 adds many improvements to IPv4 in areas such as address space, built-in security, quality of service, routing and network auto-configuration. IPv6 nodes use the Neighbor Discovery (ND) protocol to discover other nodes on the link, to determine their link-layer addresses, to find routers, to detect duplicate address, and to maintain reachability information about the paths to active neighbors. ND is vulnerable to various attacks when it is not secured. The original specifications of ND called for the use of IPsec as a security mechanism to protect ND messages. However, its use is impractical due to the very large number of manually configured security associations needed for protecting ND. For this reason, the Secure Neighbor Discovery Protocol (SEND) was proposed. In this work, we present Easy-SEND, an open source implementation of SEND that can be used in production environment or as a didactic application for the teaching and learning of the SEND protocol. Easy-SEND is easy to install and use, and it has an event logger that can help network administrators to troubleshoot problems or students in their studies. It also includes a tool to generate and verify Cryptographically Generated Addresses (CGA) that are used with SEND.

IPv4 address space will run out in the next two years. Therefore, it is necessary to deploy the new version of the Internet Protocol (IPv6) which dramatically expands the address space. One important issue for IPv6 to gain acceptance, is its end-to-end performance. For this reason, it is important to offer the Internet community some tools to compare IPv4 and IPv6 performance. In this paper, we present some models to evaluate the performance of IPv4 and IPv6. Our models can be used for any variant of Ethernet technologies (10 Mbps, 100 Mbps, or 1000 Mbps). We start by presenting a model for the one-way delay in IPv4 and IPv6. We also develop an upper bound model for IPv4 and IPv6 throughput. To validate our models, we do some experiments and compare the experimental values with the values given by the models. From this research, we can conclude that IPv4 has a better performance than IPv6 (higher throughput), but the differences are small.

Günümüzde İnternetteki hakim protokol olan IPv4’ün artık İnternet üzerindeki ihtiyaçları karşılayamaz hale gelmesi ve birçok konuda eksiklik taşıması sebebiyle, uzunca bir süredir IPv6’lere geçiş konusunda çalışmalar yapılmaktadır. IPv6, özellikle eksikliği hissedilen ihtiyaçlara çözüm bulmakla beraber, yeni ve bilinmeyen bir protokol olarak birçok güvenlik problemi ile de karşı karşıyadır. Ülkemiz açısından düşünüldüğünde, bu problemlerin bir kısmına ilişkin ülkemizin ceza hukuku mevzuatı ve özellikle kişisel verilere ilişkin AB direktifleri ile çare bulunabilir olsa da, esas çözümün bu problemler ortaya çıkmaksızın yapılacak olan çalışmalar olduğu tartışmasızdır.

The exhaustion of IPv4 addresses has forced the deployment of the new version of the Internet Protocol (IPv6). However, the migration to the new protocol is done gradually and with the due care for many reasons that include: cost, inclusion of support for IPv6 in existing applications, training of technical staff, lack of web content available over IPv6 from important providers, and obsolete devices not anymore supported by manufacturers. For those reasons, many transition mechanisms have been proposed, each one to fill distinct requirements, with different operational theory and availability according to the network environment. A performance evaluation of these mechanisms can help network administrators and researchers in their selection of the best transition technology for their environment. In this paper, we present a performance comparison of some transition mechanisms such as ISATAP, 6to4, and NAT64 in real testbeds with Debian, Windows 7, Windows 8, and Windows 10. For NAT64, two different tools were tested: TAYGA and Jool. We measure the OWD and the throughput for UDP and TCP for every mechanism, for both Ethernet and Fast Ethernet technologies. From this research, we can conclude that all the modern operating systems for PCs already have good support for IPv6, and a very similar network performance. Also, we can infer from our work that in controlled environments, native IPv4 has the best performance, closely followed by native IPv6. The difference is essentially due to the length of the IP header (20 bytes in IPv4 and 40 bytes in IPv6). The tunneling solutions chosen for this research (ISATAP and 6to4) have a similar performance, which is the lowest of the studied technologies, because of the additional IPv4 header in the tunnel.

KNX adalah standar terbuka di seluruh dunia untuk rumah dan otomatisasi bangunan, yang berasal dari fieldbus klasik protokol. Kebutuhan untuk berinteraksi dengan Internet of Things (IoT) sudah sebagian ditangani oleh KNX Web Services. KNX Web Service saat ini hanya melayani jaringan KNX IP yang menggunakan IPv4 saja. Makalah ini menjelaskan penggunaan jaringan IPv6 sebagai media KNX. Pendekatan pemetaan yang paling jelas adalah menggunakan KNXnet / IP dengan mekanisme integrasi dari IPv4 ke IPv6 dan solusi untuk beberapa masalah yang mungkin akan muncul. Tujuan utamanya adalah utilisasi fitur IPv6 untuk kemungkinan arsitektur KNX IPv6, dengan harapan menghasilkan peningkatan kinerja dan kompatibilitas dengan standar KNX. Oleh karena itu, beberapa masalah desain inti diangkat dan dibahas dalam makalah ini. Pendekatan pemetaan antara alamat KNX IPv4 dan IPv6 diusulkan untuk memfasilitasi ruang alamat IPv6 yang besar. Selanjutnya, pengenalan multi konektivitas internet yang digunakan dan mobilitas node dengan penggunaan Protokol Locator / ID (LISP) diperiksa. Pertimbangan keamanan diatasi dengan membandingkan KNX IPv4 standar untuk keamanan lapisan jaringan IPSec pada IPv6. 1. Pendahuluan KNX adalah standar komunikasi internasional untuk rumah dan layanan bangunan. Tugas utamanya didedikasikan untuk mendukung otomatisasi dan utilitisasi untuk fungsi yang berbeda, seperti pemanasan, ventilasi, AC dan pencahayaan. Standar KNX adalah dibentuk oleh penggabungan tiga teknologi Eropa yang bersaing, European Installation Bus (EIB), BatiBus, dan European Home System(EHS). Sejak itu, KNX diakui oleh EN dan ISO sebagai standar internasional yang resmi. Konsep inti dari KNX berkembang dari protokol berbasis bus-topologi yang mengurangi upaya pemasangan kabel di gedung fungsional. Munculnya Ethernet dan IP sebagai komoditas umum mendorong integrasi ke dalam jaringan kontrol untuk lebih memudahkan pemantauan dan pengembangan. Oleh karenanya KNXnet / IP dan KNX / IP sub-standar diciptakan untuk memungkinkan pertukaran informasi antara segmen fieldbus yang terisolasi dan selanjutnya untuk mengintegrasikan Protokol IP sebagai media tambahan pada sistem KNX.

Link-Local Multicast Name Resolution (LLMNR) is a zero-configuration networking protocol that permits the resolution of single label name into IP addresses. It is a standard that has been initially proposed by Microsoft and implemented in its operating system for some years now (Windows Vista/7/8/10 and Windows Server 2008/2012/2016). However, it is still rare in other operating systems. In this research work, we implement a Unix-like version of LLMNR (for Linux, FreeBSD, Solaris, etc.) and an LLMNR performance evaluation tool to assess critical parameters and behaviors of this service. Our implementation of LLMNR can be very useful for network administrators that want to install this protocol in computers with an operating system that does not have its own version of the protocol. Using our benchmarking tool, we also compare the performance of our implementation of LLMNR on Debian with the LLMNR system available in Windows 10. Our experiments seem to indicate that our implementation of LLMNR on Debian has a slightly better performance than the one of Microsoft.

Due to the shortage of public IPv4 addresses, the IETF has developed a new version of the Internet Protocol called IPv6. Many institutions all over the world had already started the migration to IPv6. Since this migration has to be done slowly, the first step is the coexistence of the two protocols (IPv4 and IPv6) for some years. One important issue for IPv6 to gain acceptance, is its performance in end-user applications. Hence, due to the availability of a variety of IPv6 implementations on different operating systems, it is important to evaluate the performance of the different IPv6 stacks, and compare it to the one shown by IPv4. In this paper, we present an upper bound model to compute TCP and UDP throughput for IPv4 and IPv6, in a full-duplex point-to-point connection. Our model can be used for any variant of Ethernet technology (10, 100, and 1000Mbps). To validate this model, we did experiments and compared the maximum theoretical throughput with the experimental ones. Experiments were done with Windows XP SP2, Solaris 10, and Debian 3.1, which are very popular operating systems. The results show that 10Mbps Ethernet technology is already very mature, since it gave performance very close to the maximum theoretical throughput. Experiments with FastEthernet (100Mbps) show a TCP and UDP throughput close to the maximum theoretical throughput, especially for large payload. In the case of GigaEthernet (1000Mbps), experimental results are not far from the maximum throughput for large TCP and UDP payload. However, for small TCP and UDP payload, the differences between our model (the maximum throughput) and the experiments are important. These differences should significantly decrease with the release of faster technology (processors and RAM).