[LEDE-DEV] [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.

[Matti Laakso]

Hi Nikolay,

On 09.12.2016 11:57, Nikolay Ledovskikh wrote:
> I'm using multiple modems
>
> config interface 'wan1'
>          option proto 'qmi'
>          option device '/dev/cdc-wdm0'
>          option apn 'internet.megafon.ru'
>          option ipv6 '0'
>          option metric '1'
>
> config interface 'wan2'
>          option proto 'qmi'
>          option device '/dev/cdc-wdm1'
>          option apn 'internet.beeline.ru'
>          option ipv6 '0'
>          option metric '2'
>
> And 2 more modems

Are all modems the same? Do they have same firmware versions? Are you 
sure that the mapping of different /dev/cdc-wdmX nodes always stay the 
same? It could be that on some boot the modem with the Megafon SIM gets 
/dev/cdc-wdm0 and on the second boot it gets /dev/cdc-wdm1 or some other 
number. Using autoconnect may ignore the APN, and the modems seem to 
work correctly. If you remove the APN options, does it work then?

>
> And with your patch logread shows endlessly:
> Fri Dec  9 09:38:15 2016 daemon.notice netifd: wan3 (18612): Command
> failed: Permission denied
> Fri Dec  9 09:38:15 2016 daemon.notice netifd: Interface 'wan3' is now down
> Fri Dec  9 09:38:15 2016 daemon.notice netifd: Interface 'wan3' is
> setting up now
> Fri Dec  9 09:38:15 2016 daemon.notice netifd: wan4 (18611): Waiting
> for network registration
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan4 (18611): Starting
> network wan4
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan3 (18625): Waiting
> for network registration
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan4 (18611): Unable to
> connect IPv4
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan3 (18625): Starting
> network wan3
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan4 (18655): Stopping
> network wan4
> Fri Dec  9 09:38:16 2016 daemon.notice netifd: wan4 (18655): Command
> failed: Permission denied

Just a note, the "Command failed: Permission denied" error is unrelated.

Matti

>
> About cgdcont:
> 1'st modem:
> at+cgdcont?
> +CGDCONT: 1,"IP","internet.megafon.ru","0.0.0.0",0,0
> +CGDCONT: 3,"IP","internet.megafon.ru","0.0.0.0",0,0
>
> 2'nd modem:
> at+cgdcont?
> +CGDCONT: 1,"IP","internet.beeline.ru","0.0.0.0",0,0
> +CGDCONT: 3,"IP","internet.beeline.ru","0.0.0.0",0,0
>
> And 2 more modems
>
> Only one (wan2) gets up and connected to network. What I'm doing wrong
>
> 2016-12-09 12:35 GMT+03:00 Matti Laakso <malaakso at elisanet.fi>:
>> On 09.12.2016 11:27, Petr Štetiar wrote:
>>> Matti Laakso <malaakso at elisanet.fi> [2016-12-09 10:23:24]:
>>>
>>>> I don't think that the autoconnect setting is "transferred" to the
>>>> network, rather it could be tied to a specific call profile index, which
>>>> has the wrong APN. If your Slovakian SIM card has several predefined
>>>> profiles, this could be the case. If your modem exposes a virtual serial
>>>> port which accepts AT-commands, you could use AT+CGDCONT? to check.
>>> Thanks for the additional hints. Details about my modem:
>>>
>>>    ATI
>>>    Quectel
>>>    EC20
>>>    Revision: EC20EQAR02A05E2G
>>>
>>> I knew, that there's only one profile defined, operator has deleted all
>>> other
>>> profiles, there's currently only one APN defined.
>>>
>>>    AT+CGDCONT?
>>>    +CGDCONT: 1,"IPV4V6","","0.0.0.0",0,0
>>
>> Well, there's no APN defined (it's an empty string), and who knows, maybe
>> the modem ignores the APN provided via QMI when enabling autoconnect... Does
>> your working Czech SIM card have a valid APN string?
>>
>> Matti
>>
>>
>>>> I agree fully. That's why I added the autoconnect option in my last
>>>> patch and defaulted it to disabled.
>>> Great, I've missed this patch. Going to take a look at it.
>>>
>>> -- ynezz
>>
>
>