'port forced close' after failed ppp

[colin.helliwell at ln-systems.com]

I have MM hooked into a Mux driver which is presenting two virtual ports:
one as the Primary, one for PPP. I'm attempting to fire up the data/PPP with
--enable and --simple-connect=.

The PPP is failing, no doubt a problem with the config in that itself, but I
have a couple of puzzlements:

 

MM is getting a "[src/mm-port-serial.c:942] common_input_available():
(ttyMux1) unexpected port hangup!" . But I can't see in the source where the
G_IO_HUP [?] would be originating - maybe a handshake signal on the port?

 

I'm unable to retry - even with a '--simple-disconnect'/'--disable'/+retry,
MM is giving "[src/mm-iface-modem-simple.c:221] connect_bearer_ready():
Couldn't connect bearer: 'Couldn't connect: cannot keep data port open.Could
not open serial device ttyMux1: it has been forced closed". Only restarting
MM seems to get rid of this - should/could this error state get cleared down
somehow?

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20170306/8ff908d3/attachment.html>