You are not logged in.
I am not entirely sure this is an issue or a mistake of configuration on my part, but I noticed that the DHCP server finds its own MAC on the network and the offers an IP address. Wether I place a fixed IP on the conf file for the server or not I noticed this behavior, this is what the log file shows:
Jan 21 17:46:48 arch dhcpd[18097]: DHCPDISCOVER from fc:aa:14:55:9e:3d via enp2s0
Jan 21 17:46:48 arch dhcpd[18097]: DHCPOFFER on 192.168.25.2 to fc:aa:14:55:9e:3d via enp2s0
Jan 21 17:47:52 arch dhcpd[18097]: DHCPDISCOVER from fc:aa:14:55:9e:3d via enp2s0
Jan 21 17:47:52 arch dhcpd[18097]: DHCPOFFER on 192.168.25.2 to fc:aa:14:55:9e:3d via enp2s0
To me this doesn't seem very problematic, but it generates unnecessary logs. Is there a way to make the dhcp server ignore its own MAC address?
Offline
Offline
Coret, you mention that setting a static ip doesn't work. Elaborating on slithery's suggestion, ensure that you have disabled dhcp client service on the server.
Offline
I set the server with a fixed IP using netctl configuration, here is the file:
Interface=enp2s0
Connection=ethernet
IP=static
Address=('192.168.25.2/24')
Gateway=('192.168.25.1')
DNS=('192.168.25.1')
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
IP6=no
I do believe that is all that I needed to do.
I still think, based on the logs, that the DHCP server "saw" that mac address on the network and offered the IP address. Though to be sure I would need to use TCP dump and analyze the network packages...
Offline
Managed to fix it, turns out there a configuration on the dhcpd conf file that can be used to ignore a mac address. With that in place there were no more of those logs messages.
Offline