LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Mystery DHCP error (http://www.linuxquestions.org/questions/linux-networking-3/mystery-dhcp-error-43126/)

Darin 01-28-2003 04:12 PM

Mystery DHCP error
 
Here is a little DHCPd stumper:

All Linux machines are Slackware 8.1 The DHCP Server does hand out IPs, 2 different Slack clients when starting the network give these errors:

dhcpcd[53]: dhcpT1value option is missing in DHCP server response. Assuming 3600 sec
dhcpcd[53]: dhcpT2value option is missing in DHCP server response. Assuming 6300 sec

Winblows boxes don't give errors but that doesn't say much. In Linux I get a valid lease and any OS/machine under DHCP can network (ping, dns, internet, etc) but I'd like to chase down these errors so on the clients...

/etc/dhclient.conf is empty

in /etc/dhcpc/dhcpcd-eth0.info these two lines stick out:
RENEWALTIME=3600
REBINDTIME=6300

I'm guessing that the server isn't giving out this info, dhcpT1value aka RENEWALTIME and dhcpT2value aka REBINDTIME but I have checked man dhclient.conf, man dhcpd.conf, man dhcpd, man dhcpcd, and the DHCP mini HOWTO but none of them reference this.

Here is my dhcpd.conf from the server:
Code:

# dhcpd.conf
default-lease-time 2400;
max-lease-time 7200;
option domain-name "mysteryinc";
ddns-update-style none;

subnet 192.168.0.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.0.255;
  option routers 192.168.0.1;
  option domain-name-servers 192.168.0.1;
  option netbios-name-servers 192.168.0.1;
  range 192.168.0.51 192.168.0.249;
}

subnet 192.168.98.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.98.255;
  option routers 192.168.98.1;
  option domain-name-servers 192.168.98.1;
  option netbios-name-servers 192.168.98.1;
  range 192.168.98.51 192.168.98.249;
}

host shaggy.mysteryinc {
    hardware ethernet 00:10:4B:97:62:16;
    fixed-address 192.168.98.10,192.168.0.10;
}

Shaggy is one of the clients but my other client gives the same errors and like I said they do get valid DHCP and can network but I'd still like to pin down these errors if possible. Any thoughts?

Darin 01-29-2003 06:18 PM

Is it just scary when I ask a network question or is it that the answer is so simple that it should be obvious to me?

MasterC 01-29-2003 06:48 PM

Click here

:)

Ok, it looks like it's just another value that dhcpcd is going to look for. If you want to try some values, it looks like you can supply this in your dhcpd.conf:
dhcpT1value=0
dhcpT2value=0

I am assuming you are also wanting to know what the hell they mean...

Got me :D

Cool

MasterC 01-29-2003 06:50 PM

And yes, it's earily scary when you ask a networking question Darin. I think you should contact http://www.isc.org/ and let them know about the glitch :D

Cool

MasterC 01-29-2003 06:59 PM

Renewal (T1) Time Value

58

4 octets

Time interval from address assignment until the client transitions to RENEWING state.
Value: seconds, as 32-bit unsigned integer

Rebinding (T2) Time Value

59

4 octets

Time interval from address assignment until the client transitions to REBINDING state.
Value: seconds, as 32-bit unsigned integer

Halfway down this page:
http://www.cisco.com/univercd/cc/td/...rapb.htm#28545

It's apparently some lease renewal/rebiding value :)

Cool

Darin 01-29-2003 08:40 PM

Ah, you googled for it too huh? I got that page with the vague reference to it also.

Thanks, I kinda gathered what renewal and rebind times actually were I just figured it would either be IN a man page or not be as simple as adding the exact line "dhcpT1value=0" into dhcpd.conf :)

I guess if it's not mentioned in docs someone at isc should know about it though and if anyone has the same question, 0 is a bad value, something like this may be feasable:

dhcpT1value=3600
dhcpT2value=6300

The weird part is that the cisco link calls it "Lease Information, MS DHCP Client" while it was my linux box asking for the values. I gather from the cisco doc that also these values can be called
dhcp-renewal-time and dhcp-rebinding-time.

MasterC 01-29-2003 09:02 PM

Sure did, couldn't just leave ya hangin ;) And since you had already replied, I didn't have to worry about stealing your 0 replies status :D

Cool

Darin 01-29-2003 10:09 PM

Quote:

...I just figured...not be as simple as...
server: dhcpT1value=36;
client: dhcpT1value option is missing...

server: option dhcp-renewal-time 3600;
client: dhcpT1value option is missing...

server: option dhcpT1value 3600;
server error line 12: unknown option dhcp.dhcpT1value, DHCP fails to start

and yes I triple checked my syntax in /etc/dhcpd.conf and I was using:

killall -HUP dhcpd
/usr/sbin/dhcpd eth0 eth2

but since it was a stumper I even tried rebooting the server (it's the windows admin in me)

P.S. feel bad having 3 comps running so been using the server as my workstation and this little dual ppro200 does run X fairly well even with mozilla and me using all 4 desktops and a couple text VCs.


All times are GMT -5. The time now is 10:46 PM.