Sure thing. It is below. I am using the default settings in Wimax Network Service 1.4.
-Brandon - <EAP> - <x0> <METHOD_TYPE>EAP_TLS</METHOD_TYPE> <VENDOR_ID>13</VENDOR_ID> <VENDOR_TYPE>13</VENDOR_TYPE> <USER_IDENTITY /> <PROVISIONED_PSEUDO_IDENTITY /> <PASSWORD /> <REALM>clearwire-wmx.net</REALM> <USE_PRIVACY>False</USE_PRIVACY> <ENCAPS /> <VFY_SRV_REALM>True</VFY_SRV_REALM> <SRV_REALM /> - <CERT> - <x0> <CERT_TYPE /> </x0> - <x1> <CERT_TYPE /> </x1> </CERT> </x0> </EAP> ________________________________ From: Inaky Perez-Gonzalez <[email protected]> To: Brandon Dell <[email protected]> Cc: Don Weeks <[email protected]>; "[email protected]" <[email protected]> Sent: Fri, April 23, 2010 12:28:47 PM Subject: Re: Generating a new XML file for a new carrier Brandon Can you post the EAP section you have in the .XML? On Fri, 2010-04-23 at 04:15 -0700, Brandon Dell wrote: > well then that means I am dead in the water. I will keep on trying > but I just can't see what is preventing this thing from connecting. > > -Brandon > > > > ______________________________________________________________________ > > From: Inaky Perez-Gonzalez <[email protected]> > To: Brandon Dell <[email protected]> > Cc: Don Weeks <[email protected]>; "[email protected]" > <[email protected]> > Sent: Thu, April 22, 2010 6:02:28 PM > Subject: Re: Generating a new XML file for a new carrier > > Hi Brandon > > On Thu, 2010-04-22 at 11:16 -0700, Brandon Dell wrote: > > Inaky, > > About those device certificates, where should they be? I do not > > have any such files on my system. I was under the impression that > the > > supplicant would handle all of the authentication stuff, however, > the > > supplicant error log seems to be looking for .pem files that it > thinks > > should be in /usr/share/wimax. > > You don't need those certificates, they are embedded in the device. > Those errors can be ignored. > > >
_______________________________________________ wimax mailing list [email protected] http://lists.linuxwimax.org/listinfo/wimax
