Details of Logo 02-C-000803

TOP > 02-C-000803

ES-2-C-20120509-000111

Management   Application Form   Extended Test Categories
Logo ID 02-C-000803
Approved Date 2012/06/29
Application ID ES-2-C-20120509-000111
Applied Date 2012/05/09
Usage Agreement Agreed
OEM Licensor's Logo ID -
Note -
Management   Application Form   Extended Test Categories
Target Information Application Phase Phase-2
Test Category Core Protocols
Vendor Name Teldat
Country ES
Product Name Atlas Series, Teldat C1+L Series, Teldat-C+ Series, Teldat-H Series, Teldat-H+ Series, Teldat-L+ Series, Regesta Series, Teldat-Auto Series, Teldat-T200 Series, Teldat-K Series and Teldat-V Series
Product Version 11.0.1
Product Classification Router
Product Description http://www.teldat.com/en/page.php?cat_id=enterprise-routers
Vendor's Note 
    Test IP6Interop.1.2: Address Autoconfiguration and Duplicate Address Detection

==============================================================================



Part D: Duplicate Address Detection- Tentative Address Duplicated (Host vs Router)



In Windows XP we use the global unicast address instead of link-local address because this address cannot be changed.  



Test IP6Interop.1.6: Path MTU Discovery and Fragmentation

=========================================================



Part B: PMTU Discovery (Router vs Router)



When NetBSD, acting as an IPv6 router, received fragmented ICMPv6 Echo Requests in the second part of the test (steps 9 to 13), it sent all the replies fragmented (it didn't use the MTU of the link and, consequently, it didn't recive the corresponding ICMPv6 Too Big message). It seems that this is the default behavior of NetBSD under this circumstances.



In order to prove the correct behaviour of our implementation, we switched the origin of the ping request from REF-Host1 to TAR-Router2. We used the command "ping6 -mm -s 1452 -c 4 2001:db8:ffff:2:215:63ff:feee:2120" to force NetBSD sending ICMPv6 Echo Requests without fragmenting.



Part E: Fragmentation/Reassembly (Router vs Router)



Same observation that part B. For this reason, the ICMPv6 Too Big message isn't show in the capture file of network 3.
Test Information Test Specification 4.0.6
Interoperability Test Scneario 4.0.4
Information for Series of Product
Management   Application Form   Extended Test Categories
Interoperable
Devices		 Router
1 Vendor Name FreeBSD Project
Device Name FreeBSD
Version 8.1-RELEASE
2 Vendor Name NetBSD Project
Device Name NetBSD
Version 5.0.2
Host
1 Vendor Name Microsoft
Device Name Windows_XP
Version SP3
2 Vendor Name Ubuntu Project
Device Name Ubuntu
Version 10.4
Target supporting
Advanced Functions:		 o Transmitting Echo Requests(Passive Node)
- Configuring Multicast Packet Size
o Multicast Routing(Router Only)
- RFC 4191 Type C Host(Host Only)
- Duplicate Overlapping Fragments
- Beyond Scope of Source Address(Router Only)
- Tracking Connections for ICMPv6
- Router Advertisement DNS (Host Only)