[review] dcbw/huawei-at-dhcp: use AT^DHCP response if available for NDISDUP-capable devices

Thomas Schäfer tschaefer at t-online.de
Thu Aug 20 04:49:37 PDT 2015

Am 19.08.2015 um 22:52 schrieb Dan Williams:
> On Wed, 2015-08-19 at 22:07 +0200, Thomas Schäfer wrote:
>> I am not sure if I understand your question.
>> The E3372s-153 (speedstick v) answers to at^dhcp?
>> But at the moment I don't understand the answer. My second problem is now,
>> that there is no interface, where I could use it.
> It gets exposed in the bearer properties for the bearer that gets
> created when you ask ModemManager to connect, the same way it does for
> HSO or Sierra modems that offer static IP config.  Unfortunately mmcli
> doesn't seem to have a way to print the bearer properties.

With (net) interface I mean, what I see with

ip link

>> ^DHCP:
>> BBA24C0A,F8FFFFFF,B9A24C0A,B9A24C0A,D2D24A0A,D3D24A0A,150000000,150000000
> That would be (ip addr), (netmask),
> (gateway), (gateway again),
> (dns1), (dns2).

The values seem to be correct.

> One thing you could do to test more: after doing the ^DHCP request, run
> actual DHCP on the net interface and see what numbers it comes up with.

I have no net interface anymore.

Maybe the kernel, usb-modeswitch or something else has changed since the 
first time I tested the stick.

The log in the last mail was created with minicom via /dev/ttyUSB0 and 
without modemmanager.


More information about the ModemManager-devel mailing list