I don't know much about multi-sim. However, if the IMSI and SIM
information are obtained by
wpa_supplicate itself, wpa_supplicate should chose the right sim card
to get necessary information, I think.
Here is an example to enable eap-sim support for wpa_supplicant.
network = {
ssid="eap-sim-ap"
key_mgmt=WPA-EAP
eap=SIM
pin="1234"
pcsc=""
}
Many Thanks,
Vincent Chang,
Software Engineer of Mozilla Taiwan
2013/8/15 Ken Chang <[email protected]>
> Currently, all Android vendors have modified the Android framework for
> EAP-SIM function.
> Moreover, Android vendors need to modify two things. One is RILD, so the
> SIM information can be passed from modem to Android framework.
> The other is wpa_supplicate(WIFI), so a new interface can be added to get
> SIM information from Android framework.
>
> The reasons why Android vendors must do these modification works are as
> follows,
> 1. Like what Vincent said, Android doesn't provide the EAP-SIM function in
> Android framework.
> 2. The wpa_supplicate only supports EAP-SIM function for "SIM card
> readers" now. This kind of design
> is for laptop, not for phone device. Please imagine this situation
> where your laptop is connected with a card reader
> with a SIM inside when you want to access the wifi network with EAP-SIM
> authentication.
> 3. The modem is only able to provide SIM information via AT command,
> AT+CSIM, for EAP-SIM.
> There is no way to get SIM information via a RIL interface in current
> Android RILD design.
>
> The purpose of this EAP-SIM architecture is not trying to modify
> wpa_supplicate or RILD. This modification work
> should be the vendors' responsibilities. We are trying to overcome the
> preceding limitations to
> provide interfaces for EAP-SIM in Gecko. In this proposal, if vendor/OEN
> uses firefox OS, they don't have to
> modify Gecko. What they need to do is just to change their RIL interface
> and wap_supplicate if they want to have
> the EAP-SIM function in their device.
>
> @Vincent,
> Does your new proposal also work on the Multi-SIM platform?
>
> Best Regards,
> Ken Chang
> --
> Mozilla Taiwan
> Email:[email protected]
> Tel:+886-2-87861100 Ext.303
> Mobile:+886-952-391521
>
>
> ----- 原始郵件 -----
> > 寄件者: "Thomas Ho" <[email protected]>
> > 收件者: "Vincent Chang" <[email protected]>
> > 副本: "Jonas Sicking" <[email protected]>, "Kyle Machulis" <
> [email protected]>, "Blake Kaplan" <[email protected]>,
> > "Blake Kaplan" <[email protected]>, "Michael Vines" <
> [email protected]>, "Dimi Lee" <[email protected]>, "dev-b2g"
> > <[email protected]>
> > 寄件備份: 2013 8 月 15 星期四 下午 3:20:07
> > 主旨: Re: [b2g] EAP-SIM Architecture proposal
> >
> > Vincent and All,
> >
> > It does seem that Android (Google) doesn't natively support EAP-SIM, but
> > there are clients available to have EAP-SIM enabled. Vincent, you may
> > want to try to understand how CHT in Taiwan provides EAP-SIM support to
> > Samsung, HTC and other brand Android phones. Thank you very much.
> >
> > --
> > Thomas Ho
> >
> > 於 13/8/14 下午7:04, Vincent Chang 提到:
> > > AOSP seems not support this feature yet, see the link below.
> > >
> https://code.google.com/p/android/issues/detail?id=9329&cnum=500&cstart=1231
> > >
> > > Many Thanks,
> > > Vincent Chang,
> > > Software Engineer of Mozilla Taiwan
> > >
> > >
> > >
> > > 2013/8/15 Michael Vines <[email protected]>
> > >
> > >> Yes we could certainly consider patching the wpa_supplicant
> distributed on
> > >> codeaurora if necessary. I'm unfamiliar with this feature though, do
> you
> > >> know if/how Android supports it?
> > >>
> > >> Thanks,
> > >> Michael
> > >>
> > >>
> > >>
> > >>
> > >> On 8/14/13 10:31 AM, "Blake Kaplan" <[email protected]> wrote:
> > >>
> > >>> On Wed, Aug 14, 2013 at 8:55 AM, Vincent Chang <[email protected]>
> > >> wrote:
> > >>>> Does it make sense that partners modify their own wpa_supplicant and
> > >>>> obtain
> > >>>> the necessary SIM information
> > >>>> from card reader driver or directly from radio driver ? In this
> cause,
> > >>>> we
> > >>>> don't need to modify wpa_supplicant or
> > >>>> create a new worker thread to listen and wait there. In this case,
> we
> > >>>> just
> > >>>> need to configure wpa_supplicant.conf
> > >>>> to enable eap sim for specific SSID.
> > >>> CC'ing mvines who might have opinions on this as well.
> > >>>
> > >>> If we're convinced that there absolutely *has* to be a patch to
> > >>> wpa_supplicant, then getting Qualcomm or actual OEMs to maintain it
> > >>> and apply it is almost certainly the way to go. mvines, is this
> > >>> something we can do?
> > >>>
> > >>> That being said, is it really impossible to do this without modifying
> > >>> wpa_supplicant?
> > >>> --
> > >>> Blake Kaplan
> > >>
> > >>
> > > _______________________________________________
> > > dev-b2g mailing list
> > > [email protected]
> > > https://lists.mozilla.org/listinfo/dev-b2g
> >
> > _______________________________________________
> > dev-b2g mailing list
> > [email protected]
> > https://lists.mozilla.org/listinfo/dev-b2g
> >
>
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
