Arch Linux

jb

Member

From: Florida

Registered: 2006-06-22

Posts: 466

[Solved]eth0: broadcasting for a lease... endlessly.

I'm at a bit of a loss here.  Periodically, I've been losing my network connection at work and on my notebook.  I didn't think too far into it until I noticed last night that my everything.log on my office workstation is now nearing 2GB after 5 months from the install date.   

This is a portion of the log file.  It starts at the point when I restarted the network and ends at the point where I probably lost the connection.  Those last three lines repeat for a good 100k times... Basically it just keeps repeating several times per second until I restart the network with the rc.d script.  After looking through it a bit more thoroughly, it looks like this all started back on October 29th.

Anyone have any thoughts as to what may be causing this?

Also, I should note that a server here that also runs arch does not lose it's network connection like my workstation and notebook, but I haven't updated it since October 3rd (according to pacman.log).

Dec  4 09:03:13 work dhcpcd[7754]: eth0: received SIGTERM, stopping
Dec  4 09:03:13 work dhcpcd[7754]: eth0: removing IP address 169.254.36.168/16
Dec  4 09:03:13 work dhcpcd[7754]: eth0: exiting
Dec  4 09:03:15 work dhcpcd[8381]: eth0: dhcpcd 3.1.7 starting
Dec  4 09:03:15 work ADDRCONF(NETDEV_UP): eth0: link is not ready
*Dec  4 09:03:15 work dhcpcd[8381]: eth0: hardware address = 00:19:b9:2c:XX:YY
Dec  4 09:03:15 work dhcpcd[8381]: eth0: broadcasting for a lease
Dec  4 09:03:17 work tg3: eth0: Link is up at 100 Mbps, full duplex.
Dec  4 09:03:17 work tg3: eth0: Flow control is on for TX and on for RX.
Dec  4 09:03:17 work ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec  4 09:03:18 work dhcpcd[8381]: eth0: offered 163.118.9.91 from 172.16.5.1
Dec  4 09:03:19 work dhcpcd[8381]: eth0: checking 163.118.9.91 is available on attached networks
Dec  4 09:03:21 work dhcpcd[8381]: eth0: leased 163.118.9.91 for 3600 seconds
Dec  4 09:03:21 work dhcpcd[8381]: eth0: adding IP address 163.118.9.91/25
Dec  4 09:03:21 work dhcpcd[8381]: eth0: adding default route via 163.118.9.126 metric 0
Dec  4 09:03:21 work dhcpcd[8381]: eth0: exiting
Dec  4 09:03:27 work eth0: no IPv6 routers present
Dec  4 09:33:21 work dhcpcd[8392]: eth0: renewing lease of 163.118.9.91
Dec  4 09:33:21 work dhcpcd[8392]: eth0: received NAK: (null)
Dec  4 09:33:21 work dhcpcd[8392]: eth0: broadcasting for a lease
Dec  4 09:33:22 work dhcpcd[8392]: eth0: offered 163.118.9.91 from 172.16.5.1
Dec  4 09:33:22 work dhcpcd[8392]: eth0: received NAK: (null)
Dec  4 09:33:22 work dhcpcd[8392]: eth0: broadcasting for a lease
Dec  4 09:33:22 work dhcpcd[8392]: eth0: offered 163.118.9.91 from 172.16.5.1
Dec  4 09:33:22 work dhcpcd[8392]: eth0: received NAK: (null)
Dec  4 09:33:22 work dhcpcd[8392]: eth0: broadcasting for a lease
Dec  4 09:33:22 work dhcpcd[8392]: eth0: offered 163.118.9.91 from 172.16.5.1
Dec  4 09:33:22 work dhcpcd[8392]: eth0: received NAK: (null)
Dec  4 09:33:22 work dhcpcd[8392]: eth0: broadcasting for a lease
Dec  4 09:33:22 work dhcpcd[8392]: eth0: offered 163.118.9.91 from 172.16.5.1
Dec  4 09:33:22 work dhcpcd[8392]: eth0: received NAK: (null)
Dec  4 09:33:22 work dhcpcd[8392]: eth0: broadcasting for a lease

*Only line I masked.

Last edited by jb (2007-12-04 23:20:39)

---

...

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: [Solved]eth0: broadcasting for a lease... endlessly.

the dhcpcd package was updated from version 3.16 to 3.17 on October 26th - seems to closely relate to when you first noticed this.  Maybe built yourself 3.16 using ABS and see if it helps?

jb

Member

From: Florida

Registered: 2006-06-22

Posts: 466

Re: [Solved]eth0: broadcasting for a lease... endlessly.

Hmm, I guess that did it.  I've maintained a connection to the school's network for a good hour or so.  I'll find out tomorrow for sure when I get back in, but I'll go ahead and call this solved for now.  Hopefully this will also be the solution for my notebook as well.

Thanks Cerebral, good catch.  I only grep'd for what I did that day forgetting that I normally leave my system on for weeks at a time.  Hopefully 3.18 will be a bit more considerate to my log files.

---

...