search for: networkd

Package: xcp-networkd Version: 1.3.2-2 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (...

Hi Clint, systemd-networkd doesn't use those files at all. On Wed, 4 Oct 2017 at 13:55 Clint Dilks <clintd at scms.waikato.ac.nz> wrote: > On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel <phil at zomojo.com> wrote: > > > Hi, > > > > If I disable ipv6 via the kernel command line, ipv6.d...

On 4 Oct 2017 6:51 pm, <m.roth at 5-cent.us> wrote: James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >> /etc/sysconfig/network-scripts/ifcfg-em1 do you see >> IPV6_FAILURE_FATAL=no >> ? >> > > Where does systemd-networkd store its settings, then? > > > > Fil...

On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: On 10/3/2017 8:14 PM, Phil Manuel wrote: > systemd-networkd doesn't use those files at all. > > If you look at the appropriate ifcfg files eg > /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no > ? > Where does systemd-networkd store its settings, then? Files in /etc/systemd/network if I'm remembering right...

Hi I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu. But I got this error while configuring xcp-xapi: xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed. when I comment the "2&gt;/dev/null" in the script I see this...

Package: xcp-networkd Version: 1.3.2-11 Severity: normal Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, '...

Hi, If I disable ipv6 via the kernel command line, ipv6.disable=1, then systemd-networkd fails to bring up any interfaces. Removing the option and networking works as expected. Phil.

And to add to the issues concerning consistency, what if you have a fail over unit and you're replicating configuration (i.e. NIC), you really prefer that NIC names remain the same. Given the hardware morass underneath all of this, the only safe choice (regardless of whether you use systemd, init scripts, whatever) is to take control and force the association of the name to the MAC address in

Okay sorry about that. No Idea if it will work in CentOS, but is it worth trying to turn off ipv6 for a single nic as as outlined at https://coreos.com/os/docs/latest/network-config-with-networkd.html ? On Wed, Oct 4, 2017 at 4:14 PM, Phil Manuel <phil at zomojo.com> wrote: > Hi Clint, > > systemd-networkd doesn't use those files at all. > > > > On Wed, 4 Oct 2017 at 13:55 Clint Dilks <clintd at scms.waikato.ac.nz> wrote: > > > On Wed, Oct...

On 08/03/17 14:54, Jonathan Billings wrote: > > If you'd like a really simple solution that avoids NetworkManager, I > suggest using systemd-networkd (both systemd-networkd and > systemd-resolved packages required). I've used it to set up a bridge > on my workstattion for use with libvirtd/kvm, and it is just as simple > a text file but future compatible. Heck, it probably even works on > other distros that use systemd. > &g...

On 10/3/2017 8:14 PM, Phil Manuel wrote: > systemd-networkd doesn't use those files at all. > > If you look at the appropriate ifcfg files eg > /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no ? Where does systemd-networkd store its settings, then?

James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >> /etc/sysconfig/network-scripts/ifcfg-em1 do you see >> IPV6_FAILURE_FATAL=no >> ? >> > > Where does systemd-networkd store its settings, then? > > > > Fil...

On 10/04/2017 01:40 PM, James Hogarth wrote: > Nope. And find /etc/systemd -name network gives zilch. Yes, systemd-networkd does store its configuration in /etc/systemd/network, but the directory isn't created by the RPM; you need to create it yourself. As noted, systemd-networkd is in the RHEL extras (or somesuch) repo, so it isn't supported by Red Hat on RHEL. It's basically just (minimally) packaged. -...

...> if you are running bind or powerdns on your local host, then it would > make sense to me to disable systemd-resolved, since you don't need so > many layers of caching dns resolvers. Alice was talking about CentOS 7.5, which doesn't have systemd-resolved nor does it have systemd-networkd. I didn't look at EL8 betas yet but we can probably expect systemd-networkd to be included there. If that's the case, we'll probably have legacy script based configs, NetworkManager and systemd-networkd/systemd-resolved. In other words, things may not get easier in the future but even...

Hai marco, Well, "My" preffered for now is systemd-networkd. Current debian still used /etc/network/ but next will be systemd as default. Ubuntu uses : /etc/netplan/ Howto configure it. wget https://raw.githubusercontent.com/thctlo/debian-scripts/master/setup-systemd-networkd.sh bash setup-systemd-networkd.sh member Nothing will be changed on the sys...

On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel <phil at zomojo.com> wrote: > Hi, > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then > systemd-networkd fails to bring up any interfaces. > > Removing the option and networking works as expected. > Hi, If you look at the appropriate ifcfg files eg /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no ?

On 04/10/17 03:46, Phil Manuel wrote: > Hi, > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then > systemd-networkd fails to bring up any interfaces. > > Removing the option and networking works as expected. > > Phil. How are you controlling your network interfaces? I am using NM. Whilst not answering your question directly, I disable ipv6 in /etc/sysctl.conf. cat /etc/sysctl.conf # sysctl set...

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log: /var/log/xcp-xapi.log:[20120707T01:36:51.361Z| warn|lab-xh3|0 thread...

...agree. "You > will conform" - no exceptions. What I fear is that we will lose the > ability to control the name, MAC address association at some future > point because "no one needs to do that" (speaking from their ivory > tower). To be honest, if you use systemd-networkd (instead of NM or the network init script), you can arbitrarily name your interfaces whatever you want, in a much more configuration-management-friendly way. It's just that systemd-networkd isn't that well-known yet. I'm on the fence about whether I like it or not. It is nice that it...

Ok, we can take both but needs to be in a specific order. So, we have two ethernet interfaces, A and B. And both are defined in /etc/systemd/network/ to use dhcp. How to guarantee that the crap provided by dhcp to A (dns, gateway, ntp) is the default? To use an example, /etc/resolv.conf should end up like nameserver IP.for.A.DNS nameserver IP.for.B.DNS domain A.domain.com Now, this must be done