sierra modem connected through serial port not working
We are using Modem manager 1.8.2. We are trying to connect sierra modem via
serial port ttyS0. We modified /lib/udev/rules.d/77-mm-sierra.rules to
ACTION!="add|change|move|bind", GOTO="mm_sierra_end"
SUBSYSTEMS=="tty", GOTO="mm_sierra"
GOTO="mm_sierra_end"
LABEL="mm_sierra"
ACTION=="add", KERNEL=="ttyS0", ENV{ID_MM_PLATFORM_DRIVER_PROBE}="1"
LABEL="mm_sierra_end"
But when we load we get following logs
syslog[4989]: [1541472622.239884] (Sierra) [ttyS0] filtered as
couldn't retrieve drivers
syslog[4989]: [1541472622.240072] [plugin manager] task 0,ttyS0:
found '0' plugins to try
syslog[4989]: [1541472622.240265] [plugin manager) task 0,ttyS0:
started
syslog[4989]: [1541472622.240424] [plugin manager] task 0,ttyS0:
finished in '1.498676' seconds
syslog[4989]: [1541472622.240912] [plugin manager] task 0,ttyS0: not
supported by any plugin
and sierra plugin is not loaded. Any help?
--
Sent from: http://gnome-networkmanager.2324886.n4.nabble.com/
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
NM - dnsmasq, shared conn. no IP to client
Hello Folks, I have 64 bit openSUSE Tumbleweed. Just a week ago my shared wifi and ethernet connections were working with NetworkManager I do not know what happened but now I got such messages and the client can not get IP address Why dnsmasq can not create that lease file in /var/lib/NetworkManager? How can I get over this problem? Thanks for your time. Here is the NetworkManager log: systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/NetworkManager.service.d └─NetworkManager-ovs.conf Active: active (running) Docs: man:NetworkManager(8) Main PID: 1319 (NetworkManager) Tasks: 4 (limit: 4915) CGroup: /system.slice/NetworkManager.service ├─1319 /usr/sbin/NetworkManager --no-daemon └─1704 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-enp5s0.pid -lf /var/lib/NetworkManager/dhclient-5aa08187-8d97-4502-836f-6f26683d034e-enp5s0.lease -cf /var/lib/N> Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6756] Executing: /usr/sbin/iptables --table nat --insert POSTROUTING --source 10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255> Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6767] dnsmasq-manager: starting dnsmasq... Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6778] device (wlp2s0f0u10): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6788] device (wlp2s0f0u10): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6790] device (wlp2s0f0u10): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 05 20:13:51 michael NetworkManager[1319]: dnsmasq: cannot open or create lease file /var/lib/NetworkManager/dnsmasq-wlp2s0f0u10.leases: Permission denied Nov 05 20:13:51 michael dnsmasq[692]: cannot open or create lease file /var/lib/NetworkManager/dnsmasq-wlp2s0f0u10.leases: Permission denied Nov 05 20:13:51 michael dnsmasq[692]: FAILED to start up Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6902] device (wlp2s0f0u10): Activation: successful, device activated. Nov 05 20:13:51 michael NetworkManager[1319]: [1541441631.6907] dnsmasq-manager: dnsmasq exited with error: Filesystem problem (missing file/directory, permissions) (3) -- Kemal If you only at least one time today, you have made God smile, then the day is a gain for you. Otherwise keep on smiling, tomorrow is another day, another chance!!! Pax et Bonum ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [RFC] Automatically remove stored SIM-PIN from gsm connection settings if it fails to unlock?
On Mon, 2018-10-08 at 11:45 +0200, Thomas Haller via networkmanager- list wrote: > On Mon, 2018-10-08 at 09:24 +0200, Aleksander Morgado wrote: > > 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 forgot about this setup and after just a couple > > of > > system reboots got the SIM-PIN blocked, and had to recover it with > > the > > PUK. > > > > Don't know if this kind of thing is done in other kinds of > > settings, > > but could we completely remove the SIM-PIN stored within the > > settings > > if it fails once, so that not even on the next reboot the unlock > > with > > the wrong PIN is attempted? Or is this considered a user error? I'm > > not exactly sure where to draw the line about this issue, I think I > > have pros and cons for both solutions, so just opening the question > > here. > > > > What do you think? > > > > (*) It also doesn't re-ask the user for the PIN right away, still > > need > > to get trace logs as thaller suggested. > > Hi, > > That sounds good to me. > > it's slightly ugly, that activating a profile may result in writing > it > anew to disk. But we already do that when (for example with Wi-Fi), > when the password is wrong and we get a better password from the > secret > agent. While a bit odd that activating a profile may re-write it, it > probably makes sense. +1 Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
