[Kea-users] Can't create gitlab account

[Nathan Faulkner]

Unless I'm misreading the spec, the length for sub-option 19 (hex 13)
should be 0.

On Sat, Jul 19, 2025, 3:54 PM Darren Ankney <darren.ankney at gmail.com> wrote:

> Hi Nathan,
>
> I think, In this case,  "-o 82,1300"  will look like sub-option 19
> with 0 length and no data at all.  This would make sense with 0
> length, but Kea is expecting you to send some data, I think, which is
> probably why it complained.  If you already have network activity with
> this option 82 content, you can shortcut this process by capturing
> packets as I said previously.  I will give a hypothetical as an
> example, however.  Let us say you want to send the circuit id: VLAN12
> as option 82 sub option 1 (circuit-id).  You would specify like so:
>
> -o 82,0106564C414E3132
>
> where:
>
> 01 = sub option 1
> 06 = 6 bytes length
> 564C414E3132 = VLAN12
>
> This is exactly what would appear on the wire.
>
> Thank you,
> Darren Ankney
>
> On Sat, Jul 19, 2025 at 12:59 PM Nathan Faulkner
> <nathanfaulkner18 at gmail.com> wrote:
> >
> > 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.
> >
> > For "-o 82,1300" the spec (
> https://www.rfc-editor.org/rfc/rfc8357.html#section-4.1) 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.
> >
> > On Sat, Jul 19, 2025, 8:14 AM Darren Ankney <darren.ankney at gmail.com>
> wrote:
> >>
> >> Hi Nathan,
> >>
> >> I think the reason you had trouble setting up an account in Gitlab was
> >> that you have an @gmail.com address.  There has been some lock-down
> >> needed due to a large amount of spam.  If you have a business email,
> >> you could probably use that.
> >>
> >> As far as: "-o 82,1300" not working, when sending option 82 data, you
> >> have to actually specify the entire suboption (id+length+data) as
> >> shown here: https://www.rfc-editor.org/rfc/rfc3046#section-2.0 It also
> >> must be converted to hex as would appear in a DHCP packet.  perfdhcp
> >> won't do any of this for you.  It will merely take what you provide,
> >> compute a length , and send: 0x52<length><your data> (at least I think
> >> that is correct).  The easiest thing to do would be to capture DHCP
> >> traffic that already contains this option, open in wireshark, and copy
> >> out the hex for the sub-option as a hex stream.  This should give you
> >> exactly what you need to use on the command line.  For some tips
> >> (though they are instructions for templates) see here:
> >> https://kb.isc.org/docs/how-to-use-perfdhcp-benchmarking-tool
> >>
> >> Thank you,
> >> Darren Ankney
> >>
> >> On Thu, Jul 17, 2025 at 9:33 PM Nathan Faulkner
> >> <nathanfaulkner18 at gmail.com> wrote:
> >> >
> >> > 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.
> >> >
> >> > I'm running kea 2.6.2.
> >> >
> >> > Here are the issues I was planning to open:
> >> >
> >> > perfdhcp should specify the relay agent relay port sub option when a
> local port is specified.  Not sure how it'd work otherwise.
> https://gitlab.isc.org/isc-projects/kea/-/issues/663 looks to be a
> related issue.
> >> > 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")
> >> > 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.
> >> >
> >> > --
> >> > ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
> >> >
> >> > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users
> .
> >> >
> >> > Kea-users mailing list
> >> > Kea-users at lists.isc.org
> >> > https://lists.isc.org/mailman/listinfo/kea-users
> >> --
> >> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
> >>
> >> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
> >>
> >> Kea-users mailing list
> >> Kea-users at lists.isc.org
> >> https://lists.isc.org/mailman/listinfo/kea-users
> >
> > --
> > ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
> >
> > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
> >
> > Kea-users mailing list
> > Kea-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/kea-users
> --
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20250719/afe86bfb/attachment-0001.htm>