I think so Henk. AFAIU, those addresses come ‘automatically’ as the result of the link-layer Neighbor Discovery Protocol (NDP). You would need to disable IPv6 in the kernel to inhibit this.
Autoconfiguration IPv6 makes the network “plug and play” capable, which means that a newly set up system integrates into the (local) network without any manual configuration. The new host uses its automatic configuration mechanism to derive its own address from the information made available by the neighboring routers, relying on a protocol called the neighbor discovery (ND) protocol. This method does not require any intervention on the administrator’s part and there is no need to maintain a central server for address allocation—an additional advantage over IPv4, where automatic address allocation requires a DHCP server.
Nevertheless if a router is connected to a switch, the router should send periodic advertisements with flags telling the hosts of a network how they should interact with each other. For more information, see RFC 2462 and the radvd.conf(5) man page, and RFC 3315.
Thanks. I thought that this would work, but your quote provides more detail.
I am going to try systemd-networking, because it takes ~28secs for wicked to get started of which I am waiting for it ~10 secs. And that for something that only requires the equivalent of
Used YaST > System > Network Settngs for configuration of all below;
Wicked;
no DHCP;
thus fixed IP address, netmask, hostname (in /etc/hosts);
also three DNS server and a search.
Manual preparations:
rm /etc/resolv.conf (thus undoing the symlink) and create a new /etc/resolv.conf with the same contents (a search statement and three nameserver statements, ymmv) without the comments.
create a /etc/systemd/network/20-wired.network with contents adapted to what is show in earlier posts here.
Then to stop all wicked (4 processes in my case) and to block it from starting again at boot:
YaST > System > Network Settings; in the tab General Options, the first item, change from Wicked to Switched off (or similar wording).
You can check what happens before and after by looking with YaST > System > Services Manager (scroll down to wicked …) and also with
ps -ef | grep wicked
To set systemd-network doing it’s thing at boot:
systemctl enable systemd-networkd.service
or using YaST > System > Services Manager (scroll down to systemd-network and switch).
You can not check for a running process (deamon) here because it only runs at boot (and that is what we want).
Reboot and everything was fine (well, I made a typo in 20-wired.network, but that is my stupidity; was edited and did a systemctl restart systemd-networkd.service ).