Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: omshell error - 9216 exceeds max (255) for precision
      (prasanth ns)


----------------------------------------------------------------------

Message: 1
Date: Sat, 25 Apr 2020 09:14:47 +0000 (UTC)
From: prasanth ns <p...@yahoo.com>
To: <dhcp-users@lists.isc.org>
Subject: Re: omshell error - 9216 exceeds max (255) for precision
Message-ID: <1073061060.92858.1587806087...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"

 > On Tuesday, March 31, 2020, 02:53:24 PM PDT, Bill Shirley 
 > <b...@c3po.polymerindustries.biz> 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> connectobj: <null>> new groupobj: group> set statements = 
"default-lease-time=100;"? ? ? ? ? ? ?obj: groupstatements = 
"default-lease-time=100;"> createobj: groupstatements = 
"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 DELETEauthoring-byte-order 
little-endian;
group ng38b7aa9835b226c0 {??dynamic;? ? ? ??supersede server.default-lease-time 
= 00;? ? ? ? << Incorrect value}

case 2
# omshell> connectobj: <null>> new groupobj: group> set statements = 
"default-lease-time=99;"obj: groupstatements = "default-lease-time=99;"> 
createobj: groupstatements = "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 DELETEauthoring-byte-order 
little-endian;group ng38b7aac835b22c30 {??dynamic;? ? ? ??supersede 
server.default-lease-time = 99;? ? ? ? << Correct value}
case 3
# omshell> connectobj: <null>> new groupobj: group> set statements = 
"default-lease-time=981;"obj: groupstatements = "default-lease-time=981;"> 
createobj: groupstatements = "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 DELETEauthoring-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
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
 _______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20200425/45782d89/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 138, Issue 11
*******************************************

Reply via email to