<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>> Subject: Re: [OpenWrt-Devel] [PATCH 1/2] wwan: Add support for CDC (Huawei 'HiLink') Modems<br><div>> To: malaakso@elisanet.fi; openwrt-devel@lists.openwrt.org<br>> CC: blogic@openwrt.org<br>> From: br1@einfach.org<br>> Date: Tue, 23 Feb 2016 17:26:33 +0000<br>> <br>> On 02/23/2016 07:11 AM, Matti Laakso wrote:<br>> >> Huawei HiLink ("h" model names) modems just provide a CDC Ethernet<br>> >> interface<br>> >> where we have to run DHCP to get an IP address (usually in the<br>> >> 192.168.8.0<br>> >> range). While this may be bad design in general it's sometimes<br>> >> necessary to<br>> >> support these modems.<br>> >><br>> >> This adds autodetection and handling of these to wwan.<br>> >><br>> >> Tested with Huawei E3030h-1.<br>> > <br>> > Why do you need an extra protocol for these? They work just fine with<br>> > the regular DHCP protocol.<br>> <br>> Hi, sorry I saw this so late... (cc: please).<br>> <br>> The reason is that I want different types of Modems to work with the<br>> same interface configuration, using 'wwan'. E.g. it's configured like<br>> this (/etc/config/network):<br>> <br>> config interface 'umts'<br>> option proto wwan<br>> option apn internet.eplus.de<br>> option metric 4<br>> <br>> And it will work with PPP, QMI, MBIM, HiLink or whatever modem supported<br>> by "wwan" (which are hopefully more and more)... Doesn't that make<br>> sense? It would help the user who doesn't want to guess wether QMI works<br>> better than PPP for a specific modem and which serial port to use, etc...<br>> <br><br>That's a good goal, but I think it's confusing for the user when apn and pin options don't work with HiLink modems but do work with all other modems handled by wwan.<br><br>Matti<br><br><br></div> </div></body>
</html>