Porteus

Posted: **23 Aug 2018, 10:59**

We have a number of kiosk terminals deployed running release 4.7.0 and every time any of them restart our Windows 2012 DHCP server generates one or more 'BAD_ADDRESS' records, using up IP addresses from the pool.

Has anyone else come across this behaviour and are there any known fixes? At the moment I've had to shorted the DHCP lease duration to ensure our address pool doesn't get exhausted. Ad this is a company network I don't get any choice other than running a Windows DHCP server so I need to find a way to make it play happily with the Porteus kiosk clients.

Posted: **23 Aug 2018, 16:16**

On the client side default option in /etc/dhcpcd.conf is 'duid':

Code: Select all

# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

We have switched to 'clientid' by default as nothing is persistent in kiosk except for MAC and i thought this would be a logical choice:

Code: Select all

# Use the hardware address of the interface for the Client ID.
clientid

So you could remaster the ISO, edit 003-settings.xzm and set 'duid' as default instead of 'clientid'.

Not sure if this helps but there is no harm to try.

Porteus

DHCP filling up with BAD_ADDRESS

DHCP filling up with BAD_ADDRESS

DHCP filling up with BAD_ADDRESS