From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] advoptions-list: Add additional dhcp options - fixes bug 12291
Date: Sun, 26 Dec 2021 22:55:12 +0100 [thread overview]
Message-ID: <20211226215512.3525919-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
- Add ms-classless-static-routes and rfc3442-classless-static-routes as options for dhcp
These are apparently required for deployiong classless IP routes
- Original static-routes option is not intended for classless IP routing but is being
left in place for backward compatibility
- The option "rfc3442-classless-static-routes" is for normal clients
- The option "ms-classless-static-routes" is for Microsoft clients
Fixes: bug 12291
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
config/cfgroot/advoptions-list | 2 ++
1 file changed, 2 insertions(+)
diff --git a/config/cfgroot/advoptions-list b/config/cfgroot/advoptions-list
index 8a1e75ebb..6330aefde 100644
--- a/config/cfgroot/advoptions-list
+++ b/config/cfgroot/advoptions-list
@@ -22,6 +22,7 @@ option mask-supplier flag;
option max-dgram-reassembly uint16;
option merit-dump string;
option mobile-ip-home-agent ip-address [, ip-address... ];
+option ms-classless-static-routes string;
option netbios-dd-server ip-address [, ip-address... ];
option netbios-node-type uint8;
option netbios-scope string;
@@ -38,6 +39,7 @@ option perform-mask-discovery flag;
option policy-filter ip-address ip-address [, ip-address ip-address... ];
option pop-server ip-address [, ip-address... ];
option resource-location-servers ip-address [, ip-address... ];
+option rfc3442-classless-static-routes string;
option root-path string;
option router-discovery flag;
option router-solicitation-address ip-address;
--
2.34.1
next reply other threads:[~2021-12-26 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 21:55 Adolf Belka [this message]
2021-12-27 10:36 ` Michael Tremer
2021-12-27 18:49 ` Peter Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211226215512.3525919-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox