I'm running Debian-Stretch 9.4 and I'm observing a similar problem that after some time my servers disappears from the network; usually first the IPv6 address, the usually some time later the IPv4 address, but not always.
All computers are connected to my FritzBox 7420:
- for IPv4 I'm using the fixed address 192.168.xxx.33/24, which the FritzBox always assigns only to that host.
- for IPv6 I get a daily changing IPv6 address from my internet provider each night, which gets propagated by RA.
The affected host is using systemd 232-25+deb9u2 and I have configured systemd-networkd to do the network configuration:
For now I have disabled DHCP for ipv4 and switched to a static configuration, as it sometimes happens that the network is flacky and does not receive an address during boot at all.
While I had that custom version running I did *not* observe those issues, but then Debian shipped a security update and since than the problem is back.
This might not be the same issue as there have been different comments in this issue mentioning ifupdown, NetworkManager, ..., but perhaps affected users should clarify their environment, e.g. IPv4 and/or IPv6, static addresses or changing addresses/prefixes, ...
I'm running Debian-Stretch 9.4 and I'm observing a similar problem that after some time my servers disappears from the network; usually first the IPv6 address, the usually some time later the IPv4 address, but not always.
All computers are connected to my FritzBox 7420:
- for IPv4 I'm using the fixed address 192.168.xxx.33/24, which the FritzBox always assigns only to that host.
- for IPv6 I get a daily changing IPv6 address from my internet provider each night, which gets propagated by RA.
The affected host is using systemd 232-25+deb9u2 and I have configured systemd-networkd to do the network configuration:
/etc/systemd/ network/ 40-dhcp. network
DHCP=ipv4
IPv6AcceptRA=yes
For now I have disabled DHCP for ipv4 and switched to a static configuration, as it sometimes happens that the network is flacky and does not receive an address during boot at all.
I once compiled my own version of systems with this patch included: /github. com/systemd/ systemd/ pull/6918/ commits/ 7f676aa324cb549 8a5f9caaaa3d51e cfe53242e0> /github. com/systemd/ systemd/ issues/ 5625>.
<https:/
It is for <https:/
While I had that custom version running I did *not* observe those issues, but then Debian shipped a security update and since than the problem is back.
This might not be the same issue as there have been different comments in this issue mentioning ifupdown, NetworkManager, ..., but perhaps affected users should clarify their environment, e.g. IPv4 and/or IPv6, static addresses or changing addresses/prefixes, ...