Project

General

Profile

Actions

Bug #6725

closed

DHCP Server > TFTP server name and custom dhcp options in GUI and in dhcpd.conf but missing on the wire

Added by Jules Hoehn almost 8 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
08/17/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

If configuring a TFTP server in the DHCP server settings (in my case for IP phones) the GUI accepts and applies the configuration. The dhcpd.conf file looks to contain the tftp server name attribute and value, but neither are seen in the bootp options on the wire from either the client or the server itself.

The issue is the same with custom options 66 and 150 in my case, the custom config in the GUI looks correct, the config in the dhcpd.conf file looks like it's missing the options values. These too are not seen on the wire.

I was unable to find any evidence of issue in DHCP logs for either lease or services. Normal DHCP operation appears to be working as expected.

options 53, 54, 1, 15,3, and 6 all show, and there appears to be no changes on the wire with any of those option or changes in the gui.

I have a hunch this issue may be similar to bug#6720

Running version 2.3.2

conf file looks like this:

option domain-name "mydomain.com";
option ldap-server code 95 = text;
option domain-search-list code 119 = text;
option arch code 93 = unsigned integer 16; # RFC4578
option custom-lan-0 code 150 = ip-address;

default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
one-lease-per-client true;
deny duplicates;
ping-check true;
update-conflict-detection false;
dhcp-cache-threshold 0;
authoritative;

subnet 192.168.X.X netmask 255.255.255.0 {
pool {
option domain-name-servers 192.168.X.X,8.8.8.8;
range 192.168.X.X 192.168.X.X;
}

option routers 192.168.X.X;
option domain-name-servers 192.168.X.X,8.8.8.8;
option ntp-servers 192.168.X.X;
option tftp-server-name "192.168.X.X";
option custom-lan-0 192.168.X.X;
}
Actions

Also available in: Atom PDF