[review] dcbw/huawei-at-dhcp: use AT^DHCP response if available for NDISDUP-capable devices
dcbw at redhat.com
Wed Aug 19 13:52:11 PDT 2015
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.
That would be 10.76.162.187 (ip addr), 255.255.255.248 (netmask),
10.76.162.185 (gateway), 10.76.162.185 (gateway again), 10.74.210.210
(dns1), 10.74.210.211 (dns2).
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.
> /tmp/speedstickv.txt lines 1-41/42 99%
> My input was
> (the first ndisdup=1,1.. is not included here, but the LED switched to
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
More information about the ModemManager-devel