Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-12 Thread Lubomir Rintel 
On Wed, 2019-09-11 at 17:50 +0200, Christian Focke wrote:
> Hi Dan,
> 
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
> WIFI-HW  WIFI WWAN-HW  WWAN 
> enabled  enabled  enabled  disabled 
> 
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio wwan on
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
> WIFI-HW  WIFI WWAN-HW  WWAN
> enabled  enabled  enabled  enabled 
> cfocke@hp-eb-x360-1030-g3:~$ 
> 
> Works now; I feel embarrassed ...

I've seen people fall into this trap before. Not sure what would be the
best way to address that, but perhaps something like this could help:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/271

Adds "sw disabled" in red to nmcli output as in:

  ttyUSB2: unavailable
  "D-Link System 8 Series/C220 Chipset xHCI"
  gsm (option1), sw disabled, hw

> Since when must I explicitly enable radio? Never had to in the past ...
> 
> Thanks, Christian
> 
> -Original Message-
> From: Dan Williams 
> To: Christian Focke , Aleksander Morgado <
> aleksan...@aleksander.es>
> Cc: Lubomir Rintel , Thomas Haller 
> , modemmanager-devel@lists.freedesktop.org <
> modemmanager-devel@lists.freedesktop.org>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Wed, 11 Sep 2019 10:08:10 -0500
> 
> On Wed, 2019-09-11 at 16:13 +0200, Christian Focke wrote:
> > Hi Dan,
> > Thanks; here's what I did:
> 
> How about:
> nmcli radio
> ?
> Dan
> 
> > 1. reboot
> > 2. 1st shellcfocke@hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee
> > simple-connect_then_simple-disconnect_2.log
> > 3. 2nd shellcfocke@hp-eb-x360-1030-g3:~$ sudo systemctl stop 
> > ModemManagercfocke@hp-eb-x360-1030-g3:~$ sudo systemctl restart 
> > NetworkManagercfocke@hp-eb-x360-1030-g3:~$ sudo nmcli gen log level 
> > tracecfocke@hp-eb-x360-1030-g3:~$ sudo systemctl start 
> > ModemManagercfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> > connect="apn=a1.net,user=p...@a1plus.at,password=ppp"successfully
> > connected the modemcfocke@hp-eb-x360-1030-g3:~$ nmcli
> > devDEVICETYPE  STATE CONNECTION
> > wlp108s0  wifi  disconnected  -- cdc-
> > wdm0  gsm   unavailable   
> > -- loloopback  unmanaged -- 
> > cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> > disconnectsuccessfully disconnected all bearers in the 
> > modemcfocke@hp-eb-x360-1030-g3:~$ 
> > 'simple-connect_then_simple-disconnect_2.log' is attached.
> > -- Should I unloop modemmanager-devel@lists.freedesktop.org?
> > Thanks, Christian
> > -Original Message-From: Dan Williams To:
> > Focke Christian ,
> > AleksanderMorgado Cc: Lubomir Rintel <
> > lkund...@v3.sk>, Thomas Haller , 
> > modemmanager-devel@lists.freedesktop.org <
> > modemmanager-devel@lists.freedesktop.org>Subject: Re: hp-lt4132
> > 'unavailable' in NetworkManager on Debian 10Date: Wed, 11 Sep 2019
> > 08:07:46 -0500
> > On Wed, 2019-09-11 at 10:10 +, Focke Christian wrote:
> > > Hi Aleksander,Thanks; I have no idea how to do that because NM is
> > > brokenwithregardto the hp-lt4132.-- I already shared the NM logs;
> > > should I possibly also share theNMconfiguration? Which files?
> > 
> > Can you start up fresh, and then:systemctl stop ModemManagersystemctl
> > restart NetworkManagernmcli genlog level tracesystemctl start
> > ModemManagerand then grab logs again? I'd like to see things from the
> > start ofwhenNM finds the modem.Also, when you connect the modem
> > through NM, does 'nmcli dev'stillshowthe cdc-wdm device as
> > "unavailable"?Dan
> > > Kind regards, Christian-Original Message-From: Aleksander
> > > Morgado  > > aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>To:
> > > FockeChristian  > > focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>Cc:Lub
> > > omir Rintel  > > lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams <
> > > d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,Tho
> > > mas Haller  > > thomas%20haller%20%3cthal...@redhat.com%3e>>, 
> > > modemmanager-devel@lists.freedesktop.org <
> > > modemmanager-devel@lists.freedesktop.org > > %22modemmanager-de...@lists.freedesktop.org
> > > %22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>Subject:
> > > Re:hp-lt4132 'unavailable' in NetworkManager on Debian 10Date: Wed,
> > > 11Sep 2019 11:38:16 +0200
> > > Hey!
> > > On Wed, Sep 11, 2019 at 11:22 AM

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Dan Williams 
On Wed, 2019-09-11 at 17:50 +0200, Christian Focke wrote:
> Hi Dan,
> 
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
> WIFI-HW  WIFI WWAN-HW  WWAN 
> enabled  enabled  enabled  disabled 
> 
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio wwan on
> cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
> WIFI-HW  WIFI WWAN-HW  WWAN
> enabled  enabled  enabled  enabled 
> cfocke@hp-eb-x360-1030-g3:~$ 
> 
> Works now; I feel embarrassed ...
> 
> Since when must I explicitly enable radio? Never had to in the past
> ...

To be fair, there's likely a bug here that NM shouldn't ever get as far
as starting the WWAN connection if the device is unavailable. I'm
pretty sure I saw that in the logs somewhere.

The non-HW state is saved in the NM state file so maybe it got toggled
at some point via a GUI (like gnome-settings), or a bug in NM, or
something like that.

Glad we solved it though!

Dan


