Re: interpretting DHCP Client messages
This is a home network so all configuration issues with the access point
are because I'm incompetent. ;)
On Fri, Feb 14, 2003 at 06:10:14PM -0500, Derrick 'dman' Hudson wrote:
> | 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.
Ok, in the DHCP tab on the browser configuration tool I've added:
DNS 1: 192.168.1.105 (which is currently not being used by any of the
three computers on the network). It had absolutely no effect (as far as I
can see):
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 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
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 = 2.9/2.9/2.9 ms
SIOCADDRT: File exists
bound: renewal in 22135 seconds.
> o the DHCP server doesn't like you
I'll save you from the story of how this is the third router we've had in
as many months. /ahem/ We love this one though...it's a Linksys (the last
two were D-link). It's one of those combo wired/wireless ones.
> | 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.
Yeah, the lease is 1 day by default or has to be set in minutes.
> | --- 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.
It's a private network?
Thanks for your help.
emma
--
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]
Reply to: