IP address is not getting assigned if I plugin the LAN cable after machine bootsup

IP address is not getting assigned my Linux machine if I plugin the LAN
cable once machine bootsup (first machine booted, then plugged in the
LAN cable). If I plugin the cable first and rebooted the machine, then
the machine gets assigned IP address, what was the reason the IP
address not getting assigned in the first case. is there any problem
with my configuration?.

In case of Windows it works in above both cases, IP address gets
assigned whether I pluin the cable before or after machine boots up.

Thanks.

(E-Mail Removed) wrote:

> IP address is not getting assigned my Linux machine if I plugin the LAN
> cable once machine bootsup (first machine booted, then plugged in the
> LAN cable).

Then presumably you aren't running software the listens for a cable being
connected and then make a DHCP request.

http://www.stud.uni-hamburg.de/users...lugd/#overview

> If I plugin the cable first and rebooted the machine, then
> the machine gets assigned IP address, what was the reason the IP
> address not getting assigned in the first case.

There was nothing available to assign an ip when the machine requested one.


--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

(E-Mail Removed) wrote:

> IP address is not getting assigned my Linux machine if I plugin the LAN
> cable once machine bootsup (first machine booted, then plugged in the
> LAN cable). If I plugin the cable first and rebooted the machine, then
> the machine gets assigned IP address, what was the reason the IP
> address not getting assigned in the first case. is there any problem
> with my configuration?.
>
> In case of Windows it works in above both cases, IP address gets
> assigned whether I pluin the cable before or after machine boots up.
>
> Thanks.

I assume you're using dhcp. If so, when the computer boots, it requests an
ip address from a dhcp server. If the computer is not connected, it can't
get that address. However, you can always restart the interface, to get
the address after connecting to the cable. XP can detect when the cable
is connected and then request a dhcp address. Some earlier versions of
Windows didn't. In SuSE Linux, you can use Yast to configure the network
adapter to detect when it's connected and then activate it.

(E-Mail Removed) wrote:

> In case of Windows it works in above both cases, IP address gets
> assigned whether I pluin the cable before or after machine boots up.
>

Further on this:

As an experiment, instead of connecting that Windows box directly into the
router or wherever you're getting the IP from, try connecting it to a
switch, with nothing else plugged into it. Then after a couple of minutes,
plug the switch into the router, and see if you now have an IP address.
You likely won't, because as soon as you plug into the switch, the computer
considers the NIC to be connected and then makes a dhcp request, which will
not be received by any dhcp server. When the router is then plugged in
after that, there is no way of telling the computer, that the dhcp server
is now available.

(E-Mail Removed) wrote in news:1113665522.243032.183530
@z14g2000cwz.googlegroups.com:

> the machine gets assigned IP address, what was the reason the IP
> address not getting assigned in the first case. is there any problem
> with my configuration?.
>

The problem is nothing is telling your computer the cable is plugged in and
to try to get an address now. You can force this by doing ifdown eth0
(assuming eth0 is your NIC), then ifup eth0.

(E-Mail Removed) wrote:
> IP address is not getting assigned my Linux machine if I plugin the LAN
> cable once machine bootsup (first machine booted, then plugged in the
> LAN cable). If I plugin the cable first and rebooted the machine, then
> the machine gets assigned IP address, what was the reason the IP
> address not getting assigned in the first case. is there any problem
> with my configuration?.
>
> In case of Windows it works in above both cases, IP address gets
> assigned whether I pluin the cable before or after machine boots up.
>
> Thanks.
>

or
"rcnetwork reload"

or dhcp.. pump what theres this command to renew the dhcp address,,, can
never remember it

Which Linux version detect automatic plugin and out just like Windows,
Please let me know, I am using RH 9.x presently, Is there any Linux
flavour out there to detect the Network cable plugin automatically?.
Thanks.

(E-Mail Removed) writes:

>Which Linux version detect automatic plugin and out just like Windows,
>Please let me know, I am using RH 9.x presently, Is there any Linux
>flavour out there to detect the Network cable plugin automatically?.
>Thanks.

No, there is nothing to detect. What you can do is to write a little cron
scrpit to test if the cable is in, and if the network is not configured to
configure it. That is probably what windows does.

(E-Mail Removed) wrote:
> Which Linux version detect automatic plugin and out just like Windows,
> Please let me know, I am using RH 9.x presently, Is there any Linux
> flavour out there to detect the Network cable plugin automatically?.
> Thanks.
>

You need the interface plug daemon. Google for 'ifplugd'.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi

Unruh wrote:
> (E-Mail Removed) writes:
>
>
>>Which Linux version detect automatic plugin and out just like Windows,
>>Please let me know, I am using RH 9.x presently, Is there any Linux
>>flavour out there to detect the Network cable plugin automatically?.
>>Thanks.
>
>
> No, there is nothing to detect. What you can do is to write a little cron
> scrpit to test if the cable is in, and if the network is not configured to
> configure it. That is probably what windows does.
>
>

No I doubt it!

I am pretty damn sure there is a hardware call that detects if theres
connectivity or not. IE to see if the little light on the nic is on or not.

BTW ISNT IT ANNOYING THAT windows resets all network connections when
the cable connection is interrupted!? AAArgh!!!

AArgh!

AAAAaaargh!

Hate SOFTWARE