[Prism54-devel] Enabling WPA on Prism-GT

Rafiq Shaikh rafiq.shaikh@analog.com
Wed, 31 Dec 2003 19:56:09 -0800


This is a multi-part message in MIME format.
--------------060706090702070601080403
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Mike,

I already did the steps that you suggested but if I use type= 0x80 then 
the firmware gives interrupt
0x4000 and card stops responding. If I use type = 0x00 then the firmware 
does not give this interrupt.
But in both the cases I don't see the new element showing up in the 
outgoing Beacon frames.

There might be open source available but I am not aware of  any such.

Regards,
-Rafiq.

Mike.Hansen@intermec.com wrote:

> Hi Rafiq,
>
> I am new to the prism54 group but experienced with the PrismGT MAC.  
> The MAC does not set a WPA IE automagically in any of the management 
> fields, regardless of security key settings. The IE management is up 
> to you to format and set. 
>
> To set an attachment to the beacon do the following:
>
> ..Set the type field in obj_attachment to 0x80 to specify an 802.11 
> beacon frame type.
>
> ..Set the id field to zero to satisfy the attachment is on all 
> broadcast and multicast frames.  (Which of course beacons are)
>
> ..And then set your data and the size field as required by your IE 
> content.
>
> ..Use DOT11_OID_ATTACHMENT to pin the attachment onto all further 
> beacons.
>
> The MAC does not know or care what you are attaching. 
>
> Can you tell me is there an open source supplicant for Prism54 clients 
> to handle the 802.1x/EAPOL key management needed for WPA?
>
> Regards,
>
> Mike
>
> -----Original Message-----
> From: Aurelien [mailto:slts@free.fr]
> Sent: Tuesday, December 30, 2003 6:27 PM
> To: prism54-devel@prism54.org
> Subject: Re: [Prism54-devel] Enabling WPA on Prism-GT
>
> What I mean is that setting the device to use TKIP key, may also make 
> it send automagicaly what you want in the beacon (whithout any 
> explicit attachement).
>
> ...And justice for all
>
> On Tue, 30 Dec 2003 14:09:56 -0800
> Rafiq Shaikh <rafiq.shaikh@analog.com> wrote:
>
> > Hi Aurelien,
> >
> > I did not set the key for this operation.
> > I don't think the key is required to send WPA IE inside of Beacon 
> frames.
> > My understanding is that once the attachment operation succeeds the new
> > element
> > should show up in the outgoing Beacon frames.
> >
> > Regards,
> > -Rafiq.
> >
> >
> > Aurelien wrote:
> >
> > >Hi,
> > >Did you try to set the type field to DOT11_PRIV_TKIP in the used key ?
> > >
> > >...And justice for all
> > >
> > >On Tue, 30 Dec 2003 13:40:37 -0800
> > >Rafiq Shaikh <rafiq.shaikh@analog.com> wrote:
> > >
> > > 
> > >
> > >>Hi,
> > >>
> > >>I understand that there is a RID FC28  Flag to enable WPA on  ISL3842
> > >>(802.11b).
> > >>Is there a similar OID available to enable WPA on Prism-GT?
> > >>
> > >>On Prism-GT to enable WPA  I set MLME to EXTENDED, attach WPA IE.
> > >>The attachment of WPA IE succeeded but the new element does not 
> show up
> > >>in the
> > >>out going Beacons or Probe Responses.
> > >>Any suggestions why this is happening?
> > >>
> > >>Regards,
> > >>-Rafiq.
> > >>
> > >>
> > >>_______________________________________________
> > >>Prism54-devel mailing list
> > >>Prism54-devel@prism54.org
> > >>http://prism54.org/mailman/listinfo/prism54-devel
> > >>
> > >>   
> > >>
> > >_______________________________________________
> > >Prism54-devel mailing list
> > >Prism54-devel@prism54.org
> > >http://prism54.org/mailman/listinfo/prism54-devel
> > >
> > >
> > > 
> > >
> >
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel
>

--------------060706090702070601080403
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Mike,<br>
<br>
I already did the steps that you suggested but if I use type= 0x80 then
the firmware gives interrupt<br>
0x4000 and card stops responding. If I use type = 0x00 then the
firmware does not give this interrupt.<br>
But in both the cases I don't see the new element showing up in the
outgoing Beacon frames.<br>
<br>
There might be open source available but I am not aware of&nbsp; any such.<br>
<br>
Regards,<br>
-Rafiq.<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Mike.Hansen@intermec.com">Mike.Hansen@intermec.com</a> wrote:<br>
<blockquote type="cite"
 cite="mid214E7E5F0186D511ADE900508BAF9D4A0A16EA2A@sintevtex3.intermec.com">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="Generator"
 content="MS Exchange Server version 5.5.2656.60">
  <title>RE: [Prism54-devel] Enabling WPA on Prism-GT</title>
  <p><font size="2">Hi Rafiq,</font>
  </p>
  <p><font size="2">I am new to the prism54 group but experienced with
the PrismGT MAC.&nbsp; The MAC does not set a WPA IE automagically in any of
the management fields, regardless of security key settings. The IE
management is up to you to format and set.&nbsp; </font></p>
  <p><font size="2">To set an attachment to the beacon do the following:</font>
  </p>
  <p><font size="2">..Set the type field in obj_attachment to 0x80 to
specify an 802.11 beacon frame type.</font>
  </p>
  <p><font size="2">..Set the id field to zero to satisfy the
attachment is on all broadcast and multicast frames.&nbsp; (Which of course
beacons are)</font></p>
  <p><font size="2">..And then set your data and the size field as
required by your IE content.</font>
  </p>
  <p><font size="2">..Use DOT11_OID_ATTACHMENT to pin the attachment
