Re: pppd timed out or didn't initialize our dbus module

[Przemyslaw Galazka]

Yes.
I am almost sure that one or two from this list:
remotename 3gppp nocrtscts modem asyncmap 0 ipcp-accept-local
ipcp-accept-remote ipparam 3gppp usepeerdns noccp noipx

but it is not supported by NM in config file. If this can be added to NM
master branch we can narrow this down. I bet on  nocrtscts and nocpp option


pon., 20 maj 2019 o 17:41 Dan Williams  napisał(a):

> On Mon, 2019-05-20 at 12:02 +0200, Przemyslaw Galazka wrote:
> > Hi Dan,
> > this question regarding bearer timeout is sorted out.  It seems that
> > bigger
> > timeout will not fix the issue. It is all about configuring ppp
> > daemon
> > correctly.
> >
> > Adding this line to /etc/ppp/options resolved the issue - IP was
> > granted.
> >
> > root@7d15519:~# cat /etc/ppp/options
> > dump remotename 3gppp nocrtscts modem asyncmap 0 ipcp-accept-local
> > ipcp-accept-remote ipparam 3gppp usepeerdns noccp noipx
>
> NM will attempt to add some options to pppd for you, so that you can
> use different options on different devices if needed. Do you know which
> of the options here are required to make it work?
>
> Dan
>
> > Device will get IP address and ppp0 interface. I am not sure if net
> > is
> > working cos when we remove cable for Ethernet it goes offline in
> > Balena
> > Dashboard. Ping is working
> >
> > root@7d15519:~# ping o2.pl -Ippp0
> > PING o2.pl (212.77.100.61): 56 data bytes
> > 64 bytes from 212.77.100.61: seq=0 ttl=55 time=909.741 ms
> > 64 bytes from 212.77.100.61: seq=1 ttl=55 time=389.459 ms
> > 64 bytes from 212.77.100.61: seq=2 ttl=55 time=325.432 ms
> > 64 bytes from 212.77.100.61: seq=3 ttl=55 time=446.667 ms
> > 64 bytes from 212.77.100.61: seq=4 ttl=55 time=425.208 ms
> > ^C
> > --- o2.pl ping statistics ---
> > 6 packets transmitted, 5 packets received, 16% packet loss
> > round-trip min/avg/max = 325.432/499.301/909.741 ms
> > root@7d15519:~#
> >
> >
> > But this is different story.
> > Thank you all for help and I hope that magic options set will help
> > others
> > to use M66
> >
> >
> >
> >
> > wt., 14 maj 2019 o 18:04  napisał(a):
> >
> > > Hi,
> > > It seems that this was answered on a different support thread as
> > > well.
> > > Give us a note if there is a pending question in this thread.
> > >
> > > Kind regards,
> > > Thodoris
> > >
> >
> > ___
> > ModemManager-devel mailing list
> > ModemManager-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>
>

-- 
best regards / z poważaniem

Przemysław Gałązka, CEO
+48 889 348 628

linkedin 

prze...@sense.com.pl
https://www.sense-monitoring.com


[image:
sense-logo_monitoring-poziom-s2-add135aef733ff520b43a7bf69e9cd05.png
(281×100)]
Sense Monitoring sp. z o.o
Nalkowskiej 11
38-500 Sanok, Poland
KRS:676863, NIP: 5213780421
BDO 62957


Please note that all information in this message or attachmentes thereof
shall be construed as business secrets and are shared only with the
intended recepients. // Otrzymana przez Panią/Pana wiadomość oraz
ewentualne załączone do niej pliki stanowią tajemnicę przedsiębiorstwa i są
przeznaczone tylko dla wymienionych adresatów.
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Dan Williams]

On Mon, 2019-05-20 at 12:02 +0200, Przemyslaw Galazka wrote:
> Hi Dan,
> this question regarding bearer timeout is sorted out.  It seems that
> bigger
> timeout will not fix the issue. It is all about configuring ppp
> daemon
> correctly.
> 
> Adding this line to /etc/ppp/options resolved the issue - IP was
> granted.
> 
> root@7d15519:~# cat /etc/ppp/options
> dump remotename 3gppp nocrtscts modem asyncmap 0 ipcp-accept-local
> ipcp-accept-remote ipparam 3gppp usepeerdns noccp noipx

NM will attempt to add some options to pppd for you, so that you can
use different options on different devices if needed. Do you know which
of the options here are required to make it work?

Dan

> Device will get IP address and ppp0 interface. I am not sure if net
> is
> working cos when we remove cable for Ethernet it goes offline in
> Balena
> Dashboard. Ping is working
> 
> root@7d15519:~# ping o2.pl -Ippp0
> PING o2.pl (212.77.100.61): 56 data bytes
> 64 bytes from 212.77.100.61: seq=0 ttl=55 time=909.741 ms
> 64 bytes from 212.77.100.61: seq=1 ttl=55 time=389.459 ms
> 64 bytes from 212.77.100.61: seq=2 ttl=55 time=325.432 ms
> 64 bytes from 212.77.100.61: seq=3 ttl=55 time=446.667 ms
> 64 bytes from 212.77.100.61: seq=4 ttl=55 time=425.208 ms
> ^C
> --- o2.pl ping statistics ---
> 6 packets transmitted, 5 packets received, 16% packet loss
> round-trip min/avg/max = 325.432/499.301/909.741 ms
> root@7d15519:~#
> 
> 
> But this is different story.
> Thank you all for help and I hope that magic options set will help
> others
> to use M66
> 
> 
> 
> 
> wt., 14 maj 2019 o 18:04  napisał(a):
> 
> > Hi,
> > It seems that this was answered on a different support thread as
> > well.
> > Give us a note if there is a pending question in this thread.
> > 
> > Kind regards,
> > Thodoris
> > 
> 
> ___
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Przemyslaw Galazka]

Hi Dan,
this question regarding bearer timeout is sorted out.  It seems that bigger
timeout will not fix the issue. It is all about configuring ppp daemon
correctly.

Adding this line to /etc/ppp/options resolved the issue - IP was granted.

root@7d15519:~# cat /etc/ppp/options
dump remotename 3gppp nocrtscts modem asyncmap 0 ipcp-accept-local
ipcp-accept-remote ipparam 3gppp usepeerdns noccp noipx

Device will get IP address and ppp0 interface. I am not sure if net is
working cos when we remove cable for Ethernet it goes offline in Balena
Dashboard. Ping is working

root@7d15519:~# ping o2.pl -Ippp0
PING o2.pl (212.77.100.61): 56 data bytes
64 bytes from 212.77.100.61: seq=0 ttl=55 time=909.741 ms
64 bytes from 212.77.100.61: seq=1 ttl=55 time=389.459 ms
64 bytes from 212.77.100.61: seq=2 ttl=55 time=325.432 ms
64 bytes from 212.77.100.61: seq=3 ttl=55 time=446.667 ms
64 bytes from 212.77.100.61: seq=4 ttl=55 time=425.208 ms
^C
--- o2.pl ping statistics ---
6 packets transmitted, 5 packets received, 16% packet loss
round-trip min/avg/max = 325.432/499.301/909.741 ms
root@7d15519:~#


But this is different story.
Thank you all for help and I hope that magic options set will help others
to use M66




wt., 14 maj 2019 o 18:04  napisał(a):

> Hi,
> It seems that this was answered on a different support thread as well.
> Give us a note if there is a pending question in this thread.
>
> Kind regards,
> Thodoris
>


-- 
best regards / z poważaniem

Przemysław Gałązka, CEO
+48 889 348 628

linkedin 

prze...@sense.com.pl
https://www.sense-monitoring.com


[image:
sense-logo_monitoring-poziom-s2-add135aef733ff520b43a7bf69e9cd05.png
(281×100)]
Sense Monitoring sp. z o.o
Nalkowskiej 11
38-500 Sanok, Poland
KRS:676863, NIP: 5213780421
BDO 62957


Please note that all information in this message or attachmentes thereof
shall be construed as business secrets and are shared only with the
intended recepients. // Otrzymana przez Panią/Pana wiadomość oraz
ewentualne załączone do niej pliki stanowią tajemnicę przedsiębiorstwa i są
przeznaczone tylko dla wymienionych adresatów.
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Dan Williams]

On Tue, 2019-05-14 at 16:44 +0200, Przemyslaw Galazka wrote:
> Thanks for input.
> 
> After changing logging level to debug for ppp demon, I can tell that
> it is
> trying to go through LCP phase and get IP address but ModemManager
> has
> configured 20 seconds timeout for this.
> It seems like NetworkManager is killing pppd in the middle of
> session,
> always after 20seconds.

Are you able to manually run pppd, without NetworkManager, to figure
out how long the PPP link setup actually takes? It's pretty unusual for
it to take 20+ seconds.  MM sends the timeout to NetworkManager, so NM
should be waiting at least 20s before terminating the connection
attempt.

Dan


> How we can change that timeout then? It seems that is is hardcoded in
> https://github.com/freedesktop/ModemManager/search?q=BEARER_IP_TIMEOUT_DEFAULT_q=BEARER_IP_TIMEOUT_DEFAULT
> 
> 
> 
> pt., 15 lut 2019 o 16:51 Reinhard Speyerer 
> napisał(a):
> 
> > On Fri, Feb 15, 2019 at 11:25:04AM +0100, Przemyslaw Galazka wrote:
> > > This is BalenaOS (resinOS) so probably yes it may be custom. I
> > > add
> > BalenaOS
> > > Support to this thread.
> > > 
> > > Florin, could you let us know what options are used for NM and
> > > ppp build
> > > regarding your OS?
> > > 
> > > pt., 15 lut 2019 o 10:25 Aleksander Morgado <
> > > aleksan...@aleksander.es>
> > > napisa??(a):
> > > 
> > > > Hey,
> > > > 
> > > > > > Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin
> > > > /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
> > > > > > Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin:
> > > > > > (plugin_init):
> > > > initializing
> > > > > > Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin:
> > > > > > (nm_phasechange):
> > > > status 3 / phase 'serial connection'
> > > > > > Jan 04 17:28:57 f8c790d NetworkManager[690]: 
> > [1546622937.1715]
> > > > ppp-manager: pppd timed out or didn't initialize our dbus
> > > > module
> > > > > > Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin:
> > > > > > (nm_phasechange):
> > > > status 1 / phase 'dead'
> > > > 
> > > > Is this a custom system that you build? if so, which are the
> > > > configure
> > > > options you use for NM and ppp?
> > > > 
> > 
> > Hi,
> > 
> > in case NM and ppp configure options look normal my suggestion for
> > narrowing down the problem would be to use the pppd command line
> > from the NetworkManager log without the "plugin
> > /usr/lib/pppd/2.4.5/nm-pppd-plugin.so" part and check if pppd also
> > times
> > out
> > when you start it manually. If it does try adding the options read
> > from
> > /etc/ppp/peers/gprs one after another. A common problem with some
> > TS 27.060
> > IP relay implementations in mobiles is the lack of proper VJ/CCP
> > support.
> > Please try adding novj noccp first.
> > 
> > Regards,
> > Reinhard
> > 
> 
> ___
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Przemyslaw Galazka]

Thanks for input.

After changing logging level to debug for ppp demon, I can tell that it is
trying to go through LCP phase and get IP address but ModemManager has
configured 20 seconds timeout for this.
It seems like NetworkManager is killing pppd in the middle of session,
always after 20seconds.

How we can change that timeout then? It seems that is is hardcoded in
https://github.com/freedesktop/ModemManager/search?q=BEARER_IP_TIMEOUT_DEFAULT_q=BEARER_IP_TIMEOUT_DEFAULT



pt., 15 lut 2019 o 16:51 Reinhard Speyerer  napisał(a):

