> On 14 Jan 2025, at 09:04, Max Gautier wrote:
>
> I have similar setup (PPPoE, /48 delegation) here are my network files:
> (It's been a while, I don't remember the reason for everything)
>
Thanks to all of you that responded. I now have every working with the
information you provided.
Thi
I have similar setup (PPPoE, /48 delegation) here are my network files:
(It's been a while, I don't remember the reason for everything)
==> /etc/systemd/network/10-extern0.link <==
[Match]
Path=platform-fe30.ethernet
[Link]
Name=extern0
==> /etc/systemd/network/10-extern0.network <==
[Match]
On Mon, Jan 13, 2025, at 12:58, Barry Scott wrote:
> This sets net.ipv6.conf.all.forwarding = 1 but, prefix delegation is broken.
>
> If I remove Ipv6Forwarding=true and then set
> net.ipv6.conf.all.forwarding = 1 mnaually forwarding works.
It could be useful to note that this setting does not a
> The IPv6 is a /48.
>
> I have the IPv4 all working well.
>
> But the IPv6 configuration I cannot figure out.
I have a similar set up and have this working.
> [Network]
> Address=2001x:x::x::1
You are specifying a /24 for IPv4, but nothing for IPv6. I'd suggest
adding a /64 if you want to de
I'm building a router for my home using Fedora server as the base.
I have a ISP that provides me with a IPv4 and Ipv6 over PPPoE.
The IPv6 is a /48.
I have the IPv4 all working well.
But the IPv6 configuration I cannot figure out.
I have two interface named internal and external.
In /etc/syst
On Sun, Dec 8, 2024 at 8:00 AM Adam Nielsen wrote:
>
> Hi all,
>
> Is there a way to tell the systemd-networkd-wait-online service to wait
> until DNS is working before continuing?
>
I have a PR open for this, which should hopefully be in v258.
https://github.com/systemd/systemd/pull/34640
-NR
> > Is there a way to tell the systemd-networkd-wait-online service to wait
> > until DNS is working before continuing?
>
> There is not, so I built a small tool for this:
> https://forge.km6g.us/km6g/wait-for-dns
>
> It doesn't just wait for a DNS resolver to be configured, it waits for a nam
On Sun, Dec 8, 2024, at 06:47, Adam Nielsen wrote:
> Hi all,
>
> Is there a way to tell the systemd-networkd-wait-online service to wait
> until DNS is working before continuing?
There is not, so I built a small tool for this:
https://forge.km6g.us/km6g/wait-for-dns
It doesn't just wait for a DN
Hi all,
Is there a way to tell the systemd-networkd-wait-online service to wait
until DNS is working before continuing?
I have an issue where I need an NFS share mounted during boot, but the
automount process is failing because the "mount" command can't resolve
the hostname of the server during b
Hi,
As I start looking at the code, is there any design documentation for
developers that describes systemd-networkd?
Specifically, I'm looking for an overview of the data-flow when an IPv6 Router
Advertisement is received, where it is processed and where it generates the
reply.
I'm slowly bu
On Thu, Mar 30, 2023, at 09:35, [email protected] wrote:
> [Match]
> name = eth0
> SSID = my-wifi
>
> would that mean, that "my-wifi" must be accessible via that interface
> (AND logic) or could that mean we configure "eth0" while "my-wifi" is
> visible on any interface (OR logic)? I had h
Hi Alvin,
On 2023-03-29 22:55, Alvin Šipraga wrote:
> Hi Torsten,
>
> On Wed, Mar 29, 2023 at 02:58:05PM +0200, [email protected] wrote:
> >
> > Dear Systemd Folx,
> >
> >
> >
> > I have a laptop that I run at different locations with different
> > networks. I want to have static(!) network setup (addre
Hi Torsten,
On Wed, Mar 29, 2023 at 02:58:05PM +0200, [email protected] wrote:
>
> Dear Systemd Folx,
>
>
>
> I have a laptop that I run at different locations with different
> networks. I want to have static(!) network setup (address, gateway, DNS,
> NTP) for my wired adapter on these networks. I c
Dear Systemd Folx,
I have a laptop that I run at different locations with different
networks. I want to have static(!) network setup (address, gateway, DNS,
NTP) for my wired adapter on these networks. I can define setup for
each of them in a .network file matching my interface (eth0), but only
tun interfaces cannot be put in a bridge because they do not use an
Ethernet-like L2 link-layer header (or any L2 header at all, really;
they're purely L3 interfaces).
You need to use a 'tap' interface instead.
On Tue, Jan 31, 2023 at 1:05 PM Thomas Köller
wrote:
> I am trying to build a VPN tu
I am trying to build a VPN tunnel through a tun interface created by
sshd. The tun interface is to be added to an existing bridge interface.
For this purpose I created a .network file (see below). However, the
operation fails, without systemd-networkd giving a useful error message
beyond 'Inval
On Sat, Oct 8, 2022 at 10:55 AM Marcel Menzel wrote:
>
> Hello List,
>
> after switching from radvd to systemd-networkd for router advertisements, I
> noticed my Android device losing IPv6 connection after a while and not
> displaying any IPv6 Addresses anymore in the network overview.
>
> I am
Hello List,
after switching from radvd to systemd-networkd for router
advertisements, I noticed my Android device losing IPv6 connection after
a while and not displaying any IPv6 Addresses anymore in the network
overview.
I am aware with IPv6 issues on Android on certain vendors / ROMs, but
Hmm, I don't understand why you need to send RAs on eth0, if that's the
connection to your VPS provider?
On Sun, Dec 12, 2021 at 5:17 AM jackyzy823 wrote:
> Dear developers.
>
> I have a question about if i can use IPv6SendRA and IPv6AcceptRA in a same
> .network file.
>
> Here's the situation.
Dear developers.
I have a question about if i can use IPv6SendRA and IPv6AcceptRA in a same
.network file.
Here's the situation. My VPS provider offers an IPv6 /64 prefix for my
machine.
I can achieve SLAAC via radvd + systemd-networkd using following config.
/etc/radvd.conf
```
interface eth0
Hi,
I hope this is the right place to post this question.
We are trying to speed up the network configuration and we've noticed
the systemd-networkd takes a while before it finalizes to set up the
DHCP (ipv4) configuration on port 'eth0'. After some debugging, we
think the reason is that the netw
On my two systems that are running systemd 249.5-1 (Debian sid
packages), I see this message in the journal once for each network
interface that systemd-networkd manages:
Could not drop routing policy rule: No such file or directory
I don't have any routing policies configured on the systems, so
For several years now, I've been enjoying the fact that the
systemd-networkd DHCP server seems to do the right thing, but a question
has arisen, and I'm getting results that I can't explain.
Basically, the embedded system we've assembled has a WAN interface and
one or more client interfaces, a
Hi list
What is the recommended way to configure mtu for veth pairs via
systemd-networkd?
From https://www.freedesktop.org/software/systemd/man/systemd.netdev.html
MTUBytes for veth is supported in the
[NetDev] configuration, however given the following foo.netdev file:
[NetDev]
Name=foo
Kind
On Fri, Apr 23, 2021 at 10:00:32 +0200 Lennart Poettering
wrote:
> On Fr, 23.04.21 08:17, Paul Menzel ([email protected])
> wrote:
>
> > Dear systemd folks,
> >
> >
> > Due to historical reasons, in our environment we have a configuration file
> > with the network device name an
On Fr, 23.04.21 08:17, Paul Menzel ([email protected]) wrote:
> Dear systemd folks,
>
>
> Due to historical reasons, in our environment we have a configuration file
> with the network device name and the to be assigned IP address:
>
> $ more /etc/local/mxhost.conf
> MX_NE
Dear systemd folks,
Due to historical reasons, in our environment we have a configuration
file with the network device name and the to be assigned IP address:
$ more /etc/local/mxhost.conf
MX_NETDEV=net02
MX_IPADDR=141.14.18.X
Then a custom service unit `network.service` [1] conf
Hello,
I'd like to create the following routes via systemd-networkd. I've
read through the systemd.network manpage and located the
MultiPathRoute= directive however the syntax in the manpage and also
in the function config_parse_multipath_route strongly suggest it requires
a gateway address. Altho
Dear systemd folks,
For several GNOME systems, systemd-networkd is an alternative to the
NetworkManager. For example, desktop systems with a plugged in Ethernet
cable, which do not use wireless devices. As systemd-networkd is often
not packaged separately by distributions, it’s a viable optio
On Mo, 26.10.20 13:04, Bruce A. Johnson ([email protected]) wrote:
> What are the state of things and the plan for the future with respect to
> iwd and systemd-networkd? A couple of years ago, I put together a
> satisfactory solution for my project in OpenEmbedded/Yocto using
> system
Hi,
On 10/26/20 6:04 PM, Bruce A. Johnson wrote:
> What are the state of things and the plan for the future with respect to
> iwd and systemd-networkd? A couple of years ago, I put together a
> satisfactory solution for my project in OpenEmbedded/Yocto using
> systemd-networkd to manage the IP con
What are the state of things and the plan for the future with respect to
iwd and systemd-networkd? A couple of years ago, I put together a
satisfactory solution for my project in OpenEmbedded/Yocto using
systemd-networkd to manage the IP connections and wpa_supplicant to
manage the underlying Wi-Fi
On Fr, 14.08.20 13:56, Marc Lasch ([email protected]) wrote:
> Hello,
>
> I recently stumbled across the following section in the systemd-networkd
> documentation for IPv6AcceptRA=:
>
> "Note that kernel's implementation of the IPv6 RA protocol is always
> disabled, regardless of this setting. [.
Hello,
I recently stumbled across the following section in the systemd-networkd
documentation for IPv6AcceptRA=:
"Note that kernel's implementation of the IPv6 RA protocol is always
disabled, regardless of this setting. [...]"
What does this mean in practice? Is the kernel's IPv6 RA implementati
That seems to be working as expected.
The initial, kernel-assigned name is always going to be an incrementing
eth#, wlan#, or something similar. It's up to the userspace (i.e. udev) to
rename it to something custom.
However, interfaces can only be renamed while they're *not* up, otherwise
the ker
Greetings,
I am using systemd-networkd and I am wondering how/why the interface names
get chosen.
Scenario:
I am expecting an interface name to be enp1s0. Instead I get eth1.
It appears that eth1 is being referenced in things like:
/etc/default/isc-dhcp-server
/etc/default/minissdpd
If I chang
Dear Luke,
On 2020-07-08 13:10, Luke Alexander wrote:
> I had a look through some of the issues against the systemd github repo but
> could not find any matching - there were a couple which look promising but
> don't completely resolve our issue.
>
> Our issue is that we have a k8s (1.18, kube-
Ah, no problem thanks for the info!
On Wed, Jul 8, 2020 at 12:17 PM Paul Menzel <
[email protected]> wrote:
> Dear Luke,
>
>
> On 2020-07-08 13:10, Luke Alexander wrote:
>
> > I had a look through some of the issues against the systemd github repo
> but
> > could not find any ma
Hi,
I had a look through some of the issues against the systemd github repo but
could not find any matching - there were a couple which look promising but
don't completely resolve our issue.
Our issue is that we have a k8s (1.18, kube-router CNI) cluster comprised
of a number of Ubuntu 16.04 node
Mea culpa, I completely overlooked this. Big sorry.
And in addition I can confirm this behaviour. Doing this rename manually
does keep the values.
I am just wondering, how can we apply that to the boot behaviour? It
does give some meat to the thesis, that something else is going on, but
how
23.05.2020 11:56, Ede Wolf пишет:
>>
>> tw:~ # systemctl stop NetworkManager.service
>> tw:~ # ip l set dev enp0s5 down
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/use_tempaddr
>> 1
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/addr_gen_mode
>> 1
>> tw:~ # echo 3 > /proc/sys/net/ipv6/conf/enp0s5/ad
Given lack of errors after interface rename, settings were most probably
applied correctly.
No. According to the log, the lack of errors after the rename result
simlpy in there are no more settings left that could be applied. Because
they all have been tried before. And failed. sysctl.conf is
22.05.2020 22:17, Ede Wolf пишет:
> Am 22.05.20 um 17:58 schrieb Andrei Borzenkov:
>>>
>>> The problem is, that sysctl.conf is being executed before the interfaces
>>> get their eventual names.
>>>
>>
>> That sounds like actual bug. What systemd version do you use?
>
> At least it is, what the jou
However, all is not gold with Deepin as well, as when using a .link file
in /etc/systemd/network to rename the interface, Deeping as well does
not work any more. Here, eth0 aka enp0s3 aka custom lan-01:
# journalctl -b0 | grep -E 'sysctl|lan-01|enp0s3|eth0'
May 22 22:31:22 test1-PC kernel: Ya
There are other issues with either systemd-245 or arch.
When NOT using any
net.ipv6.conf.xxx.use_tempaddr=2
statements in sysctl.conf, but instead are only using
IPv6PrivacyExtensions=yes
on arch/systemd-245 this setting gets ignored. On Deepin however a
temporary address is assigned, as exp
That sounds like actual bug. What systemd version do you use?
I've just did a test with Deepin, as I've had VM flying around of that
debian based distribution, and here it seems to work, using systemd 241
instead of 245. systemd-sysctl is clearly called after the renaming:
May 22 21:48:
Am 22.05.20 um 17:58 schrieb Andrei Borzenkov:
The problem is, that sysctl.conf is being executed before the interfaces
get their eventual names.
That sounds like actual bug. What systemd version do you use?
At least it is, what the journal suggest, as seen below. However,
generally it sou
22.05.2020 15:44, Ede Wolf пишет:
> Hello,
>
> Thanks for replying. As I have written, I am using no custom .rules or
> .link file. /etc/udev/rules.d is empty and /etc/systemd/network only
> contains .network files.
>
This is irrelevant. *ANY* rule can set device name which will rename
interface
Found the reason for this global issue. The not working machine had not
been moved to SLAAC, as I've though it was, but had still been
configured statically.
Bummer.
As a workaround I have set default values:
net.ipv6.conf.default.stable_secret=
net.ipv6.conf.default.addr_gen_mode=2
net.ipv6
Hello,
Thanks for replying. As I have written, I am using no custom .rules or
.link file. /etc/udev/rules.d is empty and /etc/systemd/network only
contains .network files.
But I believe the problem would not change. As wether I rename an
interface or 99-default.link as part of systemd-networ
Do you have a udev 'persistent network device name' rules file in
/etc/udev/rules.d? Many distributions install such a rules file by
default, and this renames the interfaces to 'standard' names.
On Fri, May 22, 2020 at 3:47 AM Ede Wolf wrote:
>
> Hello,
>
> I am trying to enable temporary and/or
Hello,
I am trying to enable temporary and/or stable addresses for a link and
am most likely running into troubles with the device naming. However, I
do not change any network name myself, neither in udev nor as part or a
link file, it's just the standard system settings (from Arch, in case
t
Hello list,
I am using a VRF with multiple Wireguard interfaces in it, and it
contains one dummy interface with a /128 IPv6 and a /32 IPv4 on it, all
managed by systemd-networkd.
This works until I restart systemd-networkd via systemctl restart
systemd-networkd, afterwards I am not able to ping th
On Do, 07.05.20 10:00, [email protected] ([email protected]) wrote:
> Hi there!
>
> I'm on a Yocto system with latest v241 stable systemd. The odd thing
Latest stable systemd release is actually v245.
Consider updating, there's a good chance this already works on less
old systemd.
> is, that systemd-netw
I'm migrating a linux box to systemd-network use,
uname -rm
5.6.3-24.ge840c7b-default x86_64
rpm -qa | grep ^systemd-2
systemd-234-lp151.26.13.1.x86_64
systemctl list-unit-files | grep systemd-net
systemd-networkd-wait-onli
On Thu, 2 Apr 2020 at 15:32, Susant Sahani wrote:
>
> Itshould be like this
>
> [DHCPv4]
>
> SendHostname=true
>
> Hostname=myhostname
>
Thank you Susant that's what it was :)
___
systemd-devel mailing list
[email protected]
https://l
Itshould be like this
[DHCPv4]
SendHostname=true
Hostname=myhostname
Susant
From: systemd-devel
Date: Thursday, 2 April 2020 at 6:18 PM
To: systemd Mailing List
Subject: [systemd-devel] systemd-networkd override hostname not being sent to
DHCP
Hi
I have a network file like this
Hi
I have a network file like this:
---
[Match]
Name=enp2s0
[Network]
DHCP=ipv4
Domains=faster rstore
Hostname=myhostname
SendHostname=True
After saving the file, doing a systemctl daemon-reload and a
systemdctl restart systemd-networkd it would seem that this is still
not being applied.
On Mo, 22.07.19 20:28, Ratan Gupta ([email protected]) wrote:
> Hi Team,
>
> I came across a requirement why the link local address exist with other IP
> addresses for IPv4.
>
> Suppose if I enable the link local address through systemd-networkd then as
> per the existing
>
> behavior, l
Hi Team,
I came across a requirement why the link local address exist with other
IP addresses for IPv4.
Suppose if I enable the link local address through systemd-networkd then
as per the existing
behavior, link local address(169.254.*.*) will always exist on the
interface irrespective of
Care to open an issue at GitHub ?
On Fri, Jun 28, 2019 at 7:52 PM Christian Rohmann
wrote:
>
> Hello systemd-devel,
>
> after a recent update to systemd 241 my previously working GRE tunnel
> does not work anymore:
>
> Jun 28 13:58:54 localhost systemd-networkd[637]: mytunnel:
> vti/ipip/sit/gre/
Hello systemd-devel,
after a recent update to systemd 241 my previously working GRE tunnel
does not work anymore:
Jun 28 13:58:54 localhost systemd-networkd[637]: mytunnel:
vti/ipip/sit/gre/gretap/erspan tunnel without a local IPv4 address
configured in /etc/systemd/network/mytunnel.netdev. Ignor
Thank you for pointing this out. Unfortunately, the patch does not solve
the issue.
The problem does not exist on the stable version of systemd(v242). I will
consider the update of it.
On Tue, Jun 11, 2019 at 11:51 AM William Kennington
wrote:
> Probably related to this issue
> https://github.c
Probably related to this issue
https://github.com/systemd/systemd/pull/12350
On Tue, Jun 11, 2019 at 02:25 Kaisrlík, Jan wrote:
> Hello here,
>
> I am running Yocto-thud with systemd 239 on my SoC and I've found
> interesting, when DHCP lease was prolonged, I observe the connection
> to the int
Hello here,
I am running Yocto-thud with systemd 239 on my SoC and I've found
interesting, when DHCP lease was prolonged, I observe the connection
to the internet was completely stopped.
Based on the logs in the system I strongly believe it is connected to
moment when networkd renews a dhcp lease
Please open a RFE https://github.com/systemd/systemd.
Susant
On Tue, May 7, 2019 at 6:24 PM Arnaud Lemaire wrote:
>
> Hi there,
>
> I'm trying to set up network multipath routing with systemd, but I cannot
> find a way to do it cleanly.
>
> The part that I cannot set up is :
> ```
> $ ip route
On 07/05/19 6:23 pm, Arnaud Lemaire wrote:
Hi there,
I'm trying to set up network multipath routing with systemd, but I
cannot find a way to do it cleanly.
The part that I cannot set up is :
```
$ ip route
default
nexthop via 192.168.11.1 dev inet.11 weight 5
nexthop via 192
Thx I will try that, but it looks a little bit hackish.
No way to set the multipath routing with systemd-networkd?
If no, is it expected ? a feature request ? a bug ?
On Tue, May 7, 2019 at 3:23 PM Mantas Mikulėnas wrote:
> On Tue, May 7, 2019 at 3:54 PM Arnaud Lemaire wrote:
>
>> Hi there,
>>
On Mon, May 6, 2019 at 10:56 PM Andrei Borzenkov
wrote:
> 07.05.2019 4:22, Matt Zagrabelny пишет:
>
> > Is there a way to have systemd-network assign addressing to an interface
> > without the link being up?
> >
>
> man systemd.network
>
>ConfigureWithoutCarrier=
>A boolean. A
On Tue, May 7, 2019 at 3:54 PM Arnaud Lemaire wrote:
> Hi there,
>
> I'm trying to set up network multipath routing with systemd, but I cannot
> find a way to do it cleanly.
>
> The part that I cannot set up is :
> ```
> $ ip route
> default
> nexthop via 192.168.11.1 dev inet.11 weight 5
Hi there,
I'm trying to set up network multipath routing with systemd, but I cannot
find a way to do it cleanly.
The part that I cannot set up is :
```
$ ip route
default
nexthop via 192.168.11.1 dev inet.11 weight 5
nexthop via 192.168.22.2 dev inet.22 weight 10
...
```
I'm gett
07.05.2019 4:22, Matt Zagrabelny пишет:
> Greetings,
>
> I'm using Debian Buster with systemd 241-3.
>
> I have a computer (server) that is running isc-dhcpd and I have a hardwired
> interface with static addressing on the computer:
>
> $ cat /etc/systemd/network/eth-router.network
> [Match]
> M
Greetings,
I'm using Debian Buster with systemd 241-3.
I have a computer (server) that is running isc-dhcpd and I have a hardwired
interface with static addressing on the computer:
$ cat /etc/systemd/network/eth-router.network
[Match]
MACAddress=00:01:c0:1e:25:dd
[Network]
Address=172.20.20.1/2
d
seems not exist any more to the latest Bionic. 😞
Many Thanks!
-r
De : Mantas Mikulėnas
Envoyé : lundi, 16 juillet 2018 07:37
Cc : Systemd
Objet : Re: [systemd-devel] systemd-networkd-wait-online.service take too much
time
On Mon, Jul 16, 2018 at 1:
On Mon, Jul 16, 2018 at 1:13 AM Renato _
wrote:
> hello, am working to get my Bionic image working perfectly on my BareMetal.
> which is working perfectly fine on Xenial. But on Bionic I am facing to
> boot-latency issue with systemd. I googled it and I do not find
> interesting thing.
>
> Can so
hello, am working to get my Bionic image working perfectly on my BareMetal.
which is working perfectly fine on Xenial. But on Bionic I am facing to
boot-latency issue with systemd. I googled it and I do not find interesting
thing.
Can someone assist me to get a better troubleshoot?
Many Thanks
On 27 March 2018 at 10:22, Colin Guthrie wrote:
> Dimitri John Ledkov wrote on 26/03/18 11:34:
>> Hello,
>>
>> When systemd-networkd-wait-online was originally introduced, it was
>> the only tool that correctly waited and blocked the boot, until after
>> networking is configured.
>>
>> These days,
Dimitri John Ledkov wrote on 26/03/18 11:34:
> Hello,
>
> When systemd-networkd-wait-online was originally introduced, it was
> the only tool that correctly waited and blocked the boot, until after
> networking is configured.
>
> These days, however, all/most network configurations tools ship
> a
Hello,
When systemd-networkd-wait-online was originally introduced, it was
the only tool that correctly waited and blocked the boot, until after
networking is configured.
These days, however, all/most network configurations tools ship
appropriate wait-online integration. E.g. there is network-man
On Fr, 08.12.17 20:54, Johannes Ernst ([email protected]) wrote:
> Thanks. I’m not surprised that work remains ...
>
> Related question: systemd-networkd-wait-online.target seems to
> assume that once the network is online, it stays that way. I’d like
> to also take action when it goes dow
Thanks. I’m not surprised that work remains ...
Related question: systemd-networkd-wait-online.target seems to assume that once
the network is online, it stays that way. I’d like to also take action when it
goes down, and again when it comes back up. Any pointers how to best go about
this? Is t
On Di, 05.12.17 12:21, Johannes Ernst ([email protected]) wrote:
See the discussion on
https://github.com/systemd/systemd/issues/7478#issuecomment-348508263
regarding this kind of hardware.
Lennart
--
Lennart Poettering, Red Hat
___
systemd-dev
I’m running systemd 235.38 on an ARM64 device called the EspressoBin [1]. The
EspressoBin board has an on-board Ethernet switch, which I configure with
systemd-networkd (configuration is below). The device is intended as a home
router that runs IPv4 masquerading, local DNS server etc.
I’m attem
#3669 et. al. remove route and address from managed interfaces when the
carrier is lost.
However if there is no carrier at _boot_ and the interface has a static
IP address, then the address is _not_ removed.
Is this a bug, or should static IP be preserved on an interface even if
carrier is lost?
On 07/12/2017 12:06 AM, Mantas Mikulėnas wrote:
What global flags do each network's RAs have? If I remember correctly,
there are two, "Managed Addresses" and "Managed Other", which trigger
DHCPv6 – if neither of them is set, that is supposed to mean DHCPv6 is
unneeded.
The managed and other c
On Wed, Jul 12, 2017 at 9:32 AM, Andrei Borzenkov
wrote:
> On Wed, Jul 12, 2017 at 8:06 AM, Mantas Mikulėnas
> wrote:
> > On Tue, Jul 11, 2017, 22:24 Ian Pilcher wrote:
> >>
> >> On 07/11/2017 02:58 AM, Lennart Poettering wrote:
> >> > Note that DHCPv6 is not done unless IPv6 RA packets tell ne
On Wed, Jul 12, 2017 at 8:06 AM, Mantas Mikulėnas wrote:
> On Tue, Jul 11, 2017, 22:24 Ian Pilcher wrote:
>>
>> On 07/11/2017 02:58 AM, Lennart Poettering wrote:
>> > Note that DHCPv6 is not done unless IPv6 RA packets tell networkd to
>> > do so. Hence, areyou sure the RA spoken on your network
On Tue, Jul 11, 2017, 22:24 Ian Pilcher wrote:
> On 07/11/2017 02:58 AM, Lennart Poettering wrote:
> > Note that DHCPv6 is not done unless IPv6 RA packets tell networkd to
> > do so. Hence, areyou sure the RA spoken on your network properly
> > indicates that?
>
> Interesting. I am seeing somewh
On 07/11/2017 02:58 AM, Lennart Poettering wrote:
Note that DHCPv6 is not done unless IPv6 RA packets tell networkd to
do so. Hence, areyou sure the RA spoken on your network properly
indicates that?
Interesting. I am seeing somewhat different behavior (but note that
this is systemd-networkd 2
On 07/10/2017 08:23 PM, Ian Pilcher wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> I have "DHCP=yes" in the [Network] section of my WAN inte
On Mon, 10.07.17 22:23, Ian Pilcher ([email protected]) wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> I have "DHCP=yes" in the [Network
On Tue, Jul 11, 2017 at 6:23 AM, Ian Pilcher wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> […]
>
> For some reason, though, only the IPv4
I'm playing using systemd-networkd (rather than the legacy network
service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
interface once chrony is synced" thread for background.)
I have "DHCP=yes" in the [Network] section of my WAN interface
(eth0.256.network):
[Match]
Name=eth0.256
On Wed, Jun 21, 2017 at 10:55 AM, Jakob Schürz
wrote:
> Hi!
>
> I'm fiddeling around with network, to find out, how it works. I know,
> it's not made for use in Laptops moving in different networks.
>
> But there is a solution with wpa_supplicant to connect to different
> WLANs. I also found a So
Hi!
I'm fiddeling around with network, to find out, how it works. I know,
it's not made for use in Laptops moving in different networks.
But there is a solution with wpa_supplicant to connect to different
WLANs. I also found a Solution when i connect to my mobile phone, using
usb-thetering for th
On Wed, 15.02.17 00:47, Zhou, Luwei ([email protected]) wrote:
> Hi Lennart,
>
> Thanks for the reply. Is there any command to check whether networkd
> has been installed in my image. I can find the systemd-nspawn and
> many system-* in my image. Is the networkd part of systemd package?
> Sor
ttering [mailto:[email protected]]
Sent: Tuesday, February 14, 2017 6:59 PM
To: Zhou, Luwei
Cc: [email protected]
Subject: Re: [systemd-devel] systemd-networkd meet the error of "No such file or
directory"
On Tue, 14.02.17 07:50, Zhou, Luwei ([email protected]) wrote:
Hi,
: Lennart Poettering [mailto:[email protected]]
Sent: Tuesday, February 14, 2017 6:59 PM
To: Zhou, Luwei
Cc: [email protected]
Subject: Re: [systemd-devel] systemd-networkd meet the error of "No such file
or directory"
On Tue, 14.02.17 07:50, Zhou, Luwei (luwei.z...
On Tue, 14.02.17 07:50, Zhou, Luwei ([email protected]) wrote:
> Hi,
>
> I am not sure this the place where I can post my problems. Sorry for
> broadcasting to the mailist.
> I am systemd 2.25 version on yocto linux. I meet a problem when try to
> enable systemd-networkd.service. It seems
Hi,
I am not sure this the place where I can post my problems. Sorry for
broadcasting to the mailist.
I am systemd 2.25 version on yocto linux. I meet a problem when try to enable
systemd-networkd.service. It seems I have followed the rule of
system-networkd.service but cannot find the file.
1 - 100 of 354 matches
Mail list logo
