Re: Homenet

Op 21-3-2016 om 13:43 schreef Stuart D. Gathman: On Mon, 21 Mar 2016, Xen wrote: "Addressable" is NOT the same thing as "exposed". Any sane IPv6 There is a fundamental issue with this and that is that this is a rather arbitrary "sanest method of configuration" rather than a topology feature

Re: [PATCH] UPower signaling obsolescence

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: >>> >>> "Newer upower versions no longer emit that signal since this >>> handled by systemd." >>> by Michael Biebl >>> https://lists.freedesktop.org/archives/de

Re: Homenet

Op 21-3-2016 om 11:23 schreef Tim Coote: If Bart’s view is typical, I guess that the answer to my original question is ‘No’. That’s a shame as further separation of the various Linux models (embedded, networking, phone, tablet, desktop, server, cloud), is, imo, unhelpful. But at least it give

Re: Homenet

Op 21-3-2016 om 11:23 schreef Tim Coote: If Bart’s view is typical, I guess that the answer to my original question is ‘No’. That’s a shame as further separation of the various Linux models (embedded, networking, phone, tablet, desktop, server, cloud), is, imo, unhelpful. But at least it give

Re: Homenet

Op 21-3-2016 om 14:05 schreef Thomas Haller: Note that there are also private stable addresses: https://tools.ietf.org/html/rfc7217 https://blogs.gnome.org/lkundrak/2015/12/03/networkmanager-and-privacy-in-the-ipv6-internet/ Thomas Hi thanks. That part seems to actually be a good feature,

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

On Mon, 21 Mar 2016 12:48:35 +0100 Thomas Haller wrote: > On Mon, 2016-03-21 at 01:32 -0500, Robby Workman wrote: > > On Tue, 1 Mar 2016 16:10:21 +0100 > > Beniamino Galvani wrote: > > > > > > > > I'm pleased to announce the release of the second beta version of > > > NetworkManager 1.2 (1.1

Re: Homenet

Hi Thomas > On 21 Mar 2016, at 12:20, Thomas Haller wrote: >> [snip] > > Hi Tim, > > > Until now, I only skimmed over the (large number of) documents. There is a lot. And most assume too much on the part of the reader. There’s very little that puts the context at all, or presents any top down

Re: Homenet

On Mon, 2016-03-21 at 08:43 -0400, Stuart D. Gathman wrote: > On Mon, 21 Mar 2016, Xen wrote: >  > > First of all, a random non-reusable address is clearly a bag of > > nonsense, as > > you indicate. That's no sane method of doing anything. Think of a > > programming stack, queue or list. You want

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

On Mon, 2016-03-21 at 08:01 +0100, Michael Biebl wrote: > Am 21.03.2016 um 07:32 schrieb Robby Workman: > > > > 2. Some manual pages were not installed, e.g. > > NetworkManager.conf(5), > >    although nm-system-settings.conf(5), which directs users to the > >    former, is installed. Looking at t

Re: Homenet

On Mon, 21 Mar 2016, Xen wrote: "Addressable" is NOT the same thing as "exposed".  Any sane IPv6 There is a fundamental issue with this and that is that this is a rather arbitrary "sanest method of configuration" rather than a topology feature. So is NAT. There is no longer a "port to diff

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

On Mon, 2016-03-21 at 08:01 +0100, Michael Biebl wrote: > Am 21.03.2016 um 07:32 schrieb Robby Workman: > > > > 2. Some manual pages were not installed, e.g. > > NetworkManager.conf(5), > >    although nm-system-settings.conf(5), which directs users to the > >    former, is installed. Looking at t

Re: Homenet

On Mon, 2016-03-21 at 10:23 +, Tim Coote wrote: > > > On 20 Mar 2016, at 10:56, Tim Coote > > wrote: > > > > Is it intended that NetworkManager will conform to /support / > > exploit the Homenet network name and address assignment and > > routeing protocols (http://bit.ly/1LyAE7H), either to

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

On Mon, 2016-03-21 at 01:32 -0500, Robby Workman wrote: > On Tue, 1 Mar 2016 16:10:21 +0100 > Beniamino Galvani wrote: > > > > > I'm pleased to announce the release of the second beta version of > > NetworkManager 1.2 (1.1.91), and the same version of nm-applet, > > nm-connection-editor and VPN

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

On Mon, 2016-03-21 at 01:53 -0500, Robby Workman wrote: > On Mon, 21 Mar 2016 01:32:01 -0500 > Robby Workman wrote: > > > > > 1. /var/run/NetworkManager/ is created with mode 0700, which is > >    a problem because non-root clients are unable to read the > >    resolv.conf inside it. On this sys

Re: Homenet

> On 20 Mar 2016, at 10:56, Tim Coote wrote: > > Is it intended that NetworkManager will conform to /support / exploit the > Homenet network name and address assignment and routeing protocols > (http://bit.ly/1LyAE7H ), either to provide end to end > connectivity or to

Re: Homenet

Op 21-3-2016 om 00:29 schreef Stuart Gathman: On 03/20/2016 11:36 AM, Xen wrote: By the way, if UPnP was ever a problem in terms of NAT security, obviously the problem is much worse in IPv6, since there is not even any NAT and all devices are always exposed. "Addressable" is NOT the same thin

Re: ANN: NetworkManager 1.1.91 (1.2-beta2) released

Am 21.03.2016 um 07:32 schrieb Robby Workman: > 2. Some manual pages were not installed, e.g. NetworkManager.conf(5), >although nm-system-settings.conf(5), which directs users to the >former, is installed. Looking at the Makefile.am, it appears that >maybe these are autogenerated during