> On Fri, Feb 15, 2019 at 11:25:04AM +0100, Przemyslaw Galazka wrote:
> > This is BalenaOS (resinOS) so probably yes it may be custom. I add
> BalenaOS
> > Support to this thread.
> >
> > Florin, could you let us know what options are used for NM and ppp build
> > regarding your OS?
> >
> > pt., 15 lut 2019 o 10:25 Aleksander Morgado 
> > napisa??(a):
> >
> > > Hey,
> > >
> > > >> Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin
> > > /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
> > > >> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (plugin_init):
> > > initializing
> > > >> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange):
> > > status 3 / phase 'serial connection'
> > > >> Jan 04 17:28:57 f8c790d NetworkManager[690]: 
> [1546622937.1715]
> > > ppp-manager: pppd timed out or didn't initialize our dbus module
> > > >> Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange):
> > > status 1 / phase 'dead'
> > >
> > > Is this a custom system that you build? if so, which are the configure
> > > options you use for NM and ppp?
> > >
>
> Hi,
>
> in case NM and ppp configure options look normal my suggestion for
> narrowing down the problem would be to use the pppd command line
> from the NetworkManager log without the "plugin
> /usr/lib/pppd/2.4.5/nm-pppd-plugin.so" part and check if pppd also times
> out
> when you start it manually. If it does try adding the options read from
> /etc/ppp/peers/gprs one after another. A common problem with some TS 27.060
> IP relay implementations in mobiles is the lack of proper VJ/CCP support.
> Please try adding novj noccp first.
>
> Regards,
> Reinhard
>


-- 
best regards / z poważaniem

Przemysław Gałązka, CEO
+48 889 348 628

linkedin <http://www.linkedin.com/in/przemekgalazka>

prze...@sense.com.pl
https://www.sense-monitoring.com
<https://www.sense-monitoring.com/?utm_source=stopka_medium=mail_campaign=Przemek>

[image:
sense-logo_monitoring-poziom-s2-add135aef733ff520b43a7bf69e9cd05.png
(281×100)]
Sense Monitoring sp. z o.o
Nalkowskiej 11
38-500 Sanok, Poland
KRS:676863, NIP: 5213780421
BDO 62957


Please note that all information in this message or attachmentes thereof
shall be construed as business secrets and are shared only with the
intended recepients. // Otrzymana przez Panią/Pana wiadomość oraz
ewentualne załączone do niej pliki stanowią tajemnicę przedsiębiorstwa i są
przeznaczone tylko dla wymienionych adresatów.
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Reinhard Speyerer]

On Fri, Feb 15, 2019 at 11:25:04AM +0100, Przemyslaw Galazka wrote:
> This is BalenaOS (resinOS) so probably yes it may be custom. I add BalenaOS
> Support to this thread.
> 
> Florin, could you let us know what options are used for NM and ppp build
> regarding your OS?
> 
> pt., 15 lut 2019 o 10:25 Aleksander Morgado 
> napisa??(a):
> 
> > Hey,
> >
> > >> Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin
> > /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
> > >> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (plugin_init):
> > initializing
> > >> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange):
> > status 3 / phase 'serial connection'
> > >> Jan 04 17:28:57 f8c790d NetworkManager[690]:   [1546622937.1715]
> > ppp-manager: pppd timed out or didn't initialize our dbus module
> > >> Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange):
> > status 1 / phase 'dead'
> >
> > Is this a custom system that you build? if so, which are the configure
> > options you use for NM and ppp?
> >

Hi,

in case NM and ppp configure options look normal my suggestion for
narrowing down the problem would be to use the pppd command line
from the NetworkManager log without the "plugin
/usr/lib/pppd/2.4.5/nm-pppd-plugin.so" part and check if pppd also times out
when you start it manually. If it does try adding the options read from
/etc/ppp/peers/gprs one after another. A common problem with some TS 27.060
IP relay implementations in mobiles is the lack of proper VJ/CCP support.
Please try adding novj noccp first.

Regards,
Reinhard
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: pppd timed out or didn't initialize our dbus module

[Thodoris Greasidis]

Hi,