> Thanks, Christian
> 
> -Original Message-
> From: Dan Williams 
> To: Christian Focke , Aleksander Morgado <
> aleksan...@aleksander.es>
> Cc: Lubomir Rintel , Thomas Haller <
> thal...@redhat.com>
> , modemmanager-devel@lists.freedesktop.org <
> modemmanager-devel@lists.freedesktop.org>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Wed, 11 Sep 2019 10:08:10 -0500
> 
> On Wed, 2019-09-11 at 16:13 +0200, Christian Focke wrote:
> > Hi Dan,
> > Thanks; here's what I did:
> 
> How about:
> nmcli radio
> ?
> Dan
> 
> > 1. reboot
> > 2. 1st shellcfocke@hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee
> > simple-connect_then_simple-disconnect_2.log
> > 3. 2nd shellcfocke@hp-eb-x360-1030-g3:~$ sudo systemctl stop 
> > ModemManagercfocke@hp-eb-x360-1030-g3:~$ sudo systemctl restart 
> > NetworkManagercfocke@hp-eb-x360-1030-g3:~$ sudo nmcli gen log
> > level 
> > tracecfocke@hp-eb-x360-1030-g3:~$ sudo systemctl start 
> > ModemManagercfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> > connect="apn=a1.net,user=p...@a1plus.at,password=ppp"successfully
> > connected the modemcfocke@hp-eb-x360-1030-g3:~$ nmcli
> > devDEVICETYPE  STATE CONNECTION
> > wlp108s0  wifi  disconnected  -- cdc-
> > wdm0  gsm   unavailable   
> > -- loloopback  unmanaged -- 
> > cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> > disconnectsuccessfully disconnected all bearers in the 
> > modemcfocke@hp-eb-x360-1030-g3:~$ 
> > 'simple-connect_then_simple-disconnect_2.log' is attached.
> > -- Should I unloop modemmanager-devel@lists.freedesktop.org?
> > Thanks, Christian
> > -Original Message-From: Dan Williams To:
> > Focke Christian ,
> > AleksanderMorgado Cc: Lubomir Rintel <
> > lkund...@v3.sk>, Thomas Haller , 
> > modemmanager-devel@lists.freedesktop.org <
> > modemmanager-devel@lists.freedesktop.org>Subject: Re: hp-lt4132
> > 'unavailable' in NetworkManager on Debian 10Date: Wed, 11 Sep 2019
> > 08:07:46 -0500
> > On Wed, 2019-09-11 at 10:10 +, Focke Christian wrote:
> > > Hi Aleksander,Thanks; I have no idea how to do that because NM is
> > > brokenwithregardto the hp-lt4132.-- I already shared the NM logs;
> > > should I possibly also share theNMconfiguration? Which files?
> > 
> > Can you start up fresh, and then:systemctl stop
> > ModemManagersystemctl
> > restart NetworkManagernmcli genlog level tracesystemctl start
> > ModemManagerand then grab logs again? I'd like to see things from
> > the
> > start ofwhenNM finds the modem.Also, when you connect the modem
> > through NM, does 'nmcli dev'stillshowthe cdc-wdm device as
> > "unavailable"?Dan
> > > Kind regards, Christian-Original Message-From: Aleksander
> > > Morgado  > > aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>To:
> > > FockeChristian  > > focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>Cc:L
> > > ub
> > > omir Rintel  > > lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams <
> > > d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,T
> > > ho
> > > mas Haller  > > thomas%20haller%20%3cthal...@redhat.com%3e>>, 
> > > modemmanager-devel@lists.freedesktop.org <
> > > modemmanager-devel@lists.freedesktop.org > > %22modemmanager-de...@lists.freedesktop.org
> > > %22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>Subject:
> > > Re:hp-lt4132 'unavailable' in NetworkManager on Debian 10Date:
> > > Wed,
> > > 11Sep 201

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Christian Focke 
Hi Dan,

cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
WIFI-HW  WIFI WWAN-HW  WWAN 
enabled  enabled  enabled  disabled 

cfocke@hp-eb-x360-1030-g3:~$ nmcli radio wwan on
cfocke@hp-eb-x360-1030-g3:~$ nmcli radio
WIFI-HW  WIFI WWAN-HW  WWAN
enabled  enabled  enabled  enabled 
cfocke@hp-eb-x360-1030-g3:~$ 

Works now; I feel embarrassed ...

Since when must I explicitly enable radio? Never had to in the past ...

Thanks, Christian

-Original Message-
From: Dan Williams 
To: Christian Focke , Aleksander Morgado <
aleksan...@aleksander.es>
Cc: Lubomir Rintel , Thomas Haller 
, modemmanager-devel@lists.freedesktop.org <
modemmanager-devel@lists.freedesktop.org>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 11 Sep 2019 10:08:10 -0500

On Wed, 2019-09-11 at 16:13 +0200, Christian Focke wrote:
> Hi Dan,
> Thanks; here's what I did:

How about:
nmcli radio
?
Dan

