Hi all,
I'm using systemd 216 on Archlinux (uptodate).
Everything worked fine at last boot (systemd 215, kernel 3.14.1)
Here is my tap0.network:
[Match]
Name=tap0
[Network]
DHCP=yes
[Route]
Gateway=10.3.16.1
Destination=10.3.14.0/24
[Route]
Gateway=10.3.16.1
Destination=10.3.15.0/24
And the
After git bisect-ing (following dreisner's instructions on #systemd), I get
the following info:
38de08a does not add static routes
ccf1c02 systemd-networkd is broken (does not run) (crash)
54cba0b systemd-networkd is broken (does not run) (crash)
3c9b886 systemd-networkd is broken (does not run)
Hi!
Is there a way to force a DHCPv4 release/renew with systemd-networkd?
- Mads
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Aug 27, 2014 at 10:17 AM, Mads m...@ab3.no wrote:
Is there a way to force a DHCPv4 release/renew with systemd-networkd?
We don't currently allow dynamic interaction with networkd, but you
can force renew the release by either restarting networkd or
unplugging/replugging the cable (or
This sometimes works, sometimes not. :)
https://bugzilla.redhat.com/show_bug.cgi?id=1119481
poma
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 it doesn't handle RDNSS and DNSSD options from the
RA response.
On Mon, Jul 14, 2014 at 8:06 PM, David Timothy Strauss
da...@davidstrauss.net 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
On Mon, Jul 14, 2014 at 10:38 PM, Dan Williams d...@redhat.com wrote:
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
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 it
On 15.07.2014 09:01, poma wrote:
This sometimes works, sometimes not. :)
https://bugzilla.redhat.com/show_bug.cgi?id=1119481
Resolved.
https://bugzilla.redhat.com/attachment.cgi?id=918197
https://bugzilla.redhat.com/attachment.cgi?id=918198
poma
On Tue, Jul 15, 2014 at 6:33 PM, poma pomidorabelis...@gmail.com wrote:
On 15.07.2014 09:01, poma wrote:
This sometimes works, sometimes not. :)
https://bugzilla.redhat.com/show_bug.cgi?id=1119481
Resolved.
https://bugzilla.redhat.com/attachment.cgi?id=918197
On Sat, Jul 12, 2014 at 7:38 AM, Camilo Aguilar
camilo.agui...@gmail.com wrote:
Hm, if I read the DHCP spec correctly it requires the networks to deal
with broadcast packets, as NAK is always sent as broadcast, so if this
is the case we have a bigger problem.
My interpretation is that a DHCPNAK
On Mon, Jul 7, 2014 at 10:56 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Tom Gundersen at 06/07/14 23:32 did gyre and gimble:
That worked... thanks. BTW, is yes/true still a valid argument for DHCP
(because the manpage says otherwise)?
yes is a synonym for both and no
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 information (that is, no DHCP
whatsoever). Perhaps the option should be
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
I don't mean to be pedantic, but I think any would be a better choice.
-Alex
On Mon, Jul 14, 2014 at 1:54 AM, Tom Gundersen t...@jklm.no wrote:
On Mon, Jul 7, 2014 at 10:56 AM, Colin Guthrie gm...@colin.guthr.ie
wrote:
'Twas brillig, and Tom Gundersen at 06/07/14 23:32 did gyre and gimble:
Notice that the current client code should be ok with the server
ignoring the broadcast flag, and just accept either broadcast or
unicast packages.
agreed
Hm, if I read the DHCP spec correctly it requires the networks to deal
with broadcast packets, as NAK is always sent as broadcast, so if
'Twas brillig, and Tom Gundersen at 06/07/14 23:32 did gyre and gimble:
That worked... thanks. BTW, is yes/true still a valid argument for DHCP
(because the manpage says otherwise)?
yes is a synonym for both and no for none.
While I know it's not something we need to worry about for a long,
Hi,
With systemd-215 networkd fails to set up the DHCPv4 on WAN interface:
--
$ journalctl -u systemd-networkd.service | grep wlp1s0
Jul 06 12:21:07 hermes systemd-networkd[355]: wlp1s0 : link configured
Jul 06 12:21:08 hermes systemd-networkd[355]: wlp1s0 : gained
On Sun, Jul 6, 2014 at 7:17 PM, Leonid Isaev lis...@umail.iu.edu wrote:
Hi,
With systemd-215 networkd fails to set up the DHCPv4 on WAN interface:
--
$ journalctl -u systemd-networkd.service | grep wlp1s0
Jul 06 12:21:07 hermes systemd-networkd[355]: wlp1s0 : link
On Sun, Jul 06, 2014 at 08:43:01PM +0200, Tom Gundersen wrote:
On Sun, Jul 6, 2014 at 7:17 PM, Leonid Isaev lis...@umail.iu.edu wrote:
Hi,
With systemd-215 networkd fails to set up the DHCPv4 on WAN
interface:
--
$ journalctl -u systemd-networkd.service | grep wlp1s0
On Sun, Jul 6, 2014 at 11:52 PM, Leonid Isaev lis...@umail.iu.edu wrote:
On Sun, Jul 06, 2014 at 08:43:01PM +0200, Tom Gundersen wrote:
On Sun, Jul 6, 2014 at 7:17 PM, Leonid Isaev lis...@umail.iu.edu wrote:
Hi,
With systemd-215 networkd fails to set up the DHCPv4 on WAN
There's a bug in the DHCPv6 implementation somewhere. systemd-networkd
was crashing every time it started, so I took a look in gdb:
# gdb /usr/lib/systemd/systemd-networkd
GNU gdb (GDB) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
2014-06-25 14:12 GMT+04:00 Michael Olbrich m.olbr...@pengutronix.de:
Hi,
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added Before=network.target
dependency to systemd-networkd-wait-online.service. Is that correct? If I
understand
On Sun, 29.06.14 23:58, Tom Gundersen (t...@jklm.no) wrote:
On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added Before=network.target
dependency
On Mon, Jun 30, 2014 at 1:04 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 29.06.14 23:58, Tom Gundersen (t...@jklm.no) wrote:
On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
Hi Camilo,
Sorry for taking some time to get back to you.
On Sat, Jun 21, 2014 at 9:08 PM, Camilo Aguilar
camilo.agui...@gmail.com wrote:
This is another reason why I previously suggested to expose a directive to
allow administrators to enable/disable the broadcast flag. I have seen DHCP
On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
m.olbr...@pengutronix.de wrote:
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added Before=network.target
dependency to systemd-networkd-wait-online.service. Is that correct? If I
Hi,
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added Before=network.target
dependency to systemd-networkd-wait-online.service. Is that correct? If I
understand the documentation correctly, then network.target should not be
delayed.
On Fri, Jun 20, 2014 at 12:12 PM, Michal Sekletar msekl...@redhat.com wrote:
On Wed, Jun 18, 2014 at 09:51:02PM +0200, Friedrich Kröner wrote:
Hello,
when trying systemd-networkd with =214 and the following config:
[Match]
Name=eth*
[Network]
DHCP=yes
Address=2001:db8::1234:5678/64
On Saturday 21 June 2014 15:24:03 Tom Gundersen wrote:
On Fri, Jun 20, 2014 at 12:12 PM, Michal Sekletar msekl...@redhat.com
wrote:
On Wed, Jun 18, 2014 at 09:51:02PM +0200, Friedrich Kröner wrote:
Hello,
when trying systemd-networkd with =214 and the following config:
[Match]
This is another reason why I previously suggested to expose a directive to
allow administrators to enable/disable the broadcast flag. I have seen DHCP
servers ignoring the flag and always sending broadcasted DHCPOFFERs. There
could be other servers that may only use unicast, and even networks that
On Wed, Jun 18, 2014 at 09:51:02PM +0200, Friedrich Kröner wrote:
Hello,
when trying systemd-networkd with =214 and the following config:
[Match]
Name=eth*
[Network]
DHCP=yes
Address=2001:db8::1234:5678/64
DNS=8.8.8.8
DNS=2001:db8:1::ab9:C0A8:102
I get lots of DHCP DISCOVER
On Tue, 17.06.14 13:14, Runiq (ru...@archlinux.us) wrote:
Hello all,
I'm using systemd 213 on Arch Linux, and systemd-networkd/resolved
with DHCP to connect to the internet. I'm also running a caching DNS
server on 127.0.0.1.
I'd like to make this caching server the first DNS server in
On Wed, 18.06.14 21:51, Friedrich Kröner (friedr...@mailstation.de) wrote:
Hello,
when trying systemd-networkd with =214 and the following config:
[Match]
Name=eth*
[Network]
DHCP=yes
Address=2001:db8::1234:5678/64
DNS=8.8.8.8
DNS=2001:db8:1::ab9:C0A8:102
reverting commit
On 17.06.2014 14:43:25, Mantas Mikulėnas wrote:
On Jun 17, 2014 2:14 PM, Runiq ru...@archlinux.us wrote:
Hello all,
I'm using systemd 213 on Arch Linux, and systemd-networkd/resolved with
DHCP to connect to the internet. I'm also running a caching DNS server on
127.0.0.1.
I'd like to make
Hello,
when trying systemd-networkd with =214 and the following config:
[Match]
Name=eth*
[Network]
DHCP=yes
Address=2001:db8::1234:5678/64
DNS=8.8.8.8
DNS=2001:db8:1::ab9:C0A8:102
I get lots of DHCP DISCOVER events and it doesn't aquire an IPv4 address, nor
sets the configured IPv6.
Jun
Hello all,
I'm using systemd 213 on Arch Linux, and systemd-networkd/resolved with
DHCP to connect to the internet. I'm also running a caching DNS server
on 127.0.0.1.
I'd like to make this caching server the first DNS server in the list,
but I'd also like to use the nameservers discovered
I am not sure about the part where you talk about different networks' DNS
settings.
I mean, as long as the first-listed server responds – and localhost always
responds – then the fallback servers won't be used at all.
So what's the point of having both 127.0.0.1 and external servers listed
Actually, one thing I just remembered.
resolved never actually writes to /etc/resolv.conf, if I remember
correctly. It only writes to a .conf in /run, and /etc/resolv.conf is just
a symlink to the latter.
So you could just have a static /etc/resolv.conf with 127.0.0.1 in it, and
tell your cache
On Tue, Jun 17, 2014 at 4:33 AM, Mantas Mikulėnas graw...@gmail.com wrote:
I mean, as long as the first-listed server responds – and localhost always
responds – then the fallback servers won't be used at all.
Localhost can be subject to two types of failure:
* The local daemon being down.
*
Whether predictable EHA may be applicable to bonding also?
To remind myself without caffeine, heh.
https://www.kernel.org/doc/Documentation/networking/bonding.txt
15. Frequently Asked Questions
8. Where does a bonding device get its MAC address from?
When using slave devices that
MACA ddress in addition to
/etc/systemd/network/bridge0.netdev:
[NetDev]
Name=bridge0
Kind=bridge
MACAddress=00:12:34:56:78:90
The rest is here:
https://bugzilla.redhat.com/attachment.cgi?id=881142
journal-sd-networkd-214-2.git4997cb9.20140615-3.16.0-0.rc:
[ 16.629830] sd[1]: Starting
Hi poma,
So do I understand correctly that it all works as expected for you now?
Cheers,
Tom
On Mon, Jun 16, 2014 at 3:05 PM, poma pomidorabelis...@gmail.com wrote:
MACA ddress in addition to
/etc/systemd/network/bridge0.netdev:
[NetDev]
Name=bridge0
Kind=bridge
On 06/16/2014 03:09 PM, Tom Gundersen wrote:
Hi poma,
So do I understand correctly that it all works as expected for you now?
Cheers,
Tom
Yep!
poma
man: networkd - netdev MAC addition
diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml
index c17ae9e..931d806 100644
---
On 05.06.2014 12:05, Tom Gundersen wrote:
Thanks for the reminder. I'll revert the revert :)
We grew some more features since it was first introduced, so will have
to check out how it all works with tunnels, veth devices etc, but
should definitely have this back for 314.
Cheers,
Tom
On Wed, 04.06.14 00:29, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Jun 3, 2014 at 9:58 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 02.06.14 21:02, Tom Gundersen (t...@jklm.no) wrote:
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me
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
Subject: Re: [systemd-devel] Systemd-networkd, default route
Subject: Re: [systemd-devel] Systemd-networkd, default route and multiple
interfaces
User-Agent: Leviathan/19.8.0 [zh] (Cray 3; I; Solaris 4.711; Console)
On Wed, 04.06.14 00:29, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Jun 3, 2014 at 9:58 PM, Lennart Poettering
lenn
Bridgetto is in the stable 3.14.5 kernel.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=4a68caa
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.5
.
commit 4a68caa1b3d3f382bde56a6a3d3430bcb53ecf7f
Author: Toshiaki Makita makita.toshi...@lab.ntt.co.jp
Thanks for the reminder. I'll revert the revert :)
We grew some more features since it was first introduced, so will have
to check out how it all works with tunnels, veth devices etc, but
should definitely have this back for 314.
Cheers,
Tom
On Thu, Jun 5, 2014 at 12:00 PM, poma
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me wrote:
Hello.
Since network files are applied to links whenever the links
appear, how do systemd manage the disappearance of a default route ?
For example, let's say i have one wireless interface and one ethernet
On Mon, 02.06.14 21:02, Tom Gundersen (t...@jklm.no) wrote:
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me wrote:
Since network files are applied to links whenever the links
appear, how do systemd manage the disappearance of a default route ?
You can have
On Tue, Jun 3, 2014 at 8:58 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 02.06.14 21:02, Tom Gundersen (t...@jklm.no) wrote:
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me wrote:
Since network files are applied to links whenever the links
appear,
On Tue, Jun 3, 2014 at 9:58 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 02.06.14 21:02, Tom Gundersen (t...@jklm.no) wrote:
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me wrote:
Since network files are applied to links whenever the links
On 04/14/2014 09:12 AM, Tom Gundersen wrote:
On Mon, Apr 14, 2014 at 1:17 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 04/14/2014 12:34 AM, Tom Gundersen wrote:
On Mon, Apr 14, 2014 at 12:12 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/22/2014 10:41 AM, Tom Gundersen
On Mon, Jun 2, 2014 at 8:47 PM, Reventlov
contact+systemd...@volcanis.me wrote:
Since network files are applied to links whenever the links
appear, how do systemd manage the disappearance of a default route ?
You can have several default routes, so we just configure them all and
let the kernel
This should really be added as AFAICT there is currently no way to match
on virtual devices like briges, TAP devices, batman-adv devices, etc...
which have neither a persistent MAC address nor an ID_PATH to match on.
So I think what we should do here is to allow MAC address (and other
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
This should really be added as AFAICT there is currently no way to match
on virtual devices like briges, TAP devices, batman-adv devices, etc...
which have neither a persistent MAC address nor an ID_PATH
On 12.05.2014 12:22, Tom Gundersen wrote:
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
This should really be added as AFAICT there is currently no way to match
on virtual devices like briges, TAP devices, batman-adv devices, etc...
which have
On Mon, May 12, 2014 at 5:27 PM, poma pomidorabelis...@gmail.com wrote:
On 12.05.2014 12:22, Tom Gundersen wrote:
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
This should really be added as AFAICT there is currently no way to match
on virtual
On 05/12/2014 05:45 PM, Tom Gundersen wrote:
On Mon, May 12, 2014 at 5:27 PM, poma pomidorabelis...@gmail.com wrote:
On 12.05.2014 12:22, Tom Gundersen wrote:
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
This should really be added as AFAICT there
On 12.05.2014 20:53, Tom Gundersen wrote:
On Mon, May 12, 2014 at 7:44 PM, poma pomidorabelis...@gmail.com wrote:
Why am I seeing this commit on git/stable,
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/net/bridge/br_netlink.c?id=30313a3
but not in stable complete
Hi Matthias,
On Fri, Apr 18, 2014 at 1:08 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
On 04/17/2014 11:28 PM, Dave Reisner wrote:
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
Hi,
I'd like to configure the
On 04/22/2014 04:07 PM, Tom Gundersen wrote:
Hi Matthias,
On Fri, Apr 18, 2014 at 1:08 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
On 04/17/2014 11:28 PM, Dave Reisner wrote:
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias
On Fri, Mar 21, 2014 at 10:15 PM, Tom Gundersen t...@jklm.no wrote:
On Fri, Mar 21, 2014 at 9:47 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
However, I find it disturbing that DHCP is attempted first on the wrong
MAC, only to be killed and restarted on the right MAC.
Is this really the
On Mon, Apr 21, 2014 at 6:45 PM, Tom Gundersen t...@jklm.no wrote:
On Fri, Mar 21, 2014 at 10:15 PM, Tom Gundersen t...@jklm.no wrote:
On Fri, Mar 21, 2014 at 9:47 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
However, I find it disturbing that DHCP is attempted first on the wrong
MAC,
Hi,
I'd like to configure the MAC address of a bridge device statically (as
bridges tend to change their MAC address depending on the order the
ports are added on Linux otherwise), but there doesn't seem to be a way
to match for a bridge in a .link unit. This would be very useful for
macvlans as
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
Hi,
I'd like to configure the MAC address of a bridge device statically (as
bridges tend to change their MAC address depending on the order the
ports are added on Linux otherwise), but there doesn't seem to be a way
to match
On 04/17/2014 11:28 PM, Dave Reisner wrote:
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
Hi,
I'd like to configure the MAC address of a bridge device statically (as
bridges tend to change their MAC address depending on the order the
ports are added on Linux otherwise),
On 04/18/2014 12:14 AM, Matthias Schiffer wrote:
On 04/17/2014 11:28 PM, Dave Reisner wrote:
On Thu, Apr 17, 2014 at 11:02:11PM +0200, Matthias Schiffer wrote:
Hi,
I'd like to configure the MAC address of a bridge device statically (as
bridges tend to change their MAC address depending on the
On Mon, Apr 14, 2014 at 1:17 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 04/14/2014 12:34 AM, Tom Gundersen wrote:
On Mon, Apr 14, 2014 at 12:12 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/22/2014 10:41 AM, Tom Gundersen wrote:
On Sat, Mar 22, 2014 at 5:06 AM, poma
On 03/22/2014 10:41 AM, Tom Gundersen wrote:
On Sat, Mar 22, 2014 at 5:06 AM, poma pomidorabelis...@gmail.com wrote:
systemd-networkd bridge dhcp OK
https://bugzilla.redhat.com/attachment.cgi?id=877526
Thanks for reporting back.
Cheers,
Tom
Dear all,
I started this thread about a month
On Mon, Apr 14, 2014 at 12:12 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/22/2014 10:41 AM, Tom Gundersen wrote:
On Sat, Mar 22, 2014 at 5:06 AM, poma pomidorabelis...@gmail.com wrote:
systemd-networkd bridge dhcp OK
https://bugzilla.redhat.com/attachment.cgi?id=877526
On Wednesday 02 April 2014 at 12:00:07, Umut Tezduyar Lindskog wrote:
Hi Ivan,
On Wed, Apr 2, 2014 at 11:41 AM, Ivan Shapovalov intelfx...@gmail.com
wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered After=network.target (like openvpn) are
prone to failures when they attempt to connect at
Hi Ivan,
On Wed, Apr 2, 2014 at 11:41 AM, Ivan Shapovalov intelfx...@gmail.com wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered
On 04/02/2014 03:41 AM, Ivan Shapovalov wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some networking daemons ordered After=network.target (like openvpn) are
On Wed, Apr 2, 2014 at 3:22 PM, Matthew Monaco m...@0x01b.net wrote:
On 04/02/2014 03:41 AM, Ivan Shapovalov wrote:
Hello all,
I've noticed that systemd-networkd.service (ordered Before=network.target)
finishes its startup before the connection is established/failed. Because of
this, some
On Sat, Mar 22, 2014 at 5:06 AM, poma pomidorabelis...@gmail.com wrote:
systemd-networkd bridge dhcp OK
https://bugzilla.redhat.com/attachment.cgi?id=877526
Thanks for reporting back.
Cheers,
Tom
___
systemd-devel mailing list
On Thu, Mar 20, 2014 at 8:29 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Mar 19, 2014 at 2:09 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Mar 19, 2014 at 1:25 PM, poma pomidorabelis...@gmail.com wrote:
Still the same issue, DHCPC starts too early, before the correct MAC
address is set for
On Thu, 2014-03-20 at 20:29 +0100, Tom Gundersen wrote:
My proposal is:
Whenever the MAC address changes under us networkd calls
sd_{dhcp_client,ipv4ll}_set_mac(), and it is the libs' responsibility
to then do the right thing.
Currently the libs don't support this and will fail with
On Fri, Mar 21, 2014 at 8:51 AM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
On Thu, Mar 20, 2014 at 8:29 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Mar 19, 2014 at 2:09 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Mar 19, 2014 at 1:25 PM, poma pomidorabelis...@gmail.com wrote:
Still
On Fri, Mar 21, 2014 at 9:57 AM, Patrik Flykt
patrik.fl...@linux.intel.com wrote:
On Thu, 2014-03-20 at 20:29 +0100, Tom Gundersen wrote:
My proposal is:
Whenever the MAC address changes under us networkd calls
sd_{dhcp_client,ipv4ll}_set_mac(), and it is the libs' responsibility
to then do
On Tue, Mar 18, 2014 at 10:38 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 10:10 AM, Tom Gundersen wrote:
On Tue, Mar 18, 2014 at 10:00 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 09:18 AM, Henrik /KaarPoSoft wrote:
On 03/17/2014 10:32 PM, Tom
On 03/21/2014 07:03 PM, Tom Gundersen wrote:
On Tue, Mar 18, 2014 at 10:38 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 10:10 AM, Tom Gundersen wrote:
On Tue, Mar 18, 2014 at 10:00 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 09:18 AM, Henrik
systemd-networkd bridge dhcp OK
https://bugzilla.redhat.com/attachment.cgi?id=877526
poma
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Mar 19, 2014 at 2:09 PM, Tom Gundersen t...@jklm.no wrote:
On Wed, Mar 19, 2014 at 1:25 PM, poma pomidorabelis...@gmail.com wrote:
Still the same issue, DHCPC starts too early, before the correct MAC
address is set for the bridge.
git 7bf2f4397255bc8f6cf20a0f2adab4c984ea7d14
I
On 19.03.2014 14:09, Tom Gundersen wrote:
I haven't yet gotten around to this. We probably should just restart
the dhcp client if the mac address changes, for whatever reason.
Unless anyone else has a better idea.
Cheers,
Tom
Nobody's perfect.
- NetworkManager - bridge dhcp
Still the same issue, DHCPC starts too early, before the correct MAC
address is set for the bridge.
git 7bf2f4397255bc8f6cf20a0f2adab4c984ea7d14
journalctl -b -u systemd-networkd
...
12:51:55 networkd[579]: timestamp of '/etc/systemd/network' changed
12:51:55 networkd[579]: timestamp of
On Wed, Mar 19, 2014 at 1:25 PM, poma pomidorabelis...@gmail.com wrote:
Still the same issue, DHCPC starts too early, before the correct MAC
address is set for the bridge.
git 7bf2f4397255bc8f6cf20a0f2adab4c984ea7d14
I haven't yet gotten around to this. We probably should just restart
the
On 03/17/2014 10:32 PM, Tom Gundersen wrote:
On Mon, Mar 17, 2014 at 10:21 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Hi Tom,
Thanks for your feedback...
I was briefly looking through git commits after 211 without finding anything
related. But then again I did not look into too much
On 03/18/2014 09:18 AM, Henrik /KaarPoSoft wrote:
On 03/17/2014 10:32 PM, Tom Gundersen wrote:
On Mon, Mar 17, 2014 at 10:21 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Hi Tom,
Thanks for your feedback...
I was briefly looking through git commits after 211 without finding
anything
On Tue, Mar 18, 2014 at 10:00 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 09:18 AM, Henrik /KaarPoSoft wrote:
On 03/17/2014 10:32 PM, Tom Gundersen wrote:
On Mon, Mar 17, 2014 at 10:21 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Hi Tom,
Thanks for your
On 03/18/2014 10:10 AM, Tom Gundersen wrote:
On Tue, Mar 18, 2014 at 10:00 AM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
On 03/18/2014 09:18 AM, Henrik /KaarPoSoft wrote:
On 03/17/2014 10:32 PM, Tom Gundersen wrote:
On Mon, Mar 17, 2014 at 10:21 PM, Henrik /KaarPoSoft
...
- journalctl/systemd-networkd:
systemd-networkd[597]: timestamp of '/etc/systemd/network' changed
systemd-networkd[597]: timestamp of '/run/systemd/network' changed
systemd-networkd[597]: bridge0: creating netdev
systemd-networkd[597]: enp1s6: link (with ifindex 2) added
Dear all,
*SUMMARY*
I am trying to replace dhcpcd with systemd-networkd.
Using systemd-networkd on a single physical interface works fine.
However, trying to use DHCP on a bridge fails for me.
Any help would be most appreciated.
*WORKS*
The single physical interface scenario which works:
Hi Henrik,
On Mon, Mar 17, 2014 at 5:01 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Dear all,
*SUMMARY*
I am trying to replace dhcpcd with systemd-networkd.
Using systemd-networkd on a single physical interface works fine.
However, trying to use DHCP on a bridge fails for me.
Any
Hi Tom,
Thanks for your feedback...
I was briefly looking through git commits after 211 without finding
anything related. But then again I did not look into too much detail.
Do you know which commit would solve this?
/Henrik
On 03/17/2014 09:52 PM, Tom Gundersen wrote:
Hi Henrik,
On
On Mon, Mar 17, 2014 at 10:21 PM, Henrik /KaarPoSoft
hen...@kaarposoft.dk wrote:
Hi Tom,
Thanks for your feedback...
I was briefly looking through git commits after 211 without finding anything
related. But then again I did not look into too much detail.
Do you know which commit would
201 - 300 of 326 matches
Mail list logo
