<div dir="auto">The registration page mentioned that some domains were blocked and this list could be emailed to get one unblocked, though I don't know if that included individual addresses on a domain. If not, I'm not sure how someone would contribute without paying for an email address.<div dir="auto"><br></div><div dir="auto">For "-o 82,1300" the spec (<a href="https://www.rfc-editor.org/rfc/rfc8357.html#section-4.1">https://www.rfc-editor.org/rfc/rfc8357.html#section-4.1</a>) says the length is 0. When I tested some other values in place of 13 (don't remember which, I think some random higher value and 01) they didn't seem to have an issue with 0 length data. </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Jul 19, 2025, 8:14 AM Darren Ankney <<a href="mailto:darren.ankney@gmail.com">darren.ankney@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nathan,<br>
<br>
I think the reason you had trouble setting up an account in Gitlab was<br>
that you have an @<a href="http://gmail.com" rel="noreferrer noreferrer" target="_blank">gmail.com</a> address. There has been some lock-down<br>
needed due to a large amount of spam. If you have a business email,<br>
you could probably use that.<br>
<br>
As far as: "-o 82,1300" not working, when sending option 82 data, you<br>
have to actually specify the entire suboption (id+length+data) as<br>
shown here: <a href="https://www.rfc-editor.org/rfc/rfc3046#section-2.0" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/rfc/rfc3046#section-2.0</a> It also<br>
must be converted to hex as would appear in a DHCP packet. perfdhcp<br>
won't do any of this for you. It will merely take what you provide,<br>
compute a length , and send: 0x52<length><your data> (at least I think<br>
that is correct). The easiest thing to do would be to capture DHCP<br>
traffic that already contains this option, open in wireshark, and copy<br>
out the hex for the sub-option as a hex stream. This should give you<br>
exactly what you need to use on the command line. For some tips<br>
(though they are instructions for templates) see here:<br>
<a href="https://kb.isc.org/docs/how-to-use-perfdhcp-benchmarking-tool" rel="noreferrer noreferrer" target="_blank">https://kb.isc.org/docs/how-to-use-perfdhcp-benchmarking-tool</a><br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
On Thu, Jul 17, 2025 at 9:33 PM Nathan Faulkner<br>
<<a href="mailto:nathanfaulkner18@gmail.com" target="_blank" rel="noreferrer">nathanfaulkner18@gmail.com</a>> wrote:<br>
><br>
> I was trying to create an account to report a couple of kea issues, but I got an "Email is not allowed for sign-up." message.<br>
><br>
> I'm running kea 2.6.2.<br>
><br>
> Here are the issues I was planning to open:<br>
><br>
> perfdhcp should specify the relay agent relay port sub option when a local port is specified. Not sure how it'd work otherwise. <a href="https://gitlab.isc.org/isc-projects/kea/-/issues/663" rel="noreferrer noreferrer" target="_blank">https://gitlab.isc.org/isc-projects/kea/-/issues/663</a> looks to be a related issue.<br>
> When sending the relay agent relay port sub option (by passing "-o 82,1300" to perfdhcp), the debug kea logs show the packet failing to parse for reason "OptionInt 19 truncated". (as a workaround, you can specify junk data "-o 82,13020000")<br>
> It'd be nice if perfdhcp could specify multiple servers. I was trying to test HA, and normally I'd use a relay server, but perfdhcp itself pretends to be a relay server, which causes conflicts.<br>
><br>
> --<br>
> ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
><br>
> To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
><br>
> Kea-users mailing list<br>
> <a href="mailto:Kea-users@lists.isc.org" target="_blank" rel="noreferrer">Kea-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
-- <br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank" rel="noreferrer">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
</blockquote></div>