The build options that we are using for NM are:
```
../NetworkManager-1.14.4/configure --build=x86_64-linux --host=i686-poky-linux 
--target=i686-poky-linux --prefix=/usr --exec_prefix=/usr --bindir=/usr/bin 
--sbindir=/usr/sbin --libexecdir=/usr/libexec --datadir=/usr/share 
--sysconfdir=/etc --sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib 
--includedir=/usr/include --oldincludedir=/usr/include 
--infodir=/usr/share/info --mandir=/usr/share/man --disable-silent-rules 
--disable-dependency-tracking 
--with-libtool-sysroot=/home/floion/builds/balena-edison/build/tmp/work/core2-32-poky-linux/networkmanager/1.14.4-r0/recipe-sysroot
 --disable-gtk-doc --enable-introspection --disable-ifcfg-rh 
--disable-more-warnings --with-iptables=/usr/sbin/iptables --with-tests 
--with-nmtui=yes --with-udev-dir=/lib/udev --with-resolvconf=/sbin/resolvconf 
--disable-ovs --with-config-dhcp-default=internal --with-dhclient=no 
--disable-static --enable-bluez5-dun --with-dnsmasq=/usr/bin/dnsmasq 
--enable-ifupdown --with-modem-manager-1=yes --with-crypto=nss --enable-ppp 
--disable-qt --with-systemdsystemunitdir=/lib/systemd/system 
--with-session-tracking=systemd --enable-polkit --enable-wifi=yes --enable-nls
```
which reports:


```
System paths:
prefix: /usr
exec_prefix: /usr
sysconfdir: /etc
localstatedir: /var
runstatedir: /var/run
datadir: /usr/share
systemdunitdir: /lib/systemd/system
nmbinary: ${sbindir}/NetworkManager
nmconfdir: ${sysconfdir}/NetworkManager
nmlibdir: ${prefix}/lib/NetworkManager
nmdatadir: ${datadir}/NetworkManager
nmstatedir: ${localstatedir}/lib/NetworkManager
nmrundir: ${runstatedir}/NetworkManager


Platform:
session tracking: systemd-logind
suspend/resume: systemd
policykit: main.auth-polkit=true (restrictive modify.system)
polkit agent: yes
systemd-journald: yes (default: logging.backend=journal)
hostname persist: default
libaudit: no (default: logging.audit=false)


Features:
wext: yes
wifi: yes
ppp: yes plugins:/usr/lib/pppd/2.4.5
modemmanager-1: yes
ofono: no
concheck: yes
libteamdctl: no
ovs: no
libnm-glib: no
nmcli: yes
nmtui: yes
iwd: no


Configuration plugins (main.plugins=ifupdown)
ibft: no
ifcfg-rh: no
ifupdown: yes


Handlers for /etc/resolv.conf:
resolvconf: /sbin/resolvconf
netconfig: no
config-dns-rc-manager-default: resolvconf


DHCP clients (default internal):
dhcpcanon: no
dhclient: no
dhcpcd: no


Miscellaneous:
have introspection: yes
build documentation and manpages: no
install pregenerated documentation and manpages: yes
tests: yes
more-asserts: 0
more-logging: no
more-warnings: no
valgrind: nocode coverage: no
LTO: no
linker garbage collection: yes
JSON validation for libnm: yes
crypto: nss (have-gnutls: yes, have-nss: yes)
sanitizers:
Mozilla Public Suffix List: no
```


The build options for PPP are:
```
./configure --build=x86_64-linux --host=i686-poky-linux 
--target=i686-poky-linux --prefix=/usr --exec_prefix=/usr -
-bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/libexec 
--datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com --lo
calstatedir=/var --libdir=/usr/lib --includedir=/usr/include 
--oldincludedir=/usr/include --infodir=/usr/share/info 
--mandir=/usr/share/man--disable-silent-rules --disable-dependency-tracking 
--with-libtool-sysroot=/home/floion/builds/balena-edison/build/tmp/work/core2-32-poky-linux/ppp/2.4.7-r0/recipe-s
ysroot --disable-strip --disable-staticConfiguring for Linux
```


Give us a note if you need any further details on this.


Kind regards,
Thodoris

—
Thodoris Greasidis

--- original message ---
On February 15, 2019, 12:25 PM GMT+2 p...@sense.com.pl wrote:


This is BalenaOS (resinOS) so probably yes it may be custom. I add BalenaOS 
Support to this thread.


Florin, could you let us know what options are used for NM and ppp build 
regarding your OS?



> pt., 15 lut 2019 o 10:25 Aleksander Morgado  
> napisał(a):


