<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18876"></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><FONT size=2>The original patch did this, but put attention that it looks
like the second NETWORK_ADDRESS structure overrides the first one, i.e. ALL the
data are corrupted</FONT></P>
<P><FONT size=2>See the data marked in red: 10 00 02 00 looks like the the start
of the second structure, and even the first address has gone there.</FONT></P>
<P><FONT size=2>I saw the same issue with 5 network addresses, it looked
like</FONT></P>
<P><FONT size=2>10 00 02 00 XX 10 00 02 00 XX 10 00 02 00 XX 10 00 02
00 XX 10 00 02 00 XX </FONT></P>
<P><FONT size=2>Instead of:</FONT></P>
<P><FONT size=2>10 00 02 00 { IP address of 16 bytes} 10 00 02 00 { IP address
of 16 bytes} 10 00 02 00 { IP address of 16 bytes} 10 00 02 00 { IP
address of 16 bytes} </FONT></P>
<P><FONT size=2></FONT> </P>
<P><FONT size=2>4: kd> db 0xfffffa80`0c39f240<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f240 02 00 00 00 02 00 <SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">10 00-02 00 00 00 <FONT
color=#ff0000>10 00 02 00</FONT> ................<o:p></o:p></SPAN></P>
<P class=MsoPlainText><SPAN
style="BACKGROUND: yellow; mso-highlight: yellow">fffffa80`<FONT
color=#ff0000>0c39f250 0c 7f 00 00 10 04 0c 7f-00 00</FONT></SPAN> 00 00
00 00 00 00 ................<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f260 00 00 00 00 00 00 00 00-00 00 00
00 00 00 70 9f ..............p.<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f270 04 00 08 02 45 76 65 ee-b4 05 00
00 b8 0b 00 00 ....Eve.........<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f280 00 00 00 00 70 00 00 00-00 00 00
00 00 00 00 00 ....p...........<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f290 00 00 00 00 00 00 00 00-00 00 00
00 00 00 00 00 ................<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f2a0 01 00 00 00 00 00 00 00-01 00 00
00 00 00 00 00 ................<o:p></o:p></P>
<P class=MsoPlainText>fffffa80`0c39f2b0 00 00 00 00 00 00 00 00-0c 00 08
00 00 00 00 00 ................<BR><BR><BR>-----Original
Message-----<BR>From: Fab Tillier [<A
href="mailto:ftillier@microsoft.com">mailto:ftillier@microsoft.com</A>]<BR>Sent:
Monday, August 30, 2010 9:56 PM<BR>To: Tzachi Dar; Alex Naslednikov; Hefty,
Sean; ofw@lists.openfabrics.org<BR>Subject: RE: [ofw]
[Patch][ipoib][ipoib_NDIS6_CM] Fixing a bug when OID_GEN_NETWORK_LAYER_ADDRESSES
contains bad data<BR><BR>Thanks for sending this Tzachi, we're looking into
it.<BR><BR>Tzachi Dar wrote on Mon, 30 Aug 2010 at 01:31:22<BR><BR>> On a
more practical approach (assuming there is no fix in the short<BR>> term) I
suggest that on windows 2008 R2 we will not try to parse this<BR>> structure
if it contains more than one element. Please note that this<BR>> means that
ND will not work on such machines (with more than one ip<BR>> address per
interface).<BR><BR>Why not just only parse the first address
only?<BR><BR>-Fab<BR></P></FONT></BODY></HTML>