> 1. reboot
> 2. 1st shellcfocke@hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee
> simple-connect_then_simple-disconnect_2.log
> 3. 2nd shellcfocke@hp-eb-x360-1030-g3:~$ sudo systemctl stop 
> ModemManagercfocke@hp-eb-x360-1030-g3:~$ sudo systemctl restart 
> NetworkManagercfocke@hp-eb-x360-1030-g3:~$ sudo nmcli gen log level 
> tracecfocke@hp-eb-x360-1030-g3:~$ sudo systemctl start 
> ModemManagercfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> connect="apn=a1.net,user=p...@a1plus.at,password=ppp"successfully
> connected the modemcfocke@hp-eb-x360-1030-g3:~$ nmcli
> devDEVICETYPE  STATE CONNECTION
> wlp108s0  wifi  disconnected  -- cdc-
> wdm0  gsm   unavailable   
> -- loloopback  unmanaged -- 
> cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-
> disconnectsuccessfully disconnected all bearers in the 
> modemcfocke@hp-eb-x360-1030-g3:~$ 
> 'simple-connect_then_simple-disconnect_2.log' is attached.
> -- Should I unloop modemmanager-devel@lists.freedesktop.org?
> Thanks, Christian
> -Original Message-From: Dan Williams To:
> Focke Christian ,
> AleksanderMorgado Cc: Lubomir Rintel <
> lkund...@v3.sk>, Thomas Haller , 
> modemmanager-devel@lists.freedesktop.org <
> modemmanager-devel@lists.freedesktop.org>Subject: Re: hp-lt4132
> 'unavailable' in NetworkManager on Debian 10Date: Wed, 11 Sep 2019
> 08:07:46 -0500
> On Wed, 2019-09-11 at 10:10 +, Focke Christian wrote:
> > Hi Aleksander,Thanks; I have no idea how to do that because NM is
> > brokenwithregardto the hp-lt4132.-- I already shared the NM logs;
> > should I possibly also share theNMconfiguration? Which files?
> 
> Can you start up fresh, and then:systemctl stop ModemManagersystemctl
> restart NetworkManagernmcli genlog level tracesystemctl start
> ModemManagerand then grab logs again? I'd like to see things from the
> start ofwhenNM finds the modem.Also, when you connect the modem
> through NM, does 'nmcli dev'stillshowthe cdc-wdm device as
> "unavailable"?Dan
> > Kind regards, Christian-Original Message-From: Aleksander
> > Morgado  > aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>To:
> > FockeChristian  > focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>Cc:Lub
> > omir Rintel  > lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams <
> > d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,Tho
> > mas Haller  > thomas%20haller%20%3cthal...@redhat.com%3e>>, 
> > modemmanager-devel@lists.freedesktop.org <
> > modemmanager-devel@lists.freedesktop.org > %22modemmanager-de...@lists.freedesktop.org
> > %22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>Subject:
> > Re:hp-lt4132 'unavailable' in NetworkManager on Debian 10Date: Wed,
> > 11Sep 2019 11:38:16 +0200
> > Hey!
> > On Wed, Sep 11, 2019 at 11:22 AM Focke Christian< > christian.fo...@mail.fernfh.ac.at>christian.fo...@mail.fernfh.ac.at
> > 
> > > wrote:
> > 
> > Yes I know, but with NM-GNOME and nmcli it doesn't work
> > atall;that'swhere I started from.
> > Actually it was you who instructed me to use mmcli to
> > analysetheissue on MM side.
> > 
> > Oh, ok, sorry for the confusion then :)
> > The MM analysis is done already, e.g. we can see how the
> > wholeconnection sequence works ok with mmcli --simple-connect. Now,
> > themissing part is the integration with NM. That is
> > whyLubomirrequestedfor *NetworkManager* logs while reproducing the
> > issue. Could youfollow his steps to get the logs and try to repro
> > the problem usingnmcli?


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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Dan Williams 
On Wed, 2019-09-11 at 16:13 +0200, Christian Focke wrote:
> Hi Dan,
> 
> Thanks; here's what I did:

How about:

nmcli radio

?

Dan


> 1. reboot
> 
> 2. 1st shell
> cfocke@hp-eb-x360-1030-g3:~$ sudo journalctl -fl |tee simple-
> connect_then_simple-disconnect_2.log
> 
> 3. 2nd shell
> cfocke@hp-eb-x360-1030-g3:~$ sudo systemctl stop ModemManager
> cfocke@hp-eb-x360-1030-g3:~$ sudo systemctl restart NetworkManager
> cfocke@hp-eb-x360-1030-g3:~$ sudo nmcli gen log level trace
> cfocke@hp-eb-x360-1030-g3:~$ sudo systemctl start ModemManager
> cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-connect="apn=a1.net,
> user=p...@a1plus.at,password=ppp"
> successfully connected the modem
> cfocke@hp-eb-x360-1030-g3:~$ nmcli dev
> DEVICETYPE  STATE CONNECTION 
> wlp108s0  wifi  disconnected  -- 
> cdc-wdm0  gsm   unavailable   -- 
> loloopback  unmanaged -- 
> cfocke@hp-eb-x360-1030-g3:~$ mmcli -m 0 --simple-disconnect
> successfully disconnected all bearers in the modem
> cfocke@hp-eb-x360-1030-g3:~$ 
> 
> 'simple-connect_then_simple-disconnect_2.log' is attached.
> 
> -- Should I unloop modemmanager-devel@lists.freedesktop.org?
> 
> Thanks, Christian
> 
> -Original Message-
> From: Dan Williams 
> To: Focke Christian , Aleksander
> Morgado 
> Cc: Lubomir Rintel , Thomas Haller <
> thal...@redhat.com>
> , modemmanager-devel@lists.freedesktop.org <
> modemmanager-devel@lists.freedesktop.org>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Wed, 11 Sep 2019 08:07:46 -0500
> 
> On Wed, 2019-09-11 at 10:10 +, Focke Christian wrote:
> > Hi Aleksander,
> > Thanks; I have no idea how to do that because NM is broken
> > withregard
> > to the hp-lt4132.
> > -- I already shared the NM logs; should I possibly also share the
> > NMconfiguration? Which files?
> 
> Can you start up fresh, and then:
> systemctl stop ModemManagersystemctl restart NetworkManagernmcli gen
> log level tracesystemctl start ModemManager
> and then grab logs again? I'd like to see things from the start of
> whenNM finds the modem.
> Also, when you connect the modem through NM, does 'nmcli dev'
> stillshow
> the cdc-wdm device as "unavailable"?
> Dan
> > Kind regards, Christian
> > -Original Message-From: Aleksander Morgado <
> > aleksan...@aleksander.es > aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>To: Focke
> > Christian  > focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>Cc:
> > Lubomir Rintel  > lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams <
> > d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,Tho
> > ma
> > s Haller  > thomas%20haller%20%3cthal...@redhat.com%3e>>, 
> > modemmanager-devel@lists.freedesktop.org <
> > modemmanager-devel@lists.freedesktop.org > %22modemmanager-de...@lists.freedesktop.org
> > %22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>Subject: Re:
> > hp-lt4132 'unavailable' in NetworkManager on Debian 10Date: Wed, 11
> > Sep 2019 11:38:16 +0200
> > 
> > Hey!
> > 
> > On Wed, Sep 11, 2019 at 11:22 AM Focke Christian
> > <
> > <mailto:christian.fo...@mail.fernfh.ac.at>
> > christian.fo...@mail.fernfh.ac.at
> > 
> > > wrote:
> > 
> > Yes I know, but with NM-GNOME and nmcli it doesn't work at
> > all;that's
> > where I started from.
> > 
> > Actually it was you who instructed me to use mmcli to analyse
> > theissue on MM side.
> > 
> > 
> > Oh, ok, sorry for the confusion then :)
> > 
> > The MM analysis is done already, e.g. we can see how the whole
> > connection sequence works ok with mmcli --simple-connect. Now, the
> > missing part is the integration with NM. That is why
> > Lubomirrequested
> > for *NetworkManager* logs while reproducing the issue. Could you
> > follow his steps to get the logs and try to repro the problem using
> > nmcli?
> 
> 

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Focke Christian 
Hi Aleksander,

Thanks; I have no idea how to do that because NM is broken with regard to the 
hp-lt4132.

-- I already shared the NM logs; should I possibly also share the NM 
configuration? Which files?

Kind regards, Christian

-Original Message-
From: Aleksander Morgado 
mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
To: Focke Christian 
mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
Cc: Lubomir Rintel 
mailto:lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams 
mailto:dan%20williams%20%3cd...@redhat.com%3e>>, Thomas Haller 
mailto:thomas%20haller%20%3cthal...@redhat.com%3e>>, 
modemmanager-devel@lists.freedesktop.org 
mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 11 Sep 2019 11:38:16 +0200


Hey!


On Wed, Sep 11, 2019 at 11:22 AM Focke Christian

<

<mailto:christian.fo...@mail.fernfh.ac.at>

christian.fo...@mail.fernfh.ac.at

> wrote:


Yes I know, but with NM-GNOME and nmcli it doesn't work at all; that's where I 
started from.


Actually it was you who instructed me to use mmcli to analyse the issue on MM 
side.



Oh, ok, sorry for the confusion then :)


The MM analysis is done already, e.g. we can see how the whole

connection sequence works ok with mmcli --simple-connect. Now, the

missing part is the integration with NM. That is why Lubomir requested

for *NetworkManager* logs while reproducing the issue. Could you

follow his steps to get the logs and try to repro the problem using

nmcli?

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Dan Williams 
On Wed, 2019-09-11 at 10:10 +, Focke Christian wrote:
> Hi Aleksander,
> 
> Thanks; I have no idea how to do that because NM is broken with
> regard to the hp-lt4132.
> 
> -- I already shared the NM logs; should I possibly also share the NM
> configuration? Which files?

Can you start up fresh, and then:

systemctl stop ModemManager
systemctl restart NetworkManager
nmcli gen log level trace
systemctl start ModemManager

and then grab logs again? I'd like to see things from the start of when
NM finds the modem.

Also, when you connect the modem through NM, does 'nmcli dev' still
show the cdc-wdm device as "unavailable"?

Dan

> Kind regards, Christian
> 
> -Original Message-
> From: Aleksander Morgado  aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
> To: Focke Christian  focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
> Cc: Lubomir Rintel  lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams <
> d...@redhat.com<mailto:dan%20williams%20%3cd...@redhat.com%3e>>,
> Thomas Haller  thomas%20haller%20%3cthal...@redhat.com%3e>>, 
> modemmanager-devel@lists.freedesktop.org <
> modemmanager-devel@lists.freedesktop.org %22modemmanager-de...@lists.freedesktop.org
> %22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Wed, 11 Sep 2019 11:38:16 +0200
> 
> 
> Hey!
> 
> 
> On Wed, Sep 11, 2019 at 11:22 AM Focke Christian
> 
> <
> 
> <mailto:christian.fo...@mail.fernfh.ac.at>
> 
> christian.fo...@mail.fernfh.ac.at
> 
> > wrote:
> 
> Yes I know, but with NM-GNOME and nmcli it doesn't work at all;
> that's where I started from.
> 
> 
> Actually it was you who instructed me to use mmcli to analyse the
> issue on MM side.
> 
> 
> 
> Oh, ok, sorry for the confusion then :)
> 
> 
> The MM analysis is done already, e.g. we can see how the whole
> 
> connection sequence works ok with mmcli --simple-connect. Now, the
> 
> missing part is the integration with NM. That is why Lubomir
> requested
> 
> for *NetworkManager* logs while reproducing the issue. Could you
> 
> follow his steps to get the logs and try to repro the problem using
> 
> nmcli?
> 

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Aleksander Morgado 
Hey!

On Wed, Sep 11, 2019 at 11:22 AM Focke Christian
 wrote:
>
> Yes I know, but with NM-GNOME and nmcli it doesn't work at all; that's where 
> I started from.
>
> Actually it was you who instructed me to use mmcli to analyse the issue on MM 
> side.
>

Oh, ok, sorry for the confusion then :)

The MM analysis is done already, e.g. we can see how the whole
connection sequence works ok with mmcli --simple-connect. Now, the
missing part is the integration with NM. That is why Lubomir requested
for *NetworkManager* logs while reproducing the issue. Could you
follow his steps to get the logs and try to repro the problem using
nmcli?

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Focke Christian 
Yes I know, but with NM-GNOME and nmcli it doesn't work at all; that's where I 
started from.

Actually it was you who instructed me to use mmcli to analyse the issue on MM 
side.

Kind regards, Christian

-Original Message-
From: Aleksander Morgado 
mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
To: Focke Christian 
mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
Cc: Lubomir Rintel 
mailto:lubomir%20rintel%20%3clkund...@v3.sk%3e>>, Dan Williams 
mailto:dan%20williams%20%3cd...@redhat.com%3e>>, Thomas Haller 
mailto:thomas%20haller%20%3cthal...@redhat.com%3e>>, 
modemmanager-devel@lists.freedesktop.org 
mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 11 Sep 2019 09:19:02 +0200


Hey!


thanks; the modem is plugged to the mainboard, so no simple plugging-in; 
instead, I did this


$ mmcli -m 0 --simple-connect="apn=a1.net,

<mailto:user=p...@a1plus.at>

user=p...@a1plus.at

,password=ppp"

$ # sleep some time

$ mmcli -m 0 --simple-disconnect



You should not use mmcli for anything, maybe that's the problem? If

you manually run mmcli like you did above, no other application is

going to setup the wwan network interface for you, that is totally

expected.


If you want to use NetworkManager (so that it's NM the one setting up

the network interface), you should create some WWAN modem settings for

NetworkManager (e.g. using System Settings in GNOME, or whatever other

desktop you use). Once the settings have been set up, you should be

able to connect/disconnect the modem using nmcli (not mmcli) and/or

using your desktop network settings control.

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Aleksander Morgado 
Hey!

> thanks; the modem is plugged to the mainboard, so no simple plugging-in; 
> instead, I did this
>
> $ mmcli -m 0 --simple-connect="apn=a1.net,user=p...@a1plus.at,password=ppp"
> $ # sleep some time
> $ mmcli -m 0 --simple-disconnect
>

You should not use mmcli for anything, maybe that's the problem? If
you manually run mmcli like you did above, no other application is
going to setup the wwan network interface for you, that is totally
expected.

If you want to use NetworkManager (so that it's NM the one setting up
the network interface), you should create some WWAN modem settings for
NetworkManager (e.g. using System Settings in GNOME, or whatever other
desktop you use). Once the settings have been set up, you should be
able to connect/disconnect the modem using nmcli (not mmcli) and/or
using your desktop network settings control.

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-11 Thread Focke Christian 
Hi,

thanks; the modem is plugged to the mainboard, so no simple plugging-in; 
instead, I did this

$ mmcli -m 0 
--simple-connect="apn=a1.net,user=p...@a1plus.at<mailto:user=p...@a1plus.at>,password=ppp"
$ # sleep some time
$ mmcli -m 0 --simple-disconnect

Enclosed the log.

Kind regards, Christian

-Original Message-
From: Lubomir Rintel 
mailto:lubomir%20rintel%20%3clkund...@v3.sk%3e>>
To: Focke Christian 
mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>,
 Dan Williams mailto:dan%20williams%20%3cd...@redhat.com%3e>>, 
Thomas Haller 
mailto:thomas%20haller%20%3cthal...@redhat.com%3e>>
Cc: Aleksander Morgado 
mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>,
 modemmanager-devel@lists.freedesktop.org 
mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Tue, 10 Sep 2019 14:24:31 +0200


Hi Christian,


I'm wondering if you could share the full logs? One way to grab them

would be as follows:


1.) Bump the NetworkManager log level:

# nmcli g logging level trace


2.) Start capturing the log:

# journalctl -fl |tee modem-log.txt


3.) Plug in the modem


4.) ^C, and possibly redact personal stuff from modem-log.txt

(there shouldn't be any passwords and such, but it doesn't hurt

to check twice).


Thanks

Lubo


On Tue, 2019-09-10 at 01:57 +, Focke Christian wrote:

Hi all,


below some output of mmcli and nmcli -- any idea?


Thanks, Christian



cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ mmcli -m 0


  


  General  |dbus path: /org/freedesktop/ModemManager1/Modem/0


   |device id: f83e2ed1319664354cbd7a91c6449ac197543fc2


  


  Hardware | manufacturer: HP


   |model: HP lt4132 LTE/HSPA+ 4G Module


   | revision: 11.617.09.00.11


   | h/w revision: ML1ME906SM


   |supported: gsm-umts, lte


   |  current: gsm-umts, lte


   | equipment id: 356581079177605


  


  System   |   device: /sys/devices/pci:00/:00:14.0/usb1/1-3


   |  drivers: option1, cdc_mbim


   |   plugin: Generic


   | primary port: cdc-wdm2


   |ports: ttyUSB0 (at), cdc-wdm2 (mbim), wwp0s20f0u3c3 
(net)


  


  Status   |   unlock retries: unknown (3)


   |state: connected


   |  power state: on


   |  access tech: lte


   |   signal quality: 74% (cached)


  


  Modes|supported: allowed: 2g, 3g, 4g; preferred: none


   |  current: allowed: 2g, 3g, 4g; preferred: none


  


  IP   |supported: ipv4, ipv6, ipv4v6


  


  3GPP | imei: 356581079177605


   |  operator id: 23201


   |operator name: A1


   | registration: home


  


  3GPP EPS | ue mode of operation: csps-2


  


  SIM  |dbus path: /org/freedesktop/ModemManager1/SIM/0


  


  Bearer   |dbus path: /org/freedesktop/ModemManager1/Bearer/0


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ mmcli -i 0


  ---


  General| dbus path: /org/freedesktop/ModemManager1/SIM/0


  ---


  Properties |  imsi: 232011530244334


 | iccid: 8943015618072727998


 |   operator id: 23201


 | operator name: A1


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ mmcli -b 0


  


  General|  dbus path: /org/freedesktop/ModemManager1/Bearer/0


 |   type: default


  


  Status |  connected: yes


 |  suspended: no


 |  interface: wwp0s20f0u3c3


 | ip timeout: 20


  


  Properties |apn: a1.net


 |roaming: allowed


 |   user:

<mailto:p...@a1plus.at>

p...@a1plus.at

mailto:p...@a1plus.at>

p...@a1plus.at

>


 |   password: ppp


  


  IPv4 configuration | method: static


 |address: 10.57.216.221

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-10 Thread Lubomir Rintel 
TION
> 
> wlp108s0 wifi  connectedUPC1069871
> 
> enx0050b6983a69  ethernet  unavailable  --
> 
> cdc-wdm2 gsm   unavailable  --
> 
> lo   loopback  unmanaged--
> 
> cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ nmcli 
> connection
> 
> NAME   UUID  TYPE 
>   DEVICE
> 
> UPC1069871 7e5f24ae-f378-4f77-82c6-e8e23d1fc618  wifi 
>   wlp108s0
> 
> A1 Breitband   1f1571a4-bbc7-4a91-90be-a3c9c4dfd25d  gsm  
>   --
> 
> [...]  [...] wifi 
>   --
> 
> Wired connection 1 721fa8df-e383-3cd9-8d83-5a74660ea0de  ethernet 
>   --
> 
> cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$
> 
> -----Original Message-
> From: Aleksander Morgado 
> mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
> To: Focke Christian 
> mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
> Cc: modemmanager-devel@lists.freedesktop.org 
> mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>,
>  Dan Williams 
> mailto:dan%20williams%20%3cd...@redhat.com%3e>>, Lubomir 
> Rintel mailto:lubomir%20rintel%20%3clkund...@v3.sk%3e>>, 
> Thomas Haller 
> mailto:thomas%20haller%20%3cthal...@redhat.com%3e>>
> Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
> Date: Mon, 2 Sep 2019 09:20:50 +0200
> 
> 
> cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip addr
> 
> 
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
> default qlen 1000
> 
> 
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 
> 
> inet 127.0.0.1/8 scope host lo
> 
> 
>valid_lft forever preferred_lft forever
> 
> 
> inet6 ::1/128 scope host
> 
> 
>valid_lft forever preferred_lft forever
> 
> 
> 2: wwp0s20f0u3c3:  mtu 1500 qdisc noop state DOWN 
> group default qlen 1000
> 
> 
> link/ether c6:4e:86:9d:4e:44 brd ff:ff:ff:ff:ff:ff
> 
> 
> 3: enx0050b6983a69:  mtu 1500 qdisc 
> pfifo_fast state DOWN group default qlen 1000
> 
> 
> link/ether 00:50:b6:98:3a:69 brd ff:ff:ff:ff:ff:ff
> 
> 
> 4: wlp108s0:  mtu 1500 qdisc mq state UP 
> group default qlen 1000
> 
> 
> link/ether 20:16:b9:f2:53:c3 brd ff:ff:ff:ff:ff:ff
> 
> 
> inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute 
> wlp108s0
> 
> 
>valid_lft 86280sec preferred_lft 86280sec
> 
> 
> inet6 2a02:8388:180a:f580:603a:d001:36d8:f92b/64 scope global dynamic 
> noprefixroute
> 
> 
>valid_lft 1075621sec preferred_lft 604797sec
> 
> 
> inet6 fe80::cd4a:9a4:1160:450e/64 scope link noprefixroute
> 
> 
>valid_lft forever preferred_lft forever
> 
> 
> cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip route
> 
> 
> default via 192.168.0.1 dev wlp108s0 proto dhcp metric 600
> 
> 
> 169.254.0.0/16 dev wlp108s0 scope link metric 1000
> 
> 
> 192.168.0.0/24 dev wlp108s0 proto kernel scope link src 192.168.0.31 metric 
> 600
> 
> 
> cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$
> 
> 
> ... no IP address, no route; maybe I should take this issue with the 
> NetworkManager people?
> 
> 
> 
> Thomas, Lubomir, Dan, any idea of what could be happening here?
> 
> 
> MM connection attempt using MBIM goes well, MM reports IP settings to use, NM 
> reports the device is connected, but the network interface isn't being 
> configured properly. Is there any known issue with this logic in 1.14.6?
> 
> 

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-10 Thread Focke Christian 
20%3clkund...@v3.sk%3e>>, Thomas Haller 
mailto:thomas%20haller%20%3cthal...@redhat.com%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Mon, 2 Sep 2019 09:20:50 +0200


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip addr


1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000


link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00


inet 127.0.0.1/8 scope host lo


   valid_lft forever preferred_lft forever


inet6 ::1/128 scope host


   valid_lft forever preferred_lft forever


2: wwp0s20f0u3c3:  mtu 1500 qdisc noop state DOWN 
group default qlen 1000


link/ether c6:4e:86:9d:4e:44 brd ff:ff:ff:ff:ff:ff


3: enx0050b6983a69:  mtu 1500 qdisc 
pfifo_fast state DOWN group default qlen 1000


link/ether 00:50:b6:98:3a:69 brd ff:ff:ff:ff:ff:ff


4: wlp108s0:  mtu 1500 qdisc mq state UP group 
default qlen 1000


link/ether 20:16:b9:f2:53:c3 brd ff:ff:ff:ff:ff:ff


inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute 
wlp108s0


   valid_lft 86280sec preferred_lft 86280sec


inet6 2a02:8388:180a:f580:603a:d001:36d8:f92b/64 scope global dynamic 
noprefixroute


   valid_lft 1075621sec preferred_lft 604797sec


inet6 fe80::cd4a:9a4:1160:450e/64 scope link noprefixroute


   valid_lft forever preferred_lft forever


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip route


default via 192.168.0.1 dev wlp108s0 proto dhcp metric 600


169.254.0.0/16 dev wlp108s0 scope link metric 1000


192.168.0.0/24 dev wlp108s0 proto kernel scope link src 192.168.0.31 metric 600


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$


... no IP address, no route; maybe I should take this issue with the 
NetworkManager people?



Thomas, Lubomir, Dan, any idea of what could be happening here?


MM connection attempt using MBIM goes well, MM reports IP settings to use, NM 
reports the device is connected, but the network interface isn't being 
configured properly. Is there any known issue with this logic in 1.14.6?


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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-02 Thread Focke Christian 
Hi Aleksander,


cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip addr

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host

   valid_lft forever preferred_lft forever

2: wwp0s20f0u3c3:  mtu 1500 qdisc noop state DOWN 
group default qlen 1000

link/ether c6:4e:86:9d:4e:44 brd ff:ff:ff:ff:ff:ff

3: enx0050b6983a69:  mtu 1500 qdisc 
pfifo_fast state DOWN group default qlen 1000

link/ether 00:50:b6:98:3a:69 brd ff:ff:ff:ff:ff:ff

4: wlp108s0:  mtu 1500 qdisc mq state UP group 
default qlen 1000

link/ether 20:16:b9:f2:53:c3 brd ff:ff:ff:ff:ff:ff

inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute 
wlp108s0

   valid_lft 86280sec preferred_lft 86280sec

inet6 2a02:8388:180a:f580:603a:d001:36d8:f92b/64 scope global dynamic 
noprefixroute

   valid_lft 1075621sec preferred_lft 604797sec

