>> On Tuesday, March 31, 2020, 02:53:24 PM PDT, Bill Shirley
> <
[hidden email]> wrote:
>
>> You're giving it an IPv4 address but the routers and
> domain-name-servers options are IPv6 addresses. You're
>> using a semi-colon as the separator instead of a dot. Generally, MTU
> is 1,500 or less.
>
> Thanks Bill. Apologies for the delayed response. I corrected the IPs
> as you suggested and tried to analyze the MTU issue a bit more. What I
> noticed is that the issue is not just with the interface-mtu value,
> but with any number you specify as part of the configuration on
> omshell. Here is another way I reproduced it. This time with
> default-lease-time.
>
> CASE1
>
> # omshell
>> connect
> obj: <null>
>> new group
> obj: group
>> set statements = "default-lease-time=100;"
> obj: group
> statements = "DEFAULT-LEASE-TIME=100;"
>> create
> obj: group
> statements = "default-lease-time=100;"
> name = "ng38b7aa9835b226c0"
>
> # cat /tmp/dhcpd.leases
> # The format of this file is documented in the dhcpd.leases(5) manual
> page.
> # This lease file was written by isc-dhcp-4.4.2
>
> # authoring-byte-order entry is generated, DO NOT DELETE
> authoring-byte-order little-endian;
>
> group ng38b7aa9835b226c0 {
> dynamic;
> SUPERSEDE SERVER.DEFAULT-LEASE-TIME = 00; << INCORRECT
> VALUE
> }
>
> CASE 2
>
> # omshell
>> connect
> obj: <null>
>> new group
> obj: group
>> set statements = "DEFAULT-LEASE-TIME=99;"
> obj: group
> statements = "default-lease-time=99;"
>> create
> obj: group
> statements = "default-lease-time=99;"
> name = "ng38b7aac835b22c30"
>
> # cat /tmp/dhcpd.leases
> # The format of this file is documented in the dhcpd.leases(5) manual
> page.
> # This lease file was written by isc-dhcp-4.4.2
>
> # authoring-byte-order entry is generated, DO NOT DELETE
> authoring-byte-order little-endian;
>
> group ng38b7aac835b22c30 {
> dynamic;
> SUPERSEDE SERVER.DEFAULT-LEASE-TIME = 99; << CORRECT
> VALUE
> }
>
> CASE 3
>
> # omshell
>> connect
> obj: <null>
>> new group
> obj: group
>> set statements = "DEFAULT-LEASE-TIME=981;"
> obj: group
> statements = "default-lease-time=981;"
>> create
> obj: group
> statements = "default-lease-time=981;"
> name = "ng38b7ab3935b23100"
>
> # cat /tmp/dhcpd.leases
> # The format of this file is documented in the dhcpd.leases(5) manual
> page.
> # This lease file was written by isc-dhcp-4.4.2
>
> # authoring-byte-order entry is generated, DO NOT DELETE
> authoring-byte-order little-endian;
>
> group ng38b7ab3935b23100 {
> dynamic;
> supersede SERVER.DEFAULT-LEASE-TIME = 81; << INCORRECT
> VALUE
> }
>
> In all the 3 cases above JUST 2 LEAST SIGNIFICANT DIGITS APPEARED IN
> THE LEASE FILE. In /var/log/messages I found these error messages.
>
> dhcpd: network client line 1: 100 exceeds max (255) for precision.
> dhcpd: default-lease-time=100;
> dhcpd: ^
>
> dhcpd: network client line 1: 981 exceeds max (255) for precision.
>
> dhcpd: default-lease-time=981;
> dhcpd: ^
>
> Wondering if this is parser bug or my usage is incorrect.
>
> Thanks,
> Prashanth
>
> Bill
>
> On 3/31/2020 10:02 AM, prasanth ns wrote:
>
>>
>
> Hi dhcp-users,
>
> I am trying to configure a host reservation through omshell. For some
> reason dhcpd doesn't accept mtu and I see this error in syslog. Any
> idea what is going wrong?
>
> "dhcpd: network client line 1: 9216 EXCEEDS MAX (255) FOR PRECISION.
> dhcpd: option routers=1:0:1:2; option INTERFACE-MTU=9216;"
>
> Also my lease file shows incorrect MTU of 16 instead of 9216.
>
> # cat /tmp/dhcpd.leases
>
> host some-host {
> dynamic;
> hardware ethernet 00:82:67:85:b1:94;
> fixed-address 192.168.4.40;
> supersede routers = 01:00:01:02;
> SUPERSEDE INTERFACE-MTU = 16; <<<<<<
> supersede domain-name-servers = 02:01:00:05;
> }
>
> # dhcpd --version
> isc-dhcpd-4.4.2
>
> Here are the commands I enter at omshell:
>
> new host
> set name = "some-host"
> set hardware-address = 00:82:67:85:b1:94
> set hardware-type = 1
> set ip-address = 192.168.4.40
> set statements = "option routers=1:0:1:2; option interface-mtu=9216;
> option domain-name-servers = 02:01:00:05; "
> create
>
> Thanks in advance,
> Prashanth.
>
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users>
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
