Re: Quectel UC20: Correct way to get it up and running on embedded?

On 23 March 2017 at 02:42, Dan Williams wrote: > On Wed, 2017-03-22 at 21:36 +0100, Einar Jón wrote: >> On 20 March 2017 at 19:33, Dan Williams wrote: >> > On Mon, 2017-03-20 at 12:14 +0100, Einar Jón wrote: >> > >> > > 4) Is ModemManager 1.4.10 too old? Are

Re: Quectel UC20: Correct way to get it up and running on embedded?

Hi again. This is still a mess... On 28 March 2017 at 22:45, Aleksander Morgado wrote: > On Tue, Mar 28, 2017 at 8:39 PM, Dan Williams wrote: >>> > > RE PolicyMismatch: we're not quite sure what that error >>> > > represents; >>> > > we've determined

Re: Quectel UC20: Correct way to get it up and running on embedded?

On Tue, Mar 28, 2017 at 8:39 PM, Dan Williams wrote: >> > > RE PolicyMismatch: we're not quite sure what that error >> > > represents; >> > > we've determined that in some cases it means IPv4 vs. IPv6 >> > > mismatch and >> > > profiles in the modem, but that doesn't seem to

Re: Quectel UC20: Correct way to get it up and running on embedded?

Einar Jón writes: > On 23 March 2017 at 02:42, Dan Williams wrote: >> >> RE PolicyMismatch: we're not quite sure what that error represents; >> we've determined that in some cases it means IPv4 vs. IPv6 mismatch and >> profiles in the modem, but that

Re: Quectel UC20: Correct way to get it up and running on embedded?

Thanks for the update. A couple of more question about resetting the modem, but I should probably start a new thread for follow-up questions. TLDR: 1) Once I have PolicyMismatch, I'm stuck until I reset. What to do then? See -- 1 --- below 2) I can't reset this modem using "mmcli -r -m0". What

Re: Quectel UC20: Correct way to get it up and running on embedded?

On Wed, 2017-03-22 at 21:36 +0100, Einar Jón wrote: > TLDR: I guess most of my problems are from calling ifup in the wrong > state (CONNECTING instead of CONNECTED). More inline. > I might bring some follow-up questions next week. As you say below, I was wrong in the last mail because I assumed