Re: [meetup] Announcing monthly online meetup for NetworkManager

Hey! > > In the past, we used to meet at Devconf.cz and also had virtual meetups > in the past 2 years. There was always the idea floating around, that we > could meet regularly and online. > > Now, such a meetup is scheduled. > > It will be every second Wednesday of the month. > See

Re: SARA-R4 unreliable LTE-M connection problem

Hey, > > Am Montag, 5. Juli 2021, 11:14:38 CEST schrieb Aleksander Morgado: > > > Connection can be established, I see data on the modems RX line, but > > > nothing on the TX line, which means the host sends data to the modem, but > > > gets back nothing. >

Re: SARA-R4 unreliable LTE-M connection problem

> Connection can be established, I see data on the modems RX line, but nothing > on the TX line, which means the host sends data to the modem, but gets back > nothing. > > Can this be a problem with the baudrate? I mean it's a classical serial UART, > so I would assume baudrates of host and modem

Re: Add new apn

Hey Socrates, On Wed, Mar 31, 2021 at 7:44 PM socrates via networkmanager-list wrote: > > hello, I am very satisfied with the work being developed by the > community and its supporters, I would like to add a new APN that > belongs to a new mobile operator in my country >

Re: manage a modem connection

Hey, > >> I have a "e3372h-153" Huawei 4G USB dongle. > >> > >> This dongle works with the "huawei_cdc_ncm" kernel driver. > >> > >> Once connected, two devices appear : /dev/ttyUSB0 and > >> /dev/cdc-wdm1. > >> These ones are used to talk to the modem itself. > >> > >> There is also a network

Re: manage a modem connection

Hey > > I have a "e3372h-153" Huawei 4G USB dongle. > > This dongle works with the "huawei_cdc_ncm" kernel driver. > > Once connected, two devices appear : /dev/ttyUSB0 and > /dev/cdc-wdm1. > These ones are used to talk to the modem itself. > > There is also a network interface appearing, which

Re: GSM: MBIM: How to select authentication type PAP, CHAP etc.

Hey > What I'm missing is a setting like 'gsm.auth-type'. > Can anyone point me in the right direction? In NetworkManager you configure what auth types you should NOT use; by default all these are "no": ppp.refuse-eap: no ppp.refuse-pap: no

Re: ModemManager and muxed network interfaces

Hey Thomas, > > I'm working on setting up muxed network interfaces with ModemManager > > so that e.g. you can connect to multiple APNs at the same time, each > > with its own subnet on a different virtual network interface link > > created from the "master" wwan modem interface. These links can

ModemManager and muxed network interfaces

Hey all, I'm working on setting up muxed network interfaces with ModemManager so that e.g. you can connect to multiple APNs at the same time, each with its own subnet on a different virtual network interface link created from the "master" wwan modem interface. These links can be done either

Re: Modem authentication via the NM d-bus API - how to handle PUK?

Hey, > On Fri, Oct 16, 2020 at 06:01:49PM +0200, Aleksander Morgado wrote: > > > What I could see so far is that the only thing one can provide to the > > > modem > > > via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to > > > NetworkManage

Re: Modem authentication via the NM d-bus API - how to handle PUK?

Hey, > > What I could see so far is that the only thing one can provide to the modem > via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to NetworkManager > and remain completely unhandled. > My opinion is that PIN is the only thing that NetworkManager should attempt to unlock, and

Re: Need to restart PC in order for NetworkManager to connect to LTE

Hey Yury, On Tue, Jun 30, 2020 at 10:01 AM Yury Kamnev wrote: > > I am experiencing quite a strange behavior when trying to set up LTE > connection via network manager and mc7455 usb modem. > > On first boot it just hangs: > > > nmcli > cdc-wdm0: connecting (prepare) to lte >

Re: configuring network manager connection for a Quectel EC20 WWAN device

Hey Jasper > > the journal for ModemManager: > > https://gist.github.com/ArcolaJasper/e5c16387d25f0b5b7f061559bae3ccb8 > What MM version are you using? Could you check whether autoconnect is enabled in the modem or not? E.g.: $ sudo qmicli -d /dev/cdc-wdm0 -p --wds-get-autoconnect-settings If

Agreement to relicense NetworkManager under LGPL-2.1+

Hey, I agree to relicense all the code I've written in NetworkManager to LGPL2.1+. Cheers! -- Aleksander https://aleksander.es ___ networkmanager-list mailing list networkmanager-list@gnome.org

Re: Modem stays connected when NM sets connection down

Hey, > > I’ve got some problems with my gsm-connection, managed with NetworkManager > and ModemManager. > > When my connection comes up after boot, the connection works and i can ping > my targets via gsm. > > Now, when i disable the connection and reactivated it, NetworkManager says, > it is

Re: Issues with LT4120 modem on 5.2 kernel.

> Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0 > > In modemmanager I can see that I am getting an IP address. But > NetworkManager's DHCP refuses to find it: A long shot, but this could be a mismatch in the link layer protocol between kernel and device.

Re: automatic APN selection

>> Also, I'd like to emphasize that IMHO this should not be the default in NM. >> Automatically selecting what APN to use should be explicitly enabled by the >> user somehow. Companies doing custom setups with MM+NM can enable this >> feature, even providing a "controlled" subset of the >>

Re: automatic APN selection

Hey, > > I posted yesterday question to ModemManger mailing list about > > implementing automatic APN selection (based on mobile broadband > > database) and it was pointed [0] out that this feature should be > > added to NM. My case is that embedded device using GSM modem should > > connect to

[RFC] Automatically remove stored SIM-PIN from gsm connection settings if it fails to unlock?

Hey, I've SIM-PIN blocked one of my SIM cards just by having a gsm autoconnected settings with a PIN stored and then PIN not matching the one in the device. When this happens, NM will try to unlock SIM-PIN once, and if it fails it won't try again (good) (*)... until the next reboot (bad). So, I

No new PIN request to the user if PIN stored in settings is wrong

Hey, I'm trying to understand whether this behavior is on purpose or not. I have some "gsm" settings for a broadband connection, and the settings have a PIN stored. I then try to use those settings on a modem device but the expected PIN in the modem is a different one, so the connection attempt

Re: Pantech UML290 - 106c:3718 - QMI Modem

On Sun, Apr 22, 2018 at 1:43 PM, Greg Oliver wrote: > Well, I got this modem working with raw qmi commands, but the issue of > changing to a data-format of 802-3 that dhclient understands does not > work. I know this is not a NM/MM issue, but you guys know the ins and

Re: Problems with modems/Example config for QMI-based modem,

> > I do wonder about these errors: > > Mar 6 08:26:31 ccimx6uluvalue daemon.warn ModemManager[775]: > couldn't load SIM identifier: 'Couldn't get UIM ICCID: QMI protocol error > (94): 'NotSupported'' > Mar 6 08:26:31 ccimx6uluvalue daemon.warn ModemManager[775]: > couldn't load IMSI:

[PATCH] connectivity: fix portal detection when using HTTP 204 based checks

If we're going to use a 'no content' URL (HTTP 204) to check connectivity, do not try to match prefix when the content is being received. This issue was making the check not work properly, as the content returned by the captive portal was assumed as expected (given that g_str_has_prefix(str,"")

[PATCH] connectivity: allow 204 (no content) as connectivity test

If the user is requesting an empty response ("") as expected string, let the connectivity check succeed if we actually get a 204 HTTP response code (reporting a successful request but without content). This allows using e.g. Android's default URLs for the connectivity check purpose:

Re: Pantech UML290 - 106c:3718 - QMI Modem

On Fri, Nov 17, 2017 at 12:44 AM, Greg Oliver <oliver.g...@gmail.com> wrote: > On Thu, Nov 16, 2017 at 2:57 PM, Aleksander Morgado > <aleksan...@aleksander.es> wrote: >> >> > >> > I have a Pantech UML290 LTE USB modem that talks QMI on my host.

Re: Pantech UML290 - 106c:3718 - QMI Modem

> > I have a Pantech UML290 LTE USB modem that talks QMI on my host. I am > having an issue setting the APN (and it appears PPP options when not running > LTE) for this device. > > When the device is not plugged in and I use nm-connection-editor to create a > new MobileBroadband connection, I can

