LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page Unwanted dhcpcd activity
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-07-2009, 02:47 PM   #1
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309

Rep: Reputation: 234Reputation: 234Reputation: 234
Unwanted dhcpcd activity

I use Slackware 13.0 with generic smp 2.6.29.6 kernel. From time to time I encounter unwanted dhcpcd activity. I observed it for the first time when I tried to configure NFS to exchange data between two machines. Program dhcpcd started for some reason and added IP address from the class 169.254.*.*. In result my local 192.168.*.* network didn’t work. In some other cases I observed another network related issues related to dhcpcd activity.

Here’s an abstract from today’s dhcpcd activity:

# cat /var/log/messages | grep dhcpcd
Code:
Sep  7 16:30:40 home6 dhcpcd[4343]: eth0: exiting
Sep  7 16:34:11 home6 dhcpcd[4719]: wlan0: exiting
Sep  7 16:34:11 home6 dhcpcd[4735]: eth0: exiting
Sep  7 16:34:11 home6 dhcpcd[4739]: eth0: dhcpcd 3.2.3 starting
Sep  7 16:34:11 home6 dhcpcd[4739]: eth0: hardware address = ba:be:de:ad:ab:ed
Sep  7 16:34:11 home6 dhcpcd[4739]: eth0: DUID = 00:01:00:01:12:34:16:2c:ba:be:de:ad:ab:ed
Sep  7 16:34:11 home6 dhcpcd[4739]: eth0: broadcasting for a lease
Sep  7 16:34:31 home6 dhcpcd[4739]: eth0: trying to use old lease in `/etc/dhcpc/dhcpcd-eth0.info'
Sep  7 16:34:32 home6 dhcpcd[4739]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:34:32 home6 dhcpcd[4739]: eth0: exiting
Sep  7 16:35:03 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:35:34 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:37:07 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:37:38 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:38:09 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
Sep  7 16:38:40 home6 dhcpcd[4897]: eth0: adding IP address 169.254.115.72/16
In result in /etc/dhcpc/ appeared two files – dhcpcd-eth0.info and dhcpcd.duid:

# ls /etc/dhcpc/
Code:
dhcpcd-eth0.info  dhcpcd.duid  dhcpcd.sh-sample
# cat /etc/dhcpc/dhcpcd-eth0.info
Code:
IPADDR='169.254.115.72'
NETMASK='255.255.0.0'
NETWORK='169.254.0.0'
BROADCAST='169.254.255.255'
LEASEDFROM='0'
LEASETIME='20'
RENEWALTIME='10'
REBINDTIME='17'
INTERFACE='eth0'
CLASSID='dhcpcd 3.2.3'
CLIENTID='ff:65:74:68:30:00:01:00:01:12:34:16:2c:ba:be:de:ad:ab:ed'
DHCPCHADDR='ba:be:de:ad:ab:ed'
# cat /etc/dhcpc/dhcpcd.duid
Code:
00:01:00:01:12:34:16:2c:ba:be:de:ad:ab:ed
After each such issue I remove dhcpcd-eth0.info and dhcpcd.duid but they reappear anew.

I use standard dhcclient and dhcpcd configuration:

# cat /etc/dhclient.conf
Code:
# dhclient.conf
#
# Configuration file for ISC dhclient (see 'man dhclient.conf')
#
# cat /etc/dhcpd.conf
Code:
# dhcpd.conf
#
# Configuration file for ISC dhcpd (see 'man dhcpd.conf')
#
How can I avoid unwanted dhcpcd activity in the future?
 
Old 09-07-2009, 04:12 PM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hello w1k0,

it looks like the DHCP-leasetime is running out and the dhcp-client tries to get a new lease when the DHCP-server is not available.

The ip-adresses 169.254.xxx.xxx/16 are so called apipa adresses (automatic private ip adressing), a concept which once (win98) was introduced by microsoft. Such an adress the machine gives to itself if no DHCP-server is available.

I'd suggest to take a capture of the DHCP-related networktraffic with tcpdump or wireshark. This will show you whats wrong with DHCP in your network.

Markus
Last edited by markush; 09-07-2009 at 04:15 PM.
 
Old 09-07-2009, 05:48 PM   #3
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309

Original Poster
Rep: Reputation: 234Reputation: 234Reputation: 234
I’m not sure what you mean when you suggest to capture DHCP-related network traffic with tcpdump but I did some tests.

1. I stopped PPPOE connection and I ran my private network. A few seconds later I observed dhcpcd activity in /var/log/messages:

Code:
Sep  8 00:24:18 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  8 00:24:19 home6 dhcpcd[17922]: eth0: exiting
Sep  8 00:24:19 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  8 00:24:20 home6 kernel: [drm] Num pipes: 1
Sep  8 00:24:20 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  8 00:24:20 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  8 00:24:20 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  8 00:24:21 home6 /usr/sbin/gpm[3505]: *** info [mice.c(1766)]: 
Sep  8 00:24:21 home6 /usr/sbin/gpm[3505]: imps2: Auto-detected intellimouse PS/2
Sep  8 00:24:25 home6 dhcpcd[17936]: wlan0: exiting
Sep  8 00:24:25 home6 kernel: iwl3945 0000:03:00.0: PCI INT A disabled
Sep  8 00:24:25 home6 kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Sep  8 00:24:25 home6 kernel: Registered led device: iwl-phy0:radio
Sep  8 00:24:25 home6 kernel: Registered led device: iwl-phy0:assoc
Sep  8 00:24:25 home6 kernel: Registered led device: iwl-phy0:RX
Sep  8 00:24:25 home6 kernel: Registered led device: iwl-phy0:TX
Sep  8 00:24:25 home6 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  8 00:24:25 home6 dhcpcd[17952]: eth0: exiting
Sep  8 00:24:25 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  8 00:24:25 home6 dhcpcd[17956]: eth0: dhcpcd 3.2.3 starting
Sep  8 00:24:25 home6 dhcpcd[17956]: eth0: hardware address = ba:be:de:ad:ab:ed
Sep  8 00:24:25 home6 dhcpcd[17956]: eth0: DUID = 00:01:00:01:12:37:ea:d6:ba:be:de:ad:ab:ed
Sep  8 00:24:25 home6 dhcpcd[17956]: eth0: broadcasting for a lease
Sep  8 00:24:28 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  8 00:24:28 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  8 00:24:28 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  8 00:24:33 home6 acpid: client connected from 14355[0:100] 
Sep  8 00:24:33 home6 acpid: 1 client rule loaded 
Sep  8 00:24:33 home6 kernel: [drm] Loading R500 Microcode
Sep  8 00:24:33 home6 kernel: [drm] Num pipes: 1
Sep  8 00:24:45 home6 dhcpcd[17956]: eth0: trying to use old lease in `/etc/dhcpc/dhcpcd-eth0.info'
Sep  8 00:24:45 home6 dhcpcd[17956]: eth0: probing for an IPV4LL address
Sep  8 00:24:46 home6 dhcpcd[17956]: eth0: adding IP address 169.254.214.61/16
Sep  8 00:24:46 home6 dhcpcd[17956]: eth0: exiting
Sep  8 00:25:02 home6 kernel: [drm] Num pipes: 1
Sep  8 00:25:17 home6 dhcpcd[17959]: eth0: adding IP address 169.254.214.61/16
Sep  8 00:25:28 home6 acpid: client connected from 14355[0:100] 
Sep  8 00:25:28 home6 acpid: 1 client rule loaded 
Sep  8 00:25:28 home6 kernel: [drm] Loading R500 Microcode
Sep  8 00:25:28 home6 kernel: [drm] Num pipes: 1
Sep  8 00:25:48 home6 dhcpcd[17959]: eth0: adding IP address 169.254.214.61/16
Sep  8 00:26:19 home6 dhcpcd[17959]: eth0: adding IP address 169.254.214.61/16
...as well as in /var/log/syslog:

