Re: [systemd-devel] Network Manager and systemd-networkd.service

On Wed, 2014-04-16 at 08:39 +0200, Thomas Bächler wrote: Am 16.04.2014 06:10, schrieb Andy Johnson: Hello, systemd-devel, I saw this in the manpage of systemd-networkd.service (in the systemd git tree) systemd-networkd.service, systemd-networkd — Network manager My question

Re: [systemd-devel] Systemd-networkd, default route and multiple interfaces

On Fri, 2014-06-06 at 10:52 -0400, Leonid Isaev wrote: Hi, On 06/06, Lennart Poettering wrote: Date: Fri, 6 Jun 2014 15:43:21 +0200 From: Lennart Poettering lenn...@poettering.net To: Mantas Mikulėnas graw...@gmail.com Cc: systemd Mailing List systemd-devel@lists.freedesktop.org

Re: [systemd-devel] [PATCH 00/24] Initial DHCPv6 client support

On Fri, 2014-06-13 at 16:44 +0300, Patrik Flykt wrote: Hi, This patch set provides initial DHCPv6 client support for systemd-networkd. It adds support for ICMPv6 Router Solicitation sending and Router Advertisment receiving and the very basic Solicit, Advertise, Request and Reply

Re: [systemd-devel] [PATCH 00/24] Initial DHCPv6 client support

On Fri, 2014-06-13 at 18:38 +0200, Tom Gundersen wrote: On Fri, Jun 13, 2014 at 6:26 PM, Dan Williams d...@redhat.com wrote: On Fri, 2014-06-13 at 16:44 +0300, Patrik Flykt wrote: Hi, This patch set provides initial DHCPv6 client support for systemd-networkd. It adds support

Re: [systemd-devel] [PATCH 02/24] sd-dhcp6-client: Add Router Solicitation and Advertisement support

On Fri, 2014-06-13 at 16:44 +0300, Patrik Flykt wrote: Provide functions to bind the ICMPv6 socket to the approriate interface and set multicast sending and receiving according to RFC 3493, section 5.2. and RFC 3542, sections 3. and 3.3. Filter out all ICMPv6 messages except Router

Re: [systemd-devel] [PATCH 1/2] dhcp-network: add check for DHCP.chaddr

On Thu, 2014-06-19 at 18:59 +0200, Michal Sekletar wrote: Check that received DHCP packets actually include our MAC address in chaddr field. BPF interpreter has 32 bit wide registers but MAC address is 48 bits long so we have to do check in two steps. And if the MAC address is not 48 bits

Re: [systemd-devel] systemd-networkd fails to get DHCPv4 lease with disabled IPv6

On Mon, 2014-07-14 at 11:06 -0700, David Timothy Strauss wrote: On Sun, Jul 6, 2014 at 3:32 PM, Tom Gundersen t...@jklm.no wrote: yes is a synonym for both and no for none. These are odd semantics, given that IPv6 is completely configurable using router advertisements for even DNS

Re: [systemd-devel] systemd-networkd fails to get DHCPv4 lease with disabled IPv6

On Tue, 2014-07-15 at 17:17 +0200, Lennart Poettering wrote: On Mon, 14.07.14 15:38, Dan Williams (d...@redhat.com) wrote: But that brings up another question; I don't think systemd-networkd is currently capable of ensuring a machine is completely configured when RA is enabled, because

[systemd-devel] [PATCH] networkd: set route protocol

-configured static routes now use RTPROT_STATIC (which they are) and DHCP routes use RTPROT_DHCP. There is no define for IPv4LL yet, so those are installed as RTPROT_STATIC (though perhaps RTPROT_RA is better?). Signed-off-by: Dan Williams d...@redhat.com --- src/libsystemd/sd-rtnl/rtnl-message.c

[systemd-devel] [PATCH v2] networkd: set route protocol

