Hey Dan and all,
> > > > The main issue with this approach is that ModemManager would do a
> > > > lot
> > > > of tasks that were exclusively done by NetworkManager before,
> > > > like
> > > > IP
> > > > addressing setup or IP routing setup. I'm sure we can instruct NM
> > > > to
> > > > play nic
On Thu, 2019-06-27 at 11:12 +0200, Thomas Haller wrote:
> On Thu, 2019-06-27 at 10:40 +0200, Piotr Figiel wrote:
> > Hi,
> >
> > czw., 27 cze 2019 o 10:20 Aleksander Morgado
> > napisał(a):
> > > The main issue with this approach is that ModemManager would do a
> > > lot
> > > of tasks that were
On Thu, 2019-06-27 at 10:40 +0200, Piotr Figiel wrote:
> Hi,
>
> czw., 27 cze 2019 o 10:20 Aleksander Morgado
> napisał(a):
> > The main issue with this approach is that ModemManager would do a lot
> > of tasks that were exclusively done by NetworkManager before, like IP
> > addressing setup or I
On Thu, 2019-06-27 at 10:40 +0200, Piotr Figiel wrote:
> Hi,
>
> czw., 27 cze 2019 o 10:20 Aleksander Morgado
> napisał(a):
> > The main issue with this approach is that ModemManager would do a
> > lot
> > of tasks that were exclusively done by NetworkManager before, like
> > IP
> > addressing se
On Thu, 2019-06-27 at 10:20 +0200, Aleksander Morgado wrote:
> >
> The main issue with this approach is that ModemManager would do a lot
> of tasks that were exclusively done by NetworkManager before, like IP
> addressing setup or IP routing setup.
Hi,
Configuring IP addresses and routes must b
Hi,
czw., 27 cze 2019 o 10:20 Aleksander Morgado
napisał(a):
> The main issue with this approach is that ModemManager would do a lot
> of tasks that were exclusively done by NetworkManager before, like IP
> addressing setup or IP routing setup. I'm sure we can instruct NM to
> play nicely with th
> wt., 18 cze 2019 o 14:43 Aleksander Morgado
> napisał(a):
>
> > My opinion is a bit open on this, I liked the first way because we
> > would try to be as robust as possible and totally avoid using the port
> > with wrong CLOCAL settings, but I don't think we can have that
> > robustness unless w
Hi Aleksander,
wt., 18 cze 2019 o 14:43 Aleksander Morgado
napisał(a):
> My opinion is a bit open on this, I liked the first way because we
> would try to be as robust as possible and totally avoid using the port
> with wrong CLOCAL settings, but I don't think we can have that
> robustness unles
>
> Have you seen the following commit from NetworkManager for pppd? It has
> helped solve many of the issues of being in sync with pppd and MM that I have
> seen:
>
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a251712a729f676c9c2d38e469e4f88e250229ba
>
> Even with tha
> Date: Tue, 18 Jun 2019 14:43:10 +0200
> From: Aleksander Morgado
>
> In the past months we've seen several reports of issues with the TTY
> port "forced closed" and not being able to be reopened after that and
> things like that. The root cause from this problem is that MM tries to
> reuse the
Hey!
In the past months we've seen several reports of issues with the TTY
port "forced closed" and not being able to be reopened after that and
things like that. The root cause from this problem is that MM tries to
reuse the TTY port after MM itself has detected a disconnection (via
+CGEV URCs or
11 matches
Mail list logo