Code:
Sep  8 00:24:19 home6 dhcpcd[17922]: eth0: dhcpcd not running
Sep  8 00:24:25 home6 dhcpcd[17936]: wlan0: dhcpcd not running
Sep  8 00:24:25 home6 dhcpcd[17952]: eth0: dhcpcd not running
Sep  8 00:24:45 home6 dhcpcd[17956]: eth0: timed out
Sep  8 00:24:45 home6 dhcpcd[17956]: eth0: lease information file `/etc/dhcpc/dhcpcd-eth0.info' does not exist
Sep  8 00:24:46 home6 dhcpcd[17956]: eth0: using IPV4LL address 169.254.214.61
2. In the same time tcpdump registered some DHCP-related activity:

# tcpdump -i eth0 -n port 67 and port 68
Code:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
00:24:28.398951 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:31.402976 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:34.406938 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:37.410939 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:40.414939 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:43.418939 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:56.476937 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:24:59.480940 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:25:02.484941 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:25:05.488938 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
3. Before I started these tests I removed dhcpcd-eth0.info and dhcpcd.duid from /etc/dhcpc/. After tests I noticed new versions of mentioned files as well as dhcpcd-eth0.pid:

# cat /etc/dhcpc/dhcpcd-eth0.info
Code:
IPADDR='169.254.214.61'
NETMASK='255.255.0.0'
NETWORK='169.254.0.0'
BROADCAST='169.254.255.255'
LEASEDFROM='0'
LEASETIME='20'
RENEWALTIME='10'
REBINDTIME='17'
INTERFACE='eth0'
CLASSID='dhcpcd 3.2.3'
CLIENTID='ff:65:74:68:30:00:01:00:01:12:37:ea:d6:ba:be:de:ad:ab:ed'
DHCPCHADDR='ba:be:de:ad:ab:ed'
# cat /etc/dhcpc/dhcpcd.duid
Code:
00:01:00:01:12:37:ea:d6:ba:be:de:ad:ab:ed
# cat /etc/dhcpc/dhcpcd-eth0.pid
Code:
17959
Any suggestions concerning further tests?
 
Old 09-08-2009, 12:17 AM   #4
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Ok, thats whats wrong. In the "dhcpcd-eth0.info" file dhcpcd stores the current ip-configuration of your system. As you see from your tcpdump-output dhcpcd tries to get a lease from the server and then takes the configuration from the dhcpcd-eth0-info file. This configuration is an apipa-adress which "kicks your machine out of the subnet". Normally, if everything is correct, in the dhcpcd-eth0.info file there must be stored a configuration that corresponds with the output of ifconfig if the network works correctly.

You'll have to find out, why the correct ip-configuration is not stored into dhcpcd-eth0.info when the system is working correctly. Maybe you can change it manually. Read the manpage of dhcpcd.

Markus

EDIT: on my system (slack64-13) the ip-adress in dhcpcd-eth0.info is the same as my current ip-adress.
EDIT: I read your post again, I think your DHCP-server doesn't work correct or your machine is not set up correctly as a DHCP-client.
here is my dhcpcd-eth0.info
Code:
IPADDR='192.168.178.68'
NETMASK='255.255.255.0'
NETWORK='192.168.178.0'
BROADCAST='192.168.178.255'
ROUTES=''
GATEWAYS='192.168.178.1'
DNSSERVERS='192.168.178.1'
DHCPSID='192.168.178.1'
LEASEDFROM='1252385962'
LEASETIME='864000'
RENEWALTIME='432000'
REBINDTIME='756000'
INTERFACE='eth0'
CLASSID='dhcpcd 3.2.3'
CLIENTID='ff:65:74:68:30:00:01:00:01:12:2b:4b:91:00:04:61:a5:c8:64'
DHCPCHADDR='00:04:61:a5:c8:64'
please notice that LEASEFROM has a value not null and LEASETIME is set to a correct value.
Last edited by markush; 09-08-2009 at 12:33 AM. Reason: added output from my system
 
Old 09-08-2009, 06:23 PM   #5
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309

Original Poster
Rep: Reputation: 234Reputation: 234Reputation: 234
I don’t understand well everything you suggest me to do but I managed to narrow slightly the problem with dhcpcd...

I customized dhcpcd-eth0.info without alternating LEASEDFROM, LEASETIME, RENEWALTIME and REBINDTIME settings:

# cat /etc/dhcpc/dhcpcd-eth0.info
Code:
IPADDR='192.168.1.6'
NETMASK='255.255.255.0'
NETWORK='192.168.0.0'
BROADCAST='192.168.1.255'
LEASEDFROM='0'
LEASETIME='20'
RENEWALTIME='10'
REBINDTIME='17'
INTERFACE='eth0'
CLASSID='dhcpcd 3.2.3'
CLIENTID='ff:65:74:68:30:00:01:00:01:12:38:df:95:ba:be:de:ad:ab:ed'
DHCPCHADDR='ba:be:de:ad:ab:ed'
If I run such script:

Code:
IPADDR="192.168.1.6"
BROADCAST="192.168.1.255"
NETMASK="255.255.255.0"
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
I can set up local network configuration (IP 192.168.1.6):

# ifconfig
Code:
eth0      Link encap:Ethernet  HWaddr ba:be:de:ad:ab:ed  
          inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: deaf::abbe:bade:dead:bead/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
          Memory:ee000000-ee020000
I can also use such script to set down the network and then to set it up:

Code:
/sbin/ifconfig eth0 down
IPADDR="192.168.1.6"
BROADCAST="192.168.1.255"
NETMASK="255.255.255.0"
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
Network configuration persists the same:

# ifconfig
Code:
eth0      Link encap:Ethernet  HWaddr ba:be:de:ad:ab:ed  
          inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: deaf::abbe:bade:dead:bead/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 B)  TX bytes:936 (936.0 B)
          Memory:ee000000-ee020000
And nothing wrong happens in the system:

Code:
Sep  9 00:14:32 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  9 00:14:33 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  9 00:14:33 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  9 00:14:33 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  9 00:14:55 home6 acpid: client connected from 3646[0:100] 
Sep  9 00:14:55 home6 acpid: 1 client rule loaded
But if I repeat setting down and setting up the network using the last script after a few attempts dhcpcd starts to work:

Code:
Sep  9 00:15:57 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  9 00:15:59 home6 dhcpcd[5109]: eth0: exiting
Sep  9 00:15:59 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  9 00:15:59 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  9 00:15:59 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  9 00:15:59 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  9 00:16:00 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  9 00:16:00 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  9 00:16:00 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  9 00:16:05 home6 dhcpcd[5123]: wlan0: exiting
Sep  9 00:16:05 home6 kernel: iwl3945 0000:03:00.0: PCI INT A disabled
Sep  9 00:16:05 home6 kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Sep  9 00:16:05 home6 kernel: Registered led device: iwl-phy0:radio
Sep  9 00:16:05 home6 kernel: Registered led device: iwl-phy0:assoc
Sep  9 00:16:05 home6 kernel: Registered led device: iwl-phy0:RX
Sep  9 00:16:05 home6 kernel: Registered led device: iwl-phy0:TX
Sep  9 00:16:05 home6 kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  9 00:16:05 home6 dhcpcd[5139]: eth0: exiting
Sep  9 00:16:05 home6 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  9 00:16:05 home6 dhcpcd[5143]: eth0: dhcpcd 3.2.3 starting
Sep  9 00:16:05 home6 dhcpcd[5143]: eth0: hardware address = ba:be:de:ad:ab:ed
Sep  9 00:16:05 home6 dhcpcd[5143]: eth0: DUID = 00:01:00:01:12:39:3a:62:ba:be:de:ad:ab:ed
Sep  9 00:16:05 home6 dhcpcd[5143]: eth0: broadcasting for a lease
Sep  9 00:16:08 home6 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
Sep  9 00:16:08 home6 kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep  9 00:16:08 home6 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep  9 00:16:25 home6 dhcpcd[5143]: eth0: trying to use old lease in `/etc/dhcpc/dhcpcd-eth0.info'
Sep  9 00:16:25 home6 dhcpcd[5143]: eth0: probing for an IPV4LL address
Sep  9 00:16:26 home6 dhcpcd[5143]: eth0: adding IP address 169.254.56.94/16
Sep  9 00:16:26 home6 dhcpcd[5143]: eth0: exiting
Sep  9 00:16:34 home6 acpid: client connected from 3646[0:100] 
Sep  9 00:16:34 home6 acpid: 1 client rule loaded
And tcpdump registers some requests on port 68:

