interpretting DHCP Client messages

[Emma Jane Hogbin <emmajane@xtrinsic.com>]

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?

thanks :)

emma


debian:/home/emmajane# ifup eth0
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

Listening on LPF/eth0/00:00:e2:8d:22:8b
Sending on   LPF/eth0/00:00:e2:8d:22:8b
Sending on   Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
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
No DHCPOFFERS received.
Trying recorded lease 192.168.1.100
PING 192.168.1.1 (192.168.1.1): 56 data bytes

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 5.8/5.8/5.8 ms
bound: renewal in 43013 seconds.


-- 
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]