Huawei ME906s-158 (a.k.a. HP lt4132) IPv6 support

[Sebastian Sjoholm]

My unit is actually LT4120, but the same udev sentences went well here as
well.

root at SBC01:~# mbimcli -p -d /dev/cdc-wdm0 --query-device-caps
[/dev/cdc-wdm0] Device capabilities retrieved:
     Device type: 'remote'
  Cellular class: 'gsm'
     Voice class: 'no-voice'
       Sim class: 'removable'
      Data class: 'gprs, edge, umts, hsdpa, hsupa, lte, custom'
        SMS caps: 'pdu-receive, pdu-send'
       Ctrl caps: 'reg-manual'
    Max sessions: '8'
Custom data class: 'HSPA+'
       Device ID: '358894061571414'
   Firmware info: 'T77W595.F0.0.0.5.2.GC.022'
   Hardware info: 'HP lt4120 Snapdragon X5 LTE'
root at SBC01:~#

root at SBC01:~# mbimcli -p -d /dev/cdc-wdm0 --query-device-services
[/dev/cdc-wdm0] Device services retrieved:
Max DSS sessions: '0'
       Services: (12)

         Service: 'basic-connect'
            UUID: [a289cc33-bcbb-8b4f-b6b0-133ec2aae6df]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: device-caps (1),
                  subscriber-ready-status (2),
                  radio-state (3),
                  pin (4),
                  pin-list (5),
                  home-provider (6),
                  preferred-providers (7),
                  visible-providers (8),
                  register-state (9),
                  packet-service (10),
                  signal-state (11),
                  connect (12),
                  provisioned-contexts (13),
                  ip-configuration (15),
                  device-services (16),
                  device-service-subscribe-list (19),
                  packet-statistics (20),
                  network-idle-hint (21),
                  emergency-mode (22),
                  ip-packet-filters (23)

         Service: 'sms'
            UUID: [533fbeeb-14fe-4467-9f90-33a223e56c3f]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: configuration (1),
                  read (2),
                  send (3),
                  delete (4),
                  message-store-status (5)

         Service: 'ussd'
            UUID: [e550a0c8-5e82-479e-82f7-10abf4c3351f]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: ussd (1)

         Service: 'phonebook'
            UUID: [4bf38476-1e6a-41db-b1d8-bed289c25bdb]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: configuration (1),
                  read (2),
                  delete (3),
                  write (4)

         Service: 'stk'
            UUID: [d8f20131-fcb5-4e17-8602-d6ed3816164c]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: pac (1),
                  terminal-response (2),
                  envelope (3)

         Service: 'auth'
            UUID: [1d2b5ff7-0aa1-48b2-aa52-50f15767174e]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: aka (1),
                  sim (3)

         Service: 'qmi'
            UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: msg (1)

         Service: 'ms-host-shutdown'
            UUID: [883b7c26-985f-43fa-9804-27d7fb80959c]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: notify (1)

         Service: 'unknown'
            UUID: [2d0c12c9-0e6a-495a-915c-8d174fe5d63c]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: 1, 2

         Service: 'ms-firmware-id'
            UUID: [e9f7dea2-feaf-4009-93ce-90a3694103b6]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: get (1)

         Service: 'unknown'
            UUID: [5967bdcc-7fd2-49a2-9f5c-b2e70e527db3]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: 1, 2, 3, 4, 9, 10

         Service: 'unknown'
            UUID: [6427015f-579d-48f5-8c54-f43ed1e76f83]:
     DSS payload: 0
Max DSS instances: 0
            CIDs: 1, 2, 3
root at SBC01:~#

-Sebastian

On Thu, Jul 6, 2017 at 10:55 AM, Bjørn Mork <bjorn at mork.no> wrote:

> Tore Anderson <tore at fud.no> writes:
>
> > After switching it to configuration #3 (MBIM) everything Just Worked
> > without any further tinkering. I see the blog post author went for
> > configuration #1 instead, and that looks more cumbersome pull off.
> > Maybe it has any distinct advantage over MBIM mode he needed, I don't
> > know.
>
> Having access to the full power of QMI is an advantage if you want to do
> "advanced" stuff like cell monitoring etc. But if you can run QMI over
> MBIM, and then there is absolutely no reason to use the more cumbersome
> configuration.  MBIM is also the safer choice based on what most users
> (Windows) will use.
>
> Do you see 'qmi' in the MBIM service list?:
>
> root at miraculix:/tmp# mbimcli -p -d /dev/cdc-wdm0 --query-device-services
> [/dev/cdc-wdm0] Device services retrieved:
> ..
>
>                           Service: 'qmi'
>                              UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
>                       DSS payload: 0
>                 Max DSS instances: 0
>                              CIDs: msg (1)
>
>
>
> Bjørn
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>



-- 
Sebastian Sjöholm

Simborgarvägen 116
SE-18439 Åkersberga
Sverige

Mobile : +46 76 335 0667
Email : sebastian.sjoholm at gmail.com
Skype : ssjoholm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20170706/73a7f7eb/attachment-0001.html>