# tcpdump -i eth0 -n port 67 and port 68
Code:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
00:16:08.720897 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:11.724901 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:14.728900 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:17.732896 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:20.736902 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:23.740901 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:36.816898 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
00:16:39.820903 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from ba:be:de:ad:ab:ed, length 300
In result dhcpcd changes the network configuration:

# ifconfig
Code:
eth0      Link encap:Ethernet  HWaddr ba:be:de:ad:ab:ed  
          inet addr:169.254.56.94  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: deaf::abbe:bade:dead:bead/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 B)  TX bytes:23272 (22.7 KiB)
          Memory:ee000000-ee020000
As well as my manually modified info file:

# cat /etc/dhcpc/dhcpcd-eth0.info
Code:
IPADDR='169.254.56.94'
NETMASK='255.255.0.0'
NETWORK='169.254.0.0'
BROADCAST='169.254.255.255'
LEASEDFROM='0'
LEASETIME='20'
RENEWALTIME='10'
REBINDTIME='17'
INTERFACE='eth0'
CLASSID='dhcpcd 3.2.3'
CLIENTID='ff:65:74:68:30:00:01:00:01:12:39:3a:62:ba:be:de:ad:ab:ed'
DHCPCHADDR='ba:be:de:ad:ab:ed'
***

I stated that sometimes it’s enough to set down and up the network for two or three times to activate dhcpcd and sometimes it’s necessary to perform these operations for a dozen times. Some network related actions speed up dhcpcd activation. For example if I start and stop PPPOE it’s enough to set down and up the local network for one to three times to activate dhcpcd.

