Known Issues with DHCP and IP Configuration Requirements
DHCP has problems on OS image versions 3 through 5.X.X. It is required on these image versions to use static IP addresses or re-image the device with version 6.0.0 or higher if DHCP is required or preferred. This documentation is to catalog the associated problems using DHCP with older OS versions.
OS Images 3 - 4.1
OS image versions 3 through 4.1 use dhcpcd-3.2.3 which contains a bug where duplicate address (IP conflict) detection is broken. If there is an IP conflict, the DHCP client will get an ARP reply from another device that has the duplicate address and send a DECLINE message to the DHCP server. The DHCP server ignores the DECLINE message (possibly due to an incorrectly formatted DECLINE message) and continues offering the same conflicting IP address over and over again. The DHCP client will continue requesting and declining new leases until the device with the conflicting IP address is powered off, or until the terminal is powered off. This will appear in /var/log/messages with similar repeated messages:
Aug 25 06:52:12 PSVA10300201400D649600 dhcpcd[1718]: eth0: broadcasting for a lease
Aug 25 06:52:12 PSVA10300201400D649600 dhcpcd[1718]: eth0: offered 192.168.1.103 from 192.168.1.55
Aug 25 06:52:12 PSVA10300201400D649600 dhcpcd[1718]: eth0: checking 192.168.1.103 is available on attached networks
Aug 25 06:52:12 PSVA10300201400D649600 dhcpcd[1718]: eth0: ARPOP_REPLY received from 192.168.1.103 (00:11:4b:02:46:6c)
Aug 25 06:52:12 PSVA10300201400D649600 dhcpcd[1718]: eth0: sleeping for 10 seconds
Aug 25 06:52:22 PSVA10300201400D649600 dhcpcd[1718]: eth0: broadcasting for a lease
Aug 25 06:52:22 PSVA10300201400D649600 dhcpcd[1718]: eth0: offered 192.168.1.103 from 192.168.1.55
Aug 25 06:52:22 PSVA10300201400D649600 dhcpcd[1718]: eth0: checking 192.168.1.103 is available on attached networks
Aug 25 06:52:22 PSVA10300201400D649600 dhcpcd[1718]: eth0: ARPOP_REPLY received from 192.168.1.103 (00:11:4b:02:46:6c)
Aug 25 06:52:22 PSVA10300201400D649600 dhcpcd[1718]: eth0: sleeping for 10 seconds
OS Images 4.2.0 - 4.3.3
OS image versions 4.2.0 through 4.3.3 use dhclient-4.2.4. OpenSUSE removed the duplicate address detection feature from dhclient-4.2.4. A patch was created that reintroduced this functionality. These versions sometimes do not set a default gateway.
OS Images 6.0.0 - 6.0.5
Tablet version 6.0.0 uses wicked-0.6.39 with an appropriate DHCLIENT_WAIT_AT_BOOT time set to 30 seconds.
Terminal OS image versions 6.0.1 uses wicked-0.6.31 and OS image version 6.0.5 uses wicked-0.6.39. The only known issue with these versions is that Wicked doesn't wait long enough before continuing in the background so display-manager, Firefox, etc. are sometimes started before the network is up. The default of DHCLIENT_WAIT_AT_BOOT time is 15 seconds.
OS Images 6.0.6 - 6.1.0
Terminal OS image versions 6.0.6 - 6.0.7 with an appropriate DHCLIENT_WAIT_AT_BOOT time set to 30 seconds.
Terminal OS image version 6.1.0 uses wicked-0.6.40 with an appropriate DHCLIENT_WAIT_AT_BOOT time set to 30 seconds.
Tablet OS image version 6.1.0 uses wicked-0.6.40 with an appropriate DHCLIENT_WAIT_AT_BOOT time set to 30 seconds. These versions have a DHCP requirement because we cannot use YaST to configure static routes.
Terminals
|
OS Image Versions |
DHCP Client |
Known Issues |
Static IP required? |
|
3 - 4.1 |
dhcpcd |
These version have broken IP conflict detection. |
Yes |
|
4.2.0 - 4.3.3 |
dhclient |
These versions sometimes do not set a default gateway. |
Yes |
|
6.0.1 - 6.0.5 |
wicked |
Wicked doesn't wait long enough before continuing in the
background so |
No |
|
6.0.6 - 6.1.0 |
Wicked |
None. |
No |
Tablets
|
OS Image Versions |
DHCP Client |
Known Issues |
Static IP required? |
DHCP required? |
|
5.0.4 - 5.3.4 |
dhclient |
These versions sometimes do not set a default gateway. |
Yes |
No |
|
6.0.0 |
wicked |
None. |
No |
No |
|
6.1.0+ |
wicked |
These versions have a DHCP requirement because we cannot use YaST to configure static routes. |
No |
Yes |