Details of Logo 02-C-000508

TOP > 02-C-000508

TW-2-C-20100816-000172

Logo ID 02-C-000508
Approved Date 2010/09/17
Application ID TW-2-C-20100816-000172
Applied Date 2010/08/16
Usage Agreement Agreed
OEM Licensor's Logo ID -
Note -
Target Information Application Phase Phase-2
Test Category Core Protocols
Vendor Name D-Link
Country TW
Product Name EBR-2310 C1
Product Version 3.00
Product Classification Host
Product Description Ethernet Broadband Router
Vendor's Note
    ##About ROUTER.NetBSD ##

When NetBSD, acting as an IPv6 router, received ICMPv6 Echo Requests with 1500 bytes,
it will response and fragment ICMPv6 Echo Replies within MTU 1280 bytes.
Even if NetBSD is configured by using this command "ifconfig rtk0 mtu 1500".

Note 2:
##1.6.B.D-Link.NetBSD.Network1.dump##
##1.6.B.D-Link.NetBSD.Network2.dump##

When we process this test case in the interoperability test,
NetBSD (TAR-Router2) can't receive the ICMPv6 Too Big message in procedure 12 of Test IP6Interop.1.6.B.

We exchange the direction of ping in 1.6.B.NetBSD.
NetBSD (TAR-Router2) ping REF-Host1, then TAR-Router1(our device) will send ICMPv6 Too Big packet.
We use the command "ping6 -mm -s 1452 -c 5 3ffe:0501:ffff:0101:0213:46ff:fe72:88ca"
to force NetBSD sending ICMPv6 Echo Requests without fragmenting.

Note 3:
##1.6.E.D-Link.NetBSD.Network1.dump##
##1.6.E.D-Link.NetBSD.Network2.dump##
##1.6.E.D-Link.NetBSD.Network3.dump##

When TAR-Router2 receives ICMPv6 Echo Requsts from REF-Router1 on the Network3,
it will fragment the ICMPv6 Echo Reply within MTU 1280 bytes.

REF-Router4 will not transmit ICMPv6 Too Big message.

We use the command "ping6 -mm -s 1452 -c 5 3ffe:0501:ffff:0100:02d0:59ff:fe11:1110"
to force NetBSD sending ICMPv6 Echo Request without fragmenting.
Then the REF-Router4 will send ICMPv6 Too Big message.

Note 4:
FreeBSD, acts as a router or a host, will lost the first fragmented packet,
when it use NS/NA to discover a neighbor.
These situations occur in the following test items.

## 1.6.A.Linux.D-Link.Network2.dump ##
## 1.6.A.USAGI.D-Link.Network2.dump ##
We use FreeBSD as REF-Host2.

## 1.6.B.D-Link.FreeBSD.Network2.dump ##
## 1.6.B.D-Link.NetBSD.Network2.dump ##
We use FreeBSD as REF-Host1.

## 1.6.D.Linux.D-Link.Network2.dump ##
## 1.6.D.USAGI.D-Link.Network2.dump ##
We use FreeBSD as REF-Router2.

## 1.6.E.D-Link.FreeBSD.Network2.dump ##
## 1.6.E.D-Link.NetBSD.Network2.dump ##
Test Information Test Specification 4.0.6
Interoperability Test Scneario 4.4
Information for Series of Product
Interoperable
Devices
Router
1 Vendor Name The FreeBSD Project
Device Name FreeBSD
Version 5.4-RELEASE
2 Vendor Name The NetBSD Project
Device Name NetBSD
Version 4.0.1-RELEASE
Host
1 Vendor Name Kernel.Org
Device Name Mainline Linux Kernel
Version 2.6.15.6
2 Vendor Name USAGI Project
Device Name USAGI
Version usagi-linux26-s20060327
Target supporting
Advanced Functions:
o Transmitting Echo Requests or configuring packet size (Passive Node)
o Multicast Routing
o MTU Configuration
- RFC 4191 Type C Host
- Duplicate Overlapping Fragments