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 <dcbw at redhat.com> 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 at 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 at 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 at 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 <support at balena.io> 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 at 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 <http://www.linkedin.com/in/przemekgalazka>

przemek at sense.com.pl
https://www.sense-monitoring.com
<https://www.sense-monitoring.com/?utm_source=stopka&utm_medium=mail&utm_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:0000676863, NIP: 5213780421
BDO 000062957


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20190521/25b04659/attachment.html>