From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Quectel EC200T USB: Problems with context activation
Date: Thu, 20 May 2021 12:57:56 -0500 [thread overview]
Message-ID: <4f8b7f2e-f3bb-1415-eb3b-b9b02390076a@gmail.com> (raw)
In-Reply-To: <CAFiQ674a-ymNTC-WhJrC98kR+BXe2nCcuCzAdsDDo+TnBQp5YA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3433 bytes --]
Hi Sergei,
On 5/19/21 6:35 PM, Sergei Golubtsov wrote:
> Hi Denis,
>
> Thank you very much for your quick and helpful reply.
>
> The problem is a bit vulgar actually. That's a shame that I took your
> time for that but I have another question as I am not sure about the
> findings below.
no worries.
>
> I had tried to get dump with gsmdial and gsmdial successfully
> activated the context. So the problem is that we have authentication
> method set to NONE in ofono. But gsmdial uses CHAP by default.
> I have manually set the auth to CHAP for the context in ofono and
> ofono successfully activated the context.
Yes, oFono used to use CHAP by default, but this was changed a few years ago.
> There is the provider info from mobile-broadband-provider-info about
> my provider:
>
> <provider>
> <name>China Unicom</name>
> <gsm>
> <network-id mcc="460" mnc="01"/>
> <apn value="3gnet">
> <plan type="postpaid"/>
> <usage type="internet"/>
> <username>uninet</username>
> </apn>
> <apn value="3gwap">
> <usage type="mms"/>
> <name>联通彩信</name>
> <mmsc>http://mmsc.myuni.com.cn</mmsc>
> <mmsproxy>10.0.0.172:80</mmsproxy>
> </apn>
> </gsm>
> </provider>
>
>
> Am I correct that ofono must use CHAP if the auth method is not
> specified in the db?
We used to do this, then around Sep-Oct 2018 there was a strong push to add an
explicit 'No Authentication' option for oFono from one of the modem hardware
vendors. I don't recall the exact arguments, search the archives, but the
fallout was that an empty username / password implied no authentication. Which
I think does make a certain amount of sense.
git show 6cf24fe1f9cfa2a61422ad84abfdd32e7ea2cf78. Look around at the commits
from the same author. I do seem to recall that 3GPP mandated CHAP to be used as
the default, even in the no username / password case. But my memory is fuzzy
now, and there hasn't been any problems reported since then (until now).
>
> I see that the technology used by the modem is HSPA. And I see the
> following in ofono/drivers/atmodem/lte.c:
>
> /* change the authentication method if the parameters are invalid */
> if (!*ldd->pending_info.username || !*ldd->pending_info.password)
> auth_method = OFONO_GPRS_AUTH_METHOD_NONE;
>
>
> And in ofono/plugins/mbpi.c:
>
> /* select authentication method NONE if fit */
> if (!ap->username || !ap->password)
> ap->auth_method = OFONO_GPRS_AUTH_METHOD_NONE;
>
>
> As well as ofono/plugins/fileprovision.c::
>
> /* select default authentication method */
> (*settings)[0].auth_method = OFONO_GPRS_AUTH_METHOD_NONE;
>
>
> ofono/src/lte.c:
>
> /* this must have a valid default */
> if (!gprs_auth_method_from_string(auth_method_str,
> <e->info.auth_method))
> lte->info.auth_method = OFONO_GPRS_AUTH_METHOD_NONE;
>
>
> I am not sure about the standards which may be relevant here. Sorry
> for asking this but I thought that we should use CHAP by default,
> don't we?
The question is really whether it is the network or the modem at fault here.
Does AUTH_METHOD_NONE work on other networks with this hardware?
>
> Thank you again and have a nice day.
>
> Yours sincerely,
> Sergei Golubtsov.
>
Regards,
-Denis
next prev parent reply other threads:[~2021-05-20 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFiQ675+H9QndW030-WkV2oivkVVChzcOTnKbaj+4VzW4k9P6w@mail.gmail.com>
2021-05-19 6:44 ` Quectel EC200T USB: Problems with context activation in chineese networks Sergei Golubtsov
2021-05-19 14:16 ` Quectel EC200T USB: Problems with context activation Denis Kenzior
2021-05-19 23:35 ` Sergei Golubtsov
2021-05-20 17:57 ` Denis Kenzior [this message]
2020-12-30 10:00 Sergei Golubtsov
2020-12-30 16:42 ` Denis Kenzior
2020-12-31 12:35 ` Sergei Golubtsov
2020-12-31 16:20 ` Denis Kenzior
2021-01-01 14:10 ` Sergei Golubtsov
2021-01-01 16:27 ` Sergei Golubtsov
2021-01-02 9:52 ` Sergei Golubtsov
2021-01-04 17:43 ` Denis Kenzior
2021-01-05 21:34 ` Sergei Golubtsov
2021-01-06 19:52 ` Denis Kenzior
[not found] <CAFiQ676fUqkEz9KbKUOY27o=DXTDtWRawVioPj+otEvJNryr8A@mail.gmail.com>
2020-12-29 14:09 ` Sergei Golubtsov
2020-12-29 15:55 ` Sergei Golubtsov
2020-12-29 17:56 ` Sergei Golubtsov
2020-12-29 21:49 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f8b7f2e-f3bb-1415-eb3b-b9b02390076a@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).