-configured static routes now use RTPROT_STATIC (which they are) and DHCP routes use RTPROT_DHCP. There is no define for IPv4LL yet, so those are installed as RTPROT_STATIC (though perhaps RTPROT_RA is better?). Signed-off-by: Dan Williams d...@redhat.com --- v2: rebase missed one case

[systemd-devel] [PATCH] dhcp-network: remove unused DHCP6_STATE_RS

Probably a left-over from when router solicitations were requested in the DHCP6 code. But since they are now separate, this state is no longer needed. Signed-off-by: Dan Williams d...@redhat.com --- src/libsystemd-network/dhcp6-protocol.h | 1 - src/libsystemd-network/sd-dhcp6-client.c | 4

[systemd-devel] [PATCH] sd-dhcp6-client: support custom DUIDs

The caller may have an existing DUID that it wants to use, and may want to use some other DUID generation scheme than systemd's default DUID-EN. --- src/libsystemd-network/sd-dhcp6-client.c | 52 +++--- src/libsystemd-network/test-dhcp6-client.c | 4 +--

[systemd-devel] [RFC PATCH] sd-dhcp-client: support non-Ethernet hardware addresses

Like Infiniband. See RFC 4390 section 2.1 for details on DHCP and Infiniband; chaddr is zeroed, hlen is set to 0, and htype is set to ARPHRD_INFINIBAND because IB hardware addresses are 20 bytes in length. --- NOTE: because of how dhcp_network_bind_raw_socket() does its packet filter, it's not

Re: [systemd-devel] [PATCH] sd-dhcp6-client: support custom DUIDs

On Tue, 2014-08-12 at 01:12 +0200, Tom Gundersen wrote: On Wed, Aug 6, 2014 at 6:17 PM, Dan Williams d...@redhat.com wrote: The caller may have an existing DUID that it wants to use, and may want to use some other DUID generation scheme than systemd's default DUID-EN. I have

Re: [systemd-devel] [RFC PATCH] sd-dhcp-client: support non-Ethernet hardware addresses

On Wed, 2014-08-06 at 11:22 -0500, Dan Williams wrote: Like Infiniband. See RFC 4390 section 2.1 for details on DHCP and Infiniband; chaddr is zeroed, hlen is set to 0, and htype is set to ARPHRD_INFINIBAND because IB hardware addresses are 20 bytes in length. --- NOTE: because of how

Re: [systemd-devel] Networkd dhcp hostname override

On Wed, 2014-08-13 at 18:55 -0700, Marcel Holtmann wrote: Hi Lennart, Now that networkd can send the systems hostname to the dhcp server, I would find it useful to have an option to override the hostname that gets sent. In my use case, I would like to setup a number of macvlans

Re: [systemd-devel] Networkd dhcp hostname override

On Thu, 2014-08-14 at 14:29 -0700, Thomas Suckow wrote: Typically the send-hostname thing is actually used for DNS updates, where you send the hostname to the DHCP server, which then gives you a lease and sends the hostname + IP to the DNS server, so that your machine is accessible via DNS

[systemd-devel] systemd-networkd questions

Hi, Having watched the discussion over the past week or so, I'm left with a few questions: 1) what is lacking in other userspace solutions (NetworkManager, ConnMan, wicked, initscripts, etc) that requires yet-another-network-daemon? 2) do you expect that systemd-networkd will grow to include

Re: [systemd-devel] systemd-networkd questions

On Tue, 2013-11-12 at 23:19 +0100, Tom Gundersen wrote: Hi Dan, On Tue, Nov 12, 2013 at 10:38 PM, Dan Williams d...@redhat.com wrote: 1) what is lacking in other userspace solutions (NetworkManager, ConnMan, wicked, initscripts, etc) that requires yet-another-network-daemon? Without

Re: [systemd-devel] systemd kills mdmon if it was started manually by user

On Tue, Feb 8, 2011 at 9:28 AM, Lennart Poettering lenn...@poettering.net wrote: On Tue, 08.02.11 16:54, Andrey Borzenkov (arvidj...@mail.ru) wrote: a) mdmon is perfectly capable of restarting, it is already used to take over mdmon launched in initrd. The problem is to know when to restart

[systemd-devel] [PATCH] sd-dhcp6-client: support custom DUIDs

The caller may have an existing DUID that it wants to use, and may want to use some other DUID generation scheme than systemd's default DUID-EN. --- src/libsystemd-network/sd-dhcp6-client.c | 43 +++- src/systemd/sd-dhcp6-client.h| 2 ++ 2 files changed,

[systemd-devel] [PATCH] sd-dhcp-client: support non-Ethernet hardware addresses

Like Infiniband. See RFC 4390 section 2.1 for details on DHCP and Infiniband; chaddr is zeroed, hlen is set to 0, and htype is set to ARPHRD_INFINIBAND because IB hardware addresses are 20 bytes in length. --- src/libsystemd-network/dhcp-internal.h| 10 +++--

Re: [systemd-devel] [PATCH] sd-dhcp-client: support non-Ethernet hardware addresses

On Thu, 2014-10-02 at 16:39 +0200, Tom Gundersen wrote: On Fri, Sep 26, 2014 at 10:15 PM, Dan Williams d...@redhat.com wrote: Like Infiniband. See RFC 4390 section 2.1 for details on DHCP and Infiniband; chaddr is zeroed, hlen is set to 0, and htype is set to ARPHRD_INFINIBAND because IB

Re: [systemd-devel] [PATCH] sd-dhcp-client: support non-Ethernet hardware addresses

On Fri, 2014-10-03 at 16:10 +0300, Patrik Flykt wrote: On Fri, 2014-10-03 at 15:48 +0300, Patrik Flykt wrote: On Fri, 2014-09-26 at 15:15 -0500, Dan Williams wrote: /* RFC2132 section 4.1.1: The client MUST include its hardware address in the ’chaddr’ field

[systemd-devel] [PATCH v3] sd-dhcp-client: support non-Ethernet hardware addresses

Like Infiniband. See RFC 4390 section 2.1 for details on DHCP and Infiniband; chaddr is zeroed, hlen is set to 0, and htype is set to ARPHRD_INFINIBAND because IB hardware addresses are 20 bytes in length. --- v3: use arp_type for identifying client MAC address types, and fix non-Ethernet

[systemd-devel] [PATCH] sd-dhcp-client: clean up raw socket sd_event_source when creating new UDP socket

The raw socket sd_event_source used for DHCP server solicitations was simply dropped on the floor when creating the new UDP socket after a lease has been acquired. Clean it up properly so we're not still listening and responding to events on it. --- src/libsystemd-network/sd-dhcp-client.c | 3

[systemd-devel] [PATCH] sd-dhcp6-client: fix off-by-two error in DUID length

The duid data passed by the caller does not include the DUID type, but sd_dhcp6_client_set_duid() was treating it like it did. --- src/libsystemd-network/sd-dhcp6-client.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/libsystemd-network/sd-dhcp6-client.c

Re: [systemd-devel] Changing configurations with networkd

On Wed, 2014-07-23 at 16:46 +0200, Marcel Holtmann wrote: Hi Michael, I think the lease should be remembered and reused in this case. Hm, this sounds like a bug somewhere. When the new discover is sent out it should send the same identifying information to the server, and hence be

[systemd-devel] [PATCH] sd-dhcp-client: fix REBOOT state handling

client-secs wasn't getting set in the REBOOT state, causing an assertion. REBOOT should work the same way as INIT, per RFC 2131: secs 2 Filled in by client, seconds elapsed since client began address acquisition or renewal process. REBOOT is necessary because some DHCP servers

[systemd-devel] [PATCH] sd-dhcp-lease: expose load/save functions

They're useful outside of networkd itself in the libsystemd-network library. --- src/libsystemd-network/dhcp-lease-internal.h | 3 --- src/libsystemd-network/sd-dhcp-lease.c | 4 ++-- src/network/networkd-link.c | 2 +- src/systemd/sd-dhcp-lease.h | 3 +++

[systemd-devel] [PATCH] sd-dhcp-client: allow getting/setting the client ID

The client identifier can be in many different formats, not just the one that systemd creates from the Ethernet MAC address. Non- ethernet interfaces have different client IDs formats too. Users may also have custom client IDs that they wish to use to preserve lease options delivered by servers

Re: [systemd-devel] [question] networkd: Any support for hooks?

On Tue, 2014-11-04 at 19:40 +0100, Lennart Poettering wrote: BOn Tue, 04.11.14 19:07, Tomasz Torcz (to...@pipebreaker.pl) wrote: On Thu, Oct 02, 2014 at 08:36:10AM +0200, Lennart Poettering wrote: On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote: Hello,

Re: [systemd-devel] [PATCH] sd-dhcp-client: fix REBOOT state handling

On Tue, 2014-11-04 at 11:20 -0600, Dan Williams wrote: client-secs wasn't getting set in the REBOOT state, causing an assertion. REBOOT should work the same way as INIT, per RFC 2131: secs 2 Filled in by client, seconds elapsed since client began address acquisition

Re: [systemd-devel] [PATCH] sd-dhcp-lease: expose load/save functions

On Tue, 2014-11-04 at 11:41 -0600, Dan Williams wrote: They're useful outside of networkd itself in the libsystemd-network library. Anyone had a chance to review this patch? --- src/libsystemd-network/dhcp-lease-internal.h | 3 --- src/libsystemd-network/sd-dhcp-lease.c | 4

Re: [systemd-devel] [PATCH] sd-dhcp-client: allow getting/setting the client ID

On Tue, 2014-11-04 at 11:48 -0600, Dan Williams wrote: The client identifier can be in many different formats, not just the one that systemd creates from the Ethernet MAC address. Non- ethernet interfaces have different client IDs formats too. Users may also have custom client IDs

[systemd-devel] [PATCH] sd-dhcp-lease: load/save client ID

The lease is usually tied to the client ID, so users of the lease may want to know what client ID it was acquired with. --- src/libsystemd-network/dhcp-lease-internal.h | 5 +++ src/libsystemd-network/sd-dhcp-client.c | 16 src/libsystemd-network/sd-dhcp-lease.c | 58

[systemd-devel] [PATCH v2] sd-dhcp-client: allow getting/setting the client ID

The client identifier can be in many different formats, not just the one that systemd creates from the Ethernet MAC address. Non- ethernet interfaces may have different client IDs formats. Users may also have custom client IDs that the wish to use to preserve lease options delivered by servers

Re: [systemd-devel] [BUG] too many rfkill services

On Thu, 2014-11-20 at 14:56 +0100, Michael Biebl wrote: 2014-11-20 14:17 GMT+01:00 Lennart Poettering lenn...@poettering.net: On Tue, 18.11.14 18:37, Łukasz Stelmach (stl...@poczta.fm) wrote: Hi. Recently, after I had found an update for my BIOS, my desktop started to resume properly

Re: [systemd-devel] Cycle between logind and NetworkManager in case of remote user database

On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote: On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote: NetworkManager sets logind inhibitor lock to monitor for suspend events. So it implicitly requires logind to be present when NM starts. NM doesn't actually

Re: [systemd-devel] Cycle between logind and NetworkManager in case of remote user database

On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote: В Mon, 15 Dec 2014 11:34:17 -0600 Dan Williams d...@redhat.com пишет: On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote: On Sat, 13.12.14 10:09, Andrei Borzenkov (arvidj...@gmail.com) wrote: NetworkManager

Re: [systemd-devel] Cycle between logind and NetworkManager in case of remote user database

On Tue, 2014-12-16 at 08:45 +0100, David Herrmann wrote: Hi On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams d...@redhat.com wrote: On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote: systemd tries to launch logind service which now waits for services it is ordered After

Re: [systemd-devel] Mediacast to TV - MiracleCast - Open-Source Miracast - Wifi-Display on linux

On Wed, 2015-02-04 at 00:47 +0100, poma wrote: On 03.02.2015 18:43, David Herrmann wrote: Hi On Tue, Feb 3, 2015 at 6:36 PM, poma pomidorabelis...@gmail.com wrote: On 02.02.2015 19:58, David Herrmann wrote: As I'm not really interested in hacking on network-managers, I've decided to

Re: [systemd-devel] network-online.target is not down when a physical network is down

On Thu, 2015-01-22 at 19:51 +0300, Andrei Borzenkov wrote: В Thu, 22 Jan 2015 16:44:52 +0100 Igor Bukanov i...@mir2.org пишет: For a service that should be shutdown when network is not available, I tried to use Requires=network-online.target . However, on Fedora 21 with NetworkManager

Re: [systemd-devel] network-online.target is not down when a physical network is down

NetworkManager.conf' for more info on connectivity detection. Dan On 22 January 2015 at 19:42, Dan Williams d...@redhat.com wrote: On Thu, 2015-01-22 at 19:51 +0300, Andrei Borzenkov wrote: В Thu, 22 Jan 2015 16:44:52 +0100 Igor Bukanov i...@mir2.org пишет: For a service that should be shutdown

Re: [systemd-devel] No (more) OpenVPN on Debian8 (Jessie) - Thanks systemd ?!

On Thu, 2015-03-05 at 16:00 +0100, system_error wrote: OK, thx! Am 05.03.2015 um 15:56 schrieb Tom Gundersen: This is i segfault in NetworkManager, so I would start by figuring that one out. Probably the NM mailing list may be able to help you better. nm-connection-editor, to be

Re: [systemd-devel] network interface down in container

On Thu, 2015-04-30 at 11:44 +0200, Lennart Poettering wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container Is this correct? Looks fine.

Re: [systemd-devel] Basic network with Fedora conatiner

On Wed, 2015-04-29 at 15:36 +0200, arnaud gaboury wrote: After installation of Fedora 22 container, the container (poppy) boots but no network. # journalctl -b -M poppy Apr 29 14:02:20 poppy firewalld[28]: 2015-04-29 14:02:20 ERROR: ebtables not usable, disabling

Re: [systemd-devel] [RFC 0/6] A network proxy management daemon, systemd-proxy-discoveryd

On Sun, 2015-04-12 at 20:31 +0200, Lennart Poettering wrote: On Fri, 10.04.15 14:05, Dan Williams (d...@redhat.com) wrote: So idea would basically be that we provide in all three daemons calls like: SetAdditionalNTP(ias) SetAdditionalDNS(ia(uay

Re: [systemd-devel] Synchronization Between Services at Shutdown

On Fri, 2015-04-03 at 14:01 +0200, Lennart Poettering wrote: On Thu, 02.04.15 15:04, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote: On 02/04/15 14:31, Lennart Poettering wrote: Hmm? I really don't see how the NFS vs wpa_supplicant issue has anything to do with dbus? NFS doesn't

Re: [systemd-devel] Synchronization Between Services at Shutdown

On Thu, 2015-04-02 at 15:04 +0100, Simon McVittie wrote: On 02/04/15 14:31, Lennart Poettering wrote: Hmm? I really don't see how the NFS vs wpa_supplicant issue has anything to do with dbus? NFS doesn't care about dbus at all... It does inasmuch as it requires networking to be up, which

Re: [systemd-devel] Synchronization Between Services at Shutdown

On Thu, 2015-04-02 at 16:31 +0200, Martin Pitt wrote: Lennart Poettering [2015-04-02 15:31 +0200]: You need to order wpa_supplicant and NM Before=remote-fs-pre.target and pull it it via Wants=remote-fs-pre.target. With that in place during shutdown the mounts will be unmounted first, and

Re: [systemd-devel] Use a specific device ?

On Fri, 2015-06-05 at 16:16 +0200, Jean-Christian de Rivaz wrote: Le 05. 06. 15 15:51, poma a écrit : On 05.06.2015 15:37, Jean-Christian de Rivaz wrote: Le 05. 06. 15 15:09, poma a écrit : On 05.06.2015 14:14, Jean-Christian de Rivaz wrote: Le 05. 06. 15 13:18, Aleksander Morgado a écrit

Re: [systemd-devel] Use a specific device ?

On Tue, 2015-06-09 at 19:34 +0200, Jean-Christian de Rivaz wrote: Le 09. 06. 15 17:43, Dan Williams a écrit : On Fri, 2015-06-05 at 16:16 +0200, Jean-Christian de Rivaz wrote: Le 05. 06. 15 15:51, poma a écrit : On 05.06.2015 15:37, Jean-Christian de Rivaz wrote: Le 05. 06. 15 15:09, poma

Re: [systemd-devel] Use a specific device ?

On Tue, 2015-06-09 at 21:22 +0200, Jean-Christian de Rivaz wrote: Le 09. 06. 15 19:52, Dan Williams a écrit : On Tue, 2015-06-09 at 19:34 +0200, Jean-Christian de Rivaz wrote: Le 09. 06. 15 17:43, Dan Williams a écrit : On Fri, 2015-06-05 at 16:16 +0200, Jean-Christian de Rivaz wrote: Le

Re: [systemd-devel] networkd bridge masquerading

On Thu, 2015-06-18 at 19:34 +0200, Lennart Poettering wrote: On Thu, 18.06.15 13:19, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Without adding any veth / tap interfaces to the bridge. My expectation is for such a bridge to come up correctly. However in journalctl I get:

Re: [systemd-devel] Help needed for optimizing my boot time

On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote: On 06/11/2015 02:22 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 3:10 PM, Francis Moreau francis.m...@gmail.com wrote: On 06/11/2015 01:40 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 2:26 PM, Francis Moreau

Re: [systemd-devel] Use a specific device ?

On Thu, 2015-06-11 at 10:36 +0200, Jean-Christian de Rivaz wrote: Le 11. 06. 15 09:29, Bjørn Mork a écrit : Jean-Christian de Rivaz j...@eclis.ch writes: Le 10. 06. 15 23:37, Bjørn Mork a écrit : Jean-Christian de Rivaz j...@eclis.ch writes: There is not so much modem manufacturers

Re: [systemd-devel] Use a specific device ?

On Thu, 2015-06-11 at 11:19 +0200, Jean-Christian de Rivaz wrote: Le 11. 06. 15 10:48, Bjørn Mork a écrit : Jean-Christian de Rivaz j...@eclis.ch writes: In my experience this is not true. Many vendors, many of them no-name Asian ones, release many devices each year, especially when

Re: [systemd-devel] Use a specific device ?

On Wed, 2015-06-10 at 20:52 +0200, Jean-Christian de Rivaz wrote: Le 10. 06. 15 16:36, Dan Williams a écrit : On Tue, 2015-06-09 at 21:22 +0200, Jean-Christian de Rivaz wrote: This black list, grey list, and white list system is a mess and have to die. No other application do that way

Re: [systemd-devel] Use a specific device ?

On Thu, 2015-06-11 at 00:40 +0200, Jean-Christian de Rivaz wrote: Le 10. 06. 15 23:37, Bjørn Mork a écrit : Jean-Christian de Rivaz j...@eclis.ch writes: There is not so much modem manufacturers and each of them don't even release a new product range per year. Ehh... I don't think we

Re: [systemd-devel] container virtual Ethernet link naming

On Fri, 2015-10-09 at 12:53 -0700, Johannes Ernst wrote: > man systemd-nspawn, section on --network-veth > "The container side of the Ethernet link will be named > host0." > > container> ip link > ... > 2: host0@if9: mtu 1500 qdisc fq_codel state > UP mode

Re: [systemd-devel] dhcp address change callback?

On Mon, 2016-01-25 at 14:27 +0100, Lennart Poettering wrote: > On Mon, 25.01.16 05:08, J Decker (d3c...@gmail.com) wrote: > > > On Mon, Jan 25, 2016 at 4:43 AM, Lennart Poettering > > wrote: > > > On Sat, 23.01.16 14:22, Johannes Ernst (johannes.er...@gmail.com) > > >

Re: [systemd-devel] WebUSB

On Tue, 2017-01-10 at 01:01 +0100, Lars Knudsen wrote: > On Tue, Jan 10, 2017 at 12:47 AM, Lars Knudsen > wrote: > > > A small update:  When the modemmanager finishes probing (~16 secs > > after > > connection) data seems to stop flowing in from the WebUSB bulk > > endpoint > >

Re: [systemd-devel] WebUSB

On Wed, 2017-01-11 at 14:21 +0100, Christer Weinigel wrote: > On 2017-01-10 19:55, Lars Knudsen wrote: > > On Tue, Jan 10, 2017 at 7:08 PM, Dan Williams <d...@redhat.com > > <mailto:d...@redhat.com>> wrote: > > And we're quite happy to keep blacklisti

Re: [systemd-devel] WebUSB

to the modem and does nothing else until the user (or the desktop environment configuration) tells MM to do something. Dan > On Jan 9, 2017 19:40, "Dan Williams" <d...@redhat.com> wrote: > > > On Mon, 2017-01-09 at 19:22 +0100, Lars Knudsen wrote: > > > On

Re: [systemd-devel] WebUSB

On Tue, 2017-01-10 at 18:33 +0100, Greg KH wrote: > On Tue, Jan 10, 2017 at 06:23:13PM +0100, Lars Knudsen wrote: > > > > > > On Jan 10, 2017 18:19, "Greg KH" wrote: > > > > On Tue, Jan 10, 2017 at 06:04:46PM +0100, Lars Knudsen wrote: > > > I figured that made most

Re: [systemd-devel] WebUSB

On Mon, 2017-01-09 at 19:22 +0100, Lars Knudsen wrote: > On Jan 9, 2017 18:56, "Bjørn Mork" wrote: > > > Lars Knudsen writes: > > > > > It seemed like if just one interface in the description list was > > > somehow > > > compliant with modem manager, the full

Re: [systemd-devel] sd-bus: ObjectManager difference with gdbus

On Mon, 2017-04-24 at 16:50 +0200, Lennart Poettering wrote: > On Fri, 21.04.17 13:22, David Herrmann (dh.herrm...@gmail.com) wrote: > > > > > > Anyway, gdbus bugs aside, it seems that the interfaces > > > > > reported by > > > > > sd-bus should match what gdbus does? (assuming, of course, > > >

Re: [systemd-devel] sd-bus: ObjectManager difference with gdbus

On Tue, 2017-04-25 at 07:45 +, David Härdeman wrote: > April 24, 2017 5:49 PM, "Dan Williams" <d...@redhat.com> wrote: > > On Mon, 2017-04-24 at 16:50 +0200, Lennart Poettering wrote: > > > On Fri, 21.04.17 13:22, David Herrmann (dh.herrm...@gmail.com) >

Re: [systemd-devel] Handling on network-connections and networkmanager

On Sun, 2017-06-18 at 01:47 +0200, Jakob Schürz wrote: > Hi there! > > I didn't found anything about the following problem: > There is network.target and network-online.target. In combination > with > NetworkManager network-online.target get started, when > NetworkManager-wait-online.service

Re: [systemd-devel] Replacing nss-mdns with resolved

On Fri, 2017-09-29 at 16:45 +0200, Sven Köhler wrote: > Hi, > > I want to replace nss-mdns with systemd-resolved. However, I am using > NetworkManager, not systemd-networkd. NetworkManager is configured to > pass all DNS-related information to systemd-resolved. > > Unlike networkd,