E1750 Reloaded - QMI - STATIC - DHCP - IPv4

Dan Williams dcbw at redhat.com
Mon Aug 18 07:54:57 PDT 2014


On Mon, 2014-08-18 at 11:42 +0200, poma wrote:
> On 17.08.2014 12:37, Aleksander Morgado wrote:
> > On Sat, Aug 16, 2014 at 7:37 AM, poma <pomidorabelisima at gmail.com> wrote:
> >> On 15.08.2014 22:53, Dan Williams wrote:
> >>> On Fri, 2014-08-15 at 08:24 +0200, poma wrote:
> >>>> On 14.08.2014 18:22, Dan Williams wrote:
> >>>>> On Thu, 2014-08-14 at 14:39 +0200, poma wrote:
> >>>>>> On 13.08.2014 20:21, Aleksander Morgado wrote:
> >>>>>>> On Wed, Aug 13, 2014 at 8:41 AM, poma <pomidorabelisima at gmail.com> wrote:
> >>>>>>>>> Yes... :) As I said, if this issue is something that will happen to
> >>>>>>>>> all Huawei QMI devices, we should just reflect that in the code,
> >>>>>>>>> instead of trying something and falling back to some other method if
> >>>>>>>>> it fails.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> If you have a preliminary patch don't hesitate to send it for testing purposes. ;)
> >>>>>>>
> >>>>>>>
> >>>>>>> Can you try the branch "aleksander/huawei-qmi-always-dhcp" in the
> >>>>>>> upstream MM git repo?
> >>>>>>> http://cgit.freedesktop.org/ModemManager/ModemManager/log/?h=aleksander/huawei-qmi-always-dhcp
> >>>>>>>
> >>>>>>
> >>>>>> Yea, it works! :)
> >>>>>> http://goo.gl/GQwZzX
> >>>>>
> >>>>> I tested today with my E397 and E392 and an Olivetti 200 (not Huawei).
> >>>>> All three had no problem with static configuration and that
> >>>>> configuration looked similar to poma's results.  However, that doesn't
> >>>>> static works everywhere, and there are other reports of static not
> >>>>> working with Sierra Qualcomm-based 73xx devices too.
> >>>>>
> >>>>> I have just ordered an E1750C but I'm not sure when that'll get here.
> >>>>>
> >>>>> Dan
> >>>>>
> >>>>
> >>>> And how about to be more plastic reggae fantastic regarding to MMBearerIpMethod,
> >>>> e.g.
> >>>> /etc/udev/rules.d/70-persistent-mmbeareripmethod-static.rules
> >>>> ATTRS{idVendor}=="<VID>", ATTRS{idProduct}=="<PID>", ENV{MM_BEARER_QMI_FORCE_DHCP}="0"
> >>>> so if necessary, it can be switched to STATIC.
> >>>
> >>> The problem here is that Huawei, ZTE, Sierra, and other vendors use the
> >>> same VID/PID for wildly different devices and firmware versions.  So you
> >>> simply cannot match on the VID/PID for firmware-specific behavior :(
> >>>
> >>> Dan
> >>>
> >>
> >> OK man, will an aleksander/huawei-qmi-always-dhcp branch be merged and when the MM 1.4 is scheduled for release?
> > 
> > No, won't merge that branch.... instead we'll default back to DHCP for
> > all, until we have a clearer picture. Will do that, plus a MM 1.4
> > release next week.
> > 
> 
> OK Ale, good luck with the future development.

Can you try the dcbw/qmi-always-dhcp branch and see if that also fixes
the problem?

Thanks!
Dan



More information about the ModemManager-devel mailing list