Re: MC 7304 ipv4v6 - raw-ip in qmi/mm/nm

Bjørn Mork writes: > And DHCP support is even more complex. DHCP clients must know how to > handle (add/remove/parse) L2 headers. Or lack of headers in this case. > I don't know of any client supporting that at the moment. But it should > be easier than any other L2 interface

Re: MC 7304 ipv4v6 - raw-ip in qmi/mm/nm

Thomas Schäfer writes: > Am Freitag, 18. Dezember 2015, 21:51:42 schrieb Bjørn Mork: > >> Just FYI: I ended up with an automated random address, which will be >> stable for the lifetime of the interface. This has now been accepted >> into net-next, so SLAAC will be in

Re: MC 7304 ipv4v6 - raw-ip in qmi/mm/nm

Am Freitag, 18. Dezember 2015, 21:51:42 schrieb Bjørn Mork: > Just FYI: I ended up with an automated random address, which will be > stable for the lifetime of the interface. This has now been accepted > into net-next, so SLAAC will be in place along with the qmi raw-ip > support in v4.5. It is

Re: MC 7304 ipv4v6

Bjørn Mork writes: > Bjørn Mork writes: >> Reinhard Speyerer writes: >> >>> On Sat, Nov 28, 2015 at 10:58:17PM +0100, Thomas Schäfer wrote: [...] I would be very happy if somebody tells me the steps for testing with PDP- context

Re: MC 7304 ipv4v6 - now works in (my) test environment

Am Montag, 30. November 2015, 13:23:43 schrieb Bjørn Mork: > I guess it's too late now, but testing this with MM is actually much > easier. I was able to successfully change the mode after MM had opened > the device by using > > qmicli -p -d /dev/cdc-wdm1

Re: MC 7304 ipv4v6

Reinhard Speyerer writes: > On Mon, Nov 30, 2015 at 10:53:35AM +0100, Bjørn Mork wrote: > >> hmm, "fixing" this seems simple enough: Just add the necessary code to >> net/ipv6/addrconf.c for handling ARPHRD_NONE devices. But I have two >> questions: >> >> 1) will random

Re: MC 7304 ipv4v6

Bjørn Mork writes: > Reinhard Speyerer writes: > >> On Sat, Nov 28, 2015 at 10:58:17PM +0100, Thomas Schäfer wrote: >>> [...] >>> I would be very happy if somebody tells me the steps for testing with PDP- >>> context IPv4v6. >> >> Not sure whether this also applies

Re: MC 7304 ipv4v6

Bjørn Mork writes: > Probably. I don't know how to do that. Is there an IP family setting > for qmicli? Another alternative is modifying the 802.3 default in > ModemManager. That would be this part of src/mm-port-qmi.c: > >if (ctx->set_data_format) > flags |=

Re: MC 7304 ipv4v6

I would expect to get the Ipv6-information via qmicli and setting them manually (later via mm, nm), like now for ipv4.(without dhcp, without slaac) I want to know if rawip is better than 802.3 in respect to dualstack, where some of my devices fail. Thomas Am 29.11.2015 17:43 schrieb Reinhard

Re: MC 7304 ipv4v6

On Sat, Nov 28, 2015 at 10:58:17PM +0100, Thomas Schäfer wrote: > [...] > I would be very happy if somebody tells me the steps for testing with PDP- > context IPv4v6. Not sure whether this also applies to qmi-cli as I used a different QMI client (which leaves network interface initialization to

Re: MC 7304 ipv4v6

Reinhard Speyerer writes: > On Sat, Nov 28, 2015 at 10:58:17PM +0100, Thomas Schäfer wrote: >> [...] >> I would be very happy if somebody tells me the steps for testing with PDP- >> context IPv4v6. > > Not sure whether this also applies to qmi-cli as I used a different > QMI

Re: MC 7304 ipv4v6

Am 29.11.2015 um 12:53 schrieb Aleksander Morgado: > On Sun, Nov 29, 2015 at 11:59 AM, Thomas Schäfer > wrote: >> Am 29.11.2015 um 02:24 schrieb Aleksander Morgado: >>> On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer >>> wrote: It works

Re: MC 7304 ipv4v6

Am 29.11.2015 um 02:24 schrieb Aleksander Morgado: > On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer > wrote: >> It works (tested only IPv4, LTE) with the following devices: >> >> *Telekom Speedstick LTE alias Huawei E398 >> *Vodafone K 5005 alias Huawei E398 modified >>

Re: MC 7304 ipv4v6

On Sun, Nov 29, 2015 at 11:59 AM, Thomas Schäfer wrote: > Am 29.11.2015 um 02:24 schrieb Aleksander Morgado: >> On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer >> wrote: >>> It works (tested only IPv4, LTE) with the following devices: >>> >>>

Re: MC 7304 ipv4v6

On November 27, 2015 10:35:26 PM CET, "Thomas Schäfer" wrote: >Bjørn Mork writes: > >> >> Works for me(tm). Only tested on an E392 for now: >> >> >> nemi:/tmp# ifconfig wwan1 >> wwan1 Link encap:Ethernet HWaddr 92:b9:2a:c0:4f:96 >>

Re: MC 7304 ipv4v6

> I cheated and left out some details. Like assuming that the allocated wds > cid was 1. If your modem has made other allocations earlier, for example a > previous connection attempt, then this won't hold. And you get results like > yours. > > You could continue guessing until gou hit the

Re: MC 7304 ipv4v6

Ah, right. I was probably using qmi-proxy without thinking about it. Looks like you get a reply to your get-current-settings, but it is picked up by the client doing follow-network. Try using the -p option everywhere Bjørn On November 28, 2015 12:51:44 PM CET, "Thomas Schäfer"

Re: MC 7304 ipv4v6

Am Samstag, 28. November 2015, 13:03:44 schrieben Sie: > Ah, right. I was probably using qmi-proxy without thinking about it. Looks > like you get a reply to your get-current-settings, but it is picked up by > the client doing follow-network. > > Try using the -p option everywhere Yes,

Re: MC 7304 ipv4v6

On Tue, Nov 24, 2015 at 11:52 PM, Bjørn Mork wrote: > Bjørn Mork writes: >> Dan Williams writes: >>> On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: >>> >>> My vote would be sysfs, with values "raw-ip" or "802.3" that you can >>> read and

Re: MC 7304 ipv4v6

On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer wrote: > It works (tested only IPv4, LTE) with the following devices: > > *Telekom Speedstick LTE alias Huawei E398 > *Vodafone K 5005 alias Huawei E398 modified > *Telekom Speedstick II alias ONE TOUCH L100V LTE > *MC 7304 >

Re: MC 7304 ipv4v6

On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer wrote: > crtl+c for disconnecting has crashed qmicli with segfault. any chance you could get a quick backtrace? -- Aleksander https://aleksander.es ___ networkmanager-list

Re: MC 7304 ipv4v6

Bjørn Mork writes: > > Works for me(tm). Only tested on an E392 for now: > > > nemi:/tmp# ifconfig wwan1 > wwan1 Link encap:Ethernet HWaddr 92:b9:2a:c0:4f:96 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0

Re: MC 7304 ipv4v6

Hi, Kernel did compile with the patch. Also switching sys...raw_ip seems to work. > qmicli -d /dev/cdc-wdm1 --client-cid=1 --client-no-release-cid > --wds-get-current-settings but here I get a problem because of unknown option --wds-get-current-settings Which version of qmicli are you

Re: MC 7304 ipv4v6

Thomas Schäfer writes: > Hi, > > Kernel did compile with the patch. Also switching sys...raw_ip seems to work. > > > >> qmicli -d /dev/cdc-wdm1 --client-cid=1 --client-no-release-cid >> --wds-get-current-settings > > > but here I get a problem because of unknown option

Re: MC 7304 ipv4v6

On Wed, 2015-11-25 at 08:51 +0100, Bjørn Mork wrote: > Dan Williams writes: > > > Well, if we're going to add rawip support, why bother emulating a > > netdev at all? > > (assuming you mean etherdev - we'll need the netdev in any case :) > > Good question. Asked before, but I

Re: MC 7304 ipv4v6

Am 25.11.2015 um 11:12 schrieb Bjørn Mork: Bjørn Mork writes: But I believe I implemented it the last time this was discussed. I'll see if I can dig up the old code for a demo. Not going to rush this anyway. I'd like everyone to be happy with the result. And it's going to

Re: MC 7304 ipv4v6

Thomas Schäfer writes: > Am 25.11.2015 um 11:12 schrieb Bjørn Mork: >> Bjørn Mork writes: >> >>> But I believe I implemented it the last time this was discussed. I'll >>> see if I can dig up the old code for a demo. Not going to rush this >>> anyway. I'd

Re: MC 7304 ipv4v6

Dan Williams writes: > On Wed, 2015-11-25 at 08:51 +0100, Bjørn Mork wrote: > >> The only "real" objection I once had was that I don't think there are >> any DHCP clients on Linux that will work with such an interface. But >> that is a lousy excuse. Using DHCP here is another bad

Re: MC 7304 ipv4v6

Bjørn Mork writes: > But I believe I implemented it the last time this was discussed. I'll > see if I can dig up the old code for a demo. Not going to rush this > anyway. I'd like everyone to be happy with the result. And it's going > to be immutable once it's in. git is a

Re: MC 7304 ipv4v6

Dan Williams writes: > On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: > > My vote would be sysfs, with values "raw-ip" or "802.3" that you can > read and write to the file. At least then they are human-readable. > It's also easier to use from scripts than parsing ethtool

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 23:52 +0100, Bjørn Mork wrote: > Bjørn Mork writes: > > Dan Williams writes: > > > On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: > > > > > > My vote would be sysfs, with values "raw-ip" or "802.3" that you > > > can > > > read and

Re: MC 7304 ipv4v6

Bjørn Mork writes: > Dan Williams writes: >> On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: >> >> My vote would be sysfs, with values "raw-ip" or "802.3" that you can >> read and write to the file. At least then they are human-readable. >> It's also

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 20:55 +0100, Thomas Schäfer wrote: > Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > > On Mon, 23 Nov 2015 22:42:09 +0100 > > > > > > > Would you be more specific about the problems you have and attach > > more > > information? > > * What NM, MM versions do you

Re: MC 7304 ipv4v6

On Tue, 2015-11-24 at 22:51 +0100, Bjørn Mork wrote: > Reinhard Speyerer writes: > > > This looks rather similar to the "Dualstack errors with MC7354" > > problem > > described here > > https://forum.sierrawireless.com/viewtopic.php?f=117=8295 . > > > > Apparently the qmi_wwan

Re: MC 7304 ipv4v6

Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > On Mon, 23 Nov 2015 22:42:09 +0100 > > > Would you be more specific about the problems you have and attach more > information? > * What NM, MM versions do you use? mmcli 1.4.10 nmcli tool, version 1.0.6 > * NM, MM logs are attached.

Re: MC 7304 ipv4v6

Adding libqmi-devel... On Tue, 2015-11-24 at 21:40 +0100, Reinhard Speyerer wrote: > [ please keep me CCed, I am not subscribed to the mailing list ] > > On Tue, Nov 24, 2015 at 08:55:42PM +0100, Thomas Schäfer wrote: > > Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > > > On Mon, 23

Re: MC 7304 ipv4v6

[ please keep me CCed, I am not subscribed to the mailing list ] On Tue, Nov 24, 2015 at 08:55:42PM +0100, Thomas Schäfer wrote: > Am Dienstag, 24. November 2015, 16:06:22 schrieben Sie: > > On Mon, 23 Nov 2015 22:42:09 +0100 > > > > > > > Would you be more specific about the problems you have

Re: MC 7304 ipv4v6

Reinhard Speyerer writes: > This looks rather similar to the "Dualstack errors with MC7354" problem > described here https://forum.sierrawireless.com/viewtopic.php?f=117=8295 . > > Apparently the qmi_wwan patch contained in the thread was not submitted > as a Linux kernel patch

Re: MC 7304 ipv4v6

Dan Williams writes: > Well, if we're going to add rawip support, why bother emulating a > netdev at all? (assuming you mean etherdev - we'll need the netdev in any case :) Good question. Asked before, but I have fewer and fewer arguments. I know Marcel H has wanted a raw

Re: MC 7304 ipv4v6

On Mon, 23 Nov 2015 22:42:09 +0100 Thomas Schäfer wrote: > Hi, > > There is a device stranded in front of my computer: MC7304. > It works basically under linux. But I have a problem. The dualstack > mode of the provided by Deutsche Telekom makes problems. Addresses > are

Re: MC 7304 ipv4v6

> Is there something special because of the two interfaces? (wwan0, wwan1, > cdc...0, cdc...1) The only different thing in the interfaces, as far as I know, is that one is raw-ip and the other one 803.3 by default. -- Aleksander https://aleksander.es

MC 7304 ipv4v6

Hi, There is a device stranded in front of my computer: MC7304. It works basically under linux. But I have a problem. The dualstack mode of the provided by Deutsche Telekom makes problems. Addresses are assigned (IPv4 and IPv6), but only ipv4 is usable. Do you have any ideas, where I could