https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-12-06T14:27:34ZOpen Source Mobile CommunicationsOsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=65842017-12-06T14:27:34Zpespin
<ul><li><strong>Assignee</strong> set to <i>55360</i></li></ul> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=65852017-12-06T14:46:21Zpespin
<ul><li><strong>Subject</strong> changed from <i>ofono: sierra_2 modem in prod unable to activate context</i> to <i>osmo-gsm-tester: sierra_2 modem in prod unable to activate context</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>55360</i> to <i>pespin</i></li></ul><p>The GGSN is sending an error inside the "Create PDP context request" message, as can be seen in the osmo-sgsn pcap trace in the tar.gz with all the run logs.</p>
<p>It worked in my R&D setup because I was using an older fixed version (3897). Once moving to the new trial (4117), I get the same issue in R&D. So, it seems between 3897->4117 something changed which we are not taking into account in osmo-gsm-tester, or we introduced a regression.</p> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=65862017-12-06T16:54:55Zneelsnhofmeyr@sysmocom.de
<ul></ul><blockquote>
<p>translated = gsm-wcdma-unknown-apn</p>
</blockquote>
<ul>
<li>WCDMA is the wrong RAN, this is about 2G, right?</li>
<li>Does the APN the modem is using match the osmo-ggsn config? Or does the osmo-ggsn config have a default APN set?</li>
</ul>
<p>That's what comes to mind on the first glance.</p> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=65962017-12-07T13:24:51Zpespin
<ul><li><strong>Subject</strong> changed from <i>osmo-gsm-tester: sierra_2 modem in prod unable to activate context</i> to <i>ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmi</i></li></ul><p>That's probably related to the "ims" pdp context which is an automatic one which is always created to support voice calls through packet-switched network, used for instance in LTE as far as I've been told. In the pcap traces we can actually see the modem trying to activate that one ("ims") while concurrently activating our own one ("internet").</p>
<p>The main issue seems to be that ofono doesn't have complete support for setting up contexts and it only specifies the kind of IP address it wants, but leaves the PDP type decision to the modem, which might use IPv4v6 to fullfil the IPv4 requirement. The problem is that osmo-ggsn didn't support Context Request for this kind of pdp type. I created a patch which adds support for it. After it is merged, the modem should be able to activate the context: <a class="external" href="https://gerrit.osmocom.org/#/c/5216/">https://gerrit.osmocom.org/#/c/5216/</a></p>
<p>The difference here is that in R&D, the modem tries to establish an IPv4 ctx after the IPV4v6 is rejected, and as a result it can eventually activate the context. In PROD env, however, it never tries to use IPv4 after the IPV4v6 one is rejected. lynxis pointed out that they may have been configured differently through the AT interface.</p>
<p>We still want to support specifying the type of PDP context we want to create from ofono user point of view, and so we should implement the missing bits in there to be able to do so. Consequently, I rename the task again to be ofono-related and paste here parts of the conversation with lynxis regarding next steps:<br /><pre>
ofono doesn't can not set the context type in a direct way
missing things in the ofono-qmi thing
ofono just ask the modem via qmi: attach context and I need a ipv4 address.
it should do "create pdp context type: ipv4, activate this context"
the whole pdp context handling is missing in ofono
drivers/qmimodem/gprs-context.c: qmi_activate_primary()
qmi_activate_primary is using APN/username/password/ipfamily as context. ipfamily != pdp context type
qmi_activate_primary should use "Profile Index 3GPP" or " Profile Index 3GPP2" instead which need to be created before
ipfamily = ipv4 "might" use a "dual". my ec20 first tried to get an dual context, because this fails, it's trying to get an ipv4 context
</pre></p>
<p>Information on the structures requeried to implement this new QMI WDS methods can be found in: <a class="external" href="https://cgit.freedesktop.org/libqmi/tree/data/qmi-service-wds.json">https://cgit.freedesktop.org/libqmi/tree/data/qmi-service-wds.json</a> , grep for "Create Profile", "Start Network" and "Profile Index 3GPP".</p> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=65972017-12-07T13:25:04Zpespin
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>New</i></li><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>lynxis</i></li></ul> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=67722017-12-12T15:28:51Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/2683">Bug #2683</a>: ofono: EC20 failing to create ipv6 or dual contexts</i> added</li></ul> OsmoGSMTester - Bug #2713: ofono: chosen pdp type (v4, v6, dual) not strictly followed in ofono qmihttps://osmocom.org/issues/2713?journal_id=170612020-01-08T22:40:34Zlaforge
<ul><li><strong>Assignee</strong> deleted (<del><i>lynxis</i></del>)</li></ul>