dhcpcd annoyance.

DrAxeman · 09-07-2005, 08:08 PM

Can someone assist me with a dhcpcd annoyance? I have my own wireless network scripts that setup my iwconfig params, and then call dhcpcd to start the interface. When I go from one wireless lan to another, I never get an IP address on the first try. dhcpcd acts like it got an IP address, but it doesn't. I have to kill dhcpcd and restart it to get an IP address. I have tested this on my wired lan and get the same results.

For example: While at work, my IP address is 172.20.1.34. I turn off my laptop, go home and log into my wireless lan. My home lan is 192.168.0.X. The first time I run dhcpcd I don't get an address, so I "killall dhcpcd" and then re-run my wlan script. Now I get an IP address.

Is there a way to tell dhcpcd to apply the new address if it can't use the old lease? (I think this is a lease issue.)

Has anyone seen this? I've lived with this through multiple versions of SuSE. Tonight I just decided to ask...

DrAxeman · 09-07-2005, 08:15 PM

I think I found it. There's an option in /etc/sysconfig/network/dhcp to release the lease when logging the interface off:

# Send a DHCPRELEASE to the server (sign off the address)? (yes|no)
# This may lead to getting a different address/hostname next time an address
# is requested. But some servers require it.
#
DHCLIENT_RELEASE_BEFORE_QUIT="yes"

I'll let everyone know how this works.

Thoreau · 09-07-2005, 08:17 PM

rcdhcpd restart

You have to release the settings before you can repopulate them. Essentially that's what restarting
the service is doing. For full effect, you can do a rcnetwork restart.

It's not a suse or dhcp thing. It's a low level network thing. You can't change static ip's on the fly either unless you reset the connection/device. On more complex AP lan's like cisco aeronet devices, you can roam between AP's without resetting your IP schema- but that isn't something that you'll be able to do with what you are describing.

DrAxeman · 09-08-2005, 06:36 AM

I'm not having an issue with the DHCP Daemon, it's dhcpcd, the client app. I don't even have the DHCP Daemon installed on my laptop, just a dhcp client, and I can't be expected to restart the DHCP Daemon at every location I log into!

All I want is for the dhcp client to release the lease when I log my NIC off. Either that, or accept a new license when I go to a new network. Besides, I think I found the answer already.