>> Hey,


>>>> Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin 
>>>> /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.

>>>> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (plugin_init): 
>>>> initializing

>>>> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange): 
>>>> status 3 / phase 'serial connection'

>>>> Jan 04 17:28:57 f8c790d NetworkManager[690]:  [1546622937.1715] 
>>>> ppp-manager: pppd timed out or didn't initialize our dbus module

>>>> Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange): 
>>>> status 1 / phase 'dead'


>> Is this a custom system that you build? if so, which are the configure

>> options you use for NM and ppp?


>> -- 

>> Aleksander

>> https://aleksander.es





-- 



best regards / z poważaniem




Przemysław Gałązka, CEO


+48 889 348 628




linkedin



prze...@sense.com.pl 

https://www.sense-monitoring.com





Sense Monitoring sp. z o.o

Nalkowskiej 11

38

Re: pppd timed out or didn't initialize our dbus module

[Aleksander Morgado]

Hey,

>> Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin 
>> /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
>> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (plugin_init): 
>> initializing
>> Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange): status 
>> 3 / phase 'serial connection'
>> Jan 04 17:28:57 f8c790d NetworkManager[690]:   [1546622937.1715] 
>> ppp-manager: pppd timed out or didn't initialize our dbus module
>> Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange): status 
>> 1 / phase 'dead'

Is this a custom system that you build? if so, which are the configure
options you use for NM and ppp?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

pppd timed out or didn't initialize our dbus module

[Przemyslaw Galazka]

Hello,

we have a standard generic modem (Quactel M66, one uart working in
transparent mode).
MM is working just fine - registering and connecting to the home network.
When NetworkManager pickup to establish PPP connection we get the strange
problem - seems like sth is blocking the serial port (MM?)

MM version is 1.8.2

*Logs from NM*
Jan 04 17:28:36 f8c790d NetworkManager[690]:   [1546622916.5428]
ppp-manager: starting PPP connection
Jan 04 17:28:36 f8c790d NetworkManager[690]:  [1546622916.5443]
ppp-manager: command line: /usr/sbin/pppd nodetach lock nodefaultroute ipv6
, debug ttyUSB0 noipdefault 115200 noauth usepeerdns mru 128 mtu 128
lcp-echo-failure 0 lcp-echo-interval 0 idle 0 ipparam
/org/freedesktop/NetworkManager/PPP/14 plugin
/usr/lib/pppd/2.4.5/nm-pppd-plugin.so
Jan 04 17:28:36 f8c790d NetworkManager[690]:   [1546622916.5679]
ppp-manager: pppd started with pid 2596
Jan 04 17:28:36 f8c790d NetworkManager[690]:   [1546622916.5712]
modem["ttyUSB0"]: IPv6 configuration disabled
Jan 04 17:28:36 f8c790d NetworkManager[690]:  [1546622916.5728]
device[0x16da2d8] (ttyUSB0): activation-stage: complete
activate_stage3_ip_config_start,v4 (id 1657)
Jan 04 17:28:36 f8c790d NetworkManager[690]: Plugin
/usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (plugin_init):
initializing
*Jan 04 17:28:36 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange):
status 3 / phase 'serial connection'*


Jan 04 17:28:57 f8c790d NetworkManager[690]:   [1546622937.1715]
ppp-manager: *pppd timed out or didn't initialize our dbus module*
Jan 04 17:28:57 f8c790d pppd[2596]: nm-ppp-plugin: (nm_phasechange): status
1 / phase 'dead'


*And when we use ppp demon manually (without MM and NM) all just works so
hardware is just fine.*

