This is a multi-part message in MIME format.

------=_NextPart_000_0015_01C380E6.8AD600E0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

We are porting a WPA miniport from XP SP1 to PPC 2003. We are able to =
duplicate MIC failures for testing and are seeing something strange when =
the miniport makes an authentication status indication. It appears that =
once this media-specific indication is made, all activity through the =
stacks halts (i.e., pings are no longer sent through the miniport). This =
does not appear to be an ARM alignment issue since the desktop is still =
active.

As mentioned, this driver is being ported (with no source changes =
required) from XP SP1/NDIS 5.1. We do not see the same issue on XP with =
the driver and the same tests.

Has anyone seen this?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Peter Gibson
Seabright Consulting, Inc.
peter.gibson@sbcglobal.net
(831) 477-7735=20

------=_NextPart_000_0015_01C380E6.8AD600E0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>We are porting a WPA miniport from XP SP1 to PPC =
2003. We are=20
able to duplicate MIC failures for testing and are seeing something =
strange when=20
the miniport makes an authentication status indication. It appears that =
once=20
this media-specific indication is made, all activity through the stacks =
halts=20
(i.e., pings are no longer sent through the miniport). This does not =
appear to=20
be an ARM alignment issue since the desktop is still =
active.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>As mentioned, this driver is being ported (with no =
source=20
changes required) from XP SP1/NDIS 5.1. We do not see the same issue on =
XP with=20
the driver and the same tests.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Has anyone seen this?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT =
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<BR>Peter Gibson<BR>Seabright=20
Consulting, Inc.<BR><A=20
href=3D"mailto:peter.gibson@sbcglobal.net">peter.gibson@sbcglobal.net</A>=
<BR>(831)=20
477-7735 <BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_0015_01C380E6.8AD600E0--

Re: [Q] Problems with NDIS_802_11_STATUS_INDICATION/NDIS_802_11_AUTHENTICATION_REQUEST on PPC 2003 by Soemin

Soemin
Mon Sep 22 13:26:30 CDT 2003

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C380FC.5EC1D0E0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Peter,
This is potentially due to an issue in CE NDISUIO not making a fresh =
copy of the status buffer before indicating that to the zero config =
(WZCSVC) through message queue (which happens to work asynchronously).
Please help bring this issue to our product support group to have this =
problem fixed.
Thanks,
-- Soemin ---
Windows CE Networking
This posting is provided "AS IS" with no warranties, and confers no =
rights.
"Peter Gibson" <peter.gibson@sbcglobal.net> wrote in message =
news:etvSDFSgDHA.2320@TK2MSFTNGP12.phx.gbl...
We are porting a WPA miniport from XP SP1 to PPC 2003. We are able to =
duplicate MIC failures for testing and are seeing something strange when =
the miniport makes an authentication status indication. It appears that =
once this media-specific indication is made, all activity through the =
stacks halts (i.e., pings are no longer sent through the miniport). This =
does not appear to be an ARM alignment issue since the desktop is still =
active.

As mentioned, this driver is being ported (with no source changes =
required) from XP SP1/NDIS 5.1. We do not see the same issue on XP with =
the driver and the same tests.

Has anyone seen this?

=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Peter Gibson
Seabright Consulting, Inc.
peter.gibson@sbcglobal.net
(831) 477-7735=20

------=_NextPart_000_0016_01C380FC.5EC1D0E0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Peter,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This is potentially due to an issue =
in&nbsp;CE=20
NDISUIO not making a fresh copy of the status buffer before indicating =
that to=20
the zero config (WZCSVC) through message queue (which happens to work=20
asynchronously).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Please help&nbsp;bring this issue =
to&nbsp;our=20
product support group to have this problem fixed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT><BR><FONT face=3DArial =
size=3D2>-- Soemin=20
---<BR>Windows CE Networking<BR>This posting is provided "AS IS" with no =

warranties, and confers no rights.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Peter Gibson" &lt;<A=20
=
href=3D"mailto:peter.gibson@sbcglobal.net">peter.gibson@sbcglobal.net</A>=
&gt;=20
wrote in message <A=20
=
href=3D"news:etvSDFSgDHA.2320@TK2MSFTNGP12.phx.gbl">news:etvSDFSgDHA.2320=
@TK2MSFTNGP12.phx.gbl</A>...</DIV>
<DIV><FONT size=3D2>We are porting a WPA miniport from XP SP1 to PPC =
2003. We=20
are able to duplicate MIC failures for testing and are seeing =
something=20
strange when the miniport makes an authentication status indication. =
It=20
appears that once this media-specific indication is made, all activity =
through=20
the stacks halts (i.e., pings are no longer sent through the =
miniport). This=20
does not appear to be an ARM alignment issue since the desktop is =
still=20
active.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>As mentioned, this driver is being ported (with no =
source=20
changes required) from XP SP1/NDIS 5.1. We do not see the same issue =
on XP=20
with the driver and the same tests.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Has anyone seen this?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT =
size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<BR>Peter Gibson<BR>Seabright=20
Consulting, Inc.<BR><A=20
=
href=3D"mailto:peter.gibson@sbcglobal.net">peter.gibson@sbcglobal.net</A>=
<BR>(831)=20
477-7735 <BR></DIV></BLOCKQUOTE></FONT></BODY></HTML>

------=_NextPart_000_0016_01C380FC.5EC1D0E0--