The host computer receives an arbitrary IPv6 address that does not match what is listed in the server’s dhcpd6 configuration. There is no difficulty with IPv4 address assignment.
This is just an example - you need to find out what kind of DUID your client is using. Assuming you are using wicked (you never told us), you can obtain it with
I made the change to configuration file, adding the DUID option. The local host is still receiving the undesired IP address. Is there another step required to have the server acknowledge the changed configuration, and send the IP address indicated.
Wicked is NOT a DHCP server, wicked is the software that manages your network inside your system.
Use say you (try to) use DHCP. That means that your system is the DHCP client. And that there must be a DHCP server on your network. Very often that DHCP server is in the router to the internet. The question is to tell us what (you think) is the DHCP server used by your system. And of course the plain answer “router” will not really help: make and type is what is asked for.
Ah. Correct.
I have not had to think about DHCP in quite a long time, more than a year at least. IPv6 had been delegated to a separate server and is functioning as expected. I apologize for the confusion.
DHCP4, however, is not running. An attempt to start it ended with this:
Internet Systems Consortium DHCP Server 4.3.6-P1
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Config file: /etc/dhcpd.conf
Database file: /db/dhcpd.leases
PID file: /var/run/dhcpd.pid
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 39 leases to leases file.
No subnet declaration for eth0 (no IPv4 addresses).
** Ignoring requests on eth0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth0 is attached. **
Not configured to listen on any interfaces!
I do not recall ever having to declare a port (eth0) for dhcp. Nor can I find any information that would enlighten me.
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.69.115/24 brd 192.168.69.255 scope global enp4s0
inet6 fd2f:4760:521f:3f3c::c0a8:45ec/64 scope global dynamic noprefixroute
inet6 fd2f:4760:521f:3f3c::c0a8:4573/64 scope global
IP ending with “:4573” is the desired IP. “:45ec” is the one repeatedly being assigned. by DHCP. (While the IPv4 address 192.168.69.115 is correct, I do not know where it originates.) The IPv6 DHCP server is a Sonicwall tz350 firewall unit.
That’s not what “functioning as expected” implies.
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 <br>
inet 192.168.69.115/24 brd 192.168.69.255 scope global enp4s0 <br>
inet6 fd2f:4760:521f:3f3c::c0a8:45ec/64 scope global dynamic noprefixroute <br>
inet6 fd2f:4760:521f:3f3c::c0a8:4573/64 scope global
IP ending with ":4573" is the desired IP.
This address is configured on interface. Where does it come from?
“:45ec” is the one repeatedly being assigned. by DHCP. (While the IPv4 address 192.168.69.115 is correct, I do not know where it originates.) The IPv6 DHCP server is a Sonicwall tz350 firewall unit.
We are back on square one. What DHCP server do you use? (And no, Sonicwall is not the answer. We have no idea what is inside). If you do not know - ask on support channels for your firewall appliance how to configure it to assign static addresses. Also appliances in general use so heavily customized (and often outdated) software that even knowing what it corresponds to may not really help so asking support channels is the best option anyway.
On client side if you are using wicked you may try to delete /var/lib/wicked/lease-* files to force it to request new lease. Stop network, delete files, start network.