Broadcasting for lease

When checking messages I many times get the following:

Jul 30 06:15:22 tower dhcpcd[31343]: eth0: broadcasting for a lease
Jul 30 06:15:22 tower dhcpcd[31343]: eth0: offered 192.168.1.2 from 192.168.1.1
Jul 30 06:15:22 tower dhcpcd[31343]: eth0: received NAK: (null)
Jul 30 06:15:23 tower dhcpcd[31343]: eth0: broadcasting for a lease
Jul 30 06:15:23 tower dhcpcd[31343]: eth0: offered 192.168.1.2 from 192.168.1.1
Jul 30 06:15:23 tower dhcpcd[31343]: eth0: received NAK: (null)
Jul 30 06:15:24 tower dhcpcd[31343]: eth0: broadcasting for a lease
Jul 30 06:15:24 tower dhcpcd[31343]: eth0: offered 192.168.1.2 from 192.168.1.1
Jul 30 06:15:24 tower dhcpcd[31343]: eth0: received NAK: (null)

I have a netgear WNR 1000v3 set as the DHCP server with 192.168.1.2 reserved for tower, and the address space starting at 192.168.1.2.

Network access is never interrupted.

My opensuse 12.1 is up to date.

Does anyone have any idea why the lease request keeps being broadcast?

Any and all help appreciated.

I don’t know the cause. I have seen DHCP problems when using “dhcpcd”, so I usually switch to using “dhclient”.

You can change in Yast, with “System” → “/etc/sysconfig” → “network” → “DHCP” → “DHCP client” → “DHCLIENT_BIN”

(added in edit) - there is some sort of miscommunication between dhcpcd and your DHCP server.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This can happen in a couple of cases I (or coworkers) have seen:

Multiple DHCP servers on the network.
Virus sending out NAKs for fun.
Other less-likely things.

Get a LAN trace with tcpdump and post it somewhere for review:

sudo /usr/sbin/tcpdump -n -s 0 -w /tmp/dhcp-nak0.cap

While that is running do the tests or verify the lines keep showing up
in /var/log/messages and once that is done use Ctrl+c to stop the
capture and then post it somewhere.

Good luck.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQGC/0AAoJEF+XTK08PnB5PgQP+wcIJVyf/9kihBNYCPkm2JrJ
u27YyQR7YPQg38tx1mHpIFC/qJyB0/BeruEdhLRJCo77Dnf2ofz08gNA753wgKWS
u9syvpwZ9ux9bkcZg73GucwBo7ZG/dQ8hZhluMdSlCzCz4CfCxUQjW2BamLCMZ3K
z8XLXaXQOnA2/03Blfz1rYLrsq0hs/4uZlVQ0AgS0NVlqVZTLtkLiNaWqQta1cjQ
NR6cg4tdUVfUG+q5HX+atYeZ7XkrNmHWoQGoK43HRWtlo6U9XrSWzObiGHlyApxT
5kfCPC8PVDouFndMn9UjVtc/nwiJoyPAYV1nI0ky+YPtkqvf8kajvDSwyKT05zqP
+OFtqq4Q+dEZG8LkxmhrDRfXWTSMov3kVeOzkgUHi5iJTe0Wf9ymyeG4LSEiFcre
QqdgG/4EWy+mKBCGHqBElXD0AZnSelUqnNmv6IfM2T4nKsMNDvHLmzFiLoLENwOi
yvd7zvb1E/67svZDAYnOahtrm8JGrldGyfvxVU58ENmwQ82W/nBA1hUD1oBrhC4k
+U0XsTxPi9jA8Q22TrYLV6+gW2o3ceaUbUy53XGz0ADxDPbMoRW7ziXn9lGT6Nb8
HYIJJJvMlK1lbAPHiLbAbi7ZAWES2ithixHQn995slwweUJ2YjxTgwrqMjuKPowD
hiBjqXIZipp/V/M55liE
=Q5L6
-----END PGP SIGNATURE-----

I have made the change. Now I just have to wait to see if the machine start broadcasting for a lease, and then what the answer will be.

Thanks

I did not install a DHCP server on the box. I use my Netgear router for that.
I have ClamAV installed, and have had no notifications of any infections.

I have changed to dhclient. If that does not fix things, I will try your other suggestions.

Thanks

Let me say a little more about why I switched to dhclient.

But first - broadcasting for a lease is normal. It is the repeated broadcast you are seeing that is a problem. It seems that your system broadcasts for a lease, is assigned an IP, and then receives an NAK when it attempts to use it. That looks wrong.

The problem I had was back with opensuse 11.3. The system would broadcast for a lease, and get one. That part was fine. But when the lease was running out, it failed in attempts to renew the lease. That is probably happening to you, also. Because of the failed renewal, the lease would run out, the network was reset (closing any open connections), and then a broadcast for least started over.

With dhclient, that didn’t happen. The renewals worked, so it never broadcast for a lease except just after booting.

I had this problem only at work. On my home network with the router providing the dhcp service, either dhcpcd or dhclient seems to do quite well.

Since “dhclient” is the ISC software, it probably conforms to the standards a little better than “dhcpcd” or at least it has probably been more thoroughly tested for working with a variety of dhcp servers. In any case, only your own testing can show what works best for your setup.

It has been a couple of days and I haven’t noticed the broadcasting so I am hoping the problem is solved. Thanks for the help.