DHCP client will not acquire DHCP address.

SUSE Linux Enterprise Server SLES Networking
1

After having installed a system with AutoYast, eth0 is configured for DHCP. dhcp-client is installed. However, when it tries to acquire an address, this shows up in the logs, and eth0 ends up with no address. Any ideas?

This is SLES11 SP2 on Intel Hardware. lspci below.

Dec 13 09:36:38 linux ifup-dhcp: eth0 Starting DHCP4 client
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: dhcpcd 3.2.3 starting
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: hardware address = 00:1e:67:47:49:5e
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: broadcasting for a lease
Dec 13 09:36:47 linux dhcpcd[7652]: eth0: offered 10.1.4.2 from 10.1.0.10
Dec 13 09:36:47 linux dhcpcd[7652]: eth0: checking 10.1.4.2 is available on attached networks
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: leased 10.1.4.2 for 21600 seconds
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding IP address 10.1.4.2/16
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding route to 0.255.255.0/32 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding route to 1.0.0.0/10 via 0.255.255.0 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding default route via 10.1.255.1 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: setting hostname to `shadow-2’
Dec 13 09:36:49 shadow-2 dhcpcd[7652]: eth0: exiting
Dec 13 09:36:49 shadow-2 ifup-dhcp: eth0 IP address: 10.1.4.2/16
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: received SIGTERM, stopping
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing route to 1.0.0.0/10 via 0.255.255.0 metric 0
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: No such process
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing default route via 10.1.255.1 metric 0
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: No such process
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing IP address 10.1.4.2/16
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: Cannot assign requested address
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: exiting

00:00.0 Host bridge: Intel Corporation Sandy Bridge DMI2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 1a (rev 07)
00:01.1 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 1b (rev 07)
00:02.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 2a (rev 07)
00:02.2 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 2c (rev 07)
00:03.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 3a in PCI Express Mode (rev 07)
00:04.0 System peripheral: Intel Corporation Sandy Bridge DMA Channel 0 (rev 07)
00:04.1 System peripheral: Intel Corporation Sandy Bridge DMA Channel 1 (rev 07)
00:04.2 System peripheral: Intel Corporation Sandy Bridge DMA Channel 2 (rev 07)
00:04.3 System peripheral: Intel Corporation Sandy Bridge DMA Channel 3 (rev 07)
00:04.4 System peripheral: Intel Corporation Sandy Bridge DMA Channel 4 (rev 07)
00:04.5 System peripheral: Intel Corporation Sandy Bridge DMA Channel 5 (rev 07)
00:04.6 System peripheral: Intel Corporation Sandy Bridge DMA Channel 6 (rev 07)
00:04.7 System peripheral: Intel Corporation Sandy Bridge DMA Channel 7 (rev 07)
00:05.0 System peripheral: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management (rev 07)
00:05.2 System peripheral: Intel Corporation Sandy Bridge Control Status and Global Errors (rev 07)
00:05.4 PIC: Intel Corporation Sandy Bridge I/O APIC (rev 07)
00:11.0 PCI bridge: Intel Corporation Patsburg PCI Express Virtual Root Port (rev 06)
00:16.0 Communication controller: Intel Corporation Patsburg MEI Controller #1 (rev 05)
00:16.1 Communication controller: Intel Corporation Patsburg MEI Controller #2 (rev 05)
00:1a.0 USB controller: Intel Corporation Patsburg USB2 Enhanced Host Controller #2 (rev 06)
00:1c.0 PCI bridge: Intel Corporation Patsburg PCI Express Root Port 1 (rev b6)
00:1c.7 PCI bridge: Intel Corporation Patsburg PCI Express Root Port 8 (rev b6)
00:1d.0 USB controller: Intel Corporation Patsburg USB2 Enhanced Host Controller #1 (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Patsburg LPC Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation Patsburg 6-Port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation Patsburg SMBus Host Controller (rev 06)
02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
02:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
02:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
02:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.0 Network controller: Mellanox Technologies MT27500 Family [ConnectX-3]
07:00.0 Serial Attached SCSI controller: Intel Corporation Patsburg 4-Port SATA Storage Control Unit (rev 06)
07:00.3 SMBus: Intel Corporation Patsburg SMBus Controller 0 (rev 06)
09:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200e [Pilot] ServerEngines (SEP1) (rev 05)
7f:08.0 System peripheral: Intel Corporation Sandy Bridge QPI Link 0 (rev 07)
7f:09.0 System peripheral: Intel Corporation Sandy Bridge QPI Link 1 (rev 07)
7f:0a.0 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 0 (rev 07)
7f:0a.1 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 1 (rev 07)
7f:0a.2 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 2 (rev 07)
7f:0a.3 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 3 (rev 07)
7f:0b.0 System peripheral: Intel Corporation Sandy Bridge Interrupt Control Registers (rev 07)
7f:0b.3 System peripheral: Intel Corporation Sandy Bridge Semaphore and Scratchpad Configuration Registers (rev 07)
7f:0c.0 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0c.1 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0c.2 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0c.3 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0c.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller System Address Decoder 0 (rev 07)
7f:0c.7 System peripheral: Intel Corporation Sandy Bridge System Address Decoder (rev 07)
7f:0d.0 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0d.1 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0d.2 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0d.3 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
7f:0d.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller System Address Decoder 1 (rev 07)
7f:0e.0 System peripheral: Intel Corporation Sandy Bridge Processor Home Agent (rev 07)
7f:0e.1 Performance counters: Intel Corporation Sandy Bridge Processor Home Agent Performance Monitoring (rev 07)
7f:0f.0 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Registers (rev 07)
7f:0f.1 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller RAS Registers (rev 07)
7f:0f.2 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 0 (rev 07)
7f:0f.3 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 1 (rev 07)
7f:0f.4 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 2 (rev 07)
7f:0f.5 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 3 (rev 07)
7f:0f.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 4 (rev 07)
7f:10.0 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 0 (rev 07)
7f:10.1 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 1 (rev 07)
7f:10.2 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 0 (rev 07)
7f:10.3 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 1 (rev 07)
7f:10.4 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 2 (rev 07)
7f:10.5 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 3 (rev 07)
7f:10.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 2 (rev 07)
7f:10.7 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 3 (rev 07)
7f:11.0 System peripheral: Intel Corporation Sandy Bridge DDRIO (rev 07)
7f:13.0 System peripheral: Intel Corporation Sandy Bridge R2PCIe (rev 07)
7f:13.1 Performance counters: Intel Corporation Sandy Bridge Ring to PCI Express Performance Monitor (rev 07)
7f:13.4 Performance counters: Intel Corporation Sandy Bridge QuickPath Interconnect Agent Ring Registers (rev 07)
7f:13.5 Performance counters: Intel Corporation Sandy Bridge Ring to QuickPath Interconnect Link 0 Performance Monitor (rev 07)
7f:13.6 System peripheral: Intel Corporation Sandy Bridge Ring to QuickPath Interconnect Link 1 Performance Monitor (rev 07)
80:01.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 1a (rev 07)
80:02.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 2a (rev 07)
80:03.0 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 3a in PCI Express Mode (rev 07)
80:03.2 PCI bridge: Intel Corporation Sandy Bridge IIO PCI Express Root Port 3c (rev 07)
80:04.0 System peripheral: Intel Corporation Sandy Bridge DMA Channel 0 (rev 07)
80:04.1 System peripheral: Intel Corporation Sandy Bridge DMA Channel 1 (rev 07)
80:04.2 System peripheral: Intel Corporation Sandy Bridge DMA Channel 2 (rev 07)
80:04.3 System peripheral: Intel Corporation Sandy Bridge DMA Channel 3 (rev 07)
80:04.4 System peripheral: Intel Corporation Sandy Bridge DMA Channel 4 (rev 07)
80:04.5 System peripheral: Intel Corporation Sandy Bridge DMA Channel 5 (rev 07)
80:04.6 System peripheral: Intel Corporation Sandy Bridge DMA Channel 6 (rev 07)
80:04.7 System peripheral: Intel Corporation Sandy Bridge DMA Channel 7 (rev 07)
80:05.0 System peripheral: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management (rev 07)
80:05.2 System peripheral: Intel Corporation Sandy Bridge Control Status and Global Errors (rev 07)
80:05.4 PIC: Intel Corporation Sandy Bridge I/O APIC (rev 07)
ff:08.0 System peripheral: Intel Corporation Sandy Bridge QPI Link 0 (rev 07)
ff:09.0 System peripheral: Intel Corporation Sandy Bridge QPI Link 1 (rev 07)
ff:0a.0 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 0 (rev 07)
ff:0a.1 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 1 (rev 07)
ff:0a.2 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 2 (rev 07)
ff:0a.3 System peripheral: Intel Corporation Sandy Bridge Power Control Unit 3 (rev 07)
ff:0b.0 System peripheral: Intel Corporation Sandy Bridge Interrupt Control Registers (rev 07)
ff:0b.3 System peripheral: Intel Corporation Sandy Bridge Semaphore and Scratchpad Configuration Registers (rev 07)
ff:0c.0 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0c.1 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0c.2 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0c.3 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0c.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller System Address Decoder 0 (rev 07)
ff:0c.7 System peripheral: Intel Corporation Sandy Bridge System Address Decoder (rev 07)
ff:0d.0 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0d.1 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0d.2 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0d.3 System peripheral: Intel Corporation Sandy Bridge Unicast Register 0 (rev 07)
ff:0d.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller System Address Decoder 1 (rev 07)
ff:0e.0 System peripheral: Intel Corporation Sandy Bridge Processor Home Agent (rev 07)
ff:0e.1 Performance counters: Intel Corporation Sandy Bridge Processor Home Agent Performance Monitoring (rev 07)
ff:0f.0 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Registers (rev 07)
ff:0f.1 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller RAS Registers (rev 07)
ff:0f.2 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 0 (rev 07)
ff:0f.3 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 1 (rev 07)
ff:0f.4 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 2 (rev 07)
ff:0f.5 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 3 (rev 07)
ff:0f.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Target Address Decoder 4 (rev 07)
ff:10.0 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 0 (rev 07)
ff:10.1 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 1 (rev 07)
ff:10.2 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 0 (rev 07)
ff:10.3 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 1 (rev 07)
ff:10.4 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 2 (rev 07)
ff:10.5 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller Channel 0-3 Thermal Control 3 (rev 07)
ff:10.6 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 2 (rev 07)
ff:10.7 System peripheral: Intel Corporation Sandy Bridge Integrated Memory Controller ERROR Registers 3 (rev 07)
ff:11.0 System peripheral: Intel Corporation Sandy Bridge DDRIO (rev 07)
ff:13.0 System peripheral: Intel Corporation Sandy Bridge R2PCIe (rev 07)
ff:13.1 Performance counters: Intel Corporation Sandy Bridge Ring to PCI Express Performance Monitor (rev 07)
ff:13.4 Performance counters: Intel Corporation Sandy Bridge QuickPath Interconnect Agent Ring Registers (rev 07)
ff:13.5 Performance counters: Intel Corporation Sandy Bridge Ring to QuickPath Interconnect Link 0 Performance Monitor (rev 07)
ff:13.6 System peripheral: Intel Corporation Sandy Bridge Ring to QuickPath Interconnect Link 1 Performance Monitor (rev 07)

2

It looks like for about eighty seconds eth0 does have an IP address. Are
you sure it was not there and then removed by something later as the logs
show (see timestamps)?

Also what is the output if you run the following command as ‘root’:

Code:

/usr/sbin/dhcpcd-test eth0

Do other systems on the same network, configured for DHCP, work? Does the
DHCP service give out specific IPs to specific systems based on Mac
address or anything?

I rarely watch my dhcp logs closely on clients since it usually “Just
Works” ™ but a few of your routes look pretty strange. Having the IP
address of the system here be in a full class B network also seems
strange, but perhaps the network is not really comprised of 65534 boxes
and it is how you have it setup, but the really strange stuff includes
‘adding route to 0.255.255.0/32’, and ‘adding route to 1.0.0.0/10 via
0.255.255.0 metric 0’.

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

3

Hi jkugler,

[QUOTE=jkugler;18056]After having installed a system with AutoYast, eth0 is configured for DHCP. dhcp-client is installed. However, when it tries to acquire an address, this shows up in the logs, and eth0 ends up with no address. Any ideas?

This is SLES11 SP2 on Intel Hardware. lspci below.

Dec 13 09:36:38 linux ifup-dhcp: eth0 Starting DHCP4 client
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: dhcpcd 3.2.3 starting
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: hardware address = 00:1e:67:47:49:5e
Dec 13 09:36:38 linux dhcpcd[7652]: eth0: broadcasting for a lease
Dec 13 09:36:47 linux dhcpcd[7652]: eth0: offered 10.1.4.2 from 10.1.0.10
Dec 13 09:36:47 linux dhcpcd[7652]: eth0: checking 10.1.4.2 is available on attached networks
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: leased 10.1.4.2 for 21600 seconds
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding IP address 10.1.4.2/16
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding route to 0.255.255.0/32 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding route to 1.0.0.0/10 via 0.255.255.0 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: adding default route via 10.1.255.1 metric 0
Dec 13 09:36:48 linux dhcpcd[7652]: eth0: setting hostname to `shadow-2’
Dec 13 09:36:49 shadow-2 dhcpcd[7652]: eth0: exiting
Dec 13 09:36:49 shadow-2 ifup-dhcp: eth0 IP address: 10.1.4.2/16
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: received SIGTERM, stopping
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing route to 1.0.0.0/10 via 0.255.255.0 metric 0
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: No such process
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing default route via 10.1.255.1 metric 0
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: No such process
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: removing IP address 10.1.4.2/16
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: netlink: Cannot assign requested address
Dec 13 09:38:07 shadow-2 dhcpcd[8536]: eth0: exiting[/QUOTE]

well, as ab already pointed out, this does look pretty strange to me:

  • “eth0: adding IP address 10.1.4.2/16” is good - you have your IP address
  • “eth0: adding route to 0.255.255.0/32 metric 0” Why would you have an IP address of “0.255.255.0” on some router?
  • “eth0: adding route to 1.0.0.0/10 via 0.255.255.0 metric 0” … and why/how could you route packets to it?
  • “eth0: adding default route via 10.1.255.1 metric 0” would be expected and fits the interface configuration

If that “0.255.255.0” business is really intended, I’d like to learn what it’s about :slight_smile: But most probably this is the part where things fail and the adater is taken down again. As I read RFC 1122, section 3.2.1.3, list item (b), sending a packet to that address is in violation of the RFC, so using this address as the target address is invalid.

Could you please run “dhcpcd-test eth0” on that machine and report back the results?

Regards,
Jens