Hi,
a 4g/5g provider in Germany(1&1) provides a nat64 gateway without providing
the nat64 prefix via DNS64 (it is the well known 64:ff9b::/96)
Is there a known way, how the provider could tell the user equipment the
pref64? (via RA ? ) rfc/3ggp paper?
https://modemmanager.org/docs/modemmanage
Am 08.09.21 um 09:27 schrieb Aleksander Morgado:
Hey Thomas
I know the fibocom L830-EB-00 is quite old and the modemmanager version 1.12.6
too.
Nevertheless I can confirm it works with IPv4/IPv6 in Germany with Deutsche
Telekom, Vodafone and Telefonica.
As well with Deutsche Telekom IPv6-onl
Hi,
I know the fibocom L830-EB-00 is quite old and the modemmanager version 1.12.6
too.
Nevertheless I can confirm it works with IPv4/IPv6 in Germany with Deutsche
Telekom, Vodafone and Telefonica.
As well with Deutsche Telekom IPv6-only.
Regards,
Thomas
Hi,
this email contains just some test results with the telit-le910-eu-v2 with
focus on ipv6.
Unfortunately I was not able to get the newest firmware
(20.00.403 instead of 20.00.406) for that device, so I don't know if some
issues are already fixed.
Also ModemManager is not the newest. It is s
Am Dienstag, 8. Juni 2021, 21:00:41 CEST schrieb Amardeep Manak:
> Hello
>
> So I am trying to test Sierra EM7565 using modem manager. I am using Debian
> 9 (uname -r: 4.9.0-13-amd64) and the version of modem manager is 1.6.4.
I afraid 1.6.4 is probably to old.
maybe debian 9 too
( 9 Stretch 2
Hi,
I am not sure, if I asked it already. ModemManager gets all information about
IPv6, but it ignores them.
I made a successful IPv6 (dual stack) test with a combination of
NetworkManager/ModemManager and some manual commands.
I used version 1.14.8. (the latest in tumbleweed)
I haven't compil
Am Freitag, 4. Juni 2021, 18:00:22 CEST schrieb Muhammad Moeen Yaqoob:
> Hi there,
>
> Can anyone please confirm if modemmanager (w/ qmi_wwan driver) has been
> proven to work with SierraWireless EM7565 modem? If so, which version of
> modemmanager? and which version of the underlying Linux kernel
Hi,
Recently Telefonica Germany started to enable ipv6 in its mobile network for
all customers.
For me a reason to retest my LTE-modems/sticks.
1und1-xsstick-W1208.
1und1-zte-mf79
alcatel-ik40
quectel-ec25
em7565-mbim
em7565-qmi
mc7304-mbim
mc7304-qmi
mc7455-mbim
mc7455-qmi
me909s-120
o2-zte-m
Hi,
has anyone experience with the TOBY-L2 series by ublox in combination
with IPv6(ipv4v6 or ipv6)?
The readme
https://github.com/freedesktop/ModemManager/tree/master/plugins/ublox
of the ublox plugin states, that the modem may run in different
usb-profiles (ppp, ecm, rndis) and network mode
Hi,
I got two openwrt devices
GL.iNet AR750M (openwrt by openwrt 19.07.02) + a lot of (USB)-LTE-modems(qmi/
mbim)
and
mudi GL-E750(openwrt by gl-inet, 18.06.1, with built in LTE-modem
So far I had no luck to get it running, no dualstack no IPv6-only.
https://forum.openwrt.org/search?q=ipv6%20
Am 17.12.19 um 15:40 schrieb Ulrich Mohr:
Hi there,
We are redesigning our hardware and consider replacing our UBlox Toby
modem by a different one. What would be a good choice in terms of being
proven to work good with ModemManager (using them in Germany and central
Europe).
Here are five
Hi,
in the meantime I can compare the IPv4/IPv6 behavior of telekom (alias
DTAG, t-mobile germany) and vodafone germany.
Telekom provides IPv6 (dualstack) at production level since summer of
2015 and vodafone since last month.
With android smartphones both works.
But with ~50% of my surfstick
thomas@linux-y7a7:~> mmcli -b 0
Bearer '/org/freedesktop/ModemManager1/Bearer/0'
-
Status | connected: 'yes'
| suspended: 'no'
| interface: 'wwan0'
| IP timeout: '20'
Am Donnerstag, 14. November 2019, 21:28:18 CET schrieb Thomas Schäfer:
> What is the NetworkManager part in openwrt together with ModemManager?
I found the answer here:
https://openwrt.org/docs/guide-user/network/wan/wwan/modemmanager
I will give it a chance soon.
Tho
Am Mittwoch, 9. Oktober 2019, 09:42:29 CET schrieb Aleksander Morgado:
> Hey!
> Everyone is encouraged to switch to the official openwrt packages
Just a small report with my first try ModemManager at openwrt.
It is based on my "old friend" the E398 and the IPv6-only network by DTAG,
unfortunate
Am Sonntag, 12. Mai 2019, 16:43:23 CEST schrieb Reinhard Speyerer:
> Hi Thomas,
>
> for the EM7565 you should have used AT!USBCOMP=1,3,100D to switch it to MBIM
> mode and AT!USBCOMP=1,3,10D to switch it back to QMI.
Thanks a lot!
Linux is more tolerant than windows in this case. The wrong mbi
Hi,
I played a little bit with my new device EM7565. Everything works under Linux.
qmi: ipv4, ipv4v6, ipv6
mbim: ipv4, ipv4v6,ipv6
Unfortunately I made a switch without knowing how to reverse it:
AT!ENTERCND="A710"
OK
AT!IMPREF="GENERIC"
OK
AT!USBCOMP=1,1,100D
OK
AT!BAND=00
OK
AT!RESET
OK
Hi Pavlin,
Thanks a lot for the reports!
Do you have any chances to repeat the tests with IPv6-only and IPv4v6-
dualstack?
Regards,
Thomas
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/
Am 19.09.18 um 10:30 schrieb Dennis Schridde:
The device does not even show up in NetworkManager 1.14.0, when list all
network devices with `nmcli`. Consequently I cannot configure it with KDE
Plasma NM 5.13.5.
Try to find the NIC-device with
ip l
or
ip a
then please test with dhclient the
Am 19.09.18 um 11:06 schrieb Dennis Schridde:
Also, the device asks me for a PIN ("Enter PIN" shown on the display). I
don't need ModemManager to transmit the PIN to the modem?
The device should have a web gui - so, setting PIN has to take place there.
Thomas
___
Am 19.09.18 um 11:06 schrieb Dennis Schridde:
Also, the device asks me for a PIN ("Enter PIN" shown on the display). I
don't need ModemManager to transmit the PIN to the modem?
The device should have a web gui - so, setting PIN has to take place there.
Thomas
___
Am 19.09.18 um 09:56 schrieb Dennis Schridde:
Hello!
My Huawei Mobile WiFi Pro2 E5885L (Model E5885Ls-93a) is not being detected by
ModemManager 1.6.12. Please find information about the device and a
ModemManager debug log attached. If any information is missing, please do not
hesitate to ask.
Am 21.02.2018 um 15:17 schrieb Henrique Ferreiro:
I will be using it in Spain. My current carrier offers the following
dongle: alcatel IK40V, which apparently is a rndis modem. Any idea about
this particular model/protocol?
I have this modem on my IPv6-test.
It works well with linux and wind
Hi Henrique,
Both sticks work with linux.
The mixed results are caused by different firmware versions, different
modes and of course some different development states of linux,
usb-modeswitch, NetworkManager and ModemManager.
What do you mean with "reasonably well" ?
If your are satisfied wi
34 schrieb Reinhard Speyerer:
On Sat, Oct 07, 2017 at 11:31:27PM +0200, Thomas Schäfer wrote:
Hi,
since changing the context (ipv4, ipv4v6, ipv6) is often not trivial I would
need a second opinion / report.
I noticed that one of my smartphones accepts the apn-type/context IPv6 (only),
instead of ip
Hi,
since changing the context (ipv4, ipv4v6, ipv6) is often not trivial I would
need a second opinion / report.
I noticed that one of my smartphones accepts the apn-type/context IPv6 (only),
instead of ipv4 or IPv4/IPv6.
IPv4 is not new of course, IPv4/IPv6 works for two years with exact tha
Am Samstag, 7. Oktober 2017, 14:08:20 CEST schrieb Bjørn Mork:
> Thomas Schäfer writes:
> > Hi,
... qmi --> mbim
> > So I would recommend to give the firmware update a chance.
>
> Did the USB composition really change with the firmware upgrade? That's
> une
Hi,
SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
defaults to qmi and some problems with two devices, raw-ip mode and other
things.
But it in the end it did work on my device.
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.10 Cls=00(>ifc ) Sub=00
Am Dienstag, 21. März 2017, 20:32:29 schrieb Aleksander Morgado:
> You can convince MM to use the WWAN with a udev rule like this:
>
> # Airtel branded E3372h-607, using huawei-cdc-ncm driver but with
> unresponsive cdc-wdm port
> ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
> ENV{ID_MM_HUA
Hi,
I reflashed a Telekom Speedstick V (E3372h) with the firmware from megafon.
Under Windows 10 this has the effect, that the stick is running dualstack.
This is also possible under linux, but only manually:
echo -ne '\r\nAT^NDISDUP=1,1,"internet.telekom"\r\n' > /dev/ttyUSB0
With ModemManager
Am Samstag, 14. Januar 2017, 01:16:07 schrieb Martin MOKREJŠ:
> I think NM could save some effort by first checking for
> /proc/sys/net/ipv6/conf/ttyUSB0, and only after that proceed with more
> detailed checks. Second, does ttyUSB0 support IPv6 at all? It does same for
> tun0 and tun1 interfaces
Am 12.01.2017 um 23:52 schrieb Martin MOKREJŠ:
> Hi Thomas,
>
> Thomas Schäfer wrote:
>> Hi,
>>
>> I am a little bit surprised that the modem uses the ppp-interface
>> in your case. When I read your logfiles right, then you have a
>> device which is s
Hi,
I am a little bit surprised that the modem uses the ppp-interface in your
case. When I read your logfiles right, then you have a device which is sold
under the name "Speedsick LTE V" in Germany.
This device should use the wwan-device by huawei_cdc_ncm.
I know three different kinds of this
Am Dienstag, 6. September 2016, 17:57:45 schrieb José:
> Hi,
>
> I am planning to test ModemManager with QUECTEL EC20 and EC21 cellular
> modems. These modems support the following drivers:
> * USB Serial (option.c)
> * CDC ACM
> * GobiNet
> * QMI WWAN
>
> What is the best approach for trying to
I am a little bit confused.
I started everytime with step "c)" (mmcli -L to get the right number)
Step "b)"(setting the bearer manually) was never necessary.
Because of the enumeration I also rarely used step "a)".
By the way: Does your ISP provide IPv6 too?
Am Samstag, 13. August 2016, 22:26:43 schrieb Ajay Garg:
> Thanks Thomas.
>
> On Sat, Aug 13, 2016 at 10:11 PM, wrote:
> > Am 13.08.2016 17:28 schrieb Ajay Garg :
> >> Thanks Thomas.
> >>
> >>
> >> Question 2 :
> >> =
> >>
> >> Let's take a modem working in QMI-mode.
> >>
> >> With t
Am Samstag, 13. August 2016, 12:51:17 schrieb Neil Cherry:
> On 08/13/2016 10:56 AM, Ajay Garg wrote:
> > Hi All.
> >
> > I have rarely felt so frustrated as I have since last week, with my
> > haed dizzying over how the following different technologies/tools
> > fit-in.
>
> Amen to that! I'm in
Am 25.07.2016 um 18:08 schrieb Dan Williams:
It looks like the mbim-proxy isn't installed or isn't in the expected
path.
The live cd and unfortunately the default-desktop (leap42.1)
installation from suse has incomplete mbim libraries.
Now (after adding one further mbim-package) it works w
Am 24.07.2016 um 22:58 schrieb Reinhard Speyerer:
For testing I switched a MC7304 to the USB composition used by the EM8805.
With a Xubuntu 16.04 live CD ModemManager 1.4.12 successfully created a
modem for the MC7304.
Thanks for the hint. It works out of the box in dual stack mode.
Details
Hi,
I have had a chance to test the built in EM8805.
At first I tried windows (it was already installed) to be sure the device
works and to have an idea about the configuration. Unfortunately I have only
pictures of it.
http://www.thomas--schaefer.de/windows-em8805.tgz
After that I tried to
Am Dienstag, 21. Juni 2016, 20:01:16 schrieb Thomas Lang:
> Hi,
> perhaps i can bring a good explanation for the long ping. Are you using LTE
> as a radio access network? If so it could be normal you get a first long
> ping coz in LTE the power management could put you in a "power save mode"
> it t
Am Dienstag, 21. Juni 2016, 20:30:51 schrieb Thomas Schäfer:
> Am Dienstag, 21. Juni 2016, 19:49:25 schrieb Thomas Schäfer:
> > Am Dienstag, 21. Juni 2016, 10:02:08 schrieb Dan Williams:
> > > Thomas,
> > >
> > > Could you test this patch out and make sur
Am Dienstag, 21. Juni 2016, 19:49:25 schrieb Thomas Schäfer:
> Am Dienstag, 21. Juni 2016, 10:02:08 schrieb Dan Williams:
> > Thomas,
> >
> > Could you test this patch out and make sure it works? It should fix
> > the problem you saw before.
Here is the logfile f
Am Dienstag, 21. Juni 2016, 10:02:08 schrieb Dan Williams:
> Thomas,
>
> Could you test this patch out and make sure it works? It should fix
> the problem you saw before.
>
> Dan
>
I made already a test. But despite the situation is better, it is not good.
The K5160 works, as wanted, for the
Hi,
Assumed I applied the patch correctly. It doesn't work.
The logfile is attached.
k5160 and K5150 do not work with it.
Regards,
Thomas
k5160.tar.7z
Description: application/7z-compressed
___
ModemManager-devel mailing list
ModemManager-devel@
Am 15.06.2016 um 21:41 schrieb Dan Williams:
rther investigation, can you change this line in
> connect_set_ready():
>
> ctx->ip_type = ip_type;
>
> to:
>
> ctx->ip_type = MBIM_CONTEXT_IP_TYPE_IPV4V6;
>
With this setting the modem works in dualstack.
Regards,
Th
Am 14.06.2016 um 22:43 schrieb Dan Williams:
>
> As always when there are questions, MM debug logs are usually necessary
Here are the log files. K5150 (the old one) mostly connects via
dualstack. It is an example that mbim works in principle in my setup.
(SIM, APN, NetworkManager 1.06, ModemMan
Hi,
the good news first. The modem works under linux in both modes (cdc_ether and
mbim).
cdc-ether-mode works well in dualstack too without special treatment.
I have some problem with dualstack in mbim-mode.
Using just the Networkmanager it only uses ipv4. If I use the ModemMananger
manually w
Am Freitag, 22. April 2016, 17:09:14 schrieb Dan Williams:
> On Sat, 2016-04-23 at 00:02 +0200, Thomas Schäfer wrote:
> > Maybe somebody sees the difference in what mm does different at the
> > beginning
> > compared to the dlink-dialer.
> >
> > The "
Hi,
despite windows doesn't use the mbim-mode, I attached the usb-trace. (readable
with wireshark).
Maybe somebody sees the difference in what mm does different at the beginning
compared to the dlink-dialer.
The "SIM missing" -problem should be solved independent of the ppp/mbim-mode.
Regard
Hi,
I have some problems with this modem.
But step by step.
First of all, I don't know if it works this way at all, because windows (xp)
doesn't use the mbim-mode. The device is there, but the dialer from d-link
uses only the serial port.
The first problem is the initialisation. Despite usb_
Hi,
the modem "4G LTE usb-modem U901" works with the ModemManager without
problems.
Just some additional information not only for MM-developers:
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05c6 ProdID=9
Am Montag, 25. Januar 2016, 21:18:53 schrieb Aleksander Morgado:
> On Mon, Jan 25, 2016 at 9:15 PM, Thomas Schäfer
> >> I tested it with MC7304.
> >
> > Today I tested also devices which work better with raw-ip than with 802.3.
> >
> >
> >
Am Sonntag, 24. Januar 2016, 20:35:15 schrieb Thomas Schäfer:
> Am 24.01.2016 um 17:29 schrieb Aleksander Morgado:
> > On Wed, Jan 6, 2016 at 6:24 PM, Dan Williams wrote:
> >>> The new Sierra MC74XX modules are very very different to all previous
> >>> Sierra
Am 24.01.2016 um 17:29 schrieb Aleksander Morgado:
> On Wed, Jan 6, 2016 at 6:24 PM, Dan Williams wrote:
>>
>>> The new Sierra MC74XX modules are very very different to all previous
>>> Sierra modules. Among other things, they always work in raw-ip mode,
>>> and they also don't implement "DMS UIM"
Am 29.11.2015 um 02:16 schrieb Aleksander Morgado:
>
> Is it too late to ask for some ModemManager --debug logs to have as reference?
>
No, here it is.
> Thanks for the details!
>
Thank you for your great work!
Thomas
mm-20151129.log.xz
Description: application/xz
Hi,
this is a copy from my post at:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=2434
some parts are relevant for linux kernel, but I have no access to usb-linux
mailing list any more.
( there is a german discussion about this device here:
https://forum.ubuntuusers.de/top
Am Mittwoch, 19. August 2015, 12:52:49 schrieb Dan Williams:
> Hi,
>
> I had at least one report of a HiSense device that had successful
> AT^NDISSTATQRY reply but DHCP didn't work. There's been discussion on
> this in the past [1] with no real conclusion that I can see, but maybe
> ^DHCP works h
Am Dienstag, 1. September 2015, 12:16:05 schrieb Dan Williams:
> Thomas, were you able to test out this branch?
I am sorry - no.
I have two devices, the old one E3276 and the newer one E3372, both branded by
"Deutsche Telekom".
I could give the old one a try. But the newer one has still troub
Hi,
Please forget my last mail about the missing net-interface.
I have three linux-installations. I just used the one where huawei_cdc_ncm
doesn't load. I don't know why.
I have to solve the problem before I do contribute to further tests.
Regards,
Thomas
_
Am 19.08.2015 um 22:52 schrieb Dan Williams:
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
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.
at
Am Samstag, 27. Juni 2015, 14:29:17 schrieb Vittorio Gambaletta:
> Hi,
>
> Il 27.06.2015 12:54 Thomas Schäfer ha scritto:
> > It doesn't work for me.
>
> I've got E3372h-153 with firmware 21.180.01.00.00. Is this the same of your
> key? Please note that E33
Am Freitag, 26. Juni 2015, 23:05:08 schrieb Vittorio Gambaletta:
> After testing many things, I've found the "magic" settings that do work:
>
> echo 6000 > /sys/class/net/wwan0/cdc_ncm/tx_max
> echo 0 > /sys/class/net/wwan0/cdc_ncm/min_tx_pkt
>
> After issuing these commands, the interface works
Am 21.05.2015 um 08:21 schrieb Aleksander Morgado:
Did you have to use the external powered hub? Or did the RPi2 give you
enough power in the USB port?
I used it without hub and it worked for the test. But afterwards I
removed the stick and rpi2 crashed.
So it may be better to use it with
Am Montag, 18. Mai 2015, 23:51:05 schrieb Thomas Schäfer:
> My first impression of the rpi, it should work there. I have had problems
> with some unwanted network daemons. For testing I prefer to do step by step
> manually. This is hard in time of systemd and dbus and thousand different
Am Montag, 18. Mai 2015, 22:27:12 schrieb Mindaugas Stankevičius:
> This device must work on linux, but still I do not know where can be the
> problem.
> Almost the same device (R226) router work with linunux with no problem,
> but it has different id and firmware:
> http://www.draisberghof.de/usb_
I am reading this thread for a while.
In the meantime I am also an owner of an rpi.
The old raspbian wheezy is very much outdated. My "jessie" is unfortunately
very unstable (maybe my upgrade wasn't correctly run).
Because I am new to this arch and debian I will need some time to put things
Am 18.05.2015 um 10:23 schrieb Aleksander Morgado:
On Mon, May 18, 2015 at 9:44 AM, Thomas Schäfer wrote:
Anyway, my observations with the R215 have nothing to do with the
issues from the original reporter... :)
Yes, the R215, R216, R226 from vodafone are working with
linux
Hi,
I have the same device (I will compare the IDs later).
My experience is: you can't use it under linux via USB.
ModemManager is totally wrong here, because the device behaves like a
router. (maybe you are able to switch it to different device, but this
would be an exception)
The Networkm
70 matches
Mail list logo
