No, the channel plan is good. BTW, we use individual Radio Heads at this point so our channel plans consist of a single frequency range. I am guessing that in this case, the AB, BC, stuff is kind of a wash? That I can use any of those to specify the single frequency? Oh, and based on what I read, the 5150 does not support 2.3Ghz? I am still working on it. On Thu, Apr 22, 2010 at 12:28 PM, Inaky Perez-Gonzalez < inaky.perez-gonzalez at intel.com> wrote: > On Wed, 2010-04-21 at 16:42 -0700, Don Weeks wrote: > > Finally, > > > > I am seeing my network base stations. Well, except the one with a > > NAP of F4D800. It says it is "activated" but I am not clear on the > > Hm, maybe your channel plan is not listing the channel where this one is > beeping? > > > next step. How do I "log in". IE, when does it pick up the certificate > > and authenticate with the network and give me a login prompt? > > Well, this depends on how your NAP setup is. Clearwire authenticates > based on the device's certificate (*). So the whole EAP TLS thingie is > done with that. If your NAP setup has other login method, well, the code > so far has been tested only with EAP TLS and some very light EAP TTLS > testing, so I don't know if you'd be succesful in getting a > login/password TTLS authentication working without some hacking. > > (*) in WiMAX, every device has a certificate tied to the MAC address > which can be used to uniquely identify it. > > > > > > On Fri, Apr 16, 2010 at 12:58 PM, Don Weeks <don.l.weeks.jr at gmail.com> > > wrote: > > Thanks, I'll double check my dialing plans and EAP. > > > > Don > > > > On Fri, Apr 16, 2010 at 12:01 PM, Inaky Perez-Gonzalez > > <inaky.perez-gonzalez at intel.com> wrote: > > On Fri, 2010-04-16 at 04:23 -0700, Don Weeks wrote: > > > Yes, an example of TTLS would help. That is where I > > am stuck right > > > now. I did check and I can see Clear's network using > > the driver but > > > ours does not show up. > > > > > > So this is what I got from the team; remember this is > > just the EAP > > section. If you are not seeing your network it means > > that the channel > > plan and NAP ID are probably not specified correctly > > and you still > > haven't even gotten to the EAP part. EAP is only used > > once you plug to a > > NAP/NSP. > > > > ---- example ---- > > > > I am not an expert in this.. however, following is the > > working version > > for UQ with TTLS. The only differences are the realm > > names. > > > > Even if there are a lot of fields, it is not being > > used. > > > > > > > > <EAP> > > > > <x1> > > > > <METHOD_TYPE>EAP_TTLS</METHOD_TYPE> > > > > <VENDOR_ID></VENDOR_ID> > > > > <VENDOR_TYPE></VENDOR_TYPE> > > > > <USER_IDENTITY></USER_IDENTITY> > > > > > > > <PROVISIONED_PSEUDO_IDENTITY></PROVISIONED_PSEUDO_IDENTITY> > > > > <PASSWORD></PASSWORD> > > > > <REALM>uqwimax.jp</REALM> > > > > <USE_PRIVACY>False</USE_PRIVACY> > > > > <ENCAPS></ENCAPS> > > > > > > <VFY_SERVER_REALM>False</VFY_SERVER_REALM> > > > > <SERVER_REALMS> > > > > <x0> > > > > > > <SERVER_REALM>uqwimax.jp</SERVER_REALM> > > > > </x0> > > > > </SERVER_REALMS> > > > > <CERT> > > > > <x0> > > > > > > <CERT_TYPE>DEVICE</CERT_TYPE> > > > > </x0> > > > > <x1> > > > > > > <CERT_TYPE>CA</CERT_TYPE> > > > > </x1> > > > > </CERT> > > > > </x1> > > > > <x2> > > > > <METHOD_TYPE></METHOD_TYPE> > > > > <VENDOR_ID>24757</VENDOR_ID> > > > > <VENDOR_TYPE>1</VENDOR_TYPE> > > > > <USER_IDENTITY></USER_IDENTITY> > > > > > > > <PROVISIONED_PSEUDO_IDENTITY></PROVISIONED_PSEUDO_IDENTITY> > > > > <PASSWORD></PASSWORD> > > > > <REALM></REALM> > > > > <USE_PRIVACY>False</USE_PRIVACY> > > > > <ENCAPS>1</ENCAPS> > > > > > > <VFY_SERVER_REALM>False</VFY_SERVER_REALM> > > > > <SERVER_REALMS></SERVER_REALMS> > > > > <CERT></CERT> > > > > </x2> > > > > </EAP> > > > > > > > > > > > > > > > Don > > > > > > On Thu, Apr 15, 2010 at 12:54 PM, Inaky > > Perez-Gonzalez > > > <inaky at linux.intel.com> wrote: > > > On Wed, 2010-04-07 at 10:00 -0400, Don Weeks > > wrote: > > > > Thanks Inaky, > > > > > > > > I have been gathering the details but > > we use certificates > > > and TTLS > > > > sercurity which they don't so I don't have > > an example of > > > doing those. > > > > I do have all these details for our base > > stations but just > > > missing > > > > some of the finer points. I know this is > > an OMA XML file but > > > OMA > > > > breaks their stuff down into tiny > > sections. Any idea which > > > one is the > > > > security parameters one or does someone > > have an example of > > > EAP_TTLS to > > > > go by? Also, the NDS files go > > in /usr/local/share/wimax and > > > then > > > > > > > > > I'll ask around for an example that you can > > use > > > > > > > restart wimaxd to pick them up? And is the > > file name > > > important as > > > > there are 2 NDS files in the directory. > > > > > > > > > You need to modify the file with wimaxd > > stopped, or it will > > > overwrite > > > the changes. The file name should be > > > NDnSAgentConfig_forDriver.xml. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxwimax.org/pipermail/wimax/attachments/20100423/501ef6a2/attachment.html>
