Re: bad gsm connections

2017-04-07 18:38 GMT+03:00 Dan Williams <d...@redhat.com>: > On Thu, 2017-03-30 at 19:32 +0300, matti kaasinen wrote: > > I tried to analyze log files from one card having problematic > > connection. > > First my set-up briefly: > > 1) Embedded Linux card behind H

Re: bad gsm connections

. Also feel free suggesting your choice of kernel driver I should reload to get this locked state released without booting. Thanks, Matti 2017-03-08 20:22 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > > 2017-03-07 20:11 GMT+02:00 Dan Williams <d...@redhat.com>: > >

Re: bad gsm connections

2017-03-07 20:11 GMT+02:00 Dan Williams : > > > That's the modem firmware crashing and restarting. It then > > > reappears > > > to the kernel and gets re-enumerated, and usb_modeswitch does its > > > thing > > > and then eventually it comes back as a modem. Which could be due

Re: bad gsm connections

2017-03-07 18:22 GMT+02:00 Dan Williams <d...@redhat.com>: > On Tue, 2017-03-07 at 16:28 +0200, matti kaasinen wrote: > > Hi! > > > > I would appreciate advices how to cope bad gsm connections with NM. I > > do > > have auto set-up for gsm configuratio

bad gsm connections

Hi! I would appreciate advices how to cope bad gsm connections with NM. I do have auto set-up for gsm configuration. Modem gets huawei_cdc_ncm and NM brings up WWAN0 interface. What I can see from systemd journal is that NM tries to keep connection by unplugging and plugging kernel driver (or

Re: networkmanager possibly misses udev add events occasionally

2017-01-10 18:02 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > >> Could you enable debug-logging of NetworkManager and provide full logs? >> > Ok, I'll try doing that tomorrow > >> I enabled debugging (NetworkManager -d statement in systemd unit file) No

Re: networkmanager possibly misses udev add events occasionally

2017-01-10 16:39 GMT+02:00 Thomas Haller : > > Only following two lines related to eth0/ethernet are present in > > journal when problem hits: > > Jan 10 15:04:31 cpr3 kernel[437]: [1.061954] cpsw > > 4a10.ethernet: Detected MACID = 50:72:24:bf:89:f0 > > Jan 10

networkmanager possibly misses udev add events occasionally

Hi! I have faced with a problem that eth0 is not initialized always at boot. I have traced the problem and now it seems that networkmanager (possibly??) ignores/does not notice udev add events. Ifconfig reports then only lo interface that is coming from /etc/network/interfaces. Only following two

Re: problems with updating ipv4 settings over dbus

bus/> /update-ip4-method.py <http://code.metager.de/source/xref/freedesktop/NetworkManager/NetworkManager/examples/python/dbus/update-ip4-method.py> statements manually. Now I made it sure that 'addresses' property was deleted. This time I did not get error message and setting were stored properly.

Re: problems with updating ipv4 settings over dbus

2016-12-19 22:40 GMT+02:00 Thomas Haller : > "address-data" was introduced by > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id= > d16905df633ceea08c93b6e982f660627d06ff34 > and is in 1.0.0 release (or newer). > > I certainly would expect that what you

Re: problems with updating ipv4 settings over dbus

I had forgot sending previous message. Sorry about confusion. 2016-12-19 19:15 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > I executed manually update-ip4-method lines from python shell. > Executing update returned: >

Re: problems with updating ipv4 settings over dbus

-settings.html/ipv4 settings section/addresses property description claims: "Deprecated in favor of the 'address-data' and 'gateway' properties, but this can be used for backward-compatibility with older daemons." What should I now (try to) use with nm 1.0.10? 2016-12-19 12:29 GMT+02:00 matt

Re: problems with updating ipv4 settings over dbus

". Thanks, Matti 2016-12-19 16:54 GMT+02:00 Beniamino Galvani <bgalv...@redhat.com>: > On Mon, Dec 19, 2016 at 11:15:59AM +0200, matti kaasinen wrote: > > Hi! > > > > 'ipv4' dictionary before update printed below: > > {u'address-data': dbus.Array([dbus.Dicti

Re: problems with updating ipv4 settings over dbus

NM version = 1.0.10 2016-12-19 11:15 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > Hi! > > It seems that I can't set dbus types properly. I try to follow example > setting static ipv4 addres: > freedesktop <http://code.metager.de/source/xref/freedesktop/>

problems with updating ipv4 settings over dbus

Hi! It seems that I can't set dbus types properly. I try to follow example setting static ipv4 addres: freedesktop /NetworkManager / NetworkManager

Re: Problems getting device state change events through

le" state. > >> You might try setting the "never-default" option in the VPN >> connection's config to "true", to indicate that the VPN shouldn't grab >> the default route >> > > Do you expect problems with VPN when default route is set

Re: How to avoid using policy kit with openvpn

Matti 2016-12-15 19:36 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > > 2016-12-15 18:41 GMT+02:00 Dan Williams <d...@redhat.com>: > >> > *route add default dev eth0 metric 99* >> > So, everything is fine! >> >> That implies that the d

Re: How to avoid using policy kit with openvpn

2016-12-15 18:41 GMT+02:00 Dan Williams : > > *route add default dev eth0 metric 99* > > So, everything is fine! > > That implies that the default route was not set up correctly > beforehand. What's the output of "ip route" before you add that > default route? > Yes, there was

Re: How to avoid using policy kit with openvpn

Ping started to work after executing command: *route add default dev eth0 metric 99* So, everything is fine! Cheers, Matti 2016-12-13 11:37 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > Lubomir, Dan, > I found what triggers this issue. I don't know what the reaso

Re: Problems getting device state change events through

Hi Dan, Story below is kind of follow up of my late query referenced: https://mail.gnome.org/archives/networkmanager-list/2016-April/msg00055.html 2016-12-14 16:36 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > I used to have NM 0.9.8.10 together with dhclient. Now I upgra

Problems getting device state change events through

Hi! I used to have NM 0.9.8.10 together with dhclient. Now I upgraded to NM 1.0.10 together with internal dhcp client. Old system had very cumbersome network up sequence in order to preserve dhcp provided IP. Both set-ups have also avahi/avahi-auto-ip running for providing IPv4LL addresses trying

Re: How to avoid using policy kit with openvpn

how easily one can corrupt whole Linux system - just load files to /etc whose user is not a proper user of the installation! They can be loaded to other place, change owner there and load then tho /etc. Anyhow this is none of your worry, I suppose. Cheers, Matti 2016-12-09 16:35 GMT+02:00 matti

Re: How to avoid using policy kit with openvpn

Lubo, It took some time before I had change to get to this issue again. I got new board and it did not start at all, so I had to study u-boot in between.. Anyhow, answers to your comments: 2016-11-25 18:15 GMT+02:00 Lubomir Rintel : > That sounds very strange. > > Please enable

Re: How to avoid using policy kit with openvpn

2016-11-24 16:03 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > To be more exact: service that dos not start anymore after I enable and > later disable it is avahi-daemon.service. It is told in that unit file that: > Alias=dbus-org.freedesktop.Avahi.service. > In fact,

Re: How to avoid using policy kit with openvpn

2016-11-23 19:31 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > BTW, I got a feeling that I got more services failed after I enabled > openvpn.service (like avahi). Also these problems did not disappear when I > disabled openvpn.service and booted card. Same goes with modem

Re: How to avoid using policy kit with openvpn

2016-11-23 19:31 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > 2016-11-23 18:13 GMT+02:00 Dan Williams <d...@redhat.com>: > >> If these are single-user systems, you can rebuild NM with PolicyKit >> disabled so that it never validates requests against Polic

Re: How to avoid using policy kit with openvpn

2016-11-23 18:13 GMT+02:00 Dan Williams : > If these are single-user systems, you can rebuild NM with PolicyKit > disabled so that it never validates requests against PolicyKit. > I'll try rebuilding tomorrow. I suppose (hope) there is clear switch for disabling it. > > Could

Re: How to avoid using policy kit with openvpn

Version information: OpenVPN: 2.3.8 NetworkManager: 1.0.10 ModemManager 1.4.12 Dbus-daemon:1.10.6 2016-11-23 16:37 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > Hi! > > I do have kind of manager of NetworkManager who amongst of other things > tries to connect m

How to avoid using policy kit with openvpn

Hi! I do have kind of manager of NetworkManager who amongst of other things tries to connect modem automatically because my devices are embedded cards located somewhere in nowhere. These cards communicate to server through OpenVpn tunnel. This modem connection process worked quite well untill I

Re: nmcli c does not list modem device - part 2

is related to udev installation that seems to be different. Thanks a lot of your help -Matti 2016-11-14 19:51 GMT+02:00 Dan Williams <d...@redhat.com>: > On Mon, 2016-11-14 at 16:28 +0200, matti kaasinen wrote: > > 2016-11-11 19:41 GMT+02:00 Dan Williams &

Re: nmcli c does not list modem device - part 2

2016-11-11 19:41 GMT+02:00 Dan Williams : > This should be handled by usb_modeswitch. Either it's not getting run > correctly from udev, or there's a bug in usb_modeswitch for your > device. The fact that you can run it manually probably means something > udev related, probably

Re: nmcli c does not list modem device - part 2

' | registration: 'unknown' - SIM | path: '/org/freedesktop/ModemManager1/SIM/0' - Bearers | paths: 'none' 2016-11-11 15:22 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > Hi (again)! > &

nmcli c does not list modem device - part 2

Hi (again)! I discussed this problem originally in https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00079.html I had to upgrade my set-up that is currently as follows: I am using Huawei 3131 modem whose ID should switch from 14fe to 1506 Platform is yocto based am335x board

Re: NM changes DHCP address too easily

LL addresses so that I need not bothering you again when TI gets their meta-ti 2.1 layer mature enough so that I get more recent NM available. Thanks, Matti 2016-06-08 12:35 GMT+03:00 Thomas Haller <thal...@redhat.com>: > On Wed, 2016-06-08 at 12:14 +0300, matti kaasinen wrote: > &g

Re: NM changes DHCP address too easily

ould figure out some policy to maitain IPc4LL address when dhcp client gets lease. Thanks, Matti 2016-05-17 10:15 GMT+03:00 matti kaasinen <matti.kaasi...@gmail.com>: > Hi! > Some more information - lease log from board after re-installation and > dhcp server log: > ==

Re: NM changes DHCP address too easily

anges addres for lack of addresses. There > are only couple of workstations (below 10) using dhcp addressing and > basically their address never changes. > > 2016-04-25 16:58 GMT+03:00 José Queiroz <zekk...@gmail.com>: > >> >> >> 2016-04-25 2:24 GMT-03:00 matti k

Re: NM changes DHCP address too easily

and basically their address never changes. 2016-04-25 16:58 GMT+03:00 José Queiroz <zekk...@gmail.com>: > > > 2016-04-25 2:24 GMT-03:00 matti kaasinen <matti.kaasi...@gmail.com>: > >> dhcpd3 >> >> > Sorry. I didn't make myself clear. > > Which device is you

Re: NM changes DHCP address too easily

dhcpd3 2016-04-22 18:05 GMT+03:00 José Queiroz <zekk...@gmail.com>: > > > 2016-04-22 11:59 GMT-03:00 matti kaasinen <matti.kaasi...@gmail.com>: > >> >> 2016-04-22 17:07 GMT+03:00 José Queiroz <zekk...@gmail.com>: >> >>> Shoul

Re: NM changes DHCP address too easily

2016-04-22 16:12 GMT+03:00 Beniamino Galvani : > Do you mean that the board is getting a different address at every > boot? In order to reuse the same lease, a persistent connection must > be used (i.e. a connection written on disk and not the in-memory one > automatically

Re: NM changes DHCP address too easily

2016-04-22 15:55 GMT+03:00 Thomas Haller : > Which plugin are you using? Does it change when setting "dhcp=internal" > or "dhcp=dhclient"? > Unfortunately I'm still tied to NM v.0.9.8.10 for couple of months. So I don't have chcp=internal option. I have been using dhclient.

Re: howto keep always ipv4ll address

20:33 GMT+03:00 matti kaasinen <matti.kaasi...@gmail.com>: > > 2016-04-15 19:22 GMT+03:00 Thomas Haller <thal...@redhat.com>: > >> Also, "eth0:avahi" sounds more like an interface-alias. That is not a >> separate (real) interface, just one address tha

Re: howto keep always ipv4ll address

2016-04-15 19:22 GMT+03:00 Thomas Haller : > Also, "eth0:avahi" sounds more like an interface-alias. That is not a > separate (real) interface, just one address that is show by ifconfig > tool as a separate interface (but it isn't). See `ip addr show`. > Interface alias is

Re: howto keep always ipv4ll address

2016-04-15 19:28 GMT+03:00 Dan Williams : > To clarify, not possible on NM 0.9.8. NM 0.9.10 and later make large > efforts to preserve configuration made outside NM. > > Unfortunately I have to cope with this version for a while. Arago project just started to work on Yocto

howto keep always ipv4ll address

Hi! Is there way to tell NM (v.0.9.8.10) not to drop ipv4ll address = eth0:avahi interface. It seems that this dropping happens immediately when dhcp lease is gained. What harm it would do just preserving this interface alias? Thanks, Matti ___

ip configuration over dbus

Hi! I try to configure IP settings over dbus. It seems that this is not possible over org.freedesktop.NetworkManager.IP4Config. I noticed that IP4 configuration functions are found from libnm-util/nm-setting-ip4-config.c. >From there it seems that these are private settings. I did not find

Re: ip configuration over dbus

:48 GMT+02:00 Dan Williams <d...@redhat.com>: > On Thu, 2016-03-17 at 17:02 +0200, matti kaasinen wrote: > > Hi! > > > > I try to configure IP settings over dbus. It seems that this is not > > possible over org.freedesktop.NetworkManager.IP4Config. I noticed > &g

Re: nmcli c does not list modem device

h and does not touch to configuration at all. Anyhow, now I re-built the image and it seems now working. Thank you for your help. Best regards, Matti 2016-03-14 22:11 GMT+02:00 Aleksander Morgado <aleksan...@aleksander.es>: > On Mon, Mar 14, 2016 at 2:55 PM, matti kaasinen > <matti.kaa

Re: nmcli c does not list modem device

Yes, mmcli seems workin quite nicely - no problems at all. 2016-03-14 16:27 GMT+02:00 Dan Williams <d...@redhat.com>: > On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote: > > In fact there are two more messages preceding those ones I mentioned > > before, but I gu

Re: nmcli c does not list modem device

/nm-modem-manager.c:280] poke_modem_cb(): Requesting to (re)launch modem-manager... -Matti 2016-03-14 15:39 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > There was also other one besides these (re)launch messages. The first > message was: > modem_manager_disappeared():

Re: nmcli c does not list modem device

There was also other one besides these (re)launch messages. The first message was: modem_manager_disappeared(): trying to start the modem manager... then repeating gradually: Requesting to (re)launch modem-manager... 2016-03-14 15:35 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>

Re: nmcli c does not list modem device

.es>: > On Mon, Mar 14, 2016 at 1:57 PM, matti kaasinen > <matti.kaasi...@gmail.com> wrote: > > 2016-03-14 14:53 GMT+02:00 Thomas Haller <thal...@redhat.com>: > >> > >> > I can't get modem device listed with > >> > nmcli c > >> > >&

Re: nmcli c does not list modem device

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 traffic (dbus-monitor --system) and it seems that all the information received by mmcli is seen

nmcli c does not list modem device

Hi! I can't get modem device listed with nmcli c command. So, NM does not see it and therefore it can't start connection with NM. Last week it worked fine. I wrote python code for bringing gathering up data from from modem interfrace for NM. Then NM could identify this modem and I got

Re: nm-pppd-plugin does not start

2016-03-04 13:50 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > 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

2016-03-04 12:18 GMT+02:00 matti kaasinen <matti.kaasi...@gmail.com>: > No problem at all, this was just told in the MM recipe commenting systemd > confuguration variable that was set to inhibit starting service at boot > (below). > # no need to start on boot - dbus wi

Re: nm-pppd-plugin does not start

Aleksander, thank your very much for your fine answers. Please find my replies/comments below. 2016-03-04 1:28 GMT+02:00 Aleksander Morgado : > > Did connman/ofono run a DHCP client on the interface? > No, I tried to run it manually with following procedure: ifconfig

nm-pppd-plugin does not start

Hi, For the firstly, sorry about long story.. 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