inet6 fe80::cd4a:9a4:1160:450e/64 scope link noprefixroute

   valid_lft forever preferred_lft forever

cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ ip route

default via 192.168.0.1 dev wlp108s0 proto dhcp metric 600

169.254.0.0/16 dev wlp108s0 scope link metric 1000

192.168.0.0/24 dev wlp108s0 proto kernel scope link src 192.168.0.31 metric 600

cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$

... no IP address, no route; maybe I should take this issue with the 
NetworkManager people?

Kind regards, Christian

-Original Message-
From: Aleksander Morgado 
mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
To: Focke Christian 
mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
Cc: modemmanager-devel@lists.freedesktop.org 
mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 28 Aug 2019 17:53:44 +0200


Hey,


We may need NetworkManager logs to see why that connection attempt


wasn't completed correctly in the NM side.



Attached


NetworkManager_2019-08-28_15-24-08.log -- debug log



That's weird, because NM does say it's connected:


Aug 28 15:08:51 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997731.8179] modem["cdc-wdm2"]: modem state changed, 'disabled'

--> 'enabling' (reason: user-requested)

Aug 28 15:08:51 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997731.8179] modem["cdc-wdm2"]: modem state changed, 'disabled'

--> 'enabling' (reason: user-requested)

Aug 28 15:09:04 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997744.6462] modem["cdc-wdm2"]: modem state changed, 'enabling'

--> 'enabled' (reason: user-requested)

Aug 28 15:09:04 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997744.6462] modem["cdc-wdm2"]: modem state changed, 'enabling'

--> 'enabled' (reason: user-requested)

Aug 28 15:09:05 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997745.0301] modem["cdc-wdm2"]: modem state changed, 'enabled'

--> 'registered' (reason: unknown)

Aug 28 15:09:05 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997745.0301] modem["cdc-wdm2"]: modem state changed, 'enabled'

--> 'registered' (reason: unknown)

Aug 28 15:09:30 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997770.3645] modem["cdc-wdm2"]: modem state changed, 'registered'

--> 'connecting' (reason: user-requested)

Aug 28 15:09:30 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997770.3645] modem["cdc-wdm2"]: modem state changed, 'registered'

--> 'connecting' (reason: user-requested)

Aug 28 15:09:31 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997771.1699] modem["cdc-wdm2"]: modem state changed, 'connecting'

--> 'connected' (reason: user-requested)

Aug 28 15:09:31 hp-eb-x360-1030-g3 NetworkManager[748]: 

[1566997771.1699] modem["cdc-wdm2"]: modem state changed, 'connecting'

--> 'connected' (reason: user-requested)


After the connection attempt, is the WWAN network interface configured

with an IP address (run "ip addr")? Is there a default route through

the WWAN interface (run "ip route")?

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-09-02 Thread Aleksander Morgado 

> cfocke@hp-eb-x360-1030-g3:~$ ip addr
> 
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
> default qlen 1000
> 
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 
> inet 127.0.0.1/8 scope host lo
> 
>valid_lft forever preferred_lft forever
> 
> inet6 ::1/128 scope host
> 
>valid_lft forever preferred_lft forever
> 
> 2: wwp0s20f0u3c3:  mtu 1500 qdisc noop state DOWN 
> group default qlen 1000
> 
> link/ether c6:4e:86:9d:4e:44 brd ff:ff:ff:ff:ff:ff
> 
> 3: enx0050b6983a69:  mtu 1500 qdisc 
> pfifo_fast state DOWN group default qlen 1000
> 
> link/ether 00:50:b6:98:3a:69 brd ff:ff:ff:ff:ff:ff
> 
> 4: wlp108s0:  mtu 1500 qdisc mq state UP 
> group default qlen 1000
> 
> link/ether 20:16:b9:f2:53:c3 brd ff:ff:ff:ff:ff:ff
> 
> inet 192.168.0.31/24 brd 192.168.0.255 scope global dynamic noprefixroute 
> wlp108s0
> 
>valid_lft 86280sec preferred_lft 86280sec
> 
> inet6 2a02:8388:180a:f580:603a:d001:36d8:f92b/64 scope global dynamic 
> noprefixroute
> 
>valid_lft 1075621sec preferred_lft 604797sec
> 
> inet6 fe80::cd4a:9a4:1160:450e/64 scope link noprefixroute
> 
>valid_lft forever preferred_lft forever
> 
> cfocke@hp-eb-x360-1030-g3:~$ ip route
> 
> default via 192.168.0.1 dev wlp108s0 proto dhcp metric 600
> 
> 169.254.0.0/16 dev wlp108s0 scope link metric 1000
> 
> 192.168.0.0/24 dev wlp108s0 proto kernel scope link src 192.168.0.31 metric 
> 600
> 
> cfocke@hp-eb-x360-1030-g3:~$
> 
> ... no IP address, no route; maybe I should take this issue with the 
> NetworkManager people?
> 

Thomas, Lubomir, Dan, any idea of what could be happening here?

MM connection attempt using MBIM goes well, MM reports IP settings to use, NM 
reports the device is connected, but the network interface isn't being 
configured properly. Is there any known issue with this logic in 1.14.6?


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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-08-28 Thread Aleksander Morgado 
Hey,

> We may need NetworkManager logs to see why that connection attempt
>
> wasn't completed correctly in the NM side.
>
>
> Attached
>
> NetworkManager_2019-08-28_15-24-08.log -- debug log
>

That's weird, because NM does say it's connected:

