Hi Sami,
Having an E3276 would be nice for developing this further. I have already a
patch for comgt ready which allows it to be used with non-TTY device nodes
(i.e., /dev/cdc-wdmX), I just need to test it before sending. Then I could dig
further into netifd integration.
Matti___
Matti, would you like to have the Huawei e3276 for debugging this
after I get it back? Yours to keep if you want to :) Mine skills is
kinda not there with this, but need for working NCM is more than
needed for me :)
Sami Olmari
On Sat, Nov 15, 2014 at 6:31 AM, John Crispin wrote:
> no and i wil
Hi Jamie,
> On Thu, Oct 30, 2014 at 12:58:40PM +0200, Matti Laakso wrote:
> > Hi Sami,
> >
> > >Using John's version:
> > >
> > >config interface 'wan'
> > > option proto 'wwan'
> > > option apn 'opengate'
> > ># option device '/dev/cdc-wdm0' (with or without commenting this
Shouldn't there be declared "proto_config_add_string ifname" somewhere
at the /lib/netifd/proto/ncm.sh ? and use that as argument somewhere
in here:
echo "ncm[$$]" "Connected, starting DHCP"
proto_init_update "*" 1
proto_send_update "$interface"
And something similar for t
On Thu, Oct 30, 2014 at 12:58:40PM +0200, Matti Laakso wrote:
> Hi Sami,
>
> >Using John's version:
> >
> >config interface 'wan'
> > option proto 'wwan'
> > option apn 'opengate'
> ># option device '/dev/cdc-wdm0' (with or without commenting this)
> >
> >Does absolutely noth
okay:
config interface 'wan'
option ifname 'wwan0'
option proto 'ncm'
option apn 'opengate'
option device '/dev/cdc-wdm0'
Thu Oct 30 21:06:18 2014 daemon.notice netifd: wan (2446): comgt
21:06:18 -> -- Error Report --
Thu Oct 30 21:06:18 2014 daemon.notice netifd:
Hi Sami,
Using John's version:
config interface 'wan'
option proto 'wwan'
option apn 'opengate'
# option device '/dev/cdc-wdm0' (with or without commenting this)
Does absolutely nothing, nothing in logread...
However now when using
config interface 'wan'
opti
Using John's version:
config interface 'wan'
option proto 'wwan'
option apn 'opengate'
# option device '/dev/cdc-wdm0' (with or without commenting this)
Does absolutely nothing, nothing in logread...
However now when using
config interface 'wan'
option proto 'ncm'
*cough* fixed in r43071
On 26/10/2014 15:06, Matti Laakso wrote:
> Hi Sami,
>
>> Well this is what John told me:
>>
>> "try /dev/cdc-wdm0 as a device or simply do
>>
>> config interface
>> option proto wwan
>> option apn opengate
>>
>> the new wwan proto will automagically detect your needed prot
Hi Sami,
> Well this is what John told me:
>
> "try /dev/cdc-wdm0 as a device or simply do
>
> config interface
> option proto wwan
> option apn opengate
>
> the new wwan proto will automagically detect your needed prot and device"
>
>
> I had also tried this and variations, but same resuls:
>
> c
Sami Olmari writes:
> Well this is what John told me:
>
> "try /dev/cdc-wdm0 as a device or simply do
>
> config interface
> option proto wwan
> option apn opengate
>
> the new wwan proto will automagically detect your needed prot and device"
Ah, right. So I am only confusing things with my wil
Well this is what John told me:
"try /dev/cdc-wdm0 as a device or simply do
config interface
option proto wwan
option apn opengate
the new wwan proto will automagically detect your needed prot and device"
I had also tried this and variations, but same resuls:
config interface 'wan'
op
Sami Olmari writes:
> option proto 'wwan'
I don't know much about how this is supposed to work (don't have any
Huawei NCM modem), but I do see this in the patch posted earlier in this
thread:
> diff --git a/package/network/utils/comgt/files/3g.usb
> b/package/network/utils/comgt/files/
I wonder would this thread reach most of interested persons, not just
John whom I've talked with plenty :)
I have Huawei e3276, latest openwrt trunk, used kernel 3.14 (ar71xx
target), I have chosen proper drivers and comgt-ncm etc, but for any
reason when wan is set to assumedly proper settings, l
John Crispin writes:
> i am currently using a vodafone k5105 which is a huawei rebrand. at
> 150 euro its very expensive. any other good ones ?
I find it impossible to recommend any specific modems because important
firmware features like MBIM depend on both operator branding and
geographical ta
On 09/10/2014 14:58, Bjørn Mork wrote:
> John Crispin writes:
>
>> ok, i am currently bumping some targets to v3.17. lets assume it
>> is broken for < 3.16 and hope 3.17 works.
>>
>> NCM seems to be broken by design and only a container as each
>> dongle apparently uses its own AT magic. at le
On 09/10/2014 15:35, Conor O'Gorman wrote:
> On 09/10/14 13:25, John Crispin wrote:
>>
>> personally i have been using mbim since i wrote umbim and it
>> just works :)
>>
>
> Ah, nice. I have some similar code, but in lua, from the json
> files. It's only a management protocol.
>
> Note that
"Conor O'Gorman" writes:
> On 09/10/14 13:25, John Crispin wrote:
>>
>> personally i have been using mbim since i wrote umbim and it just works :)
>>
>
> Ah, nice. I have some similar code, but in lua, from the json
> files. It's only a management protocol.
>
> Note that MBIM uses the NCM code for
On 09/10/14 13:25, John Crispin wrote:
personally i have been using mbim since i wrote umbim and it just works :)
Ah, nice. I have some similar code, but in lua, from the json files.
It's only a management protocol.
Note that MBIM uses the NCM code for the bulk packet data, so it's
packet
John Crispin writes:
> ok, i am currently bumping some targets to v3.17. lets assume it is
> broken for < 3.16 and hope 3.17 works.
>
> NCM seems to be broken by design and only a container as each dongle
> apparently uses its own AT magic. at least between Motorola, Sony and
> Huawei they are to
On 09/10/2014 14:14, Bjørn Mork wrote:
> "Conor O'Gorman" writes:
>> On 08/10/14 11:00, John Crispin wrote:
>>> the e3267 that sami sent me works with this proto, but i am
>>> failing to get a DHCP addr. could someone with a ncm dongle
>>> please try this patch on top of latest trunk please and
"Conor O'Gorman" writes:
> On 08/10/14 11:00, John Crispin wrote:
>> the e3267 that sami sent me works with this proto, but i am failing to
>> get a DHCP addr. could someone with a ncm dongle please try this patch
>> on top of latest trunk please and tell me if they are getting a dhcp addr ?
>
> I
On 08/10/14 17:42, John Crispin wrote:
On 08/10/2014 17:27, Conor O'Gorman wrote:
On 08/10/14 11:00, John Crispin wrote:
the e3267 that sami sent me works with this proto, but i am
failing to get a DHCP addr. could someone with a ncm dongle
please try this patch on top of latest trunk please
hi conor
On 08/10/2014 17:27, Conor O'Gorman wrote:
>
>
> On 08/10/14 11:00, John Crispin wrote:
>> the e3267 that sami sent me works with this proto, but i am
>> failing to get a DHCP addr. could someone with a ncm dongle
>> please try this patch on top of latest trunk please and tell me
>> if
On 08/10/14 11:00, John Crispin wrote:
the e3267 that sami sent me works with this proto, but i am failing to
get a DHCP addr. could someone with a ncm dongle please try this patch
on top of latest trunk please and tell me if they are getting a dhcp addr ?
I had a similar problem with a Huawe
the e3267 that sami sent me works with this proto, but i am failing to
get a DHCP addr. could someone with a ncm dongle please try this patch
on top of latest trunk please and tell me if they are getting a dhcp addr ?
On 08/10/2014 05:17, John Crispin wrote:
> From: Matti Laakso
>
> Signed-off-b
From: Matti Laakso
Signed-off-by: Matti Laakso
---
package/network/utils/comgt/Makefile | 15 ++
package/network/utils/comgt/files/3g.usb |2 +-
package/network/utils/comgt/files/ncm.json| 49 +++
package/network/utils/comgt/files/ncm.sh | 156
27 matches
Mail list logo
