Date: Tue, 3 Jan 2006 16:54:09 -0500
From: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [dhcptest:00092] Tahi DHCPv6 Relay Tests
To: "haoda" <haoda@64translator.com>, <dhcptest@tahi.org>
Message-Id: <8E296595B6471A4689555D5D725EBB210109A1E9@xmb-rtp-20a.amer.cisco.com>
X-Mail-Count: 00092

Hi:

I see now why the relay tests are failing.

Because of research I did a while ago and based on the various platforms
our servers supports, when sending the RELAY-REPLY we'll an
appropriately scoped address, if available, based on the original
destination.

So, relay messages are being sent to ff05::1:3 which is a site-local
multicast address. Since a link-local address is scoped much more
narrowly than a site-local, we attempt to find a broarder scoped address
and hence end up using the global unicast address assigned to the server
system.

Thus, the TN is ignoring our Relay-Reply because the address isn't what
it expected:

ng compare _HDR_IPV6_relay_reply_nut_relay.SourceAddress
received:2001:420:3800:4801:203:baff:fe6c:9fb8 =
fe80::203:baff:fe6c:9fb8

Perhaps we can look at the request's source address instead of the
destination address when chosing the address to use in the Relay-Reply.

- Bernie