Re: primary device changing from boot to boot

On Tue, Sep 5, 2017 at 9:40 PM, Tim Harvey wrote: > On Tue, Sep 5, 2017 at 9:56 AM, Pičugins Arsenijs wrote: >> I don't know if it's going to help you with this issue, but if you can >> hardcode a path to the serial port somewhere, take a look in the

Re: MC7455 'Call Failed'

On Thu, Jun 22, 2017 at 10:11 PM, Tim Harvey wrote: >>> Also, I'm unclear how to NetworkManager on the QMI devices: >>> root@ventana:~# nmcli connection add type gsm ifname cdc-wdm1 con-name >>> mc7455 apn h2g2 >>> Connection 'mc7455' (5dc4516e-e857-4917-9542-0dee211b692a)

Re: MC7455 'Call Failed'

Hey, > > The MC7455 presents two QMI+WWAN pairs which I think is quite common > for the Sierra Wireless modems. The first appears to be raw-ip and the > 2nd 802.3. Most of the qmicli commands won't work on cdc-wdm0 (raw-ip) > and I believe this is expected but I'm not clear exactly why (could >

Re: help needed to use a Sierra Wireless MC7354 3G modem with a Raspberry Pi3 running Angstrom v2016.12 - Kernel 4.4.35

Hey Phil, > > I think the problem lies with NetworkManager: > > root@raspberrypi3:/# nmcli con show > > NAMEUUID TYPE > DEVICE > > Wired connection 1 bdc6b7b3-1e60-453c-bfca-11ce7519826d 802-3-ethernet > eth0 > > cellular

Re: Newer NM for Yocto?

On Wed, Mar 15, 2017 at 2:45 PM, Alex Ferm wrote: > I'm experimenting with moving my system to yocto, does anyone have a > recipe for a newer version of network manager than 1.4.2? I was hoping to be > able to upgrade to a version that supported "sim-operator-id" for GSM

Re: NetworkManager not starting ppp connection.

On Sat, Sep 3, 2016 at 9:56 PM, A. F. Cano wrote: > Sep 2 21:02:58 fbx NetworkManager[1317]: [1472864578.5172] manager: > (ttyACM0): new Broadband device (/org/freedesktop/NetworkManager/Devices/26) > Sep 2 21:02:58 fbx NetworkManager[1317]: [1472864578.5180]

Re: Crash in Modem-Manager on Ubuntu

On Mon, Aug 15, 2016 at 12:51 PM, Ajay Garg wrote: > Thanks Aleksander for the reply. > > A small query, if a modem supports both DirectIP and QMI, which is the > recommended mode? > If I'm not mistaken, Sierra Wireless is suggesting to use QMI or MBIM, they are

Re: Crash in Modem-Manager on Ubuntu

On 13/08/16 03:24, Ajay Garg wrote: > First of all, my requirement is to have network-connectivity via the > modem; and have the ability to read SMSes and run AT-commands WITHOUT > losing the network-connectivity. > > I guess mmcli would do the trick, as modem-manager now comes plugged > in with

Re: Crash in Modem-Manager on Ubuntu

> > Thanks Aleksander. > > I updated the modem-manager, but still run into problems. > > One query, the modem product-code is 1199:68A3, meaning that it is in > DirectIP mode. > Do modem-managers support DirectIP-mode modems at all? Or will I have > to get the OEM-password and unlock its QMI-mode

Re: Crash in Modem-Manager on Ubuntu

On Wed, Aug 10, 2016 at 7:32 AM, Ajay Garg wrote: > I tried on Ubuntu-14 on Linux-Kernel-3.16 and Linux-Kernel-4.2, and > behaviour is same. > > The modemmanager version is 1.0.0-2ubuntu1.1 on both. > I tried "apt-get install", but I am told it is the latest-version

Re: [PATCH] UPower signaling obsolescence

On Mon, Mar 21, 2016 at 8:11 PM, poma <pomidorabelis...@gmail.com> wrote: > On 21.03.2016 17:12, Dan Williams wrote: >> On Mon, 2016-03-21 at 10:16 +0100, Aleksander Morgado wrote: >>> On 20/03/16 20:39, poma wrote: >>>> >>>> "N

Re: nmcli radio off connected to ModemManager power state low

On Mon, Mar 14, 2016 at 5:01 PM, Carlo Lobrano wrote: >> I'm not entirely sure what you mean with "power off" and "shut down the >> radio", but here are the definitions I'm using: >> power off: the entire modem is powered off not just the radio. The >> device does not

Re: Could not find "pppd" binary

On Tue, Mar 15, 2016 at 2:28 AM, Ali Nematollahi wrote: > I finally got MM 1.4.12 and 1.0.10 working and talking to each other...after > a long battle. > I got NM to a point that it detects MM and after all MM set up is done, it > tries to bring up the connection I have up

Re: nmcli c does not list modem device

On Mon, Mar 14, 2016 at 2:55 PM, matti kaasinen wrote: > In fact there are two more messages preceding those ones I mentioned before, > but I guess they have nothing to do with this problem. I'll get following > messages, if I have MM running from boot: > >

Re: nmcli c does not list modem device

On Mon, Mar 14, 2016 at 1:57 PM, matti kaasinen wrote: > 2016-03-14 14:53 GMT+02:00 Thomas Haller : >> >> > I can't get modem device listed with >> > nmcli c >> >> do you mean `nmcli d` (for [d]evice)? > > > > Yes, indeed. > BTW, I just monitored dbus

Re: nmcli radio off connected to ModemManager power state low

On Sun, Mar 13, 2016 at 1:56 PM, Carlo Lobrano wrote: >> The problem is that if the modem is totally powered off with a CFUN=0, >> > then how do we power it back on? CFUN=4, where the modem is still >> > alive but with radio off is already more than enough in most cases. >>

Re: nm-pppd-plugin does not start

+ MM mailing list On Sun, Mar 6, 2016 at 11:04 PM, Aleksander Morgado <aleksan...@aleksander.es> wrote: >>> > Good point, ppp is not enabled! Option seems to be --enable-ppp. >>> > I'll try >>> > > >>> > > it. This NDISDUP seem

Re: nmcli radio off connected to ModemManager power state low

On Sun, Mar 13, 2016 at 10:28 AM, Carlo Lobrano wrote: > > thank you, it is more clear now. I will check in my system for rfkill. > One more question, do you think it will be feasible for NM to check whether > rfkill is available and, if not, to set the modem in power off in

Re: nmcli radio off connected to ModemManager power state low

On Fri, Mar 11, 2016 at 5:18 PM, Dan Williams wrote: >> making some changes in ModemManager "set power state", I observed >> that setting >> setting a radio interface to OFF with nmcli, the ModemManager power >> state >> triggered is the LOW one, while I expected it to be the OFF

Re: nm-pppd-plugin does not start

On Fri, Mar 4, 2016 at 5:54 PM, Dan Williams wrote: >> > Good point, ppp is not enabled! Option seems to be --enable-ppp. >> > I'll try >> > > >> > > it. This NDISDUP seemp pretty problematic. In fact I found MM >> > > patch whose >> > > introduction comment describes pretty much

Re: nm-pppd-plugin does not start

On Fri, Mar 4, 2016 at 12:28 AM, Aleksander Morgado <aleksan...@aleksander.es> wrote: > >> QUESTIONS: >> = >> 1) What is missing in my set-up? > > I think you're missing ... I think you're basically missing the NM "gsm" connection that you

Re: nm-pppd-plugin does not start

Hey, > > Background: > = > I'm trying to integrate Huawei 3131 modem, VID=21d1. Original PID=14fe that > switches to PID=1506. > > I'm working on am335x based embedded board running yocto/linux-ti-staging > based Linux with 4.1 kernel. NM version is 0.9.8.10 and MM version 1.4.2. > Board

Re: NetworkManager not re-connecting modem connection after hangup

Hey, On 22/12/15 15:45, Cezary Manista wrote: > I found following issue: > > 1. GSM connection is Activated . > 2. Modem connection ends being hanged up on the operators side > 3. NetworkManager tries to auto-activate the connection but it fails > with error: > > Dec 21 13:43:23 6 1 buzby2-tcm

Re: MC 7304 ipv4v6

On Sun, Nov 29, 2015 at 11:59 AM, Thomas Schäfer <tschae...@t-online.de> wrote: > Am 29.11.2015 um 02:24 schrieb Aleksander Morgado: >> On Sat, Nov 28, 2015 at 10:58 PM, Thomas Schäfer <tschae...@t-online.de> >> wrote: >>> It works (tested only I

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

> 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

Re: [PATCH] device: prefer wifi over wwan by default

I, on the other hand, just want to be on-line whenever I can, so I simply use autoconnect=true for all available connections. Now I just need Aleksander to figure out what's going on in fdo#90973 and everything'll be just peachy. :-) Speaking of which, I just got hit by a related issue in my

