[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: interpretting DHCP Client messages



On Fri, Feb 14, 2003 at 04:19:36PM -0500, Emma Jane Hogbin wrote:
| Hey all:
| 
| I'm curious to know what's actually happening when I pull up my wireless
| ethernet connection. Below is what I do and then what I see. I don't
| understand what the DHCPOFFERS received means. This seems to be the
| longest part of the connection. Is there a way to optomize this so that it
| takes less time?

Yeah, fix the network :-).

| DHCPREQUEST on eth0 to 255.255.255.255 port 67
| DHCPREQUEST on eth0 to 255.255.255.255 port 67

This is basically "give me address X.X.X.X, please".  It was sent
twice because no server offered the address the first time.

| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
| DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

This is "hello, I'm alive, what address can I have?".  Due to the lack
of offers, the broadcast is repeated.  The interval is an attempt to
be nice to the network, in case it is temporarily congested or
something.

| No DHCPOFFERS received.

This is bad.  No offers means one (or more) of the following :

    o   no network connection between you and other nodes on the subnet
    o   no DHCP server on the subnet
    o   the DHCP server has no available leases to offer to you
    o   the DHCP server doesn't like you

| Trying recorded lease 192.168.1.100
| PING 192.168.1.1 (192.168.1.1): 56 data bytes

Failing to get an offer, dhcp-client tries to see if the (expired!)
lease it had before still works.

| --- 192.168.1.1 ping statistics ---
| 1 packets transmitted, 1 packets received, 0% packet loss

That's more-or-less good, at least the network infrastructure (apart
from DHCP) works.  I wonder why it tried pinging that address, since
it's a "private" address and often times doesn't exist on a given
network.

I'd check the DHCP server and see what is wrong with it.  In a home
environment you shouldn't be running out of leases (though one of the
labs at school has half of the jacks on a subnet with no available
leases).

-D

-- 
No harm befalls the righteous,
but the wicked have their fill of trouble.
        Proverbs 12:21
 
http://dman.ddts.net/~dman/

Attachment: pgpYfalHX0oQm.pgp
Description: PGP signature


Reply to: