Getting gprs context username and password

Getting gprs context username and password

[Mark van der Putten]

[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]

In the gemalto plugin (static void gemalto_post_sim(struct ofono_modem
*modem)) or maybe something sooner in startup phase I would like to
implement AT^SGAUTH

> AT^SGAUTH specifies the authentication protocol, password and user
name to be
> given if a Packet Domain network requires authentication and the
subscriber
> uses AT+CGACT for PDP context activation.

Because connecting with lte to this private APN must be done with radius
authentication.
Hard coding does the trick, but what would be the correct ofono way to
execute the following:

g_at_chat_send(data->app, "AT^SGAUTH=1,2,\"xxx\",\"xxx\"",NULL, NULL,
NULL, g_free);

substituting xxx with username and password.

PS gprs context 1 has correct values for:
[context1]
Name=gprs
AccessPointName=private.apn
Username=xxx
Password=xxx
AuthenticationMethod=chap
Type=internet
Protocol=ip


Regards,
Mark

Please consider the environment before printing this email. This e-mail, and any files transmitted with it, is confidential and is intended solely for the use of the person or entity to whom it is addressed. If you have received this e-mail in error, please notify the sender and delete it from your records. On all our offers, sales and deliveries our General Terms of Delivery are applicable, excluding all other Terms and Conditions. Our terms have been deposited at the Chamber of commerce Eindhoven (The Netherlands), reference number 17065041, a copy of these terms is enclosed with all quotations, a hardcopy also can be send on your request. You can find our General Terms online at https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-ENGELS.pdf Op al onze aanbiedingen, verkopen en leveringen zijn, met uitsluiting van alle andere voorwaarden, onze algemene voorwaarden van toepassing. Deze zijn gedeponeerd bij de Kamer van Koophandel te Eindhoven onder nummer 17065041. Bij iedere offerte hoe ook verzonden zijn de algemene voorwaarden bijgevoegd, een kopie kan op aanvraag ook per post worden toegezonden. U kunt onze algemene voorwaarden online inzien op https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-NEDERLANDS.pdf

Re: Getting gprs context username and password

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

Hi Mark,

On 09/06/2018 11:31 AM, Mark van der Putten wrote:
> In the gemalto plugin (static void gemalto_post_sim(struct ofono_modem
> *modem)) or maybe something sooner in startup phase I would like to
> implement AT^SGAUTH

Hmm, are you sure you actually need the AT^SGAUTH?

Gemalto is using the atmodem driver.  This driver uses PPP.  Generally 
any CHAP/PAP authentication is done during PPP negotiation phase, not 
via any vendor +FOOAUTH commands (although I think there are a few 
exceptions now)

For modems that use a high-speed interface, the auth parameters are sent 
during context setup phase.  e.g. after +CGDCONT.  See 
drivers/ifxmodem/gprs-context.c setup_cb() for an example.

If you do need the SGAUTH, then the logical place to put it would be 
into drivers/atmodem/gprs-context.c and use a vendor quirk for gemalto. 
E.g. something like:

switch(gcd->vendor) {
case OFONO_VENDOR_GEMALTO:
	g_at_chat_send(gcd->chat, "AT^XGAUTH..."....);
	break;
}

Regards,
-Denis

Re: Getting gprs context username and password

[Giacinto Cifelli]

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

hi Mark,

may I know which module are you using?

Regards,
Giacinto



On Thu, Sep 6, 2018 at 6:43 PM Denis Kenzior <denkenz@gmail.com> wrote:

> Hi Mark,
>
> On 09/06/2018 11:31 AM, Mark van der Putten wrote:
> > In the gemalto plugin (static void gemalto_post_sim(struct ofono_modem
> > *modem)) or maybe something sooner in startup phase I would like to
> > implement AT^SGAUTH
>
> Hmm, are you sure you actually need the AT^SGAUTH?
>
> Gemalto is using the atmodem driver.  This driver uses PPP.  Generally
> any CHAP/PAP authentication is done during PPP negotiation phase, not
> via any vendor +FOOAUTH commands (although I think there are a few
> exceptions now)
>
> For modems that use a high-speed interface, the auth parameters are sent
> during context setup phase.  e.g. after +CGDCONT.  See
> drivers/ifxmodem/gprs-context.c setup_cb() for an example.
>
> If you do need the SGAUTH, then the logical place to put it would be
> into drivers/atmodem/gprs-context.c and use a vendor quirk for gemalto.
> E.g. something like:
>
> switch(gcd->vendor) {
> case OFONO_VENDOR_GEMALTO:
>         g_at_chat_send(gcd->chat, "AT^XGAUTH..."....);
>         break;
> }
>
> Regards,
> -Denis
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> https://lists.ofono.org/mailman/listinfo/ofono
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1918 bytes --]

Re: Getting gprs context username and password

[Mark van der Putten]

[-- Attachment #1: Type: text/plain, Size: 3544 bytes --]

Hi Denis,

Hmm, are you sure you actually need the AT^SGAUTH?
I can explain a bit of the reason why I came to AT^SGAUTH modification.
@Giacinto it is module PLS8-E (Testing with firmware 3.017)

3G support from providers in NL is at its end. So we switched to PLS8-E (lte) modem. All seems to be working as expected 3G and also the switch to lte, this is on stock provider sim card.
But a customer uses a private APN with radius authentication. 3G context activation is fine but connecting with lte did not happen.

Research by the provider showed that authentication on lte did not happen.



MSISDN

Procedure

Duration

IPv4 Address

RAT

Cause

Initiator

LTE

3197012229997

PDN Create Session Rejected

00:00:00.015


EUTRAN

User authentication failed (92)

MME

LTE

3197012229997

PDN Create Session Rejected

00:00:00.015


EUTRAN

User authentication failed (92)

MME

LTE

3197012229997

PDN Create Session Rejected

00:00:00.019


EUTRAN

User authentication failed (92)

MME

LTE

3197012229997

PDN Create Session Rejected

00:00:00.009


EUTRAN

User authentication failed (92)

MME

LTE

3197012229997

PDN Create Session Rejected

00:00:00.009


EUTRAN

User authentication failed (92)

MME

2G/3G

3197012229997

PDP Context Activated

00:00:00.161

xxxx

UTRAN

Request accepted (128)

SGSN


For test purposes hardcode AT^SDAUTH fixes the authentication.

Gemalto is using the atmodem driver.  This driver uses PPP.  Generally any CHAP/PAP authentication is done during PPP negotiation phase, not via any vendor +FOOAUTH commands (although I think there are a few exceptions now)

For modems that use a high-speed interface, the auth parameters are sent during context setup phase.  e.g. after +CGDCONT.  See drivers/ifxmodem/gprs-context.c setup_cb() for an example.

If you do need the SGAUTH, then the logical place to put it would be into drivers/atmodem/gprs-context.c and use a vendor quirk for gemalto. E.g. something like:

switch(gcd->vendor) {
case OFONO_VENDOR_GEMALTO:
    g_at_chat_send(gcd->chat, "AT^XGAUTH..."....);
    break;
}

Regards,
-Denis
Regards,
Mark
Please consider the environment before printing this email. This e-mail, and any files transmitted with it, is confidential and is intended solely for the use of the person or entity to whom it is addressed. If you have received this e-mail in error, please notify the sender and delete it from your records. On all our offers, sales and deliveries our General Terms of Delivery are applicable, excluding all other Terms and Conditions. Our terms have been deposited at the Chamber of commerce Eindhoven (The Netherlands), reference number 17065041, a copy of these terms is enclosed with all quotations, a hardcopy also can be send on your request. You can find our General Terms online at https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-ENGELS.pdf Op al onze aanbiedingen, verkopen en leveringen zijn, met uitsluiting van alle andere voorwaarden, onze algemene voorwaarden van toepassing. Deze zijn gedeponeerd bij de Kamer van Koophandel te Eindhoven onder nummer 17065041. Bij iedere offerte hoe ook verzonden zijn de algemene voorwaarden bijgevoegd, een kopie kan op aanvraag ook per post worden toegezonden. U kunt onze algemene voorwaarden online inzien op https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-NEDERLANDS.pdf

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 14634 bytes --]

Re: Getting gprs context username and password

[Giacinto Cifelli]

