[SOLVED] Disable dhcp polling for eth0 at boot up?

damgar · 04-20-2010, 08:39 PM

During installation I set eth0 to use dhcp to get an IP address. I then installed gnome and networkmanger which handles my interfaces and works fine. But during bootup the system pauses for 5 seconds or so while it polls for dhcp. It then times out and gives me a 169.254.xx which is then replaced when networkmanager starts up at the end of bootup.

How do I stop the polling to cut out the 5 seconds?

bgeddy · 04-20-2010, 08:58 PM

Quote:

How do I stop the polling to cut out the 5 seconds?

I you want to stop polling for dhcp on boot you need to change USE_DHCP[0]="yes" to USE_DHCP[0]="" in /etc/rc.d/rc.inet1.conf. This will stop dhcpcd running.

jefro · 04-20-2010, 09:11 PM

Opps never mind. I thought network manager should have edited that file.

damgar · 04-20-2010, 09:14 PM

Quote:

Originally Posted by bgeddy

I you want to stop polling for dhcp on boot you need to change USE_DHCP[0]="yes" to USE_DHCP[0]="" in /etc/rc.d/rc.inet1.conf. This will stop dhcpcd running.

Very nice! The polling must have been taking longer to timeout than I noticed because that reboot was probably half of all the previous boots.

Thank you.

EDIT: That's also a nice file to know about. The init scripts have always made me a little nervous. It's probably time I start poking around to see what's going on in there.

bgeddy · 04-20-2010, 09:41 PM

Quote:

EDIT: That's also a nice file to know about. The init scripts have always made me a little nervous. It's probably time I start poking around to see what's going on in there.

Yes - the init scripts are useful. If you wanted a dialogue driven script to do the same you can always run netconfig as root which is the same as what the installer does however editing the configuration file gives more control. Glad you got it worked out so quickly.

rizitis · 04-21-2010, 12:49 PM

I did not set eth0 to use dhcp to get an IP address during installation, but after I change my mind.
But I didnt know about USE_DHCP[0]="" in /etc/rc.d/rc.inet1.conf so I put in /etc/rc.d/rc.local a link of this script

Code:

#!/bin/bash
echo "Starting internet conection...";
ifconfig eth0 up && dhclient eth0
ifconfig eth0

I am wondering, if there is any problem with that?

bgeddy · 04-21-2010, 01:16 PM

That's OK - but not really the Slackware default way of doing this. The Slackware scripts look at rc.inet1.conf for their configurations and it's here you make your settings. Slackware by default uses dhcpcd as it's dhcp client rather than dhclient. Also the included scripts have facilites to up or down interfaces from the command line.

So in a nutshell I would advise you to either run netconfig or manually change /etc/rc.d/rc.inet1.conf and disable you changes to rc.local. This will be more compliant with a stock Slackware setup.

rizitis · 04-21-2010, 01:24 PM

thank you!

BobNutfield · 04-21-2010, 04:10 PM

Quote:

Originally Posted by bgeddy

That's OK - but not really the Slackware default way of doing this. The Slackware scripts look at rc.inet1.conf for their configurations and it's here you make your settings. Slackware by default uses dhcpcd as it's dhcp client rather than dhclient. Also the included scripts have facilites to up or down interfaces from the command line.

So in a nutshell I would advise you to either run netconfig or manually change /etc/rc.d/rc.inet1.conf and disable you changes to rc.local. This will be more compliant with a stock Slackware setup.

dhcpcd does not work for me, I have no idea why. dhclient using wicd DOES work. What effect would it have on my networking if I disable dhcpcd for ALL network devices (includng wireless) in rc.inet1 and just use dhclent in wicd to connect each time?

Bob

Richard Cranium · 04-21-2010, 04:36 PM

Quote:

Originally Posted by BobNutfield

dhcpcd does not work for me, I have no idea why. dhclient using wicd DOES work. What effect would it have on my networking if I disable dhcpcd for ALL network devices (includng wireless) in rc.inet1 and just use dhclent in wicd to connect each time?

