> On 08 November 2017 at 16:54 Thomas Haller wrote:
>
> On Wed, 2017-11-08 at 13:40 +0100, Iñigo Martínez wrote:
>
> > Hi all,
> >
> > These past few months I have been porting some libraries and
> > applications to meson build system[0], within the "MesonPorting"
> > initiative[1] that tries
> On 11 October 2017 at 14:56 Thomas Haller wrote:
>
> On Wed, 2017-10-11 at 13:49 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I've noticed that my system has a delay during boot-up, of about
> > 20secs. It
> > *looks* like NM is waiting for urandom - there's no " NetworkManager
> > (v
> On 07 September 2017 at 17:13 Colin Helliwell
> wrote:
>
> > On 07 September 2017 at 16:37 Dan Williams wrote:
> >
..
> > client = NM.Client.new(None)
> > c =
> > client.get_connection_by_uuid(sys.argv[1])
> > secrets =
> > c.ge
> On 07 September 2017 at 16:37 Dan Williams wrote:
>
> On Thu, 2017-09-07 at 09:31 +0100, Colin Helliwell wrote:
>
..
> > Thanks Dan, that gets it.
> > Now I'm struggling to *modify* the password :S I see that I can
> > do a
> > settings.set
> On 07 September 2017 at 16:37 Dan Williams wrote:
>
> On Thu, 2017-09-07 at 09:31 +0100, Colin Helliwell wrote:
>
> > > On 06 September 2017 at 17:18 Dan Williams wrote:
> > >
> > > On Wed, 2017-09-06 at 12:51 +0100, Colin Helliwell wrote:
> &g
> On 06 September 2017 at 17:18 Dan Williams wrote:
>
> On Wed, 2017-09-06 at 12:51 +0100, Colin Helliwell wrote:
>
> > > On 06 September 2017 at 11:14 Thomas Haller
> > > wrote:
> > >
> > > On Wed, 2017-09-06 at 10:20 +0100, colin.helliw..
> On 06 September 2017 at 11:14 Thomas Haller wrote:
>
> On Wed, 2017-09-06 at 10:20 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I'm python-scripting to get a connection's gsm properties, and want
> > to get
> > the password - which "c.for_each_setting_value(print_values, None)"
> > se
> On 30 August 2017 at 17:51 Thomas Haller wrote:
>
> On Wed, 2017-08-30 at 17:17 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I've not used nmcli in any of its more intricate ways, but are there
> > some
> > easily-parsed commands which will allow me to tell whether an
> > Ethernet
> >
> On 28 July 2017 at 09:47 Beniamino Galvani wrote:
>
> On Fri, Jul 28, 2017 at 08:34:49AM +0100, Colin Helliwell wrote:
>
> > Still asserting with this morning's Head.
> > gdb reports:
> > [...]
>
> Hi,
>
> I pushed a fix, can you please update
Still asserting with this morning's Head.
gdb reports:
[1501227099.2422] devices added (path: /sys/devices/virtual/net/ppp0,
iface: ppp0)
[1501227099.2427] device added (path: /sys/devices/virtual/net/ppp0,
iface: ppp0): no ifupdown configuration found.
[Thread 0x759ff3e0 (LWP 1275) exited]
> -- Original Message --
> From: Beniamino Galvani
> To: colin.helliw...@ln-systems.com
> Cc: networkmanager-list@gnome.org
> Date: 27 July 2017 at 17:06
> Subject: Re: IPv4 problem with latest head version
>
> On Thu, Jul 27, 2017 at 02:04:44PM +0100, colin.helliw...@ln-systems.
> On 10 July 2017 at 21:21 Alex Ferm wrote:
>
> Hello all,
>
> I manage a bunch of cellular connected embedded devices running
> NetworkManager+ModemManager. I use the same software image on all
> devices regardless of which cell network they run on.
>
> My current solution to selecting the ap
> On 10 July 2017 at 21:12 Thomas Haller wrote:
>
> On Mon, 2017-07-10 at 16:28 +0100, Colin Helliwell wrote:
>
...
> >
> > The commit that breaks it for me [no IPv6 support in my kernel] is ht
> > tps://cgit.freedesktop.org/NetworkManag
> On 10 July 2017 at 15:36 Thomas Haller wrote:
>
> On Mon, 2017-07-10 at 15:03 +0100, Colin Helliwell wrote:
>
> > > On 10 July 2017 at 14:34 Colin Helliwell > > s.com> wrote:
> > >
> > > > On 10 July 2017 at 14:26 Thomas Haller
>
> On 10 July 2017 at 14:34 Colin Helliwell
> wrote:
>
> > On 10 July 2017 at 14:26 Thomas Haller wrote:
> >
..
> > And which exact commit are you testing?
>
> Very latest Head, just an hour or so ago. I'll see if I can get Yocto to pull
> some of t
> On 10 July 2017 at 14:26 Thomas Haller wrote:
>
...
>
> hi,
>
> please provide a stack-trace
>
> like:
>
> $ gdb /sbin/NetworkManager
>
> > run --debug
> > ...
> > bt
>
> (make sure, you have debugging symbols available)
>
Hmmm.. gdb not something I currently have on my [embed
I've been working for the past week or so with a version built around 4th July.
I've just updated to the latest, and seem to be getting a seg fault somewhere.
(/usr/libexec/nm-dispatcher is running afterwards)
I fairly sure nothing else in the system is different.
Compared with below, the log of
> On 07 July 2017 at 01:10 Greg Oliver wrote:
>
.
> I would really have completely different routing tables for this rather than
> changing metrics. Source routing /netfilter is your friend here, but source
> routing also comes with security risks, so you need to make sure netfilter is
>
> On 03 July 2017 at 15:50 Colin Helliwell
> wrote:
>
> > On 03 July 2017 at 15:39 Thomas Haller wrote:
> >
> > ah, it's "modify", not "set".
> >
> > nmcli device modify enp0s25 ipv4.route-metric 42
>
> O
> On 03 July 2017 at 19:18 Greg Oliver wrote:
>
> On Mon, Jul 3, 2017 at 4:50 AM, Colin Helliwell
> wrote:
>
> > > On 03 July 2017 at 15:39 Thomas Haller wrote:
> > >
> > > On Mon, 2017-07-03 at 14:32 +0100, Colin Helliwell wrote:
> > >
&
> On 03 July 2017 at 15:39 Thomas Haller wrote:
>
> On Mon, 2017-07-03 at 14:32 +0100, Colin Helliwell wrote:
>
> Hi,
>
> > > An alternative, a bit more graceful is
> > >
> > > nmcli connection modify "$CON" ipv4.route-metric 42
> &g
> On 03 July 2017 at 14:32 Colin Helliwell
> wrote:
>
> Thanks for the tips, Thomas [but see below]
>
...
> > An alternative, a bit more graceful is
> >
> > nmcli connection modify "$CON" ipv4.route-metric 42
> > nmcli device reapply "
Thanks for the tips, Thomas [but see below]
> On 30 June 2017 at 20:55 Thomas Haller wrote:
>
> On Thu, 2017-06-29 at 13:14 +0100, Colin Helliwell wrote:
>
> > Is there a way to get NM to alter fully on-the-fly which connection
> > is preferred/default for traffic?
>
Is there a way to get NM to alter fully on-the-fly which connection is
preferred/default for traffic?
I see that I can modify the route-metric parameter: if the connection is taken
down and up again then I see the change in the output of 'route', and indeed
this seems to change which connection
> On 28 June 2017 at 17:24 Thomas Haller wrote:
>
> Hi,
>
> On Wed, 2017-06-28 at 16:15 +0100, Colin Helliwell wrote:
>
> > The system has eth0 and a gsm connection (via ModemManager).
> > I have in /etc/network/interfaces:
> > auto lo
> > iface
Sorry this is long
I'm back getting to grips with NM, after time out on other aspects. I'm using
the git master (1.9.1), on a SysV system, no graphical desktop, no netconfig or
resolvconf.
Looks like quite a few updates since I was last engrossed in it, so it may be
that my configs and - mor
I've been trying out some failure scenarios with Eth vs. GSM modem (under
ModemManager) - e.g. Eth link getting disconnected/reconnected.
eth0 was present in my /etc/network/interfaces:
auto eth0
iface eth0 inet dhcp
therefore I used the "managed=true" setting in NetworkManager.conf, with
> On 10 May 2017 at 16:04 Dan Williams wrote:
>
>
> Yes, the pptp package, typically obtained from your distro or from:
>
> http://pptpclient.sourceforge.net/
>
> Dan
Sorry to be a pain, but are you able to quickly tell me what binary it's
actually looking for? I think I've installed the pp
> On 10 May 2017 at 16:04 Dan Williams wrote:
>
> On Wed, 2017-05-10 at 15:18 +0100, Colin Helliwell wrote:
>
> >
> > So an additional package (the "pptp client binary") needed...?
>
> Yes, the pptp package, typically obtained from your distro or from
> On 10 May 2017 at 15:12 Thomas Haller wrote:
>
> On Wed, 2017-05-10 at 14:57 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I'd like to get NM VPN connections going on my platform.
> > We have a VPN for dial-in from home, so I'll just test out with that
> > to
> > begin with. We use a D
> On 02 May 2017 at 16:23 Colin Helliwell
> wrote:
>
> > On 02 May 2017 at 16:07 Dan Williams wrote:
> >
> > On Tue, 2017-05-02 at 15:54 +0100, colin.helliw...@ln-systems.com
> > wrote:
> >
> > > I'm hoping to use NetworkManager on a s
> On 02 May 2017 at 16:07 Dan Williams wrote:
>
> On Tue, 2017-05-02 at 15:54 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I'm hoping to use NetworkManager on a system which doesn't have
> > systemd . So
> > far I'm hitting a few dependency problems but, before I start trying
> > to wade
Does this look like one which should be punted over to MM mailing list?
> On 20 April 2017 at 09:23 Colin Helliwell
> wrote:
>
> > On 19 April 2017 at 19:06 Dan Williams wrote:
> >
> > On Wed, 2017-04-19 at 14:47 +0100, Colin Helliwell wrote:
> >
> &
> On 20 April 2017 at 17:28 Dan Williams wrote:
>
> On Mon, 2017-04-10 at 14:40 +0100, Colin Helliwell wrote:
>
> > A couple of things I've noticed in integrating NM with ModemManager:
> >
> > 1. It seems that eth0 doesn't come up - i.e. dhcp client no
> On 19 April 2017 at 19:06 Dan Williams wrote:
>
> On Wed, 2017-04-19 at 14:47 +0100, Colin Helliwell wrote:
>
> > > On 19 April 2017 at 14:01 Colin Helliwell > > ms.com> wrote:
> > >
> > > > On 18 April 2017 at 14:36 Colin Helliwell &g
> On 19 April 2017 at 14:01 Colin Helliwell
> wrote:
>
> > On 18 April 2017 at 14:36 Colin Helliwell
> > wrote:
> >
> > > On 17 April 2017 at 18:32 Dan Williams wrote:
> > >
> > > On Sat, 2017-04-15 at 13:11 +0100, Colin Helliwell w
> On 18 April 2017 at 14:36 Colin Helliwell
> wrote:
>
> > On 17 April 2017 at 18:32 Dan Williams wrote:
> >
> > On Sat, 2017-04-15 at 13:11 +0100, Colin Helliwell wrote:
> >
> > > I have NM setup with ModemManager and GSM modem, and can bring up
> On 17 April 2017 at 18:32 Dan Williams wrote:
>
> On Sat, 2017-04-15 at 13:11 +0100, Colin Helliwell wrote:
>
> > I have NM setup with ModemManager and GSM modem, and can bring up the
> > connection. But when I enable a SIM PIN lock, the first 'nmcli conn
> &g
I have NM setup with ModemManager and GSM modem, and can bring up the
connection. But when I enable a SIM PIN lock, the first 'nmcli conn up' from
reboot fails.
I can see that the modem is being unlocked ok, and is indeed registered
afterwards. And a retry of the 'conn up' also works.
I wonder i
Are there mechanisms/settings in NM to trigger a 'fail-over' i.e. bring up a
backup connection if connectivity is lost on another?
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-l
A couple of things I've noticed in integrating NM with ModemManager:
1. It seems that eth0 doesn't come up - i.e. dhcp client not fired off - until
MM has done it's startup operations on the GSM modem. It so happens that my GSM
has a long power-on pause, and that is holding up the system's eth ne
> On 07 April 2017 at 17:35 Dan Williams wrote:
>
> On Fri, 2017-04-07 at 17:17 +0100, Colin Helliwell wrote:
>
> > > On 07 April 2017 at 17:15 Colin Helliwell > > ms.com> wrote:
> > >
> > > > On 07 April 2017 at 17:06 Dan Williams wrote:
> On 07 April 2017 at 17:15 Colin Helliwell
> wrote:
>
> > On 07 April 2017 at 17:06 Dan Williams wrote:
> >
> > On Fri, 2017-04-07 at 16:12 +0100, Colin Helliwell wrote:
> >
> > > I've got NM installed n running on my embedded system. I can
> On 07 April 2017 at 17:06 Dan Williams wrote:
>
> On Fri, 2017-04-07 at 16:12 +0100, Colin Helliwell wrote:
>
> > I've got NM installed n running on my embedded system. I can 'nmcli
> > conn up modem' and the ppp link on my GSM modem comes up nicel
I've got NM installed n running on my embedded system. I can 'nmcli conn up
modem' and the ppp link on my GSM modem comes up nicely - ifconfig reports inet
and P-t-P addresses, and I seem able to ping/traceroute through it to the
interweb, but I may have some clutter.
Being embedded and headles
> On 07 April 2017 at 11:41 Thomas Haller wrote:
>
> On Fri, 2017-04-07 at 11:23 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I'm building from the latest git master, and hitting a compile error
> > on
> > 'nm-core-enum-types.h' not existing
>
> Hi,
>
> This should be fixed by
> https
> On 05 April 2017 at 16:08 Thomas Haller wrote:
>
> On Mon, 2017-04-03 at 11:25 +0100, Colin Helliwell wrote:
>
> > > On 03 April 2017 at 10:55 Thomas Haller wrote:
>
> PS:
>
> on master branch I did
>
> https://cgit.freedesktop.org/N
> On 03 April 2017 at 10:55 Thomas Haller wrote:
>
> On Mon, 2017-04-03 at 10:00 +0100, Colin Helliwell wrote:
>
> > > On 30 March 2017 at 18:14 Colin Helliwell > > ms.com> wrote:
> > >
> > > > On 30 March 2017 at 17:34 Thomas Haller
>
> On 30 March 2017 at 18:14 Colin Helliwell
> wrote:
>
> > On 30 March 2017 at 17:34 Thomas Haller wrote:
> >
> > Hi,
> >
> > Not surprisingly, when cross compiling, you also need python and
> > pygobject in the other architecture.
> >
> On 30 March 2017 at 17:34 Thomas Haller wrote:
>
> Hi,
>
> Not surprisingly, when cross compiling, you also need python and
> pygobject in the other architecture.
>
> That makes it rather cumbersome.
>
> As I wrote in the other email, you can pre-generate those files on
> another host, duri
> On 30 March 2017 at 16:09 Thomas Haller wrote:
>
> On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I was able to build NM 1.4.2 with G-I enabled, and have now moved up
> > to
> > 1.8/master.
> > But hitting a build failure (cross-compiling, in Yocto):
> >
...
> On 30 March 2017 at 16:09 Thomas Haller wrote:
>
> On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I was able to build NM 1.4.2 with G-I enabled, and have now moved up
> > to
> > 1.8/master.
> > But hitting a build failure (cross-compiling, in Yocto):
> >
...
> On 29 March 2017 at 19:58 Dan Williams wrote:
>
> On Wed, 2017-03-29 at 16:52 +0100, Colin Helliwell wrote:
>
> > > On 29 March 2017 at 15:13 Dan Williams wrote:
> > >
> > > On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
> > &
> On 29 March 2017 at 15:13 Dan Williams wrote:
>
> On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
>
> > > > On 27 March 2017 at 14:25 Colin Helliwell > > > tems.com> wrote:
> >
> > ...
> >
> > > > ... but still ha
> > On 27 March 2017 at 14:25 Colin Helliwell
> > wrote:
> >
...
> > ... but still have subsequent errors which seem to have been due to output
> > directories not having been created e.g. libnm-core, introspection.
> > I can get it to limp a little furthe
> On 27 March 2017 at 17:04 Dan Williams wrote:
>
...
>
> The build process takes Introspection data from the NM objects
> (NMDevice, NMConnection, etc) and generates files that nmcli uses to
> provide help text, properties, etc, rather than hardcoding things
> twice. So unfortunately, if you w
> On 27 March 2017 at 17:04 Dan Williams wrote:
>
...
>
> The build process takes Introspection data from the NM objects
> (NMDevice, NMConnection, etc) and generates files that nmcli uses to
> provide help text, properties, etc, rather than hardcoding things
> twice. So unfortunately, if you w
> On 27 March 2017 at 17:02 Dan Williams wrote:
>
> On Sat, 2017-03-25 at 13:29 +0000, Colin Helliwell wrote:
>
> > > On 25 March 2017 at 06:31 Dan Williams wrote:
> > >
> > > On Fri, 2017-03-24 at 13:53 +, Colin Helliwell wrote:
> > >
> On 27 March 2017 at 14:25 Colin Helliwell
> wrote:
>
> I think it was missing [under yocto/bitbake] the autogen.sh step.
> I've corrected that (as a 'pre-configure' step), but still have subsequent
> errors which seem to have been due to output directori
I think it was missing [under yocto/bitbake] the autogen.sh step.
I've corrected that (as a 'pre-configure' step), but still have subsequent
errors which seem to have been due to output directories not having been
created e.g. libnm-core, introspection.
I can get it to limp a little further by cr
> On 25 March 2017 at 06:31 Dan Williams wrote:
>
> On Fri, 2017-03-24 at 13:53 +0000, Colin Helliwell wrote:
>
> > > On 23 March 2017 at 19:43 Dan Williams wrote:
> > >
> > > On Thu, 2017-03-23 at 18:26 +, colin.helliw...@ln-systems.com
> >
> On 23 March 2017 at 19:43 Dan Williams wrote:
>
> On Thu, 2017-03-23 at 18:26 +, colin.helliw...@ln-systems.com
> wrote:
>
> > NetworkManager[1398]: [1490292215.0368] (ttyMux1): modem
> > state
> > changed, 'connected' --> 'registered' (reason: user-requested)
> > NetworkManager[1398]: [
> On 24 March 2017 at 11:19 Thomas Haller wrote:
>
...
> [[OFF-TOPIC]]
>
> btw, instead of setting the environment variable, you can also enable
> logging of pppd via
> sudo nmcli general logging level KEEP domains PPP:DEBUG
> or with /etc/NetworkManager/NetworkManager.conf
> [logging]
> dom
63 matches
Mail list logo