<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">W dniu 30.09.2016 o 23:08, Sylvan Miles
pisze:<br>
</div>
<blockquote
cite="mid:EC68DF4B48128B46AE6CF21935794DFB37E119A5@CTCv-Exchange.Consolidated.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is it possible to hand out classless static
routes with Kea (I’m running 1.1.0)?
</p>
</div>
</blockquote>
Sure. Kea does not provide its definition, but you can do that
easily with custom option defintions.<br>
<blockquote
cite="mid:EC68DF4B48128B46AE6CF21935794DFB37E119A5@CTCv-Exchange.Consolidated.local"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">DHCP option 121 under defined under
RFC3442.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If not, is it on the roadmap or can it be
added as a feature request?</p>
</div>
</blockquote>
It currently isn't. We can do custom option for now, but it would be
useful to have proper support for it. Can you create a new ticket
for it? Please go to kea.isc.org, log in (create an account if you
don't have one) and create new ticket for it. We will triage it and
assign to a milestone.<br>
<blockquote
cite="mid:EC68DF4B48128B46AE6CF21935794DFB37E119A5@CTCv-Exchange.Consolidated.local"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If so, what would the relevant kea.conf
look like?<o:p></o:p></p>
</div>
</blockquote>
There are couple ways you can get it. The one you provided - to
define everything as integers - would surely work, but it's a bit
cumbersome. Here's a slightly more convenient one:<br>
<br>
"option-def": [<br>
{<br>
"name": "classless-static-routes",<br>
"code": 121,<br>
"space": "dhcp4",<br>
"type": "record",<br>
"record-types": "uint8,uint8,uint8,ipv4-address"<br>
}],<br>
<br>
"option-data": [<br>
{<br>
"name": "classless-static-routes",<br>
"data": "9,10,0, 172.25.16.1"<br>
}], <br>
<br>
You can probably skip the "space:" "dhcp4" part, but I have not
tested it. If you want to add multiple entries in that option,
adding "array": true may be useful.<br>
<br>
The option-def has to be defined in the global scope of Dhcp4, while
option-data can be defined anywhere you need it: in the global or
subnet scope or even in host reservations if you want to provide
different values to different hosts.<br>
<br>
The definition above assumes that the netmask will be between 9 and
16, so the actual network part will be encoded on 2 bytes, hence the
uint8,uint8,uint8. If you want to define 10.0.0.0/8 for example,
you'd need to use "uint8,uint8, ipv4-address". <br>
<br>
If you want to know more, this topic is discussed in detail in the
Kea User's Guide, in section 7.2.9 "Custom option definitions". You
probably want to take a look at the Table 7.3, too.<br>
<br>
If you need a full working example, I have uploaded one here:
<a class="moz-txt-link-freetext" href="http://kea.isc.org/~tomek/cfg/stateless-class-routes.conf">http://kea.isc.org/~tomek/cfg/stateless-class-routes.conf</a><br>
<br>
Hope that helps.<br>
<br>
Tomek Mrugalski<br>
ISC<br>
<br>
</body>
</html>