I didn’t try to alternate LEASEDFROM, LEASETIME, RENEWALTIME and REBINDTIME settings because I think that increasing those timers doesn’t remove the problem but reschedules it in the time.

Now I know that I can’t set down and up the local network because these operations affect dhcpcd activity.

I simply don’t understand why dhcpcd starts to work on my machine. I investigated the files from /etc/ directory but I found nothing relevant.

Anyway thank you for your assistance.
 
Old 09-09-2009, 12:13 AM   #6
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hi w1k0,

be aware that the leasetime is the amount of time (in seconds) after which the DHCP-lease runs out. Normaly the renewaltime is half the amount of the leasetime and the DHCP client tries to get a new lease after this amount of time. So your dhcpcd begins exactly 10 seconds after starting the system to request for a new lease.

Maybe you can disable dhcpcd and configure your system for a static ip-configuration.

Again: anything is wrong with your DHCP-configuration or the DHCP-server.

Markus

EDIT: i remember that I've read that something with dhcpcd is buggy, but I'm not sure.
Last edited by markush; 09-09-2009 at 12:16 AM.
 
Old 09-09-2009, 07:41 AM   #7
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309

Original Poster
Rep: Reputation: 234Reputation: 234Reputation: 234
In my case dhcpcd do nothing ten seconds after the start of the system. My local network is set up out of the box. To use it is enough to run less restrictive firewall because by default I run restrictive firewall used during PPPOE connections that blocks local network traffic too. So far I switched firewall by running the script that called firewall and set down and up the network. Unfortunately these operations caused unwanted dhcpcd activity. Fortunately it isn't necessary to rerun local network since it's just configured. It's enough to switch firewall.

