標題: 校園IPv6實驗網:架構、運作與經驗
On Campus IPv6 Beta Site: Architecture, Operations and Lessons
作者: 柯瑞固
Kulkarni Raghavendra Manohar
林盈達
Lin, Ying-Dar
網路工程研究所
關鍵字: 實驗網,雙堆疊,真實的IPv6測試平台,評估,穩定性,功能性,一致性;Betasite, dual stack, real IPv6 testbed, evaluation, stability, functionality, conformance
公開日期: 2010
摘要: Betasite測試是一種用來驗證新網路產品效能與品質的測試架構。從目前網際網路發展的趨勢來看,從IPv4轉換到IPv6是必然的趨勢。因此,在IPv6網路產品能夠正式被商業化之前,這些產品有需要透過一種測試環境並以真實的網路流量來驗證其品質。本篇論文的目的想要深入研究實作IPv6測試環境時會遇到的困難並利用此測試環境來找出各種網路產品的缺陷。我們在國立交通大學的校園網路中設計了一個針對IPv6架構的Betasite,利用校園中的網路流量來幫助廠商測試各種網路產品,幫助使用者可以輕易地存取IPv6網路,並且也幫助校園網路管理者可以擷取與分析IPv6流量的特性。對於廠商而言,我們建立了一個由數個test zone所組成的測試環境,來測試各種類型的網路產品。對於使用者而言,我們在校園網路拓樸中佈設了一個雙堆疊(dual stack)機制。而對於校園網路管理者而言,我們建立了一個快速網路修復機制。在我們的IPv6 Betasite測試平台中,待測物 (DUT)的路由(routing)與通道建立(tunneling)功能都已經經過為期一年的測試。在這個測試當中,我們辨識出五個OS-level,四個function level,兩個kernel level和一個conformance level的缺陷。大部分所觀察到的網路產品缺陷是由於協定實作和裝置設定上的問題。
Betasite testing represents a typical clinical trial, the results of which are used to validate new network devices. In view of the present Internet situation, transitioning from IPv4 towards IPv6 is inevitable. Hence, before IPv6 network devices can be transformed into commercial products, testing them under the environment of real network flow becomes essential. The purpose of carrying out this work was to understand the intricacies in IPv6 implementation with a view to spot the weak points. We design and deploy an IPv6 Betasite on the campus of National Chiao Tung University, Hsinchu, Taiwan, for vendors to test different kinds of network devices; for users to easily transfer to IPv6 network and for network administrators to capture and analyze IPv6 traffic. For vendors, we establish environments such as an array of test zones for testing different types of network devices. For ease of operation to the users, we employ the dual stack mechanism in our campus network topology. For network administrators we establish mechanisms of speedy network recovery. In our IPv6 Betasite testbed, addressing, routing, tunneling and administrator supporting test cases were designed and tested for the duration of one year. In these tests, we identified 5 OS-level, 4 function level, 2 kernel level and one conformance level defects. Most of the defects were due to protocol implementation issues and few of them due to configuration issues.
URI: http://140.113.39.130/cdrfb3/record/nctu/#GT079756550
http://hdl.handle.net/11536/46039
Appears in Collections:Thesis


Files in This Item:

  1. 655001.pdf