*root@f8c790d:~#  pppd call gprs*
pppd options in effect:
debug # (from /etc/ppp/peers/gprs)
nodetach # (from /etc/ppp/peers/gprs)
dump # (from /etc/ppp/peers/gprs)
noauth # (from /etc/ppp/peers/gprs)
user internet # (from /etc/ppp/peers/gprs)
remotename 3gppp # (from /etc/ppp/peers/gprs)
/dev/ttyUSB0 # (from /etc/ppp/peers/gprs)
115200 # (from /etc/ppp/peers/gprs)
lock # (from /etc/ppp/peers/gprs)
connect chat -s -v -f /etc/chatscripts/quectel-chat-connect -T playmetric #
(from /etc/ppp/peers/gprs)
disconnect chat -s -v -f /etc/chatscripts/quectel-chat-disconnect # (from
/etc/ppp/peers/gprs)
nocrtscts # (from /etc/ppp/peers/gprs)
modem # (from /etc/ppp/peers/gprs)
asyncmap 0 # (from /etc/ppp/options)
mru 296 # (from /etc/ppp/peers/gprs)
mtu 296 # (from /etc/ppp/peers/gprs)
lcp-echo-failure 4 # (from /etc/ppp/options)
lcp-echo-interval 30 # (from /etc/ppp/options)
show-password # (from /etc/ppp/options)
novj # (from /etc/ppp/peers/gprs)
novjccomp # (from /etc/ppp/peers/gprs)
ipcp-accept-local # (from /etc/ppp/peers/gprs)
ipcp-accept-remote # (from /etc/ppp/peers/gprs)
ipparam 3gppp # (from /etc/ppp/peers/gprs)
noipdefault # (from /etc/ppp/peers/gprs)
ipcp-max-failure 30 # (from /etc/ppp/peers/gprs)
defaultroute # (from /etc/ppp/peers/gprs)
usepeerdns # (from /etc/ppp/peers/gprs)
noccp # (from /etc/ppp/peers/gprs)
noipx # (from /etc/ppp/options)
abort on (BUSY)
abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (ERROR)
abort on (NO ANSWER)
timeout set to 30 seconds
send (AT^M)
expect (OK)
^M
OK
 -- got it

send (ATE0^M)
expect (OK)
^M
^M
OK
 -- got it

send (ATI;+CSUB;+CSQ;+CPIN?;+COPS?;+CGREG?;^M)
expect (OK)
^M
^M
Quectel_Ltd^M
Quectel_M66^M
Revision: M66FAR01A08BT^M
^M
SubEdition:V03^M
^M
+CSQ: 29,0^M
^M
+CPIN: READY^M
^M
+COPS: 0,0,"T-Mobile.pl"^M
^M
+CGREG: 0,5^M
^M
OK
 -- got it

send (AT+CGDCONT=1,"IP","playmetric",,0,0^M)
expect (OK)
^M
^M
OK
 -- got it

send (ATD*99#^M)
expect (CONNECT)
^M
^M
*CONNECT*
 -- got it

Script chat -s -v -f /etc/chatscripts/quectel-chat-connect -T playmetric
finished (pid 29953), status = 0x0
Serial connection established.
using channel 13
Using interface ppp0
Connect: ppp0 <--> /dev/ttyUSB0
sent [LCP ConfReq id=0x1   
 ]
rcvd [LCP ConfReq id=0x1]
sent [LCP ConfAck id=0x1]
rcvd [LCP ConfNak id=0x1 ]
sent [LCP ConfReq id=0x2   
 ]
rcvd [LCP ConfAck id=0x2   
 ]
sent [LCP EchoReq id=0x0 magic=0x604edc61]
sent [PAP AuthReq id=0x1 user="internet" password="internet"]
rcvd [LCP EchoRep id=0x0 magic=0x0]
rcvd [PAP AuthAck id=0x1 ""]
*PAP authentication succeeded*
sent [IPCP ConfReq id=0x1   ]
rcvd [IPCP ConfReq id=0x1 ]
sent [IPCP ConfAck id=0x1 ]
rcvd [IPCP ConfNak id=0x1  
]
sent [IPCP ConfReq id=0x2  
]
rcvd [IPCP ConfAck id=0x2  
]
local  IP address 10.195.226.215
remote IP address 192.168.254.254
primary   DNS address 89.108.195.20
secondary DNS address 89.108.202.21
Script /etc/ppp/ip-up started (pid 29971)
Script /etc/ppp/ip-up finished (pid 29971), status = 0x0


*And connection works...*

*root@f8c790d:~# ping 8.8.8.8 -Ippp0*
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=802 ms
64 bytes fr