[-- Attachment #1: Type: text/plain, Size: 4789 bytes --]

Hi Mark,

I am updating the gemalto driver, and it will support cdc-ecm (AT^SWWAN)
instead of PPP for this module.
The AT^SGAUTH is already in my code, but not only: several modules use
AT+CGAUTH instead.
I am not sure when I will upload it, but I hope by the end of this month.

@Denis: about the authentication, we are also modifying the lte core/atom,
because some use cases require to have an authentication also for the LTE
combined attach.
I have a private APN use case that requires it, and it seems it is needed
for a Japanese certification.
For this, we will use AT+CGAUTH as default (because it is in the 27.007),
and AT^SGAUTH for some Gemalto modules.
Is this ok for you?

thank you,
Giacinto



On Fri, Sep 7, 2018 at 9:01 AM Mark van der Putten <
mark.van.der.putten@intemo.com> wrote:

> Hi Denis,
>
> Hmm, are you sure you actually need the AT^SGAUTH?
>
> I can explain a bit of the reason why I came to AT^SGAUTH modification.
> @Giacinto it is module PLS8-E (Testing with firmware 3.017)
>
> 3G support from providers in NL is at its end. So we switched to PLS8-E
> (lte) modem. All seems to be working as expected 3G and also the switch to
> lte, this is on stock provider sim card.
> But a customer uses a private APN with radius authentication. 3G context
> activation is fine but connecting with lte did not happen.
>
> Research by the provider showed that authentication on lte did not happen.
>
>
> MSISDN
>
> Procedure
>
> Duration
>
> IPv4 Address
>
> RAT
>
> Cause
>
> Initiator
>
> LTE
>
> 3197012229997
>
> PDN Create Session Rejected
>
> 00:00:00.015
>
> EUTRAN
>
> User authentication failed (92)
>
> MME
>
> LTE
>
> 3197012229997
>
> PDN Create Session Rejected
>
> 00:00:00.015
>
> EUTRAN
>
> User authentication failed (92)
>
> MME
>
> LTE
>
> 3197012229997
>
> PDN Create Session Rejected
>
> 00:00:00.019
>
> EUTRAN
>
> User authentication failed (92)
>
> MME
>
> LTE
>
> 3197012229997
>
> PDN Create Session Rejected
>
> 00:00:00.009
>
> EUTRAN
>
> User authentication failed (92)
>
> MME
>
> LTE
>
> 3197012229997
>
> PDN Create Session Rejected
>
> 00:00:00.009
>
> EUTRAN
>
> User authentication failed (92)
>
> MME
>
> 2G/3G
>
> 3197012229997
>
> PDP Context Activated
>
> 00:00:00.161
>
> xxxx
>
> UTRAN
>
> Request accepted (128)
>
> SGSN
>
> For test purposes hardcode AT^SDAUTH fixes the authentication.
>
> Gemalto is using the atmodem driver.  This driver uses PPP.  Generally any
> CHAP/PAP authentication is done during PPP negotiation phase, not via any
> vendor +FOOAUTH commands (although I think there are a few exceptions now)
>
> For modems that use a high-speed interface, the auth parameters are sent
> during context setup phase.  e.g. after +CGDCONT.  See
> drivers/ifxmodem/gprs-context.c setup_cb() for an example.
>
> If you do need the SGAUTH, then the logical place to put it would be into
> drivers/atmodem/gprs-context.c and use a vendor quirk for gemalto. E.g.
> something like:
>
> switch(gcd->vendor) {
> case OFONO_VENDOR_GEMALTO:
>     g_at_chat_send(gcd->chat, "AT^XGAUTH..."....);
>     break;
> }
>
> Regards,
> -Denis
>
> Regards,
> Mark
> Please consider the environment before printing this email. This e-mail,
> and any files transmitted with it, is confidential and is intended solely
> for the use of the person or entity to whom it is addressed. If you have
> received this e-mail in error, please notify the sender and delete it from
> your records. On all our offers, sales and deliveries our General Terms of
> Delivery are applicable, excluding all other Terms and Conditions. Our
> terms have been deposited at the Chamber of commerce Eindhoven (The
> Netherlands), reference number 17065041, a copy of these terms is enclosed
> with all quotations, a hardcopy also can be send on your request. You can
> find our General Terms online at
> https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-ENGELS.pdf
> Op al onze aanbiedingen, verkopen en leveringen zijn, met uitsluiting van
> alle andere voorwaarden, onze algemene voorwaarden van toepassing. Deze
> zijn gedeponeerd bij de Kamer van Koophandel te Eindhoven onder nummer
> 17065041. Bij iedere offerte hoe ook verzonden zijn de algemene voorwaarden
> bijgevoegd, een kopie kan op aanvraag ook per post worden toegezonden. U
> kunt onze algemene voorwaarden online inzien op
> https://www.intemo.com/wp-content/uploads/2018/05/FHI-Algemene-Leveringsvoorwaarden-2014-NEDERLANDS.pdf
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> https://lists.ofono.org/mailman/listinfo/ofono
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 12191 bytes --]