Link to home
Start Free TrialLog in
Avatar of ez_talk
ez_talk

asked on

How to release IP not using "dhclient -r"

Hi folks!

I have a cable connection that demands me to release the IP before switching to another OS (from Win to Linux and vice-versa). When I was using RedHat 8 I simply used "dhclient -r eth0" and it was done, but now I'm trying the ASPLinux distro, what is quite nice and fast, but it doesn't come with the dhclient package.

I intended to try installing the package from my RH CDs, but rpm complained of dependencies and I would need to mess TOO MUCH with the default installation to add it, so I'm wondering how could I release the IP from my machine without using dhclient.

The "great" support from my ISP told me to use ifconfig, but it only shuts down the adapter and doesn't release the IP.

Thanks in advance!

PS.: Don't try those funny answers like "why don't you just DON'T SWITCH OSes.." :)))))
ASKER CERTIFIED SOLUTION
Avatar of majorwoo
majorwoo

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ez_talk
ez_talk

ASKER

I tried dhclient right from /sbin but it was not there, so I used "find" and got nothing, and to be sure I searched the CDs for dhclient package and there was none there.

I have not tried pump...gonna check soon, as long as I finish my "Windows-needed" stuff for today.

Thank you for the tips on RPM repositories. Going to check them now.
Avatar of ez_talk

ASKER

Oh! I also tried dhcpcd, which was installed, and when I used "dhcpcd -k" it replied dhcpcd was not running, but I was using the internet normally.

RedHat uses a separate package for dhclient, just like Conectiva, and that is what I was trying to install prior to notice how painful it would be, since ASP doesn't provide it.
hmm that's really odd as all the docs i read seemed to indicate ASP used dhcpd
Avatar of ez_talk

ASKER

My system seemed to be kidding me. Twice I booted it up after installation  for regular use and strangely it was taking too long to start eth0 up, and the whole thing with dhcpcd saying it was not running and all.

But last time it found eth0 in a flash, I logged in, and when I typed "pump -r" ready to find the right answer, it replied me with an error message, so I risked "dhcpcd -k" again and voilá! The SOAB was there and I could kill it!!!!!

Guess it was some jealous curse from my Windows installation.......

Thanks, majorwoo, for all the tips anyway! :)
heh ;-) gotta love that stuff.