Aug 28 15:08:51 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997731.8179] modem["cdc-wdm2"]: modem state changed, 'disabled'
--> 'enabling' (reason: user-requested)
Aug 28 15:08:51 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997731.8179] modem["cdc-wdm2"]: modem state changed, 'disabled'
--> 'enabling' (reason: user-requested)
Aug 28 15:09:04 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997744.6462] modem["cdc-wdm2"]: modem state changed, 'enabling'
--> 'enabled' (reason: user-requested)
Aug 28 15:09:04 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997744.6462] modem["cdc-wdm2"]: modem state changed, 'enabling'
--> 'enabled' (reason: user-requested)
Aug 28 15:09:05 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997745.0301] modem["cdc-wdm2"]: modem state changed, 'enabled'
--> 'registered' (reason: unknown)
Aug 28 15:09:05 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997745.0301] modem["cdc-wdm2"]: modem state changed, 'enabled'
--> 'registered' (reason: unknown)
Aug 28 15:09:30 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997770.3645] modem["cdc-wdm2"]: modem state changed, 'registered'
--> 'connecting' (reason: user-requested)
Aug 28 15:09:30 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997770.3645] modem["cdc-wdm2"]: modem state changed, 'registered'
--> 'connecting' (reason: user-requested)
Aug 28 15:09:31 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997771.1699] modem["cdc-wdm2"]: modem state changed, 'connecting'
--> 'connected' (reason: user-requested)
Aug 28 15:09:31 hp-eb-x360-1030-g3 NetworkManager[748]: 
[1566997771.1699] modem["cdc-wdm2"]: modem state changed, 'connecting'
--> 'connected' (reason: user-requested)

After the connection attempt, is the WWAN network interface configured
with an IP address (run "ip addr")? Is there a default route through
the WWAN interface (run "ip route")?

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

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-08-28 Thread Focke Christian 
Hi,

Thanks for picking this up.


We may need NetworkManager logs to see why that connection attempt

wasn't completed correctly in the NM side.

Attached

  *   NetworkManager_2019-08-28_15-24-08.log -- debug log

(same sequence of commands as in ModemManager_2019-08-27_00-43-36.odt)


Also, what exact NM version are you using?

cfocke@hp-eb-x360-1030-g3<mailto:cfocke@hp-eb-x360-1030-g3>:~$ 
/usr/sbin/NetworkManager --version
1.14.6

Thanks, Christian

-Original Message-
From: Aleksander Morgado 
mailto:aleksander%20morgado%20%3caleksan...@aleksander.es%3e>>
To: Focke Christian 
mailto:focke%20christian%20%3cchristian.fo...@mail.fernfh.ac.at%3e>>
Cc: modemmanager-devel@lists.freedesktop.org 
mailto:%22modemmanager-de...@lists.freedesktop.org%22%20%3cmodemmanager-de...@lists.freedesktop.org%3e>>
Subject: Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10
Date: Wed, 28 Aug 2019 13:14:36 +0200


Hey,



Since migrating from Debian 9 to Debian 10, my hp-lt4132 is 'unavailable' in 
NetworkManager.


Attached


ModemManager_2019-08-27_00-43-36.odt -- commands used to enable modem and 
connect to bearer

ModemManager_2019-08-27_00-39-18.log -- debug log



Thanks, Christian



The log shows how the modem gets successfully connected:

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337603] IPv4 configuration available: 'address, gateway,

dns, mtu'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337637]   IP addresses (1)

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337682] IP [0]: '100.103.53.15/27'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337720]   Gateway: '100.103.53.1'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337745]   DNS addresses (2)

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337811] DNS [0]: '194.48.128.199'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337862] DNS [1]: '194.48.139.254'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337891]   MTU: '1500'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.337914] IPv6 configuration available: 'none'

Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 

[1566858606.338080] (wwp0s20f0u3c3): port now connected


We may need NetworkManager logs to see why that connection attempt

wasn't completed correctly in the NM side.

Also, what exact NM version are you using?

Aug 28 15:06:20 hp-eb-x360-1030-g3 systemd[1]: Starting Network Manager...
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8267] NetworkManager (version 1.14.6) is starting... (for the first time)
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8268] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8267] NetworkManager (version 1.14.6) is starting... (for the first time)
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8268] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8277] wifi-nl80211: (wlp108s0): using nl80211 for WiFi device control
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8277] wifi-nl80211: (wlp108s0): using nl80211 for WiFi device control
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8321] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8321] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8328] manager[0x5603d4d3b020]: monitoring kernel firmware directory '/lib/firmware'.
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8328] monitoring ifupdown state file '/run/network/ifstate'.
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8328] manager[0x5603d4d3b020]: monitoring kernel firmware directory '/lib/firmware'.
Aug 28 15:06:20 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997580.8328] monitoring ifupdown state file '/run/network/ifstate'.
Aug 28 15:06:20 hp-eb-x360-1030-g3 systemd[1]: Started Network Manager.
Aug 28 15:06:21 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997581.0564] hostname: hostname: using hostnamed
Aug 28 15:06:21 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997581.0564] hostname: hostname changed from (none) to "hp-eb-x360-1030-g3"
Aug 28 15:06:21 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997581.0564] hostname: hostname: using hostnamed
Aug 28 15:06:21 hp-eb-x360-1030-g3 NetworkManager[748]:   [1566997581.0567] dns-mgr[0x5603d4d46900]: init: dns=default, rc-manager=resolvconf
Aug 28 15:06:21 hp-eb-x360-103

Re: hp-lt4132 'unavailable' in NetworkManager on Debian 10

2019-08-28 Thread Aleksander Morgado 
Hey,

>
> Since migrating from Debian 9 to Debian 10, my hp-lt4132 is 'unavailable' in 
> NetworkManager.
>
> Attached
>
> ModemManager_2019-08-27_00-43-36.odt -- commands used to enable modem and 
> connect to bearer
> ModemManager_2019-08-27_00-39-18.log -- debug log
>
>
> Thanks, Christian
>

The log shows how the modem gets successfully connected:
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337603] IPv4 configuration available: 'address, gateway,
dns, mtu'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337637]   IP addresses (1)
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337682] IP [0]: '100.103.53.15/27'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337720]   Gateway: '100.103.53.1'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337745]   DNS addresses (2)
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337811] DNS [0]: '194.48.128.199'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337862] DNS [1]: '194.48.139.254'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337891]   MTU: '1500'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.337914] IPv6 configuration available: 'none'
Aug 27 00:30:06 hp-eb-x360-1030-g3 ModemManager[5204]: 
[1566858606.338080] (wwp0s20f0u3c3): port now connected

We may need NetworkManager logs to see why that connection attempt
wasn't completed correctly in the NM side.
Also, what exact NM version are you using?

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