[Kea-users] Fw: [kea-dev] Vendor Specific Options (Code 17)

[sathish k]

________________________________
From: sathish k <sat98 at hotmail.com>
Sent: Monday, March 28, 2022 3:02 PM
To: Francis Dupont <fdupont at isc.org>
Cc: kea-dev at lists.isc.org <kea-dev at lists.isc.org>
Subject: Re: [kea-dev] Vendor Specific Options (Code 17)

Hi Francis,
    Thanks again for helping ,  is there a way you can provide a sample config file .  here is my config file , the vendor-ids provided is not real ones . i have 2 vendors configured with code 17 8888 and 9999 and each of these has 2 options defined for address and port .  When i use this as per the spec my relay reply comes with the vendor specified last in the sequence (in this case 8888) .

Thanks for your help



  "option-data": [
       {
        "space": "dhcp6",
        "name": "vendor-opts",
        "code": 17,
        "data": 9999    //  Do you want me to change this to Hex ?? Tried changing this to Hex but service fails to start with error .
      },
       {
        "space": "dhcp6",
        "name": "vendor-opts",
        "code": 17,
        "data": 8888    // Fake VendorID  Do you want me to change this to Hex ?? Tried changing this to Hex but service fails to start with error .
      },
      {
        "space": "vendor-9999",
        "name": "addr",
        "code": 3,
        "data": "fd00::11:ff90", //Do you want me to change this to Hex ??
        "always-send": true
      },
      {
        "space": "vendor-9999",
        "name": "port",
        "code": 4,
        "data": "11000",      // Do you want me to change this to Hex ??
        "always-send": true
},
      {
        "space": "vendor-8888",
        "name": "addr1",
        "code": 1,
        "data": "fdf4::11:ff80",
         "always-send": true
      },
      {
        "space": "vendor-8888",
        "name": "port1",
        "code": 2,
        "data": "11000",
         "always-send": true
      },
      {
        "space": "dhcp6",
        "name": "rapid-commit",
        "code": 14,
        "data": ""
      },
      {
        "space": "dhcp6",
        "name": "serverid",
        "code": 2,
        "csv-format": false,
        "data": "000300060001020311223344"
      }
    ],
    "option-def": [
      {
        "space": "vendor-9999"
        "name": "addr",
        "code": 1,
        "type": "ipv6-address"
      },
      {
        "space": "vendor-9999",
        "name": "port",
        "code": 2,
        "type": "uint16"
      },
      {
        "space": "vendor-8888"
        "name": "addr1",
        "code": 3,
        "type": "ipv6-address"
      },
      {
        "space": "vendor-8888",
        "name": "port1",
        "code": 4,
        "type": "uint16"
      }
    ],




________________________________
From: Francis Dupont <fdupont at isc.org>
Sent: Tuesday, March 22, 2022 4:28 AM
To: sathish k <sat98 at hotmail.com>
Cc: Francis Dupont <fdupont at isc.org>; kea-dev at lists.isc.org <kea-dev at lists.isc.org>
Subject: Re: [kea-dev] Vendor Specific Options (Code 17)

sathish k writes:
>    Appreciate the quick reply , can you confirm my understanding of your re=
> ply is correct
>
>
>   1.  Add multiple vendors in config file as usual
>   2.  but use the Hook to pkt_send6 to compile the options from config file
>  and insert to final packet ?

=> I thought use a sheat of paper to compute the wanted value of the
vendor option with multiple vendors and insert the hexadecimal result
in the configuration. Now you can do it using a hook and some code
merging (v4) or pushing (v6) multiple vendor options with one vendor
per option from the configuration...

Thanks

Francis Dupont <fdupont at isc.org>

PS: the option collection type is a multimap so the code supports
multiple options with the same type/code as required for the v6 vendor
option 17. Now it is the only place in the code where this feature is
*currently* supported...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20220328/2c491b22/attachment.htm>