onto all further beacons.</font>
  </p>
  <p><font size="2">The MAC does not know or care what you are
attaching.&nbsp; </font>
  </p>
  <p><font size="2">Can you tell me is there an open source supplicant
for Prism54 clients to handle the 802.1x/EAPOL key management needed
for WPA?</font></p>
  <p><font size="2">Regards,</font>
  </p>
  <p><font size="2">Mike</font>
  </p>
  <p><font size="2">-----Original Message-----</font>
  <br>
  <font size="2">From: Aurelien [<a href="mailto:slts@free.fr">mailto:slts@free.fr</a>]
  </font><br>
  <font size="2">Sent: Tuesday, December 30, 2003 6:27 PM</font>
  <br>
  <font size="2">To: <a class="moz-txt-link-abbreviated" href="mailto:prism54-devel@prism54.org">prism54-devel@prism54.org</a></font>
  <br>
  <font size="2">Subject: Re: [Prism54-devel] Enabling WPA on Prism-GT</font>
  </p>
  <p><font size="2">What I mean is that setting the device to use TKIP
key, may also make it send automagicaly what you want in the beacon
(whithout any explicit attachement).</font></p>
  <p><font size="2">...And justice for all</font>
  </p>
  <p><font size="2">On Tue, 30 Dec 2003 14:09:56 -0800</font>
  <br>
  <font size="2">Rafiq Shaikh <a class="moz-txt-link-rfc2396E" href="mailto:rafiq.shaikh@analog.com">&lt;rafiq.shaikh@analog.com&gt;</a> wrote:</font>
  </p>
  <p><font size="2">&gt; Hi Aurelien,</font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; I did not set the key for this operation.</font>
  <br>
  <font size="2">&gt; I don't think the key is required to send WPA IE
inside of Beacon frames.</font>
  <br>
  <font size="2">&gt; My understanding is that once the attachment
operation succeeds the new </font>
  <br>
  <font size="2">&gt; element</font>
  <br>
  <font size="2">&gt; should show up in the outgoing Beacon frames.</font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; Regards,</font>
  <br>
  <font size="2">&gt; -Rafiq.</font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; Aurelien wrote:</font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; &gt;Hi,</font>
  <br>
  <font size="2">&gt; &gt;Did you try to set the type field to
DOT11_PRIV_TKIP in the used key ?</font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;...And justice for all</font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;On Tue, 30 Dec 2003 13:40:37 -0800</font>
  <br>
  <font size="2">&gt; &gt;Rafiq Shaikh <a class="moz-txt-link-rfc2396E" href="mailto:rafiq.shaikh@analog.com">&lt;rafiq.shaikh@analog.com&gt;</a>
wrote:</font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;&nbsp; </font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;Hi,</font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;I understand that there is a RID FC28&nbsp;
Flag to enable WPA on&nbsp; ISL3842 </font>
  <br>
  <font size="2">&gt; &gt;&gt;(802.11b).</font>
  <br>
  <font size="2">&gt; &gt;&gt;Is there a similar OID available to
enable WPA on Prism-GT?</font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;On Prism-GT to enable WPA&nbsp; I set MLME to
EXTENDED, attach WPA IE.</font>
  <br>
  <font size="2">&gt; &gt;&gt;The attachment of WPA IE succeeded but
the new element does not show up </font>
  <br>
  <font size="2">&gt; &gt;&gt;in the</font>
  <br>
  <font size="2">&gt; &gt;&gt;out going Beacons or Probe Responses.</font>
  <br>
  <font size="2">&gt; &gt;&gt;Any suggestions why this is happening?</font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;Regards,</font>
  <br>
  <font size="2">&gt; &gt;&gt;-Rafiq.</font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt;
&gt;&gt;_______________________________________________</font>
  <br>
  <font size="2">&gt; &gt;&gt;Prism54-devel mailing list</font>
  <br>
  <font size="2">&gt; &gt;&gt;<a class="moz-txt-link-abbreviated" href="mailto:Prism54-devel@prism54.org">Prism54-devel@prism54.org</a></font>
  <br>
  <font size="2">&gt; &gt;&gt;<a
 href="http://prism54.org/mailman/listinfo/prism54-devel"
 target="_blank">http://prism54.org/mailman/listinfo/prism54-devel</a></font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt; &gt;&gt;&nbsp;&nbsp;&nbsp; </font>
  <br>
  <font size="2">&gt; &gt;&gt;</font>
  <br>
  <font size="2">&gt;
&gt;_______________________________________________</font>
  <br>
  <font size="2">&gt; &gt;Prism54-devel mailing list</font>
  <br>
  <font size="2">&gt; &gt;<a class="moz-txt-link-abbreviated" href="mailto:Prism54-devel@prism54.org">Prism54-devel@prism54.org</a></font>
  <br>
  <font size="2">&gt; &gt;<a
 href="http://prism54.org/mailman/listinfo/prism54-devel"
 target="_blank">http://prism54.org/mailman/listinfo/prism54-devel</a></font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; &gt;&nbsp; </font>
  <br>
  <font size="2">&gt; &gt;</font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">_______________________________________________</font>
  <br>
  <font size="2">Prism54-devel mailing list</font>
  <br>
  <font size="2"><a class="moz-txt-link-abbreviated" href="mailto:Prism54-devel@prism54.org">Prism54-devel@prism54.org</a></font>
  <br>
  <font size="2"><a
 href="http://prism54.org/mailman/listinfo/prism54-devel"
 target="_blank">http://prism54.org/mailman/listinfo/prism54-devel</a></font>
  </p>
</blockquote>
</body>
</html>

--------------060706090702070601080403--