Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
On 06 March 2017 at 16:47 Dan Williams wrote:On Mon, 2017-03-06 at 15:35 +, colin.helliw...@ln-systems.comwrote:I have MM hooked into a Mux driver which is presenting two virtualports:one as the Primary, one for PPP. I'm attempting to fire up thedata/PPP with--enable and --simple-connect=.The

Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
(Sorry - misformatted that last one) > On 06 March 2017 at 16:47 Dan Williams wrote: > > On Mon, 2017-03-06 at 15:35 +, colin.helliw...@ln-systems.com > wrote: > > > I have MM hooked into a Mux driver which is presenting two virtual > > ports: > > one as the Primary, one for PPP. I'm attemp

Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
> On 07 March 2017 at 09:43 Colin Helliwell > wrote: > > (Sorry - misformatted that last one) > > > On 06 March 2017 at 16:47 Dan Williams wrote: > > > > On Mon, 2017-03-06 at 15:35 +, colin.helliw...@ln-systems.com > > wrote: > > > > > I have MM hooked into a Mux driver which is presen

ID_VENDOR_ID and ID_MODEL_ID reported wrong?

2017-03-07 Thread Aleksander Morgado
Hey, Looks like getting ID_VENDOR_ID and ID_MODEL_ID from the tty sysfs path may give the serial controller vid:pid, instead of the actual device vid:pid (which we get when getting the properties from the physical device sysfs path instead of the tty sysfs path). $ udevadm info -p /sys/devices/pc

Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
Is it right that MM should be showing the ppp port as going disconnected part way through the ppp negotiation? [see below] > On 07 March 2017 at 10:13 Colin Helliwell > wrote: > > ... > In case it's of use, here's the log of MM+pppd when trying (after a --enable) > the --simple-connect fo

Re: 'port forced close' after failed ppp

2017-03-07 Thread Aleksander Morgado
On Tue, Mar 7, 2017 at 1:26 PM, Colin Helliwell wrote: >> Mar 7 10:05:25 wg2 daemon.debug pppd[944]: sent [IPCP ConfReq id=0x1 >> ] >> Mar 7 10:05:25 wg2 daemon.info ModemManager[896]: [141125.484324] >> [src/mm-port-serial.c:1294] mm_port_serial_open(): (ttyMux0) device open >> count is

Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
> On 07 March 2017 at 13:50 Aleksander Morgado wrote: > > On Tue, Mar 7, 2017 at 1:26 PM, Colin Helliwell > > wrote: > > > > Mar 7 10:05:25 wg2 daemon.debug pppd[944]: sent [IPCP ConfReq id=0x1 > > > ] > > > Mar 7 10:05:25 wg2 daemon.info ModemManager[896]: [141125.484324] > > > [src/m

Re: 'port forced close' after failed ppp

2017-03-07 Thread Aleksander Morgado
On Tue, Mar 7, 2017 at 3:46 PM, Colin Helliwell wrote: >> > > Mar 7 10:05:25 wg2 daemon.debug pppd[944]: sent [IPCP ConfReq id=0x1 >> > > ] >> > > Mar 7 10:05:25 wg2 daemon.info ModemManager[896]: [141125.484324] >> > > [src/mm-port-serial.c:1294] mm_port_serial_open(): (ttyMux0) device ope

Re: 'port forced close' after failed ppp

2017-03-07 Thread Colin Helliwell
> On 07 March 2017 at 14:55 Aleksander Morgado wrote: > > On Tue, Mar 7, 2017 at 3:46 PM, Colin Helliwell > > wrote: > > > Yes, I see what you mean. Now, [my] confusion is: the PDP is (I believe) > > being activated on ttyMux1 - the virtual port which is set as the PPP port. > > But the con

Re: Parsing Cinterion RadioBand

2017-03-07 Thread Aleksander Morgado
On Mon, Mar 6, 2017 at 11:38 AM, wrote: > I’m using the Cinterion plugin on an EHS5. This does include ‘Radio Band’ in > its response to ‘AT^SCFG=?’, but in a format that > mm_cinterion_parse_scfg_test () may not be able to parse? > >^SCFG: "Radio/Band",("1"-"147") > > > > (Which I take to pr

Re: Parsing Cinterion RadioBand

2017-03-07 Thread Colin Helliwell
> On 07 March 2017 at 16:28 Aleksander Morgado wrote: > > On Mon, Mar 6, 2017 at 11:38 AM, wrote: > > > I’m using the Cinterion plugin on an EHS5. This does include ‘Radio Band’ in > > its response to ‘AT^SCFG=?’, but in a format that > > mm_cinterion_parse_scfg_test () may not be able to pars

[PATCH] cinterion: improve ^SCFG=? response parser to handle EHS5 format

2017-03-07 Thread Aleksander Morgado
Two main changes in the regex: * Ignore double quotes around interval numbers. * Ignore second set of values (i.e. the one after the comma), as it may not even be given). We now support at least these two formats: ^SCFG: "Radio/Band",("1-511","0-1") ^SCFG: "Radio/Band\",("1"-"147") Re

Re: [PATCH] cinterion: improve ^SCFG=? response parser to handle EHS5 format

2017-03-07 Thread Aleksander Morgado
On Tue, Mar 7, 2017 at 6:39 PM, Colin Helliwell wrote: > >> On 07 March 2017 at 16:44 Aleksander Morgado >> wrote: >> >> Two main changes in the regex: >> >> * Ignore double quotes around interval numbers. >> * Ignore second set of values (i.e. the one after the comma), as it >> may not even

Re: [PATCH] cinterion: improve ^SCFG=? response parser to handle EHS5 format

2017-03-07 Thread Colin Helliwell
> On 07 March 2017 at 16:44 Aleksander Morgado wrote: > > Two main changes in the regex: > > * Ignore double quotes around interval numbers. > * Ignore second set of values (i.e. the one after the comma), as it > may not even be given). > > We now support at least these two formats: > ^SC