Bob

You will not be able to automatically mount remote drives (NFS, CIFS, or SMB) listed in /etc/fstab as part of startup. The services started in rc.inet2 may not be able to start or will not start correctly if none of your network connections are up.

I doubt that rc.ntpd will start correctly either.

BobNutfield · 04-21-2010, 04:48 PM

Thank you, hope I am not hijacking the thread. But I did not mean no networking at all. I get connected just fine to both my home network and the net, but dhcpcd will not give ne an IP address. I DO get a DHCP address when I use dhclient with wicd. dchpcd is started automatically at boot, but just results in errors. Once the boot process is complete, I just connect with wicd with dhclient. My question was about just disabling dhcpcd, not networking all together. I am getting SMB connections to other computers on my home network using the method I am using.

Bob

Richard Cranium · 04-21-2010, 05:01 PM

In other words, your gateway has given you an IP address but you aren't getting it.

What is the result of...

Code:

ls -lart /etc/dhcpc

...?

BobNutfield · 04-22-2010, 02:27 PM

Quote:

Originally Posted by Richard Cranium

In other words, your gateway has given you an IP address but you aren't getting it.

What is the result of...

Code:

ls -lart /etc/dhcpc

...?

No, the gateway is not giving me an address using dhcpcd. It results in:

Code:

err, wlan0: Option 43 has zero length
      err, wlan0: could not parse packet

It repaeats that several times, then times out. However, when I reach the desktop, disconnect from the failed address of 169.254..15.XX, then reconnect using wicd, which I have configured to use dhclient instead of dhcpcd, it does in fact give me the address of 192.168.1.40, which connects me to my home network and the net. I could be wrong, but I do not think this problem can be solved. I am not worried as long as I can connect. What I was asking is what the effect would be of disabling dhcpcd since I am not using it.

The request results:

Code:

bash-3.1$ ls -lart /etc/dhcpc
total 28
-rwxr-xr-x  1 root root 1359 2009-03-09 04:20 dhcpcd.sh-sample
-rw-r--r--  1 root root   42 2010-04-17 21:08 dhcpcd.duid
-rw-r--r--  1 root root  299 2010-04-18 08:16 dhcpcd-wlan1.info
-rw-r--r--  1 root root  298 2010-04-19 20:26 dhcpcd-eth0.info
-rw-r--r--  1 root root  299 2010-04-19 20:26 dhcpcd-wlan0.info
drwxr-xr-x  2 root root 4096 2010-04-22 20:02 .
drwxr-xr-x 69 root root 4096 2010-04-22 20:02 ..

Thanks

Bob

Richard Cranium · 04-22-2010, 03:46 PM

If your gateway did not think that you had an address, you wouldn't be getting any TCP/IP traffic from your gateway.

You could perhaps log into your gateway (if that's possible; my gateway is another slackware box) to see if you have been given an address.

As for the message you are seeing...

Quote:

err, wlan0: Option 43 has zero length
err, wlan0: could not parse packet

...according to RFC 2132, that's a bad message. From the RFC...

Quote:

The code for this option is 43 and its minimum length is 1.

(http://docstore.mik.ua/rfc/rfc2132.html#s8. and scroll down to 8.4)

BobNutfield · 04-22-2010, 04:02 PM

Thank you for your assistance, but I am not sure I am being clear. I DO get an IP address, but only when using wicd with dhclient, and not dhcpcd. Slackware defaults inet1 to using dhcpcd when the opetion USE_DHCP="yes" is used. It is when inet1 broadcasts for a lease that I get this error message and it times out to an "unconnected" IP address of 169.XXX.XXX.XX. I do not have to query the gateway (my router) to confirm whether I have an IP addrress. I am given 192.168.1.40, but ONLY when I connect with dhclient through wicd. In short, if dhcpcd broadcasts for a lease, it does not obtain one.

Bob