From 9efa7b2ecc9b1b54f0a1fbea46ccda86aafaaef5 Mon Sep 17 00:00:00 2001
From: Brad Kollmyer <bradk@vitalsoft.com>
Date: Wed, 15 Jul 2026 12:17:15 -0700
Subject: dhcp-server: T9093: allow option interface-mtu up to 16000

DHCP option 26 (Interface MTU, RFC 2132) is a 16-bit unsigned value and Kea
accepts the full range, but the CLI validator capped it at 9000 - below the
9216 used on common jumbo fabrics and below VyOS's own interface MTU maximum
of 16000.

Relax the constraint to 576-16000 and exercise a jumbo value (9216) in the
smoketest.

Co-authored-by: Christian Breunig <christian@breunig.cc>
---
 interface-definitions/include/dhcp/option-v4.xml.i | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'interface-definitions/include')

diff --git a/interface-definitions/include/dhcp/option-v4.xml.i b/interface-definitions/include/dhcp/option-v4.xml.i
index 0f446c9a9..177e1aa7e 100644
--- a/interface-definitions/include/dhcp/option-v4.xml.i
+++ b/interface-definitions/include/dhcp/option-v4.xml.i
@@ -87,11 +87,11 @@
       <properties>
         <help>Interface MTU</help>
         <valueHelp>
-          <format>u16:576-9000</format>
+          <format>u16:576-16000</format>
           <description>Client interface MTU</description>
         </valueHelp>
         <constraint>
-          <validator name="numeric" argument="--range 576-9000"/>
+          <validator name="numeric" argument="--range 576-16000"/>
         </constraint>
       </properties>
     </leafNode>
-- 
cgit v1.2.3