Adding the list: One of mine is F4D800 and I have never sucessfully seen that and the other one is actually set to 0. The 0 one scans every time but the F4D800 never shows (BTW, I do convert it to decimal). This follows the ITU's definition of MCC-MNC. See the following IEEE document: https://standards.ieee.org/regauth/BOPID/Broadband_OperatorID_Tutorial.html. As yet, I am trying to get the files I need (certificate files) and I was wondering where you were supposed to place them. Don On Thu, Apr 22, 2010 at 7:15 AM, Brandon Dell <stymiecc04 at yahoo.com> wrote: > Also, > > I am trying to connect to the Clear network but I noticed that I do not > have any of those cert.pem files that the supplicant log indicates should be > in /usr/share/wimax. Do you have have .pem files in your /usr/share/wimax or > /usr/local/share/wimax directory? > > Thanks, > Brandon > > > ------------------------------ > *From:* Don Weeks <don.l.weeks.jr at gmail.com> > *To:* Inaky Perez-Gonzalez <inaky.perez-gonzalez at intel.com> > *Cc:* "wimax at linuxwimax.org" <wimax at linuxwimax.org> > *Sent:* Wed, April 21, 2010 7:42:56 PM > *Subject:* Re: Generating a new XML file for a new carrier > > 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 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? > Don > > > 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/20100422/03787fd2/attachment.html>
