AW: No dhcpoffer on HL Serie
Stefan Gruber
sgruber at dh-electronics.de
Thu Jan 18 11:01:30 UTC 2018
Thanks a lot Dan. It is working now but I am not able to use the --query-ip-configuration. I am working on Debian Jessie.
Latest version of libmbim on Jessie is 1.10 which NOT support --query-ip-configuration.
I use ModemManger und mmcli to extract the IP/DNS/GW. But I am not very satisfied with my solution.
I do not want to upgrade to Debian Stretch. Is there another possibility to extract the IP with mbimcli?
On Wed, 2018-01-17 at 13:39 +0000, Stefan Gruber wrote:
> Hi
> I am working with a HL Module from Sierra Wireless on an embedded
> Debian System (so not all modules are include). I can configure it on
> PPP and get access to the Internet.
> But I have problems with the MBIM Interface.
> I get a cdc-wdm0 device and try to get it up with mbim-network.
>
> mbim-network /dev/cdc-wdm0 start
> Loading profile...
> APN: internet.telekom
> Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-
> subscriber-ready-status --no-close'...
> [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state:
> 'initialized' Subscriber ID: 'somethin' SIM ICCID: 'alsosomethin'
> Ready info: 'unknown' Telephone numbers: (1) '+49??' [/dev/cdc-wdm0]
> Session not closed: TRID: '3'
> Saving state... (TRID: 3)
> Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-
> registration-state --no-open=3 --no-close'...
> [/dev/cdc-wdm0] Registration status: Network error: 'unknown'
> Register state: 'home' Register mode: 'automatic' Available data
> classes: 'gprs, edge' Current cellular class: 'gsm' Provider ID:
> '26201' Provider name: 'Telekom.de' Roaming text: 'unknown'
> Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0]
> Session not closed: TRID: '4'
> Saving state... (TRID: 4)
> Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-
> packet-service --no-open=4 --no-close'...
> Saving state... (TRID: 5)
> Starting network with 'mbimcli -d /dev/cdc-wdm0 --
> connect=internet.telekom --no-open=5 --no-close'...
> Network started successfully
>
> My /etc/mbim-network.conf:
>
> APN=internet.telekom
> APN_AUTH=PAP
>
>
> When I now want a IP I use dhclient
MBIM devices usually do not support DHCP as they are raw IP interfaces, not really ethernet. After running mbim-network and getting a successful connect response, you run:
. /tmp/mbim-network-state-cdc-wdm0
mbim-cli -d /dev/cdc-wdm0 --query-ip-configuration=${TRID}
and then parse and apply that configuration to the network interface, update DNS/resolv.conf, and update default route if required. mbim- network doesn't currently do this for you, because DNS and routing are system-wide properties that must be set in cooperation with other tools, and mbim-network is just a simple demo-type utility.
Dan
> dhclient -v wwan0
> Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014
> Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Listening on LPF/wwan0/16:f4:54:ec:7e:35
> Sending on LPF/wwan0/16:f4:54:ec:7e:35
> Sending on Socket/fallback
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 13
> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 13 No
> DHCPOFFERS received.
> No working leases in persistent database - sleeping.
>
> And I have no access to the internet...
>
>
> When I use ModemManager I get the same. Here are the Outputs:
>
> mmcli -m 0 -e
> successfully enabled the modem
> mmcli -m 0
>
> /org/freedesktop/ModemManager1/Modem/0 (device id
> '467fb43f937df307bb12c8a99bca3
> -------------------------
> Hardware | manufacturer: 'Generic'
> | model: 'MBIM [8087:0911]'
> | revision: 'M2M_7160_MBIM_CAT1_WW_01.1710.'
> | supported: 'gsm-umts, lte'
> | current: 'gsm-umts, lte'
> | equipment id: 'fgdsg34'
> -------------------------
> System | device: '/sys/devices/soc0/soc/2100000.aips-
> bus/2184000.usb
> | drivers: 'cdc_acm, cdc_mbim'
> | plugin: 'Generic'
> | primary port: 'cdc-wdm0'
> | ports: 'cdc-wdm0 (mbim), wwan0 (net), ttyACM0
> (at)'
> -------------------------
> Numbers | own : 'dsfg3'
> -------------------------
> Status | lock: 'none'
> | unlock retries: 'sim-pin2 (3)'
> | state: 'registered'
> | power state: 'on'
> | access tech: 'gprs, edge'
> | signal quality: '0' (cached)
> -------------------------
> Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
> | current: 'allowed: 2g, 3g, 4g; preferred: none'
> -------------------------
> Bands | supported: 'unknown'
> | current: 'unknown'
> -------------------------
> IP | supported: 'ipv4, ipv6, ipv4v6'
> -------------------------
> 3GPP | imei: 'fu6tr65'
> | enabled locks: 'sim, fixed-dialing'
> | operator id: '26201'
> | operator name: 'Telekom.de'
> | subscription: 'unknown'
> | registration: 'home'
> -------------------------
> SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
>
> -------------------------
> Bearers | paths: 'none'
>
> mmcli -m 0 --simple-connect="apn=internet.telekom"
> successfully connected the modem
>
> When I now run dhclient I get the same like above except with another
> MAC of wwan0
>
> Listening on LPF/wwan0/86:c9:99:98:f1:4f
> Sending on LPF/wwan0/86:c9:99:98:f1:4f
> Sending on Socket/fallback
>
>
> Should I configure the gateway + DNS of the wwan0 Interface manually?
> I can myself not explain what I am doing wrong.
> I read somewhere they use a 4G Dongle on a Raspberry and use
> usb_modeswitch to enter QMI mode...
> _______________________________________________
> libmbim-devel mailing list
> libmbim-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libmbim-devel
More information about the libmbim-devel
mailing list