I still wonder why dhcpcd activates itself in described circumstances. I'm used to configure every service in my system from the scratch. In /etc/rc.d/rc.inet1.conf I set up local network without DHCP:

Code:
# Config information for eth0:
IPADDR[0]="192.168.1.6"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
Earlier it was enough to get rid of DHCP. With Slackware 13.0 it isn't enough and unwanted DHCP starts automagically when I'm reloading network settings. I still don't understand it.

Thank you for your assistance. It motivated me to perform some tests. I didn't solve the problem but I found the way to live with it.
Last edited by w1k0; 09-09-2009 at 07:44 AM.
 
Old 07-16-2010, 07:18 AM   #8
nl1at
LQ Newbie
 
Registered: Mar 2004
Location: Uitgeest Netherlands
Posts: 26

Rep: Reputation: 15
Sorry to revive an old tread..
But I had some "magic" respawn of the dhcpcd after dhcpcd -x eth0 so after some investigation it was wicd (which i installed for easy wireless config) which was bringing dhcpcd back to life..
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
dhcpcd wireless problems. dhcpcd wlan0 removes essid entry in iwconfig. Romanus81 Slackware 3 08-25-2008 10:34 PM
Unwanted link Hugh Jass Linux - Software 4 10-25-2006 06:22 PM
Unwanted link mat_uk111 SUSE / openSUSE 1 05-18-2006 09:04 PM
Unwanted HD detecting. Nukem Mandriva 14 01-24-2004 11:47 AM
Unwanted shutdown tireseas Linux - Hardware 17 01-02-2004 06:35 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:44 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration