I am running the latest version of slackware (v 11.0) and I am wondering if there is a way to make slackware tell me that it has picked up the dynamic ip address from my ISP.

When I reboot the machine I see it waits for a moment when trying to get the ip address but it would be nice to see that it got it, or that it didn't get it.

If I put the command to call 'rc.inet1' from the rc.local file - than I see when the
ip address is recieved. But not where it normally is run from.

Can anyone tell me if this is possible and if so, what do I have to do to see the ip address being recieved..

as long as the network card is enabled and pluged in

running
ifconfig

from the command line will display the IP Address you have been assigned

Firstly, you should configure /etc/dhcpc/dhcpcd.exe from the sample. That puts out a line whenever an IP is acquired.

Then, which kernel are you running. Out of the box, the 2.4 based system uses hotplug, which does an excellent job of supressing all the messages generated by the scripts that are run as each device has been discovered. So you won't see the message. HA

With 2.6, it should appear just fine.

Cheers.

Thanks for your input fellows. It is appreicated.

I am running the kernel provided, right out of the box. 2.4.33.3.
And what I want to see is what is happening at the time of 'boot'.
I know that after the machine comes up I can look at what the ip address is by doing ifconfig eth0/eth1 etc... but I would like to see the system acquiring the ip address while it is coming up.

Right now - I see it sitting there, at the point where it is trying to acquire the address (waiting for the 60 secs) and after that it takes off. Away it goes..

What I did to gain some assurance, was to add rc.inet1 restart to the rc.local file.
That shows me that it gets the ip address or fails. But I would like to do it right and only acquire the address from the rc.M file..

But - apparently kernel 2.4 suppresses all that is happening during boot which means I will never see it picking up the address as long as I run kernel 2.4 ??

What a bummer...

And kernel 2.6 is no good for some of my applications....

Thanks anyway fellows. Your input is appreciated..

It's not the kernel that supresses eveything, it's hotplug.

Cheers.

In my experience, if the boot hangs for 60 seconds while trying to acquire an IP address, you can be pretty much assured that it HAS failed. It normally takes less than 3-5 seconds to get an IP address on my systems when everything is working as it should be.

Bob