Package: ifupdown
Version: 0.8.35
Severity: important
Tags: ipv6
Dear Maintainer,
iI have a network where machines get ULA-SLAAC-addresses via router
advertisments (router is a pfsense).
If I want to set an address to a static address after the machine has
acquired an ULA-SLAAC (e. g. during installation), the SLAAC-address
reamains active. It also will be actively used by the system for
communication (e.g. ping, telnet etc.). If I remove the SLAAC-address
with ip addr del .... it wil imediately gets re-added to the system and
be used for communication. The static ipv6 address is showing up with ip
addr and can be accessed from outside, but it ist not acitvely used for
outside communication.
I had to manually set the preferred lifetime with ip addr change ...
preferred_lifetime 5 and wait till the address gets deprecated. Then I
was able to remove it permanently.
I don't think this is the correct behaviour, as I have another network
with valid public ipv6-Addresses which I get from my ISP (also pfsense
is the router). If a machine gets (public) SLAAC during the installation
and I configure the machine to use a static ULA address afterwards, the
(public) SLAAC-addresses immediately gets removed and the static ULA is
used for communication.
The configuration on both machines were the same. I set a static ipv6 in
/etc/network/interfaces with the option autoconf 0.
I expected the same behaviour in both situations.
-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ens160
iface ens160 inet dhcp
# This is an autoconfigured IPv6 interface
iface ens160 inet6 static
address fdb3:27fb:4170:20::153
netmask 64
autoconf 0
--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory
--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 256 Apr 1 2016 resolvconf
/etc/network/if-post-down.d:
total 0
/etc/network/if-pre-up.d:
total 0
/etc/network/if-up.d:
total 4
-rwxr-xr-x 1 root root 817 Apr 1 2016 000resolvconf
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ifupdown depends on:
ii adduser 3.118
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii lsb-base 10.2019051400
Versions of packages ifupdown recommends:
ii dhcpcd5 [dhcp-client] 7.1.0-2
ii isc-dhcp-client [dhcp-client] 4.4.1-2
Versions of packages ifupdown suggests:
pn ppp <none>
pn rdnssd <none>
-- no debconf information