Re: [PATCH] device: prefer wifi over wwan by default

On Wed, Jul 22, 2015 at 8:10 PM, Bastien Nocera had...@hadess.net wrote: While WiFi at least imply that the user select an SSID, there exists SIM cards that are delivered configured to not require a PIN code or a APN password from the user. This reminded me of something I've been

Re: ModemManager and Thuraya XT

On Wed, Jun 17, 2015 at 9:22 AM, Thomas Sailer sai...@sailer.dynip.lugs.ch wrote: On 06/17/2015 04:58 PM, Dan Williams wrote: That would seem to indicate that we need a ModemManager plugin for the XT to selectively ignore COPS. Given that the modem probably only has one operator and probably

Re: Interaction with ModemManager

On Wed, Jun 3, 2015 at 11:29 AM, Pieter Cardoen pieter.card...@hotmail.com wrote: This should be possible. I already have some experience with Python and NetworkManager-ModemManager. By now, there isn't a Python library available for the ModemManager dbus interface but there is for the

Re: NM coding style regarding private gobject data

On Wed, Apr 29, 2015 at 2:49 PM, Thomas Haller thal...@redhat.com wrote: It's my personal annoyance with the verboseness of: NM_TYPE_NAME_GET_PRIVATE (self)-my_field nm_type_name_get_instance_private (self)-my_field vs. self-priv-my_field Bonus point: it's easier in

Re: jhbuild run for NetworkManager

On Mon, Apr 13, 2015 at 1:42 PM, Lubomir Rintel lrin...@redhat.com wrote: One problem is that the system-wide NetworkManager instance gets D-Bus activated at random times. E.g. systemctl stop NetworkManager # NetworkManager gets D-Bus activated again ./src/NetworkManager --debug

Re: You must be root to run NetworkManager --version / --help

On Tue, Apr 7, 2015 at 6:17 PM, poma pomidorabelis...@gmail.com wrote: $ ModemManager --version ** (ModemManager:4483): WARNING **: Unknown option --version You get a warning there? No pun intended, what MM version is that? -- Aleksander https://aleksander.es

Re: You must be root to run NetworkManager --version / --help

On Tue, Apr 7, 2015 at 6:28 PM, poma pomidorabelis...@gmail.com wrote: $ ModemManager --version ** (ModemManager:4483): WARNING **: Unknown option --version You get a warning there? No pun intended, what MM version is that? $ rpm -q ModemManager ModemManager-1.4.6-2.fc21.x86_64 Ah, ok. I

[PATCH] wwan: don't assume DNS info is always available

Fixes segfault with e.g. Ericsson modems that reply just with IP+gateway, without DNS info. [mm-port-serial-at.c:440] debug_log(): (ttyACM8): -- 'AT*E2IPCFG?CR' [mm-port-serial-at.c:440] debug_log(): (ttyACM8): -- 'CRLF*E2IPCFG: (1,10.191.64.12)(2,10.191.64.10)CRLF' [mm-port-serial-at.c:440]

Re: ANN: NetworkManager 1.0.0 released!

On Tue, Dec 23, 2014 at 12:43 PM, Bjørn Mork bj...@mork.no wrote: So you need the full context type choice for QMI as well. The odd two-step dual-stack connection does not change this. The PDP type is always selected by the first connection. Is that true even if we use different separate

Re: ANN: NetworkManager 1.0.0 released!

On Sun, Dec 21, 2014 at 10:39 PM, Tore Anderson t...@fud.no wrote: Hi Aleksander, Are you suggesting that by default NM should try with IPv4 or IPv6 PDP context types if both are enabled and IPV4V6 fails? Yes, I think that would be the best solution. In QMI modems it is ModemManager the

Re: ANN: NetworkManager 1.0.0 released!

Are you suggesting that by default NM should try with IPv4 or IPv6 PDP context types if both are enabled and IPV4V6 fails? Yes, I think that would be the best solution. In QMI modems it is ModemManager the one connecting separately IPv4 and IPv6 WDS sessions when IPv4v6 is requested. Yep,

Re: ANN: NetworkManager 1.0.0 released!

On Sun, Dec 21, 2014 at 12:15 PM, Tore Anderson t...@fud.no wrote: This release brings [...] WWAN IPv6 support Before you rush off to upload 1.0.0 to the various distros, I'd like to remind you of https://bugzilla.gnome.org/show_bug.cgi?id=733696. This is going to break WWAN connections for

Re: ANN: NetworkManager 1.0.0 released!

On Fri, Dec 19, 2014 at 6:42 PM, Dan Williams d...@redhat.com wrote: * New client library: libnm A new GObject-based client library, libnm, has been written, merging the existing libnm-util and libnm-glib and simplifying the API while using modern GLib APIs (such as using GDBus rather

Re: Mobile broadband on an embedded 3G modem

On Fri, Oct 17, 2014 at 10:35 AM, Marius Kotsbak mar...@kotsbak.com wrote: We're trying to get a 3G modem connection going on an embedded device. The modem is a MultiTech SocketModem MTSMC-H5-IP and it appears on /dev/ttyAPP3 (i.e. hardware UART port on the SoC). If I run `screen

New ModemManager-only bugzilla in freedesktop.org

Hey, There is a new Bugzilla for ModemManager issues in freedesktop.org: https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager This means that new ModemManager bugs shouldn't be reported to the NetworkManager bugzillla in gnome.org any more. I'll try to move all the relevant bugs from

Re: [MM PATCH] port-serial: fix forced closing after b28230411

On Wed, Oct 8, 2014 at 8:25 PM, Dan Williams d...@redhat.com wrote: On Wed, 2014-10-08 at 00:29 +0200, Aleksander Morgado wrote: On Tue, Oct 7, 2014 at 11:06 PM, Dan Williams d...@redhat.com wrote: b28230411 moved up the self-priv-forced_close = TRUE, which caused mm_port_serial_close

Re: [MM PATCH] port-serial: fix forced closing after b28230411

On Tue, Oct 7, 2014 at 11:06 PM, Dan Williams d...@redhat.com wrote: b28230411 moved up the self-priv-forced_close = TRUE, which caused mm_port_serial_close() to just return without actually closing the port and cleaning up. Also, cancel the reopen separately from closing the port since the

Re: Debian 7 (wheezy) - mobile broadband support in NetworkManager unstable

On Fri, Jul 11, 2014 at 9:37 AM, Phil Reynolds phil...@tinsleyviaduct.com wrote: It never has been very stable, but in recent weeks I've noticed that NetworkManager is very unstable when it comes to my mobile connection. I am using Debian wheezy (the stable release) on a Lenovo Thinkpad

connections-read signal not emitted reliably?

Hey, Using NM 0.9.8.8 and seeing an issue with the connections-read callback in NMClient.RemoteSettings; basically, the callback isn't being fired. This only seems to happen if NM is started and right away (after NM is in the bus) a program creates a NMClient.RemoteSettings and connects to the

Re: connections-read signal not emitted reliably?

Hey, On Wed, Jun 25, 2014 at 9:53 AM, Aleksander Morgado aleksan...@aleksander.es wrote: Using NM 0.9.8.8 and seeing an issue with the connections-read callback in NMClient.RemoteSettings; basically, the callback isn't being fired. This only seems to happen if NM is started and right away

[PATCH] ppp: avoid pppd exiting when no traffic going through

By default pppd will suicide if there are 600s without traffic going through: pppd[30575]: Terminating connection due to lack of activity. pppd[30575]: Connect time 10.0 minutes. pppd[30575]: Sent 0 bytes, received 0 bytes. This is likely to happen when e.g. the system has both a mobile

pppd: Terminating connection due to lack of activity.

Hey hey, Is there any good reason why when launching pppd, for e.g. a mobile connection, we don't use idle 0 by default? Otherwise pppd will suicide after 10 mins (default) of inactivity in the channel: Apr 01 01:22:38 pppd[23180]: Terminating connection due to lack of activity. Apr 01 01:22:38

Re: ZTE MF60 3G Modem Not Working with ModemManager/NetworkManager

On Wed, Mar 12, 2014 at 8:30 AM, Marko Myllynen mylly...@redhat.com wrote: On 2014-03-10 21:51, Aleksander Morgado wrote: On Mon, Mar 10, 2014 at 7:12 PM, Dan Williams d...@redhat.com wrote: I've been trying to get a ZTE MF60 3G modem working with MM/NM but even though recent updates have

Re: ZTE MF60 3G Modem Not Working with ModemManager/NetworkManager

On Mon, Mar 10, 2014 at 7:12 PM, Dan Williams d...@redhat.com wrote: Hi all, I've been trying to get a ZTE MF60 3G modem working with MM/NM but even though recent updates have provided some progress it's still quite not working. It's not explicitly listed in the page of Supported Devices [1]

Re: Nokia 21M-02 failing to be recognised as Icera

Hey Tore, On Wed, Feb 26, 2014 at 9:12 PM, Tore Anderson t...@fud.no wrote: By dcbw's request, here's some logs plus mmcli output from a Nokia 21M-02 that's usually failing to be recognised as an Icera device and handled by the nokia-icera plugin. What seems to happen is that either it's too

Re: [PATCH 0/3] Compile fixes with --with-newest-qmi-commands

Hey Guido, On Sun, Jan 26, 2014 at 4:37 PM, Guido Günther a...@sigxcpu.org wrote: Hi, while building with --with-newest-qmi-commands against latest libqmi-glib HEAD I got these compile warnings. Please apply if these look o.k. Wrong mailing list for ModemManager patches; use this one instead:

Re: [PATCH 0/3] Compile fixes with --with-newest-qmi-commands

On 26/01/14 20:00, Aleksander Morgado wrote: Hi, while building with --with-newest-qmi-commands against latest libqmi-glib HEAD I got these compile warnings. Please apply if these look o.k. Wrong mailing list for ModemManager patches; use this one instead: http://lists.freedesktop.org

Re: HUWAEI E1750 NDISDUP

On 17/12/13 23:50, poma wrote: This and similar devices are apparently working in this way also. Is it planned to support such a mode in the NetworkManager? You mean with NDISDUP=1,1 and the like? ModemManager 1.2 will do that already, you'll just need: # mmcli -m 0

Re: Problems with several modems after upgrade to ModemManager-1

On 22/11/13 14:59, Harald Jung wrote: Update: When modemmanager is built with mbim support the activation und registrationm works but it wasn't able to aquire an IP by dhcp. Now i lost the connection to the notebook with the device and I can't do any debugging for the next days. In

Re: Problems with several modems after upgrade to ModemManager-1

Hey, Modem 12d1:1001 needs a very long time to initialize and isn't able to register: T: Bus=01 Lev=02 Prnt=02 Port=01 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=12d1 ProdID=1001 Rev=00.00 S:

Re: altair/tests/test_modem_helpers_altair_lte-test-modem-helpers-altair-lte.o

Hey! Hello NM MM Mailinglist, Actually this is the new MM mailing list: http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel Over here I have a strange error while compiling modem-manager from git. This is what `make` gives me: screenshot CC

Re: Preventing modem-manager from accessing specific serial ports?

On 24/10/13 04:37, Volker Kuhlmann wrote: http://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/77-mm-usb-device-blacklist.rules Thank you very much Dan, adding ID_MM_DEVICE_IGNORE is trivial once one knows that is the trick to use. Are there *any* modems using any of the FTDI

Re: 3g modems that no longer work

On 22/10/13 13:14, Perazim wrote: Back in F-14 with your help I was able to get the following 3G USB modems to work: Alcatel X220D lsusb: T A Mobile Phones, 1bbb:0017 and T-Mobile ZTE MF636 lsusb: ONDA Communications Spa, 19d2:0031 Both of these do not seem to work in either F-19

Re: Sierra Wireless MC8355 - Gobi 3000 with ATT

On 02/10/13 17:05, Kenneth Berland wrote: NM moves along well until it errors-out with these lines (I think): Oct 2 07:35:50 ken-x230 ModemManager[1811]: info error: couldn't start network: QMI protocol error (14): 'CallFailed' Oct 2 07:35:50 ken-x230 ModemManager[1811]: info call end

Re: Sierra Wireless MC8355 - Gobi 3000 with ATT

On 03/10/13 10:15, Bjørn Mork wrote: Could very well be that they forbid using that APN with a Sierra Wireless IMEI. Really? Why would they do that? -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org

Re: wwan0 built in toshiba

On 31/08/13 13:06, Bjørn Mork wrote: Something like the attached simple patch should fix it. Pushed to git master and mm-1-0 after Thomas' test. -- Aleksander ___ networkmanager-list mailing list networkmanager-list@gnome.org

Re: [HELP] Modem manager v1.0.0 can't work with network manager

On 06/08/13 10:44, 李晋 wrote: If I also need to develop plugin for v0.6? Because I find that many latest Linux distributions still use MM 0.6 now. I would really just focus on 1.0 for now on; which is what distros will be picking up in the next releases I guess. -- Aleksander

Re: USB dongle with NAS v1.4 and older

On 30/07/13 06:46, Dan Williams wrote: On Mon, 2013-07-29 at 01:31 -0700, sisiferl wrote: Hi, I am in the process to select some/any usb dongle to work with QMI/libqmi, and for my purpose, I need anything where the NAS version is newer than v1.4. The Huawei e398 apparently has NAS 1.8.

Re: How frequently org.freedektop.ModemManager.Modem.Cdma.SignalQuality signals signal strength?

Hey, hi, this is what i've done... 1. i found 3 endpoints on interface 0. 2. # echo 1-1.2:1.0 /sys/bus/usbl/drivers/option/unbind 3. # modprobe qmi_wwan 4. echo 19d2 fff1 /sys/bus/usb/drivers/qmi_wwan/new_id 5. installed libqmi-utils i didnt find

Re: [PATCH][RFC][ModemManager] udev rules: port to hwdb where applicable

Hey Tom! Udev recently gained a hardware database, which is an efficent replacement for the kind of rules shipped with modemmanager. This patch ports all the relevant udev rules to hwdb format, which should significantly speed up the processing of usb add events. I also fixed up some

Re: [PATCH][RFC][ModemManager] udev rules: port to hwdb where applicable

it would be interesting if we could make this more generic and not just ModemManager specific. If we could create proper hwdb that can be both used by oFono and ModemManager, then we could gain something here. In addition they could be just merged into systemd directly. We already

Re: [PATCH][RFC][ModemManager] udev rules: port to hwdb where applicable

On 22/07/13 08:57, Aleksander Morgado wrote: it would be interesting if we could make this more generic and not just ModemManager specific. If we could create proper hwdb that can be both used by oFono and ModemManager, then we could gain something here. In addition they could be just

ANN: ModemManager 1.0.0 released

Hey! I'm pleased to announce the release of ModemManager 1.0.0. This release includes major changes since the last 0.6.x stable version, including a completely new D-Bus API. http://www.freedesktop.org/software/ModemManager/ModemManager-1.0.0.tar.xz This release introduces the new

Re: AT!ICCID before PIN-entry fails

On 07/18/2013 12:24 PM, Andrew Bird wrote: To be honest I can't remember what the encoding is called, but it is as you say pair swapped. If the length is odd it's padded with the 'F' character. I'm pretty sure it's used elsewhere in mobile comms, so ModemManager may have an

Re: AT!ICCID before PIN-entry fails

I hope I'm right here with this question. We use the LTE-modem Sierra MC 77100 with Direct-IP Firmware in a standalone box. The box must connect to the internet by itself - so I must store the pin in the box. I want make shure that the pin is not sent to the modem, when the SIM-card is

  1   2   3   4   5   6   7   >